Database Info

Not to alarm people, but this OTA update bricked a stock Captivate

Take this for what it is. One person with a stock captivate phone who had problems.
He claims he didn't stop the update half way through the process or anything like that.
the latest software update from at&t bricked my ****ing phone. ***** i talked to through online at&t chat said it's the manufacturer's fault when it's really not. who do i contact to replace the phone?
Click to expand...
Click to collapse
He was asked if this update included 2.2...
i have no idea. i think it was just a gps update. the thing is i'm running a completely un-modded phone. this is ****ing bull**** if i have to pay money for something that samsung/at&t ****ed up. it's completely bricked. won't boot, won't power on, won't even charge. tried reseating the battery and sim card a dozen times and i tried doing the volume buttons + power button boot thing and it's just ****ed.
Click to expand...
Click to collapse
comment from someone else
AppSmasher says: September 22, 2010 at 11:23 AM
Updated my Captivate and it’s working great. I have heard of those that cancel in the middle of the update could experience problems – some even claim it bricked their phone.
so bro, tell us the truth.. Did you turn off ur phone or cancel the update mid way?
Click to expand...
Click to collapse
he was asked to check here for help...
i saw the thread. i dont think there's anything i can do. it won't boot into recovery or download mode. it's like completely dead.
Click to expand...
Click to collapse
i never said it was forced. i read a post about froyo maybe being available so i clicked the 'software updates' thing and it said an update was available. it downloaded and said it was going to reboot the phone to presumably install it. the phone rebooted to a white screen with a blue loading bar and said 'update failed.' now it no longer powers on or even recognizes being charged.
Click to expand...
Click to collapse

I can attest to the update bricking. I did cancel the download half way to turn on wifi and figured it would be simply restarting the download, but instead it started installing what was there and it stated it was going to restart so I let it and then nothing happened...tried taking the battery out and tried getting into download mode to no avail. Anyone got any ideas?

Yeah call att. Sorry bro looks like its dead dead
Sent from my SAMSUNG-SGH-I897 using XDA App

tytdfn said:
Yeah call att. Sorry bro looks like its dead dead
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
the poor guy did call AT&T. It's at the top of the post. They said they weren't responsible.

Citznfish said:
the poor guy did call AT&T. It's at the top of the post. They said they weren't responsible.
Click to expand...
Click to collapse
He spoke to the wrong person then and should call back. Mine is broken also, and it's past the 30 days, so all I could get was a refurbished one. Better than nothing. I'm never doing an OTA update again. Flashed my phone upwards of 20 times and if something messed up I could alway reset to download and re-flash.

majinzen said:
He spoke to the wrong person then and should call back. Mine is broken also, and it's past the 30 days, so all I could get was a refurbished one. Better than nothing. I'm never doing an OTA update again. Flashed my phone upwards of 20 times and if something messed up I could alway reset to download and re-flash.
Click to expand...
Click to collapse
This.
I went to the warranty and repair center in my area (dunno if everyone has one?) and they have ordered a new (refurb?) captivate for me. As long as it works and isn't too beat up, I don't really care. I'm just sick of this E63. lol

is the internal 16gb an internal memory card? Maybe if it is, you can pull that out and rebuild the whole OS of the phone through another source such as a card reader.

I tried the update on my phone. It's rooted and set up for sideload as well as a few other hacks.
However, I only bought my phone about 3 weeks ago. The update has failed 4 times for me, then i checked the existing firmware on the phone. It's already at I897UCJH7.
Take it for what it's worth.

Mine is totally stock and it was also bricked last night. I tried everything to fix it but it is completely dead. I tried the update last night and didn't interrupt it at all. The progress bar made it to 50%, stalled for a minute and then gave a message that the update failed. It tried to restart and it went completely dead. I've tried using Odin, but nothing happens. sin
I also called AT&T and was initially less than pleased after I was told to call Samsung for a possible fix. I told CS that I didn't buy the phone from Samsung and that I wasn't calling them, since it was an AT&T problem. I finally got someone to authorize a return and my new one should be here in a couple of days, but the fact that this thing was totally bricked so easily because of an official update is ridiculous.

The only updates out there is JH7/2.1. Bricking phones while OTA update to JH7 is nothing new. Just check all the JH7 threads. Stay away from OTA updates for now.
You won't get 2.2 OTA update until weeks after it is talked about all over the place.

A-Rob said:
Mine is totally stock and it was also bricked last night. I tried everything to fix it but it is completely dead. I tried the update last night and didn't interrupt it at all. The progress bar made it to 50%, stalled for a minute and then gave a message that the update failed. It tried to restart and it went completely dead. I've tried using Odin, but nothing happens. sin
I also called AT&T and was initially less than pleased after I was told to call Samsung for a possible fix. I told CS that I didn't buy the phone from Samsung and that I wasn't calling them, since it was an AT&T problem. I finally got someone to authorize a return and my new one should be here in a couple of days, but the fact that this thing was totally bricked so easily because of an official update is ridiculous.
Click to expand...
Click to collapse
way to revive a several month old thread...

Samsung Galaxy S3 acting possessed

Lack of a better subject description the only thing I can describe it as is possessed. I've never had this problem before. Searched various different keywords and couldn't find anything. So if this is a repost then I apologize.
I have a Samsung Galaxy S3 from Verizon white 32gb. Never been rooted. Around the time Verizon pushed out the last update for the phone it's been acting strange since the update and it's progressively gotten worse. It's almost made purchases for me while I'm browsing google play it'll randomly press areas and randomly click buy at times. Or I'm trying to text someone and it'll either type something on it's own or start trying to delete/lock/resend, etc messages. It starts up s voice randomly too.
So basically it's like having a set of ghost fingers/hand trying to control my phone while I'm trying to control it and the ghost is winning and I'd rapidly hit the home button to exit out of whatever I was trying to do. If the screen is on and unlocked it'll do the same thing even if I'm not touching it but this is maybe 1 out of 5 times compared to the while I'm trying to actively use my phone it'll be 1 out of 2.
Temporary fixes have been to just restart the phone and at first it would only occur every couple days and then once a day and now every few hours to every few minutes. Anyone have any suggestions on what I can do? Any tips would be greatly appreciated. Thanks!

All you have available right now is factory data reset or refurb. If don't fix reflash the latest available stock software via Odin or root and unlock it and flash anything. Can even root stock and have access to better apps.

Try a factory reset if you haven't.
Sent from my SCH-I535 using xda premium

I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!

If i were in your position I would try to Odin back to the stock rom you had before the update. There is a sticky in the development section that tell you how to do that and much more
Sent by one of my many Anthromorphic Personifications

elayn said:
I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!
Click to expand...
Click to collapse
It sounds defective. I'd take it back.

What you are describing happened to my Droid Incredible a few times: it appeared that someone else was creating random tap events on my phone. Turned out to be a slightly dirty and/or stuck optical trackball - once that was cleaned (easy), everything was back to normal.
Now, the Galaxy S III does not have a trackball. I don't see a direct correlation with my Incredible, but the symptoms you describe are oddly similar: perhaps try cleaning your various pushable keys, just in case?
Might install and run Symantec Antivirus just for a final check, then call Verizon Support if it's still happening and perhaps see what they can offer.
- ooofest

Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.

adoublearonn said:
Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.
Click to expand...
Click to collapse
Because the device is so new you have a very good chance of getting a new replacement. I had something happen to my GNEX and they replaced it with a new phone no refurb.

Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.

elayn said:
Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.
Click to expand...
Click to collapse
Or Odin stock firmware instead of waiting. Can Odin without root.

prdog1 said:
Or Odin stock firmware instead of waiting. Can Odin without root.
Click to expand...
Click to collapse
I'll give that a try tomorrow morning and hope it works. I'll check in either way. Thanks!

Take a look at this, and look into this virus some more:
blog.lookout.com/blog/2010/12/29/geinimi_trojan/
I did some research and someone said those are the symptoms of the virus...
Sent from my SCH-I535 using xda app-developers app

It's Verizon, some tech there is having fun with the remote capabilities of the new OTA.

Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.

elayn said:
Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.
Click to expand...
Click to collapse
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.

BiasedThunder said:
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the tip but if you read through the whole post. I did default to calling 611 like I usually do and they wouldn't do anything about it. Yes, I did tell em I did the factory reset. It's not the first time I had a phone replaced through 611 I've gone through maybe 10+ replacements on one of my past phones because they kept sending me a defective one over and over again. I did call 611 again since you suggested it but I was told the same exact thing as last time.

I had this happen a few times with my phone before the update verizon pushed (stock, rooted). I would end up pulling the battery to get it to stop. Hasn't happened to me in a while though. Now i'm running JellyWiz RLS12

Restored to Factory, Phone is freaking out, Screaming/Rebooting every couple seconds

Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you

Wickidmasshole said:
Okay, So ive been banging my head against the wall for 2 days straight now with this problem so ive finally come to post about it to see if anybody has ANY idea how i can fix this. I have searched high and low for anyone who has come across this problem and i cant find another poor soul stuck in this predicament.
I have the D850, and have had it since last July. It was Bumped the day that it came out and ive been happily running roms on it since. I have honestly probably tried every ROM that was ever released for this phone, never had any issues.
I had flashed back to stock maybe a few weeks ago bc i had never done so, and after flashing a million roms i figured id try out straight stock for the first time in a year. SO i flashed the kitkat stock rom, and booted up everything was fine, then there was maybe 2 updates that i did OTA. I knew lollipop was out so i updated to that and all was well. I eventually got weary of straight stock quickly so i rooted and installed some of the fun stuff. Now this is where i noticed something i hadn't had before- when i would boot into TWRP i would get an unsecured boot error: error 1300- or at least i think that's what it said...Everything would flash fine and boot up so i didn't think much of it, but now that im having the issues im having, i think this is where it stems from.
Fast forward to 2 days ago- i figured i would flash back to 100% stock because i will be receiving my 6P next week and was going to donate this phone to my aunt bc i have taken such good care of it i figured id hand it down to a needy relative instead of get $20 bucks for it on ebay- All goes well i get the Blue screen with the 3 on it, pull battery and reboot. Everything seems normal..att logo...welcome screen..i go to touch the screen and its frozen. then reboots. weird. it does this a few more times, sometimes staying alive for up to 3 mins before freezing and rebooting again. Sometimes it even screams at me- no joke- it will freeze and make a high pitch screeching noise then shut down. scared the Sh*t out of me the first time it did it.
Ive tried everything people...i have downloaded fresh tot files/tried 5 different computers/fresh installs of flashtool/LG PC suit/hard reset/ran in safe mode/changed flash settings form upgrade to Board- to no avail. I honestly don't know how the phone hasn't died yet bc i think ive flashed the thing 30 times in the last 2 days from various computers. Remember- every time i flash in flash tool it passes, its only when it boots back up that it freezes/screams/reboots.
Sorry for the long winded post, but i wanted to give you some context. I'm going to try and mess around with it some more today but i keep getting closer and closer to throwing it off the wall bc this is frustrating. I think my problems would be solved if there was a lollipop tot file to flash, but i looked around and couldn't find anything. Thanks for reading everyone, any ideas are welcome. I'm out of warranty so ill try ANYTHING to fix this. At this point even if i FUBAR it i don't gaf bc its broken right now anyways. Any ideas are welcome. Thanks guys and i hope this never happens to you
Click to expand...
Click to collapse
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk

hyelton said:
If it's making noise and freezing after flashing, that sounds like an hardware issue. Since you've already tried reflashing it several times and it still does it nothing else can really be done. You can try selecting board_id in flash tool at the tot selection screen and try that.
Also I always gotten secure boot error when booting into twrp on my LG phones I've rooted and loaded twrp on them.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.

wait- did you mean select board DL?

Wickidmasshole said:
Yea man i tried that and it it boots into a screen that says DO NOT TOUCH SCREEN and then just continues to boot to that and i get a fail on the flash tool . thanks for your tutorial btw, thats what i used for all this troubleshooting. i found a thread about actually taking the phone apart and shorting it out and then trying to flash. i am going to give that a try if i cant get this f0cker to boot up correctly.
Click to expand...
Click to collapse
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.

hyelton said:
When it continues to boot what happens? Flash tool is supposed to fail.. Once the phone is out of download mode flash tool will fail as its done and has no connection. Once flash tool hits 80/85% its done. Never heard of the LG phone and taking it apart to short it out. That would be something if you had a brick and the phone doesnt go into download mode.
Click to expand...
Click to collapse
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!

Wickidmasshole said:
so it faild out at 89%, then the miniOS screen comes up, but then it just keeps boot looping into the AAT-mini OS 3.1 screen where it says AUTO TOUCH TEST dont touch screen!!
Click to expand...
Click to collapse
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk

hyelton said:
Strange. But yeah once phone reboots it's done. Flash tool percent means nothing. But very strange.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh well it was a great phone while it lasted. Thanks for the input.

S7 keeps freezing and restarting

Hi Guys /girls.
Just got an S7, brand new on O2 (UK). I usually root my phones but haven't touched this as it's quick enough and I don't want to play around with it until the warranty ends.
In the past few days the phone has been freezing, then it will turn off, sometimes restarting entering a bootloop. It will come back on for a minute or two, then repeats.
At the moment it is working following a forced restart but not sure if this will last. Has anyone else had these issues? Or does anyone know what it could be? Going to get it swapped anyway just to make sure but I can't understand the cause. Thanks in advance

Had the same issue this moth, send it to warranty it will only be worse over the days. Samsung replaced my mbo and now everything is ok

Getting worse.... Trying to get it sorted with O2 is an absolute joke, their customer service is disgusting. Been into two stores and on the phone to them twice and they're not simply swapping it for me.... I haven't even had the device three weeks

richyharrison04 said:
Getting worse.... Trying to get it sorted with O2 is an absolute joke, their customer service is disgusting. Been into two stores and on the phone to them twice and they're not simply swapping it for me.... I haven't even had the device three weeks
Click to expand...
Click to collapse
Contact Samsung on twitter, they offered to send a courier to my house free of charge to collect mine and fix the pink dot problem

*Detection* said:
Contact Samsung on twitter, they offered to send a courier to my house free of charge to collect mine and fix the pink dot problem
Click to expand...
Click to collapse
Thanks mate. They have just said they're sending out a new one tomorrow... Fingers crossed!

richyharrison04 said:
Thanks mate. They have just said they're sending out a new one tomorrow... Fingers crossed!
Click to expand...
Click to collapse
Nice one, good luck

New phone arrived. Definitely more responsive with a better battery life than the first one..
However it froze and restarted this morning....hoping it's a one off.

richyharrison04 said:
New phone arrived. Definitely more responsive with a better battery life than the first one..
However it froze and restarted this morning....hoping it's a one off.
Click to expand...
Click to collapse
Are you using anything the same as with the last one, like a MicroSD card or headphones etc?
Anything that is common between the two phones?
Same app that might be doing it? Maybe a restore from a Google backup when you first boot up reinstalling a buggy app?

Did you upgrade firmware to the latest version? It might be a software bug.

Seems fine now cheers guys. Auto frmware updates (x2) were done last night....must have been a one off. Definitely won't be rooting this device like my older phones!

G930F - crash bootloop issues

Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks

Sacher_Masoch said:
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Click to expand...
Click to collapse
Hi
Do a factory reset , do not restore anything see if it works ok , if so then it maybe an app causing the problem
or you could flash a stock rom to test the phone and make sure there is no hardware issues

Thank you for your answer.
I'll take a try this weekend with a stock rom as I have the issue with 2 custom roms so far.
If anybody has other ideas until that, please let me know

Little feedback. I flashed the stock Samsung rom two days ago and it seems to work fine for now. But it was also quite fine with the custom rom at the beginning, so I will do another feedback after one or two weeks.

Well... The phone froze and rebooted 5 times in 10 minutes after trying to update some apps itself...

I had the same problem. At the end I was not able to boot Android. I had to claim my cell phone to seller. After one month it was repaired. The final verdict was SOFTWARE problem. They said that EFS was corrupted. One of Samsung firmware has bug which cause problem with EFS.

I also had that problem. I also had to send my phone to the repair center. In my case they replaced the mainboard.

I bought one early september and after two weeks it started doing just that. I tried everything, then sent it to the seller (ebay seller...) and the repair shop couldn't anything about it. I only got my money back yesterday. Back when I invesitgated the issue, nobody was talking about it. So since I liked the phone, I bought a new one from another place (less shady) yesterday... I now think I shouldn't have. Anybody knows more about this ?
Edit: I'm thinking that if I root the phone and backup the EFS and all sensitive partitions before starting using it (or even getting updates) I should be safe...

Yeah, that would be great, but your KNOX will be 0x1. So you will have problem to return this phone back with status 0x1.
Odoslané z SM-G930F pomocou Tapatalku

Hello everybody,
Sorry for the very late reply. I actually sent my phone to another shop here in Japan. But this week, they send me a mail to say that they were not able to fix the issue. But still they taker me 50$ for the time...
I was thinking about buying a new one, but now that some of you are talking about an EFS issue, I'll try to fix again. I will look for some tutorial for that, but if you know how to procede, just reply here
Merry Christmas guys !

hello, i've been having a similar issue.
My phone would be fine for 2 weeks, maybe a month then Suddenly it would reboot to no end, it even reboots from TWRP.
It doesn't reboot while in Download mode. Then what i do to fix it is flash a stock rom from ODIN, sometimes the first couple or 5 times it will reboot during initial first boot up of this stock Rom. I would leave it alone for a while like half day then try it again in the evening or the next day.
Today for example, it started boot looping late last night and I installed Stock ROM with PIT FILE and Nand ERASE and Repartition ticked, boot loop, again, boot loop, tried it again, also rebooted before it started up to stock recovery and factory reset. Then it started up fine and has not rebooted so far.
But this has happened many times and it'll happen after 2 weeks or 1 month. When it does, i first go and delete cache and delvic cache to see if that would fix it, but it doesn't.
Right now it works, but for how long i don't know, when it works, everything is fine with the phone, no imei or calling or heating issues.
I can't guess whats wrong, is it really EFS that got corrupted but not fully but eventually its finding a problem and causing boot loops or something if that makes sense??