Hello guys! Welcome to the second #GalaxyS7 post for the day. In this material, we talk about uncommon yet serious boot problems that some S7 users have encountered. We hope you’ll find this post helpful.
If you are looking for solutions to your own #Android issue, you can contact us by using the link provided at the bottom of this page.
When describing your issue, please be as detailed as possible so we can easily pinpoint a relevant solution. If you can, kindly include the exact error messages you are getting to give us an idea where to start. If you have already tried some troubleshooting steps before emailing us, make sure to mention them so we can skip them in our answers.
Below are specific topics we’re bringing for you today:
Problem 1: Galaxy S7 “Device storage corrupt. the data partition has been corrupted. you need to reset your device to factory default settings. this will erase all your data” error
Hello!! I am at USA now and using Samsung Galaxy S7 edge SM-G935FD Duos factory unlocked GSM smartphone international version. Earlier my device used be to automatic reboot. so i did factory reset so many times when it used to happen but now it’s even unable to open in safe mode and also factory reset. now, when i switched on my device it shows a message that “Device storage corrupt. the data partition has been corrupted. you need to reset your device to factory default settings. this will erase all your data” and at bottom “RESET DEVICE” button icon shows which does not responds. and after few seconds it again restarts and keep showing same message. please help me to solve this problem. thank you in advanced. — Mahesh Tambe
Solution: Hi Mahesh. There are two possible reasons why your phone is showing “Device storage corrupt. the data partition has been corrupted. you need to reset your device to factory default settings. this will erase all your data” message. One is the possibility that the error is accurate and that memory partition/s have been corrupted. The second is the chance that there’s a physical malfunction that rendered the memory chip unusable. This rarely happens to relatively new devices like a Galaxy S7 although constantly or regularly reflashing a device may hasten the degradation of the memory chip.
To see if your case is the first one, try flashing a stock bootloader, then firmware. If manual installation of official ROM won’t fix the problem, you’re out of luck. That means the issue goes beyond the software and there’s a need to replace the motherboard.
Problem 2: Galaxy S7 bootloader exception error after failed update
Dear The Droid Guy. Regarding the previous issue of my phone showing weird pixels before freezing and getting stuck in a bootloop, I managed to update its firmware from 6.0.1 to Nougat (7.0+). It was working perfect for some time until a few hours ago when a random line of pixels appeared again which I restarted (and it continued working perfectly). It was fine until it went to shut down by itself all of a sudden a few minutes ago and it got stuck in a bootloop for a while before turning on. I got a notification to update my firmware further so I immediately pressed it and updated my firmware (100%) before it got to the restarting part. It was stuck on the Samsung logo for quite a few minutes and I assumed it was the bootloop again so I restarted my phone (probably shouldn’t have). It restarted to the Samsung logo and then blacked out. This time, for real. Volume down + power or any other button combination isn’t working. I plugged in my charger and no response. The phone does feel warmer upon plugging in but completely no response. Just a black screen. I am sure it is not powered, as a powered black screen will show the pink line (another problem due to display hardware issue) and this is completely black. Hence I know that the screen has no power at all. I have tried multiple plugs and I conclude there isn’t any issues with the charger as well. Any idea how to make this work? Thank you!
Update to the previous email. My phone died for the past hour or so and I got two sets of error codes from this.
Set 1: Bootloader exception [AST_STAT = 0x1000000] Exception: do_handlr_sync: UNKNOWN(esr:0x2000000) socket:s0 pc: 0x8f000a00 lr:0x0f000a10 sp:0x8f10b800 r:qauxd_socket:s0 /dev/socket/qaux_radio(/.*)?
Set 2: Bootloader exception [AST_STAT = 0x1000000] EVT 1.0 ASV TBL VER=0, Grade = C ECT: LOT_ID=N92VW CHIP_ID=000000000000 CHIP_ID2=00000000 MNGS:0’C APOLLO:0’C G30:0’C ISP:0’C [this part is same as set 1] Exception: do_handlr_sync: UNKNOWN(esr:0x2000000) socket:s0 pc: 0x8f000a00 lr:0x0f000a10 sp:0x8f10b800 r:qauxd_socket:s0 /dev/socket/qaux_radio(/.*)?
I think there are a few typos in there. Can’t really see very clearly. under the pc, lr, sp, r line is a really weird line like an underline that isn’t straight. Does that help? It is currently working now for some amount of time that I am not sure, but this problem seem to be occurring more often, please help me! Thank you. — Kwan On
Solution: Hi Kwan. The error codes usually show up to indicate a corrupted bootloader. We don’t know what exactly happened since you did not provide any background information other than that untimely interruption you did when the phone was still trying to complete an installation. That may or may not be the direct reason for the error codes now but we did notice them before in cases wherein devices had corrupted memory chips or bootloader.
The only suggestion we can give you at this time is to try to reflash the bootloader back to stock so the old one is replaced with a new one. Reflashing the bootloader can fix a number of variations of bootloop problems so it’s worth giving it a try. If that won’t work, contact Samsung so they can replace the device.
Below are the sample steps on how to flash a bootloader. Exact steps may be slightly different for your particular device so kindly look for more accurate guides meant for your specific phone model.
- Look for the correct firmware for your phone model and download it. Make sure that you select the right one. It should be the same exact firmware that ran previously on your device. We assume that you list down the firmware version somewhere. If you did not take note of it before, there’s a chance that you may pick the wrong one. As you may know now, using an incorrect firmware can cause complications so good luck with that.
- Let’s now say that you have identified the correct firmware. You then want to download it to your computer. The firmware file should have a bunch of files in it like AP_, BL_, CSC_, etc.
- Look for the file that starts with a label BL; this should be the corresponding bootloader file for this firmware. Once you’ve identified the bootloader file, copy it to your computer’s desktop or to any other folder that you can easily access.
- Proceed with the rest of the flashing procedure using the Odin program.
- In Odin, click on the BL tab and make sure to use the bootloader file you’ve identified earlier.
- Now, make sure that the “Device Added” status and its “ID:COM box” has turned blue before hitting the START button. This will initiate the flashing of your phone’s bootloader.
- Restart the phone once the procedure is finished.
Problem 3: Galaxy S7 edge moisture detected error, won’t charge
After installing the latest update on my Galaxy s7 Edge I started getting the “moisture in charging port” message. Tried to clear the cache and got the “no command” with resting android message. Now my battery is dead and even when plugged into the charger it will not respond to any of the button combination “fixes.” Any other suggestions? I’m really in a bad place now because T-Mobile won’t do a warranty exchange or let me trade it in on a new phone. — Rose Purcell
Solution: Hi Rose. Moisture detected error is feedback to let the user know that charging is being put on hold because there’s water or moisture in the charging port. Unless you address the error first by making sure that the charging port is fully dried, you’ll be unable to charge the device via USB cable. However, if you have a wireless charger, the phone should still be able to charge fine albeit at a slower rate.
To dry the charging port, first you want to gently shake the phone to force the water out. If that won’t remove every moisture there, try placing the device near an indirect heat source like the back of a TV or computer. Water will eventually evaporate so just let the device stay in the heated spot for up to 24 hours.
DO NOT apply direct heat or place the phone near fire or oven. Direct heat will damage heat sensitive components in the motherboard.
If the error message continues even after letting the phone stay near an indirect heat source, bring it to Samsung service center or to an independent electronics shop that fixes wet devices. Once the error is gone, you should then be able to charge the phone normally again via USB cable.
Engage with us
If you are one of the users who encounters a problem with your device, let us know. We offer solutions for Android-related problems for free so if you have an issue with your Android device, simply fill in the short questionnaire in this link and we will try to publish our answers in the next posts. We cannot guarantee a quick response so if your issue is time sensitive, please find another way to resolve your problem.
If you find this post helpful, please help us by spreading the word to your friends. TheDroidGuy has social network presence as well so you may want to interact with our community in our Facebook and Google+ pages.