Stuck at "phone is starting", touchscreen not responding. - OnePlus 5T Questions & Answers

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.

Related

Can't flash any rom - Gnex (Maguro) TWRP

Hello guys
I decided to re-flash CM 11 because in these days my phone started to freeze continously and reboot.
I followed the usual procedure (wipe system, data, cache, dalvik) but the problems seemed to multiply, e.g. the phone couldn't get any signal with the SIM inside.
Then I tried with another rom (Paranoid 4.6 beta 6) with no results and I reflashed CM 11.
Unfortunately after my last installation the phone stuck on the Google screen.
As last resource I restored my phone with an old backup which i made previously but the phone is still stuck in the Google text screen.
Because the things seem to get worse, i decided to write this thread.
Do you have any tip? Do you think it could be an hardware problem?
Thanks in advance
Extra information
I forgot to say that fastboot mode is available, in fact I can easily access to TWRP. However even though I reflash the rom, the phone is still stuck in the Google boot screen.

Getting bootloops after rebooting for being laggy

Hi all, I would like to have some feedback if some of you is experiencing the same issue as I am. My N5X is running Stock Marshmallow (latest release) and it's rooted (SuperSU v2.71) with Xposed (latest version for arm64).
Every now and then (usually with an uptime more than 80 hours) the device becomes very laggy and my usual solution for eliminating the lag is rebooting. It would be the ideal solution if only the device wasn't remaining stuck in bootloop after rebooting.
For now the only "solution" I have found is doing a factory reset from TWRP, after performing a backup of /data. Uninstalling from recovery Xposed or simply wiping cache/dalvik or even flashing separately the stock images (boot, cache, system, vendor) did nothing without a factory reset.
The first times I got bootloops on the device I knew why it was happening (one time I modified build.prop forgetting to change the permissions, another time a similar thing but with the transfer of an app in /system), but these kinds of bootloop remain a mistery for me.
It also occurred without Xposed installed and with both stock and ElementalX kernel.
A peculiar thing I noticed while in TWRP is that the Cache was displayed occupying 0 MB. Might it be related to this issue?
Now, I know now that I should probably reboot more often, but I still would like to know why this happens because it's being very annoying doing the restore procedure every damn week.
And so, while doing my research, I wanted to have some feedback from those of you who had similar issues with a similar setup.
Thanks and cheers!
A new kind of problem occurred. This time Telegram wasn't connecting to the net and so I rebooted. And BOOM, stuck at the boot animation (the four colored points) for no apparent reason.
If I only wiped Dalvik and Cache in recovery, the phone would go past the boot animation, but after the Android logo, it would display only a black screen.
This time, before doing a factory reset, I flashed via fastboot boot, cache, system and vendor, hoping that could solve something for the future.
I have no idea why this is happening. After the new reset, I will try to limit the modifications to /system by not installing Stericson's Busybox and GSam Root Companion app, but I'm still wandering in the dark. It looks like my 5X is possessed.
Please, if you have any sort of feedback or insight, I will gladly listen.
Update: today I had no issues but I rebooted anyway. Result: stuck at bootanimation.
As you English speakers say:"F*ck this sh*t, I'm out".
Yeah, I decided that I'm done with the stock ROM and decided to flash PureNexus ROM in the hope that the **** up I was doing with the stock ROM will never happen again.
Maybe now the mods can close this thread.

[d855] Kernel crash during install

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?

[SOLVED] sprint SGS3 stuck on bootloops and crashes (tried everything)

I disassembled my phone lately for maintenance reasons, The battery was out for about 30 minutes, (My phone already had a trouble keeping the clock even though the battery was taken out for a short period), after assembling the phone, it booted up properly till the lock screen appeared and it all became black. software and hardware buttons were working properly, but the LCD itself was totally black.
I booted-up the phone in recovery mode and wiped everything from system, data, to cache, and then installed the newest version of Lineage. After booting the system gave me "process system isn't responding" and close and wait options with infinite bootloops.
I tried installing the full stock Rom and it gave me "setting has stopped working" and "google play services has stopped working".
My guess then was the time on the device, so I went back into recovery opened a shell session and fixed the time using "date" and "hwclock", but it never worked.
After searching online I found that this might be a battery issue, so I bought a new one, and guess...It didn't work either.
I really need help with this device! :crying:
_____________________________________
Solved it by installing the NJ2:
Wiped everything, then installed the stock rom using odin 3.10, after that the system kept telling me the same messages, so I went back and installed twrp 3.10 .. I guess .. then wiped everything except for the system and internal memory, then I corrected my clock using this method:
https://forum.xda-developers.com/galaxy-s3-sprint/help/how-to-edit-time-hardware-time-using-t3621875
and frankly it worked! and booted up normally.
Sadly I wasn't able to install any linage version! ... I hope that I find the solution so soon!

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.

Categories

Resources