Is it acceptable to you that a $800 phone dead in 21 months?

[Phalanx7621]

Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.

Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?

Well yes , I've never had to do this so someone chime in if I'm wrong , I know they used to use the last_ kmsg but someone told me it had moved to a new location after Android 6 You can pull console-ramoops to see what if any kernel issues or panics there may be. You'll need a root explorer, here's a free one https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic After it does it's next random reboot, open that root explorer and navigate to /sys/fs/pstore/ and look for the file console-ramoops . Upload it here as an attachment and hopefully we can get a kernel dev or someone to take a look and see what they can see. I mean there's also log cats you can take using ADB, but I'm not sure if that would help when it's rebooting. I've never dealt with this to this level of detail, hopefully we can get someone who can delve further into this and help figure it out with us.

 

[premedicated]

Well yes , I've never had to do this so someone chime in if I'm wrong , I know they used to use the last_ kmsg but someone told me it had moved to a new location after Android 6 You can pull console-ramoops to see what if any kernel issues or panics there may be. You'll need a root explorer, here's a free one https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic After it does it's next random reboot, open that root explorer and navigate to /sys/fs/pstore/ and look for the file console-ramoops . Upload it here as an attachment and hopefully we can get a kernel dev or someone to take a look and see what they can see. I mean there's also log cats you can take using ADB, but I'm not sure if that would help when it's rebooting. I've never dealt with this to this level of detail, hopefully we can get someone who can delve further into this and help figure it out with us.

Got it installed. It appears as though it'll go into a bootloop for 30-90 minutes before starting up normally. It will run for about the same amount of time, 30-90 minutes before freezing up and going back into a bootloop... Question is, what should I open/save that console-ramoops file as? I can open as a text file, image, music, video, zip, apk or script. All of which open their own subcategories... I'm assuming text file, which gives the option of HTML viewer, calendar, contacts, docs or RB Text Editor... but again I don't really know.

 

[premedicated]

So it ran all night on the nightstand without a reset/boot loop according to battery manager. This morning I played some music and browsed around a bit, no issues. About two hours worth of actively messing with it before it reset and went into another boot loop. Once it finally loads back up I’ll pull that log out and hopefully that’ll provide us with some information.

 

[Lei.SHI]

Thanks to premedicated and Phalanx7621 for putting your effort on troubleshooting the loop issue, I'm a bit busy today, and might try what your guys did over this weekend.

 

[Lei.SHI]

I tried over the weekend all I can know of. fastboot boot twrp.img, flashing kernel, magisk, even factory image, no luck;
During my cycles of work, I found the device is getting worse, last week before I post this issue to xda, I can get into recovery mode(or twrp) 8 times of 10, and now I can only get into recovery mode(or twrp) maybe 1 time of 50.
During the time I was testing in twrp, I tap the Restart button, and twrp warned me that my device doesn't have a system/OS to boot up, but according to the flash-all.sh output, there were no error/failure while I flashing the stock image, so I'm guessing, if I choose to believe twrp, then the flash-all script was "lying" that something wrong with the system partition, or maybe the whole partition table.
When I tried to use twrp to install magisk zip, I was getting "Error 1", which indicates the installation failed to "repack boot.img", I google it, other people saying it may due to twrp and migisk version compatibility, so I decided to use various versions combination to retry. however, like I already said, I'm struggling getting in to twrp now, maybe it will never bring me back to twrp forever, sicne I think I'm already tried over 50 times now I think.