Recent samsung devices rebooting a/root cf-auto?

[droseofc]

I follow a handful of samsung device threads, tab 3, s6, note 5 etc..., and every one of them have had recent issues that cause the phone to have a reboot that occurs a minute or so after booting up that havent been able to fix with reflashing firmwares or anything related.
My note 5 had to be replaced (no biggie) and others are in the process of doing so as well. A possible fix has been posted by one user but im wondering if possibly the cause is from cf autoroot as it appears that everyone or close to that posted having a similar issue mention cf auto rooting prior.
My steps were flash stock lollipop. Flash stock mm. Cf autoroot stock mm and after that my signal bars or area for were gone completely and the phone rebooted within a minute regardless of airplane mode on or anything else i tried. It did not reboot the same while in recovery stock or custom or download mode as those stayed kn as normal.
I know the warnings and such with cf auto root an whatnot but just wanted to make the observation so that if it is the issue it can be acknowledged before more threads appear with this rebooting issue as it is a PITA.

 

[droseofc]

I follow a handful of samsung device threads, tab 3, s6, note 5 etc..., and every one of them have had recent issues that cause the phone to have a reboot that occurs a minute or so after booting up that havent been able to fix with reflashing firmwares or anything related.
My note 5 had to be replaced (no biggie) and others are in the process of doing so as well. A possible fix has been posted by one user but im wondering if possibly the cause is from cf autoroot as it appears that everyone or close to that posted having a similar issue mention cf auto rooting prior.
My steps were flash stock lollipop. Flash stock mm. Cf autoroot stock mm and after that my signal bars or area for were gone completely and the phone rebooted within a minute regardless of airplane mode on or anything else i tried. It did not reboot the same while in recovery stock or custom or download mode as those stayed kn as normal.
I know the warnings and such with cf auto root an whatnot but just wanted to make the observation so that if it is the issue it can be acknowledged before more threads appear with this rebooting issue as it is a PITA.

I did do my best to make it grammar friendly but apparently where i put the tabs and spaces for paragraphs only put the tabs and not the spaces so i giveup on future paragraphing efforts

 

[bonebeatz1234]

Well there replacing my battery which i doubt will fix it but when i get another phone im staying away from rooting until this problem get solved . I lost alot of stuff on that device also my next phone will have a sd card or I'm not buying it cloud storage with sprint service =failure

Sent from my SM-N920P using XDA-Developers mobile app

 

[patmorris]

I didn't cf auto root and had the unfixable reboot problem.

 

[Jimmy1life]

Me either i did day one when rolled to 6.0.1 but had odin stock since then only odin twrp then flash supersu2.71.zip.
So im not convinced that cfauto did it now mine is working perfect or better lol. The reboot issue did u pull sim card flash stock. i flashed it but still rebooted any rom it rebooted but i think after that i click repartition in odin with stock tar but then re did it stock tar in odin again . i odined the stock tar into pitfile. then i re odin stock tar after that let it die. im not sure how i fixed it but i did.

---------- Post added at 09:08 PM ---------- Previous post was at 09:03 PM ----------

I also flashed twrp and restored radio and efs back multiple times

---------- Post added at 09:10 PM ---------- Previous post was at 09:08 PM ----------

Once it worked sucker was booting up in 14 or 15 seconds and has seemed better then ever maybe cuz i lost this bad baby for few days while she rebooted idk good luck though

 

[bonebeatz1234]

We all did the usual troubleshooting in all my time with the g1,mytouch,htc hd2,samsung vibrant,htc sensation, htc evo,htc 3d,htc evo 4glte, galaxy nexus, galaxy s2, galaxy s3, galaxy s4 , galaxy s5 ,galaxy note 1,2,3,4,5 nexus 6 , lg optimus,lg g2,lg g3, gflex,glex 2, htc max, nexus 5, i bricked several devices and fixed them all. This note 5 problem takes the cake i wasted to much time trying to fix it before i said enough. The security on every device year by year is getting ridiculous no matter what you do anything can be hacked.

Sent from my SM-N920P using XDA-Developers mobile app

 

[Jimmy1life]

I guess one more thing to my rambling.
It happened right after i restored a back up but i swiped to restore i saw that efs was checked i said nooooo but it was to late. I never touch that for the most part. one other time i restored it in 5.1.1 i took 2 or 3 minutes before signal.

 

[Jimmy1life]

Well i helped another he tried everything it was rebooting on any rom. i suggested let it die well his worked after that
IF CONSTANT REBOOTING FLASH STOCK
LET BATTERY DIE COMPLETELY

 

[droseofc]

I retract my observation about autoroot then and apologize for that. I just got the same issue with this replacement phone after flashing skyhigh 3.4 in twrp. I let it die as others say works and it did work but su was gone so flashed su in twrp and then had the same issue. Let it die and now i am running skyhigh 3.4 with the su i flashed with no issue. Leaves only one possibility, seems as if its not skyhigh, not su or autoroot but could it be twrp?

 

[droseofc]

Im using 3.0.2.0 twrp with the theme options flashed to it if that makes a difference but to be specific and possibly narrow it down.

 

[rayraycarter4]

Can someone down grade twrp and find out

Sent from my SM-N920P using XDA-Developers mobile app

 

[Jimmy1life]

Well several on g920p the s6 have had the problem we got twro 3.0.0-1 build by sac23 works newer ones wont boot. i got the tebooting problem for 2 days right after a efs restore.

---------- Post added at 04:01 AM ---------- Previous post was at 03:53 AM ----------

Still its unofficial so this is where them problem starts but maybe somebody needs logs while rebooting nonstop

 

[droseofc]

I cant say its twrp for positive, im just saying in my case, i flashed skyhigh 3.4 in twrp. Had the no signal reboot issue. Let it die. Charged and rebooted and was fixed running skyhigh 3.4. Su was gone tho, so i went to twrp and flashed su, got the same issue.
Let it die, charge reboot and su was installed and everything was fine. The only thing that was the same throughout the problems was twrp. At the same time, twrp successfully flashes with no issues most if not all of the time, its just in this case twrp was used for two different flashes and the same issue occured and a die and reboot displayed both flashed objects running successfully so I would have to point to twrp as it couldnt be skyhigh or supersu and those would be the only 3 possibilities in this case.
I had issues installing the twrp 3.0.2.0 from the twrp.me site, it would bootloop to the recovery is not seandroid enforcing until i flashed a recovery that either worked or flashed stock rom, until i came across tdunhams recovery file listed in his moar mm thread linked note 5 recoveries. Its hard to say its twrp because it works for sure, its just a few times where it hasnt there arent many other things it could be.