My OnePlus 6 suddenly started rebooting non-stop and is currently unusable

Search This thread
Feb 10, 2018
8
0
Good morning,
I am currently struggling even trying to diagnose what the issue is. About 2 weeks ago my OnePlus 6 (last released Android update, stock ROM, rooted) has started randomly powering off and rebooting; it only happened sporadically and didn't cause any major problems whatsoever, until a few days ago, when it started freezing and rebooting while (obviously) not under load. The first problems appeared: sometimes when it happened the device wouldn't recognise my SIM card, and sometimes upon restarting the airplane mode was on. It was frustrating to experience but still could use my phone after a few random reboots. Then the problem got worse and the Wi-Fi icon would grey out from time to time, or the Wi-Fi would simply not turn on. Left with no Internet connection (couldn't 'fix' it manually restarting the phone a couple times as I was previously able to) I decided to make a backup and tried to wipe everything, the problem still appeared and I was not able to continue. During the struggle I wiped my phone's cache but it didn't get any better nor did it stop the phone from reeboting over again, sometimes the phone would work for hours (thankfully allowing me to take a backup), sometimes it freezed right upon reaching the unlock screen. Once it started working again by simply removing the case, then the problem came back (probably a coincidence?), do you think it could be a hardware issue? I haven't found anything specific on what has happed to me on the Internet, I am hoping you kind sirs have some knowledge or experience on this exact problem that you can share with me...
Thanks in advance :)
 
Nov 29, 2021
17
0
Moto G7 Plus
If I am reading correctly, you didn't get a backup of the phone prior to the issue occuring, is that correct? If so then doing a restore is, most likely, not going to help as you are simply restoring the same issue back into the partitions. When I wiped out my IMEI I had a known good backup, but on a crappy SD card. This corrupted the backup, which in turn corrupted the partition that was restored from said backup. This caused the issue to persist over many restores and resets. Are you able to get a copy of your stock ROM that the phone began with, not the current update? This is the best source of untainted partition data. That is how I was able to fix my corrupted EFS partitions. This may not be the exact scenario for your particular situation, but to me it sounds software related. Hardware issues tend to be very consistent, whereas software issues are inconsistent at the best of times. Also is there anything particular that you noticed that would always make the problem occur?
 
Feb 10, 2018
8
0
If I am reading correctly, you didn't get a backup of the phone prior to the issue occuring, is that correct? If so then doing a restore is, most likely, not going to help as you are simply restoring the same issue back into the partitions. When I wiped out my IMEI I had a known good backup, but on a crappy SD card. This corrupted the backup, which in turn corrupted the partition that was restored from said backup. This caused the issue to persist over many restores and resets. Are you able to get a copy of your stock ROM that the phone began with, not the current update? This is the best source of untainted partition data. That is how I was able to fix my corrupted EFS partitions. This may not be the exact scenario for your particular situation, but to me it sounds software related. Hardware issues tend to be very consistent, whereas software issues are inconsistent at the best of times. Also is there anything particular that you noticed that would always make the problem occur?
I thought about that so I didn't restore my backup, I just took the backup and after the ROM was wiped the issues persisted (only reason I took a backup was for the photos, I wouldn't have restored everything that might have been corrupted).
Also I didn't notice anything particular, the problem would occur randomly, at first it seemed it was the SIM card, I removed it and it fixed it, then it came back, it was the Wi-Fi and if the phone managed to restart correctly the Wi-Fi would not turn on if tapped (also sometimes the airplane mode was on upon restarting, which of course I didn't switch on prior to reboot), then the problem seemed the case, upon removing the phone came back to life but with the same connectivity issues...
In general I can tell you I haven't found precise and reliable behaviours that led to freezing and rebooting, the problem only got worse and worse.
 
Nov 29, 2021
17
0
Moto G7 Plus
Yes trying another ROM is not a bad idea. And lineage OS is a great ROM. HoweverI noticed with my phone I had issues that were unique to the phone only when I was using custom ROMs, as most custom ROMs are not built for my phone, I use a Moto g7 Plus. You of course using the OnePlus 6 are more likely to find a ROM that was built specifically for your phone. However, did you try to flash it back to the stock ROM? Or is that what you were referring to when you said you took the back up after it was wiped? Also just a thought but a lot of the custom ROMs are very, well customised heavy, this can lead to making narrowing down the root cause of the problem even more difficult. If you were going to flash a custom ROM, I would look towards something more on the later end of the feature heavy ROMs. If only just to remove some functions and see if the problem still persists, if it does well then you have less functions to go over as possibles.
 
Last edited:
Feb 10, 2018
8
0
Yes trying another ROM is not a bad idea. And lineage OS is a great ROM. HoweverI noticed with my phone I had issues that were unique to the phone only when I was using custom ROMs, as most custom ROMs are not built for my phone, I use a Moto g7 Plus. You of course using the OnePlus 6 are more likely to find a ROM that was built specifically for your phone. However, did you try to flash it back to the stock ROM? Or is that what you were referring to when you said you took the back up after it was wiped? Also just a thought but a lot of the custom ROMs are very, well customised heavy, this can lead to making narrowing down the root cause of the problem even more difficult. If you were going to flash a custom ROM, I would look towards something more on the later end of the feature heavy ROMs. If only just to remove some functions and see if the problem still persists, if it does well then you have less functions to go over as possibles.
I haven't managed to reflash the original ROM, I just wiped out everything, so I guess now I will begin with trying the original ROM (via reflashing) before flashing a custom one.
 
Nov 29, 2021
17
0
Moto G7 Plus
I haven't managed to reflash the original ROM, I just wiped out everything, so I guess now I will begin with trying the original ROM (via reflashing) before flashing a custom one.
It will definitely eliminate any issues that were due to customization. Also if the OnePlus has any software similar to RSA, which is the recovery and software assistant for Motorola phones, that you can use to refresh the stock ROM with it would be a good idea to start with that and then if that doesn't seem to function probably try flashing it with something like TWRP.
 
Feb 10, 2018
8
0
I tried to ADB sideload the original ROM and at 47% it said:
adb: failed to read command: No error
TWRP, on the other hand, stated 'Successful'
If I boot nothing has changed...
Edit: only thing changed is that it overwrote the recovery and now TWRP is gone
 
Nov 29, 2021
17
0
Moto G7 Plus
I tried to ADB sideload the original ROM and at 47% it said:
adb: failed to read command: No error
TWRP, on the other hand, stated 'Successful'
If I boot nothing has changed...
Edit: only thing changed is that it overwrote the recovery and now TWRP is gone
For starters, I have also noticed the 47% thing when flashing ROMs, both the original and some of the custom ones did this as well. However, that was always completed with a success message. One thing that is possible is that your stock ROM doesn't recognize TWRP, or the other way around, as using the correct procedure during flash. Do you have the .img file for your stock ROM? Also, I found more than one of the custom ROMs I tried would not boot properly, or at all even, unless I rebooted to recovery upon Comp of the initial flash. Without flashing, or reflashing TWRP, try to flash the ROM again, reboot to recovery, then reboot to the system from there. This allows the a\b system to cycle through to allow for the partitions to completely update with the new information. Only after a successful system first boot should you use fastboot to reinstall TWRP.
 
Feb 10, 2018
8
0
For starters, I have also noticed the 47% thing when flashing ROMs, both the original and some of the custom ones did this as well. However, that was always completed with a success message. One thing that is possible is that your stock ROM doesn't recognize TWRP, or the other way around, as using the correct procedure during flash. Do you have the .img file for your stock ROM? Also, I found more than one of the custom ROMs I tried would not boot properly, or at all even, unless I rebooted to recovery upon Comp of the initial flash. Without flashing, or reflashing TWRP, try to flash the ROM again, reboot to recovery, then reboot to the system from there. This allows the a\b system to cycle through to allow for the partitions to completely update with the new information. Only after a successful system first boot should you use fastboot to reinstall TWRP.
no biggie, I decided to flash LineageOS 19.1. While installing Open GApps, however, it tells me I have Android 11 (LineageOS 19.1 should be Android 12.1). I sideloaded the GApps for Android 11 and it says Error, status 70: Insufficient storage space available in System Partition... WTH?

Edit: this is the open_gapps_log.txt

# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | lineage_enchilada-userdebug 12 SQ3A.220705.004 89272a802b
ROM Version increment | 2111252325
ROM SDK version | 30
ROM/Recovery modversion | 19.1-20220816-NIGHTLY-enchilada
Device Recovery |
Device Name | OnePlus6
Device Model | ONEPLUS A6003
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | true
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 450
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /sideload/package.zip
Installing GApps Version | 20220215
Installing GApps Type | nano
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | true[NoRemove]
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | true[NoRemove]
Ignore Google Package Installer | false[PackageInstallerGoogle]
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | true
Total System Size (KB) | 2837072
Used System Space (KB) | 2629400
Current Free Space (KB) | 191288
Additional Space Required (KB) | 390972 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log

INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.

NOTE: The Stock/AOSP WebView is not available on your
ROM (anymore), not all Google WebViewProviders will be removed.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Keyboard is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Contacts is not available on your
ROM (anymore), the Google equivalent will not be removed.
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.

# Begin GApps <> ROM Duplicate File List
/system/app/GoogleExtShared
/system/app/GooglePrintRecommendationService
/system/priv-app/GooglePackageInstaller
# End GApps <> ROM Duplicate File List

# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 191288 | 191288
Remove | Existing GApps | + 3284 | 194572
Remove | Obsolete Files | + 119228 | 313800
Remove | androidauto | + 0 | 313800
Remove | extservicesstock | + 0 | 313800
Remove | extsharedstock | + 0 | 313800
Remove | packageinstallerstock | + 0 | 313800
Remove | provision | + 0 | 313800
Install | Core | - 227284 | 86516
Install | batteryusage | - 6788 | 79728
Install | calsync | - 2396 | 77332
Install | dialerframework | - 12 | 77320
Install | gearheadstub | - 3168 | 74152
Install | googletts | - 62180 | 11972
Install | markup | - 8252 | 3720
Install | packageinstallergoogle | - 3144 | 576
Install | search | - 321668 | -321092
Install | soundpicker | - 6184 | -327276
Install | speech | - 39128 | -366404
Install | wellbeing | - 15352 | -381756
| Buffer Space | - 9216 | -390972
------------------------------------------------------------------
Additional Space Required | 390972
------------------------------------------------------------------

# End GApps Size Calculations

# Begin User's gapps-config

# End User's gapps-config

Edit 2: I eventually installed GApps pico package

Edit 3: First LineageOS boot, say hello to QUALCOMM CrashDump Mode...
No message, just a freeze and the bare QUALCOMM CrashDump Mode phrase.
 
Last edited:
Nov 29, 2021
17
0
Moto G7 Plus
no biggie, I decided to flash LineageOS 19.1. While installing Open GApps, however, it tells me I have Android 11 (LineageOS 19.1 should be Android 12.1). I sideloaded the GApps for Android 11 and it says Error, status 70: Insufficient storage space available in System Partition... WTH?

Edit: this is the open_gapps_log.txt

# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | lineage_enchilada-userdebug 12 SQ3A.220705.004 89272a802b
ROM Version increment | 2111252325
ROM SDK version | 30
ROM/Recovery modversion | 19.1-20220816-NIGHTLY-enchilada
Device Recovery |
Device Name | OnePlus6
Device Model | ONEPLUS A6003
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | true
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 450
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /sideload/package.zip
Installing GApps Version | 20220215
Installing GApps Type | nano
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | true[NoRemove]
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | true[NoRemove]
Ignore Google Package Installer | false[PackageInstallerGoogle]
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | true
Total System Size (KB) | 2837072
Used System Space (KB) | 2629400
Current Free Space (KB) | 191288
Additional Space Required (KB) | 390972 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log

INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.

NOTE: The Stock/AOSP WebView is not available on your
ROM (anymore), not all Google WebViewProviders will be removed.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Keyboard is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Contacts is not available on your
ROM (anymore), the Google equivalent will not be removed.
!!! WARNING !!! - Duplicate files were found between your ROM and this GApps
package. This is likely due to your ROM's dev including Google proprietary
files in the ROM. The duplicate files are shown in the log portion below.

# Begin GApps <> ROM Duplicate File List
/system/app/GoogleExtShared
/system/app/GooglePrintRecommendationService
/system/priv-app/GooglePackageInstaller
# End GApps <> ROM Duplicate File List

# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 191288 | 191288
Remove | Existing GApps | + 3284 | 194572
Remove | Obsolete Files | + 119228 | 313800
Remove | androidauto | + 0 | 313800
Remove | extservicesstock | + 0 | 313800
Remove | extsharedstock | + 0 | 313800
Remove | packageinstallerstock | + 0 | 313800
Remove | provision | + 0 | 313800
Install | Core | - 227284 | 86516
Install | batteryusage | - 6788 | 79728
Install | calsync | - 2396 | 77332
Install | dialerframework | - 12 | 77320
Install | gearheadstub | - 3168 | 74152
Install | googletts | - 62180 | 11972
Install | markup | - 8252 | 3720
Install | packageinstallergoogle | - 3144 | 576
Install | search | - 321668 | -321092
Install | soundpicker | - 6184 | -327276
Install | speech | - 39128 | -366404
Install | wellbeing | - 15352 | -381756
| Buffer Space | - 9216 | -390972
------------------------------------------------------------------
Additional Space Required | 390972
------------------------------------------------------------------

# End GApps Size Calculations

# Begin User's gapps-config

# End User's gapps-config

Edit 2: I eventually installed GApps pico package

Edit 3: First LineageOS boot, say hello to QUALCOMM CrashDump Mode...
No message, just a freeze and the bare QUALCOMM CrashDump Mode phrase.
Hello sorry about the delay in the response. Speak to my phone and hopefully it types the right things. I do know about the Google apps or g apps if you will causing the needs more space issue if you downloaded anything other than the nano your system partition tends to have not enough space whether it actually does or not I had over a gigs worth of space on my system partition when I installed g ups once the GF file itself was only 300 megs yet because it wasn't the smaller version if you will it fail to install try downloading the micro or nano versions of the G apps and install that. Spilling things out correctly I do apologize for the terrible misspellings however I do not have time to edit with the old fashioned keyboard if I am unclearing anything please ask me and I will try to clarify
 
Feb 10, 2018
8
0
Hello sorry about the delay in the response. Speak to my phone and hopefully it types the right things. I do know about the Google apps or g apps if you will causing the needs more space issue if you downloaded anything other than the nano your system partition tends to have not enough space whether it actually does or not I had over a gigs worth of space on my system partition when I installed g ups once the GF file itself was only 300 megs yet because it wasn't the smaller version if you will it fail to install try downloading the micro or nano versions of the G apps and install that. Spilling things out correctly I do apologize for the terrible misspellings however I do not have time to edit with the old fashioned keyboard if I am unclearing anything please ask me and I will try to clarify
As mentioned in the edits I eventually managed to install the pico GApps file, but now the problem is the SIM still doesn't get recognized, the Wi-Fi won't turn on and the system crashes are back, this time accompanied by the QUALCOMM CrashDump Mode (no message, it just freezes, the OS crashes and the CrashDump mode appears).
Don't worry abouut your response time, you're the only one replying afterall.
 
Nov 29, 2021
17
0
Moto G7 Plus
As mentioned in the edits I eventually managed to install the pico GApps file, but now the problem is the SIM still doesn't get recognized, the Wi-Fi won't turn on and the system crashes are back, this time accompanied by the QUALCOMM CrashDump Mode (no message, it just freezes, the OS crashes and the CrashDump mode appears).
Don't worry abouut your response time, you're the only one replying afterall.
Does the USDD code *#*#4636#*#* work on your phone? Done through the dialer. If so are any of the fields blank or obviously missing information? It's the testing menu, look under phone information. Here's the main menu from my phone.
 

Attachments

  • Screenshot_20220819-141441.png
    Screenshot_20220819-141441.png
    69.2 KB · Views: 7
Nov 29, 2021
17
0
Moto G7 Plus
I had a chance to look at a few places and I found some of the codes that are specific to your phone.


This site has many codes that are supposed to give you access to various testing menu to run diagnostics on your phone and it's hardware. I do recommend caution while exploring these menus as they are designed for use only by developers and engineers. Please keep me posted on the development of your issue. I also have an email that I created just for giving to XDA members
[email protected]
If you need to pm me.
 
Nov 29, 2021
17
0
Moto G7 Plus
Here's the Phone info section
Now see, now we are getting somewhere. Where I'm not 100% yet but we are not stagnant. So with some of those fields being blank I want to ask you about where you are from, it really does pertain to the topic and what can come about from it would you mind sending me an email to [email protected] so I can not have to ask some questions that might be best done in a less public environment. If you would like, I have an email service that I am owner/admin of and have created an email to loan to people to help keep their privacy in tact while still being able to send PM's the account info is:
Webmail: https://webmail.dynu.com/
Username: [email protected]
Password: [email protected]$5word
Please let me know what you decide as I had this very issue with my phone and no one was willing to help so I had to figure it out myself. All the whole everyone was telling me to give up and send it in or just buy a new phone. I would just like to not be that kind of tech. I primarily do pc repair Linux and windows systems.
 
Nov 29, 2021
17
0
Moto G7 Plus
Now see, now we are getting somewhere. Where I'm not 100% yet but we are not stagnant. So with some of those fields being blank I want to ask you about where you are from, it really does pertain to the topic and what can come about from it would you mind sending me an email to [email protected] so I can not have to ask some questions that might be best done in a less public environment. If you would like, I have an email service that I am owner/admin of and have created an email to loan to people to help keep their privacy in tact while still being able to send PM's the account info is:
Webmail: https://webmail.dynu.com/
Username: [email protected]
Password: [email protected]$5word
Please let me know what you decide as I had this very issue with my phone and no one was willing to help so I had to figure it out myself. All the whole everyone was telling me to give up and send it in or just buy a new phone. I would just like to not be that kind of tech. I primarily do pc repair Linux and windows systems.
Just wanting to clarify that depending on where in the world you are at Some of the questions I have next can have legal issues. They do not here in the US where I am at, but I don't know where you are and I don't want to say the wrong thing in a public forum.
 
Nov 29, 2021
17
0
Moto G7 Plus
Just wanting to clarify that depending on where in the world you are at Some of the questions I have next can have legal issues. They do not here in the US where I am at, but I don't know where you are and I don't want to say the wrong thing in a public forum.
I understand if you do not want to communicate privately so I will ask this and determine how to proceed. Is any of the information (ie. The numbers that are missing from the phone information menu) protected by laws that, whether by accident or on purpose, if changed can cause you to have any legal trouble? I ask this very serious question because I would like to help you but not at the risk of you getting in trouble. If you cannot say just simply thank me for my time and I will recommend you get a new device. I just recently fixed this very complex issue with my phone and it was incredibly difficult to get any information on the subject, so I know how sending it is. Please let me know how you would like to proceed.
 
Nov 29, 2021
17
0
Moto G7 Plus
Well, I am not sure if you will read this but here's what has most likely happened to your device; the partition system that android devices employ is comprised of dozens of different partitions that all have a unique role to play. Boot, system, a few data(user files being one), vendor, oem, and so on. Most have two now for the A/B devices. This is so that updates can take place while the system is operating without having to unmount the partitions. There is a pair of partitions labeled EFS or "modema" & "modemb" these partitions contain, among other critical data, the IMEI or at least the function used to write the software copy of it. This is when the phone reads the firmware, or burned in, IMEI and passes it to the OS. The problem that happened, as did in my case, is that if those partitions become corrupted then they fail to pass the correct information to the OS. This means that the system no longer is getting an IMEI number assigned at boot like normal. As it is pertinent to have not only a valid, but matching IMEI to access cell service you will have no service at all without an IMEI. This can easily be confirmed by booting to the bootloader and checking the IMEI that the bootloader can see, and then booting to the system and running the code *#06# from the dialer(or the "06" variant specific to your device) and seeing how they compare. If the bootloader has the correct IMEI and the system does not, then your device is loading corrupted partitions at boot. This can be solved by getting a valid copy of the ROM that your device began with (The one it left the factory for the first time with). You must then flash the ROM to all partitions (both a and b if applicable) without rebooting until all partitions have been reset to factory standards. Once this has been done a simple reboot should be all that is necessary to get the IMEI back. In some cases a new SIM is required in order to get cell service again. If you check the bootloader, however, and it does not either have the correct IMEI or none at all, then your firmware has been damaged and will need to be replaced. This can only be done with specialized equipment and will most likely be rather expensive. Hopefully this covers the extent of this issue, and that there is no major legal issues to deal with over having changed (whether by accident or not) the IMEI number in your local area. And finally, good luck, this is more information in one place then I could ever find so I hope it helps.