Database Info

Recent samsung devices rebooting a/root cf-auto?

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 said:
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.
Click to expand...
Click to collapse
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

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

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

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

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

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.

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

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?

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.

Can someone down grade twrp and find out
Sent from my SM-N920P using XDA-Developers mobile app

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

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.

[6045l] My phone stops detecting the SIM card on the stock ROM

When I have the stock ROM installed, my phone stops detecting my SIM card after a while. It does not happen on custom ROMs. I have tried new SIMs, taking it out and putting it back in, and multiple reboots. The only thing that solves it as far as I'm aware is factory resetting. Does anyone have another solution? As well, does anyone have a flashable radio/modem/baseband for the 6045l (preferably stock 6.0)? I'd like to try that.

How you know that it works now also on the custom ROMs? When you are aware of making factory reset?
I think factory reset is always a first step when in trouble.
And you cannot use radio/modem/baseband/ from 6.0 on your 5.0.2 (i think, because you cannot use 5.0.2 r/b/m on 6.0).

DallasCZ said:
How you know that it works now also on the custom ROMs? When you are aware of making factory reset?
I think factory reset is always a first step when in trouble.
And you cannot use radio/modem/baseband/ from 6.0 on your 5.0.2 (i think, because you cannot use 5.0.2 r/b/m on 6.0).
Click to expand...
Click to collapse
Hmm I know when on 6.0 I can use either the 6.0 or the 5.0.2 radio but haven't tried it in reverse...the general assumption would be that it would work.
---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------
hjelfman said:
When I have the stock ROM installed, my phone stops detecting my SIM card after a while. It does not happen on custom ROMs. I have tried new SIMs, taking it out and putting it back in, and multiple reboots. The only thing that solves it as far as I'm aware is factory resetting. Does anyone have another solution? As well, does anyone have a flashable radio/modem/baseband for the 6045l (preferably stock 6.0)? I'd like to try that.
Click to expand...
Click to collapse
The marshmallow thread in android development has a link to a folder I created with some flashable radio zips including both 6045i ones however if you are on t-mobile then using the 6.0 one is just going to lose you features...specifically it loses band 12 LTE if you happen to use that band.

famewolf said:
Hmm I know when on 6.0 I can use either the 6.0 or the 5.0.2 radio but haven't tried it in reverse...the general assumption would be that it would work.
---------- Post added at 06:46 AM ---------- Previous post was at 06:44 AM ----------
The marshmallow thread in android development has a link to a folder I created with some flashable radio zips including both 6045i ones however if you are on t-mobile then using the 6.0 one is just going to lose you features...specifically it loses band 12 LTE if you happen to use that band.
Click to expand...
Click to collapse
I have the same issue on 4045Y, I unlocked boot loader on panasonic firmware but it failed first time(stuck on Powered by Android Panasonic version) I then restored with mobile upgrade Q en got back on stock but my SIM wasn't getting detected anymore. After that I tried to go back to Panasonic firmware only with a different pc, This time it did work and I got signal but that is on the panasonic firmware is there a way for me to get Signal back on stock?

No Network Signal In Nexus 5X

Please Help !!!
Need help from experts.
there is a network error in my Nexus 5x (LGH791)
i went to testing mode on my N5x by using this code *#*#4636#*#*
and saw lots of things.
i went to the phone info option
and curiously i clicked on the "select radio band"
and pressed on the "USA Band".
after that all signals and network service is completely gone from my device.
its just showing me my operator name and "Emergency calls only" bt no signals.
same SIM is working perfectly on other device.
i tried with other sim in my N5x.they all are working in other device.
i did factory reset my device 2 times and erased all data and storage cache.
but problem is going on the same way.
My N5x is running on now android 6.0.1 (Build MTC19V).
please help me to get rid of this problem and have back my N5x working perfectly.
Some site is telling that factory image flashing will resolve this problem
but i have some doubt.
after doing this, is it going to stop all lateset OTA firmware update from google ?
and which firmware should i download from the google developer site the "Nexus factory images" or "Latest Nexus OTA images"
am confused.pls help
i just want my phone back work perfectly like first. nothing more i want.
pls suggest me step by step solution. pls help
TIA

You can try that. But tell me do you know how to flash a rom?
Then just download a stock rom and flash it. Hope it will save you.
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
Remember mate, don't ever try to do things which you can't understand or having no knowledge about them.

Why is my S7 Stuck on the T-Mobile screen / Doesn't work and how do I fix it?

So, I rooted my S7. It worked fine. One day, randomly out of no where it bootlooped (Google play services crashed. I restarted phone and it bootlooped. )
I have not made a single system modification other then rooting it. Didn't mod anything or mess with system files, and I had barely even been using the phone when it happened.
So I unrooted it (The phone still gave me the "Custom" symbol though) and Just now-- It randomly restarted. I didn't restart it. it just did it by itself. And it came into a bootloop. I don't understand why. What can I do to fix this?
MORE SPECIFICALLY: By Bootloop, I mean it stays on the T-Mobile screen and vibrates every minute or so and does not do anything (I even left it alone for ~ 30minutes and it never got past this screen)
Factory resetting the phone fix's it, but I don't want to factory reset my $400 phone every week! I don't understand how I could fix this either.

What method did you use to unroot? Did you flash stock firmware with odin?

sparky2029 said:
What method did you use to unroot? Did you flash stock firmware with odin?
Click to expand...
Click to collapse
All I did pretty much was flash stock s7 firmware. (More specifically boot.img)
Originally couldn't find a stock s7 image then I just used one I already had and it worked fine

EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open

Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Just now noticed wat your problem is sorry for being late so yes to fix the bootloop refladh stock firm and when you go through all the root steps install xposed (yes it's possible it's insane on how they got it to work but it's possible I've done with my self)after getting xposed installed through flash fire go to xposed and get xtouchwiz something it's a blue gear install that And it will set your system status as official
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
Andrew S.S. said:
EDIT: Flashed the entirety of G930TUVU4APK1 firmware, (Rom and all) Hopefully this will fix my issue and stop it from happening but if Anyone has any ideas or suggestions, I'm all open
Click to expand...
Click to collapse
Here's a quick explanations of wat i think it is it's becuz you've ether heavenly been modding the phone or if your phone status is custom then that's the problem I had with mine after asking around someone gave me the fix i put it in the other comment hope this fixes your issue it worked for me 2 months of no bootloop I switched to 7.0 vzw beta so I lost root

Was 920I now 920F should I be concerned?

Hi, I am not for miller with everything and I am concerned about what I did.
I followed instructions to install Android 10 on my S6 and when it failed
I got into a panic and found this download CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip
and not paying attention to 920F I installed it using Odin and my phone worked again
but the screen was inverted to the touch screen and on this forum, I found by typing in a sequence of numbers on the keypad
I inverted the touch screen back to be able to use the phone again.
few days later I tried again...
I then installed TWRP and EvolutionX_4.1.69_zerofltexx-10.0-20200331-0232-OFFICIAL Samsung S6 Firmware
and everything went to plan but I am finding my phone to be slower than before, about a 2 second delay to open things and somethings like
opening the camera can take a long time and sometimes it hangs and I need to close the App and try again & the flash only works if I tap to focus first.
My question is should I change my phone back to 920i or is my phone now working as a 920F perfectly fine?
And if so would anyone know where I can find the CF Root zerofltexx sm-g920i download I need?
I have searched and searched and can only find a full factory firmware of 1.88Gb but the file I used "CF-Auto-Root-zeroflte-zerofltexx-smg920f.zip" is only 33.4Mb
I feel I need to find this 920i download to correct my phone back to how it was. Or like I said should I not be worried about it now being 920F?
Thanks

question here is does it work correctly like this? you cannot fix something that is not broken
---------- Post added at 09:11 PM ---------- Previous post was at 09:03 PM ----------
in all seriousness, those issues sound pretty experience-effecting, if i were you i would grab a version of odin and the latest stock rom for g920I, flash stock and eventually get yourself set up with twrp and a recent rom which works with magisk.
i do not see any need for cf-autoroot anywhere in my suggestion, but for the sake of information both cf-autoroot and stock roms should be obtainable on firmware.mobi (and if the download seems to be cruelly slow, this little tool used to be able to get much faster speeds for stock roms but I am not sure if this is still the case anno 2020.)