Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
jfm91 said:
Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
Click to expand...
Click to collapse
Factory reset from recovery?
Yes. full wipe on everything
jfm91 said:
Yes. full wipe on everything
Click to expand...
Click to collapse
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
*Detection* said:
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
Click to expand...
Click to collapse
After you replied I tried to flash again.
Flashing took 3 mins.
After that the phone went straight to boot loop. I have now waited 15 minutes, and still no boot. The screen have turned black, and blue led indicator is on
Sounds like something else is wrong if it still loops after flashing CSC, that contains the PIT file, which repartitions the phone, and also resets it
Got a MicroSD card in? Try removing that in case it's faulty, otherwise hopefully someone else has some ideas
Could try flashing the Nougat Beta as a test
I have removed SD-card. (Have it in my backup phone now.)
Could it be hardware issue?
I'm considering to contact my insurance company, for a new phone
Could be, but sounds more like a firmware issue
Tried Smart Switch firmware recovery?
*Detection* said:
Tried Smart Switch firmware recovery?
Click to expand...
Click to collapse
Doesn't help either
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Problem is that I have "custom binary count"
jfm91 said:
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
Click to expand...
Click to collapse
Mabey you should try flashing an older firmware like PE1 and then updating later!
http://www.theandroidsoul.com/download-galaxy-s7-firmware
using Odin but first try only flashing the AP, CP, and CSC don't do the BL. If that fails then try doing a flash with the BL included. Hopefully this works!
If worst comes to worst, if your knox isn't tripped, then send in or warranty.
Did you put a custom recovery on it?
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
jfm91 said:
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
Click to expand...
Click to collapse
better question. Can you last on your old phone til Galaxy 8 comes out for sale?
Alikhan821 said:
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Click to expand...
Click to collapse
Did you manage too solve this issue ? I am facing the same problem.
Cheers
Hi,
Samsung repaired the phone for me so the issue was solved.
Do you remember what the issue was about and how much it costed you ?
Thanks.
Since the phone was in warranty and I never rooted it, it was repaired for free. They arranged to come collect it from my house and I had it back within 3 days. They replaced the motherboard in my case.
Related
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...
Hi everyone,
Right I have a serious issue with a 4 day old S6 from the UK bought SIM-Free off Amazon.
My phone was rooted but didn't have ADB or any sort of custom recovery. I edited the build.prop file for the RAM management thing, and created a copy back up on my storage. I didn't like it too much, so I copied the back up over the edited one and restarted - phone went into boot loop.
I have attempted to use Odin and flash a stock firmware ROM (had to settle for a H3G variation because the XEU unbranded was off some download website that takes 10 hours to download). I went through all the steps with Qbking77's walkthrough with Odin and it came up that it failed at the end.
The phone then booted into the Emergency Recovery screen, and couldn't get back into Recovery (to do the Smart Switch recovery), and can only get back into the Download bit.
I've tried flashing it again, and no avail.
I seriously, seriously hope someone can help me out here, it's a brand new phone and I love it and I don't want to be left with a brick.
Thanks.
I was in the same boat, if you rooted and didn't trip Know, your best bet is the Samsung Store, they're all over the UK
Well an update:
After the third time flashing failed, I did a root via Odin which had previously failed, and it booted up, completely normal and set up the device as normal.
I have no idea how that worked - but it did. Probably tripped the Knox I think but it works.
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
SirMilkaPeach said:
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
Click to expand...
Click to collapse
This just happened to me and I the problem was that I had Secure Startup enabled under Lock screen and security. I just disabled it and re-rooted it and that fixed the problem. Hope it works for you.
Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!
MTS0 said:
Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!
Click to expand...
Click to collapse
Try this thread linked below, try the instructions in post #6. Don't use any files that are linked in the thread, they are not for your device. Make CERTAIN that you use the files for your device but try those steps and instructions, they should work the same for your device.
If the instructions in post #6 don't work, try reading further in the thread , there may be more solutions discussed.
https://forum.xda-developers.com/showthread.php?t=2302144
@MTS0, I forgot to add the link, sorry, hope it helps.
Sent from my SM-S903VL using Tapatalk
Thanks for your reply, but I can't go into recovery mode. Boot loop and download mode is the only thing it still does. I can't even turn the device off, need to wait for the battery to empty.
I was checking out that thread, they are talking about flashing the PIT and param. Do I have any chance with that? I just need to acces my data....
Thanks
SM-G930F
TWRP 3.62_9-0
Last Known ROM: [TeamExyKings][S7_S7Edge_G930_G935_F_FD][Pie_9.0][15-January-2020][Note_FE_Port][v20]LightROM
I'm trying to get my S7 to stock. I have no idea where it's going wrong. This all started when I went to get my phone off the charger and it looked like it took a hard crash. Im not sure why either. I can get into DOWNLOAD MODE, and I can reflash my TWRP with ODIN. Whenever I go to flash a ROM in TWRP, it freezes on install, and I have to hard reset it. Anyways, my end goal is to get my S7 back to stock. Thank you so much in advance.
I've managed to get a rom(LightROM) in.. but I am stuck on a BLUE LED and a Black Screen? Anyone got the possible solution to get back to a stock rom? I am actually having a hard time finding a stock rom as well.
RowtronX said:
SM-G930F
TWRP 3.62_9-0
Last Known ROM: [TeamExyKings][S7_S7Edge_G930_G935_F_FD][Pie_9.0][15-January-2020][Note_FE_Port][v20]LightROM
I'm trying to get my S7 to stock. I have no idea where it's going wrong. This all started when I went to get my phone off the charger and it looked like it took a hard crash. Im not sure why either. I can get into DOWNLOAD MODE, and I can reflash my TWRP with ODIN. Whenever I go to flash a ROM in TWRP, it freezes on install, and I have to hard reset it. Anyways, my end goal is to get my S7 back to stock. Thank you so much in advance.
I've managed to get a rom(LightROM) in.. but I am stuck on a BLUE LED and a Black Screen? Anyone got the possible solution to get back to a stock rom? I am actually having a hard time finding a stock rom as well.
Click to expand...
Click to collapse
Going back to stock is probably the best option, download the firmware from here selecting your country and carrier
Download Samsung Galaxy S7 SM-G930F firmware
Download the latest Samsung firmware for Galaxy S7 with model code SM-G930F. Check out our free download or super fast premium options.
www.sammobile.com
you will have two csc files the csc file wipes the phone whereas the home csc upgrades the software, you would use home if you had a working rom say Android 7 and wanted to upgrade to 8. You want to wipe the phone.
Not_Rich said:
Going back to stock is probably the best option, download the firmware from here selecting your country and carrier
Download Samsung Galaxy S7 SM-G930F firmware
Download the latest Samsung firmware for Galaxy S7 with model code SM-G930F. Check out our free download or super fast premium options.
www.sammobile.com
you will have two csc files the csc file wipes the phone whereas the home csc upgrades the software, you would use home if you had a working rom say Android 7 and wanted to upgrade to 8. You want to wipe the phone.
Click to expand...
Click to collapse
well i went in TWRP and formatted/wiped everything. Would i still need a rom? I feel like something is mad corrupted. Maybe a Kernel? I haven't been successful of flash a room or getting into the OS yet. I just need to get into the phone and have it turn on.