[Q] Galaxy S4 Sensor issues - Galaxy S 4 Q&A, Help & Troubleshooting

Hi All,
I've been experiencing some sensor issues lately on my Samsung Galaxy S4 I9505. The issue is basically, that they don't work. After running tests and ensuring that it's not me being stupid, I sent it back for repair under warranty into Phones4u, (DO NOT ever do that if you take my advice) saying it's a hardware issue. That was in august (precisely on the 30st).
The first time the phone came back to me in september (25th) saying it had been repaired. And guess what, it had not. Same issues. (I'll skip the part where I complained over phone and emailed them and basically they ignored / didn't get back to me, or refused to give me a replacement phone saying I'm not with the ripoff insurance company they had offered) Cheers for that!
So I sent it back for a second round with an A4 sheet describing the issue in details.
After waiting almost a month - again - I got my phone back (yesterday.. Oct 19th) with the engineer's comments: "Couldn't find the problem."
Great!
BUT! Surprisingly, all sensors worked! wow!
But my joy didn't last long, as after a few hours the test Failed again. I restarted the phone and it turned out that restarting the phone helps SOMETIMES temporarily, and that's only confusing because I would've thought that I'm facing a hardware issue. But if they SOMETIMES work it must be a software issue.
So I went ahead and downloaded the latest OFFICIAL firmware (XXEUEMI8) with 4.3 android. With this I'm not voiding the warranty and keep the binary counter on 0 just in case it has to go back again. (Oh yes, the phone hasn't been rooted. )
But no, didn't work. Still the same issues.
In the video here you see my latest factory reset and sensor tests.
Any ideas? Suggestions? Maybe someone with similar issues?

Related

[Q] Camera icon gone, camera not startable

I turned on my phone last night, pressed the camera icon in the list of programs and it disappeared and hasn't come back since?????
Then went to the picture and movie tab and pressed the camera tab (both for taking picture and movie) and nothing happens, no camera launches.
I've had the phone sitting in the cupboard for days and it's cold where I live so I wonder if it's possible that the camera hardware has frozen and the icon disappears because the system cannot detect working hardware?
I don't know but my phone is out of warranty and I am worried.
Would flashing a new ROM help do you think?
normally your phone should not be out of warranty yet, since htc offers a 24 months warranty.
and if the camera worked with your rom before, changing the rom should not be necessary, but maybe a radio/rilphone upgrade would help or a hard reset.
Thanks for the reply
I've emailed the local distributor of my phone (bad reputation for replies) who paralell import it from singapore so I might be out of luck.
Done several hard resets and also warmed the phone up to see if the camera hardware was maybe stuck from the cold but no luck.
Tried to burn a new rom (The EnergyRom looked good) and the software keeps complaining that it lost communication with the phone so I can't even do that. Tried 10 times already.
So, I guess I have to wait for the supplier but they said the warranty is only one year.
afaik htc generally offers a 2 year warranty, so they are probably the ones, you'd want to contact about that issue, but before actually sending it to them, make sure to flash back the stock rom, radio and spl.
As I said above, I tried burning a new rom but the software keeps complaining that it loses communication with the phone so I've given up.
Thanks for the suggestions though.
I absolutely agree with Chef_Tony.
You've tried enough to exclude everything. It must be a hardware issue.
I think you can check the production date via the sn below the batt. I would just go ahead with HTC and call them, and NOT your local dealer.
You can also open a ticket online but from my experience that is a waste of time since they will start asking stuff to do and email them again.
HTC provides 24 months of warranty in most areas and the sn will be enough for them to decide if it is warranty or not.
Also do not mention the custom roms as that will void your warranty, even if the issue was there on the stock rom!
So go back to everything stock, everything that you need is in the sticky on the rom page, and give HTC a call.
The ROM is a stock one. I mentioned in my above post that when I tried to burn a new one that the phone lost comms so I never could get a new rom on to test if the camera would come back so I am still stock.
HTC mentioned all the same things you guys did.
Spoke to my supplier, looks like I have to send this back. Damnation!!!!!
Okay, made a few mistakes about trying a new rom but under severe pressure since my father died so I can't comprehend much at the moment.
Will try all the steps later when I am less distressed.
Sellers have gone, phone is worse.
Just to update people, this post can be locked now.
Blue Fly Mobile are gone, nobody can find them. They told me to send the phone back for repairs and when I was just about to, they turned up missing.
Web site is gone, no contact anywhere and I read in many forums about their bad rep.
Camera still gone. Battery may last a day if that. Phone randomly cuts of calls when I make them or when people make them to me.
Looks like I will be waiting for the new Samsung Galaxy Tab 10.1 when it hits OZ as it's better for my eyes.
Now, how to convince my wife that I absolutely need it???

Sensors and MCU not working

Hi guys,
New owner of a S4 (GT-I9505 international) here with a problem. 2 days ago I noticed the screen wasn't rotating anymore. I used to rotate it portrait/landscape in applications like Camera or Internet (browser). The moment when it started to bother me was when looking at pictures with the phone in portrait and the image was landscape. Trying to rotate the phone didn't help. It was frozen. I called a buddy of mine who has some experience with Samsung devices and told me to verify the "Auto-Rotation" settings. It was all OK and enabled. Then he suggested turning the phone off and pulling out the battery and SIM card for 5 minutes and putting it all back. This didn't help either. Finally we got to the point where he told me to enter *#0*# in the Phone dialing application. As you might already know, this code gives you access to the "testing" hidden utility. There I tested all the options available. Everything was fine except for the Sensors and SensorHub Selftest.
In the Sensors section, all the tests failed, starting with the Accelerometer and ending with the Temperature. I uploaded screenshots taken during the tests. Please remember this started 2 days ago. Before this it was working perfectly. I don't recall making and major changes like updating any OS components or installing/running stress utilities related to sensors or device behavior. After doing some research online and reading about other people's similar problems I got to the point where I started to suspect a problem with the MCU (Micro Controller Unit). This component, according to Samsung, controls all the sensors and reads raw data from them without accessing the AP (Application Processor) this way extending the battery life. I believe the problem is here because it seems odd that none of the sensors are working all of a sudden. Can this component put the sensors into a sleep state and shut them down completely? Might this be the case here?
Below are the solutions I tried in order to revive the MCU and finally the sensors. I was all without success:
1) Turned off the phone and pulled the battery and SIM out. Put the back in after about 5 minutes. Result: sensors not working.
2) Reset to factory-settings from the settings option while the phone was in the working state (turned on). Result: sensors not working.
3) Rooted the phone, installed Clockwork Recovery, made a full system and applications backup and then installed custom ROM (two actually: PACMan, Google Play Edition (4.3)). I did this in order to exclude a problem related to drivers in the stock Samsung ROM, even if it was logical that Samsung being the owner and manufacturer of the device might have the "best" drivers and applications for inquiring the device components/sensors. I am aware this ended the warranty for me, but can I know it can easily be undone. Result: sensors not working.
4) Restored the original stock Samsung ROM. Result: sensors not working.
The utilities used for sensor testing were: Sensor Kinetics and Sensor Tester. Both can be found in the Play Store. On my wives phone, which is an old HTC Desire, both utilities picked up the available sensors and created graphs with the results. On my S4, I only got blank charts/graphics/results. In Sensor Kinetics for the Gyro for example, the message was "Waiting for the Gyroscope sensor...", just that, stuck.
If there are any other guys (or ladies!) out there who encountered this awful experience, please reach out and tell me if you found any practical solution, any other then just taking the device back to warranty. I'm open to any suggestions.
Best regards,
Andrei
Most likely a defective device ... can't you claim warranty and sent it back?
Sounds like hardware failure. This would be an issue for Samsung to solve.
Sent from my GT-I9505
AvelonTs said:
Most likely a defective device ... can't you claim warranty and sent it back?
Click to expand...
Click to collapse
Unfortunately I bought it second-hand and it does not have any warranty. I guess it's one of those moments I wish I had patience and gathered more cash to buy a new one from the store. Anyway, it's my bad luck. I had it working perfectly for weeks after buying it. I will use it like this for the time being..
i´ve got the exact same problem since yesterday...
i think i´ll take it to the shop for warranty
I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...
darklord said:
I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...
Click to expand...
Click to collapse
Hi there. I had same problem with sensors and MCU test failed, so i took phone to service. They said its hardware failure and replaced main board. Im picking phone tommorow and we will see...
Hi guys,
I took mine to a local phone service, not the official one, but they are an affiliate. They could not figure out exactly what the problem was so they replaced the logic/main board just for testing. It was all working fine. They called and informed me of the findings. Given the fact I don't have warranty for it, they suggested to send it to our main service in Bucharest where they have a more sophisticated testing equipment. It is possible to get a more precise answer regarding the defective component and maybe a less pricey solution to the problem. At this time, the only viable option is to get a new logic board in place, which is about to set me back 250 USD. I will get an answer from Samsung in Bucharest by tomorrow or the day after tomorrow.
I will get back to you with my final solution... hopefully something not so expensive
@darklord, @eweu: please post back you findings. Maybe in the future when some other unfortunate owner finds his way in here, will have a better understanding of whats on the plate for him.
Thanks,
Hard reset did not work as expected. Going to drop it off at a local official repair center....
S4 Sensors failing
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week
KSal7506 said:
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week
Click to expand...
Click to collapse
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!
canaris1780 said:
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!
Click to expand...
Click to collapse
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.
i'm tired
canaris1780 said:
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.
Click to expand...
Click to collapse
really i'm tired to solve this issue.
when i install new stock software the sensors work fine just a few minutes only yhen return to fail again.
i think its software issue and i'll solve it :good::good::good:
Sensors work again
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again
abdali_m2 said:
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again
Click to expand...
Click to collapse
I have the same thing here
all sensors are broken because of SensorHub BIN FW Version: AT0199999
then i try to update firmware with *#2663# it failed.
I have the same problem with my S4 GT-I9505.
Suddenly the device do not auto-rotate, and no air gestures with gyroscope and accelerometer are working.
The SensorHubTest end with FAIL.
Mid december I got one OTA firmware update and I didn't notice any problems first.
A few days after newyear I notice that my auto-brightness adjustment did not work properly.
Can't remember if auto-rotate didn't work when I notice the auto-brightness problem.
But finally I am here because I searched for sensors problems.
I did the SensorsHub Test with *#0*# and it ends with FAIL.
It seems that there is a problem with the 4.3x firmware.
With 4.2x all was fine.
Can anybody confirm my thoughts - that the firmware is broken and not the MCU itself?
What can we try? Downgrade? I read that one was lucky with "factory reset" but it didn't helped to revive the MCU of my device.
Thanks for reading
and answering
___
DK
Hi, i am a owner of a sch-i545 phone, and i have the same problem with the phone: no response of any sensor and a fail on test (or upgrade firmware) of the sensorhub.
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Yesterday i give the phone to a technician (a close friend of another best friend), he will test the phone on this weekend to determine what is the problem to try to fix it.
When He fix this phone, i will post any news!
Regards.
remy1004 said:
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Regards.
Click to expand...
Click to collapse
Thanks for your answer. I have hope that the next firmware will fix it.
What is strange that none of any reseller/privers know this problem. It seems that also Samsung has no knowledge about this special error.
Well if the next firmware didn't fix the problem, I can replace my model with a working one, that is what the guy at the phone shop offers to me.
___
DK
Same Problem Here
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves. I have thought about this and looked around and to me it seems like there are only 3 possibilities for the problem:
1) The SensorHub BIN FW Version is out of date and needs to be updated manually (not through *#2663 as it doesn't work)
2) There is a connection issue e.g. the cable from the sensorhub to the motherboard is loose or broken
3) The sensorhub is broken (not the sensors)
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan
shadowsoulxp said:
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves.
[...]
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan
Click to expand...
Click to collapse
Thanks Dan for your reply.
I assume that your S4 shows the same behaviour as my one and the phone is still working fine.
The sensorhubtest failed and your light sensor for automatic adjusting and the sensor for turning the display are not working.
What is really strange that I went to a vodafone shop in Hamburg and ask them if there is any other one having problems with the S4.
You know the answer? They where wondering and telling me that this is wierd and they heard the first time of such an issue from me.
I showed them the device and showed them how I test the sensors. *#0*# funny they didn't know this combo
I hope that you succeed and share your knowledge,
with best regards.
___
DK

[Q] unauthorised software found by technician

hi,
i have a 3 month old samsung galaxy note 3, 4 weeks ago received this msg Error: An application has been forced to stop for an unauthorized attempt to access system in your device then a week after it started rebooting by itself, i brought it back to my service provider and they sent it away for repair, then the technician found unauthorised software on my phone, they said now its "custom" not "official", it voided my warranty and have to pay for the costs of repair, i have rang samsung as well regarding my concers, but they too doesnt seem to be so much help they said maybe an app caused this "unauthorised software" they said it rooted to my software. the funny thing is i did not root my phone or tamper it in any way?
anyone who has experienced the same thing? any thoughts? d you know any apps that can cause this problem?
cheers
I know a few years ago devs stopped using Rage because malicious hackers were putting it into apps to root phones and steal data without the phone's owner knowing. See if a factory reset works.
Sent from Spaceball One.
Have you tried Avast or Lookout to remove any malware or viruses?
Sent from my rooted Note 3 (N900T) using XDA Premium
As far as rebooting goes, did you wipe cache and perform factory reset? Because it does seem like a software problem and those should fix it.
Now for the the root itself: assuming you got your phone brand new (not some refurb or used) and not rooted it on purpose, it would be nice to find which program did it, so you could avoid it in the future. Again assuming you did not give your phone to your friends to play with it for example, I would make a list of all the programs downloaded, especially from unofficial sources (outside of Google Play) and basically look around for most likely source of your problems. The reason you should go with all this trouble is:
1. Even if fixed now, there is pretty good chance you could download this program again and it could be serious, harmful virus.
2. You could try fighting with Samsung, arguing that such and such particular program caused flag to be tripped, without your knowledge or consent and that would be Samsung fault not to properly protect the phone.
There is a big difference between somebody going to all the trouble of rooting on purpose and some virus messing your phone up.
And again all this assumes you didn't forgot to mention some important detail.
tine1224 said:
hi,
i have a 3 month old samsung galaxy note 3, 4 weeks ago received this msg Error: An application has been forced to stop for an unauthorized attempt to access system in your device then a week after it started rebooting by itself, i brought it back to my service provider and they sent it away for repair, then the technician found unauthorised software on my phone, they said now its "custom" not "official", it voided my warranty and have to pay for the costs of repair, i have rang samsung as well regarding my concers, but they too doesnt seem to be so much help they said maybe an app caused this "unauthorised software" they said it rooted to my software. the funny thing is i did not root my phone or tamper it in any way?
anyone who has experienced the same thing? any thoughts? d you know any apps that can cause this problem?
cheers
Click to expand...
Click to collapse
I actually experienced this a few days ago. I got another Note 3 on the first of this month, that was actually a first batch device and running the software that the Note 3's shipped on. It stopped working a few days later.. long story.
Anyway the replacement Note 3 I got was running a slightly newer, though not most up to date software. On the first Note 3 I went from version 1 shipping software to the latest update and there were no issues. With the second Note 3 I went from the updated software to the most up to date, and somewhere along the lines of me updating I got the error message that you are getting.
It is my belief that the update Samsung released causes this in some circumstances. An easy fix is just to do a factory data reset, worked for me and it hasn't popped up since. Samsung are completely wrong for accusing you of rooting though, I can replicate this and I have not rooted whatsoever.
hi there guys, thanks for all your reply
I definitely did not root my phone or tamper with it, I have not downloaded any other apps that are outside of google play and i have not downloaded any apps other than the common ones, (FB SKYPE ETC).
Also my phone is brand spanking new when I bought it, When it broke down I tried factory reset but nothing happened just keep on restarting..same problem
anyway, Just an update on my phone, I got it back from repair, however within minutes of getting it back, it started the same problem again,, BOOT LOOP, I havent even had a chance to download any apps, so I went back to the service provider and I told them what happened and I demanded for a new phone and a refund, the customer support guy then told me they have to escalate it first but he will note it on the ticket that i want a new phone and refund, I cant blame the guy though he is just following their protocol
Its been five days i havent heard anything from them yet, I will keep you guys updated on what happened

SM-N910F - mmc_read_failed Error

Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
The problem is "mmc_read failed" message. It seems that your internal memory got damaged. It's like a computer without a hdd. Good luck
You are fine for warranty.
popic_u said:
The problem is "mmc_read failed" message. It seems that your internal memory got damaged. It's like a computer without a hdd. Good luck
You are fine for warranty.
Click to expand...
Click to collapse
Thanks but the System Status Custom message, is that normal??
And what will they do under Warranty? that is what will they change?
dg170775 said:
Thanks but the System Status Custom message, is that normal??
And what will they do under Warranty? that is what will they change?
Click to expand...
Click to collapse
No its not normal, if you've never rooted it, it should be Official and not Custom.
You bought it from a 2nd hand or new ?
EDIT : And its the same for the "Knox 0x1(0)" wich isn't normal too, it should be on 0x0 and not 0x1.
It was bought new.. Infact I pre ordered
Sent from my Nexus 6P using Tapatalk
dg170775 said:
It was bought new.. Infact I pre ordered
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Are you really sure you've never attempted to root it or did something wich can void the knox warranty ?
KeTuRr74 said:
Are you really sure you've never attempted to root it or did something wich can void the knox warranty ?
Click to expand...
Click to collapse
No.. only thing out of the ordinary that I tried was to try Emergency Firmware recovery via KIES, but that too failed halfway, with some messages about unable to write or something
So, what do I do now? To get it back on warranty? Problem is that phone's pretty much un-usable, to even try anything at the moment.
dg170775 said:
Hi All,
Any advice would be great as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Taking a look on Reddit and you will see hundreds of comments complaining about MMC errors for Note 4. I too just got it and was pissed.
Note 4's are dropping like fly's after a year and half of use. Like Xbox and RROD.
I called Samsuck and they told be to fly a kite and wouldn't cover anything.
Call them and give them crap! Hopefully the calls will add up.
To fix, I found a broken Note 4 on eBay and swapped the working motherboard from it. If you need any help fixing it just PM.
The phone will only get worse over time.
dg170775 said:
Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Don't worry about the custom status.
Mine has started doing the same after about 14 months - freezing, restarting, switching off. I got the mmc read fail and custom status on a reboot as well (mines never seen root or a custom firmware) but if I manually boot it in to download mode , the status reads official. Try it on yours.
Apparently it's down to having a 64gb card installed when the phone fails ti boot but I can't varify that.
James.Miller said:
Don't worry about the custom status.
Mine has started doing the same after about 14 months - freezing, restarting, switching off. I got the mmc read fail and custom status on a reboot as well (mines never seen root or a custom firmware) but if I manually boot it in to download mode , the status reads official. Try it on yours.
Apparently it's down to having a 64gb card installed when the phone fails ti boot but I can't varify that.
Click to expand...
Click to collapse
You are so right.. I just checked it, and if I get into Bootloader manually I see that the SYSTEM STATUS is Official
Even the Knox Warranty line is slightly different
KNOX WARRANTY VOID: 0x1 (4)
So, I guess I'll take the trip down to Samsung Centre, and as the Engineer in the chat confirmed, they'll repair for FREE, under Warranty
Also curious if you've got your phone sorted?? and If so, what did you do?
dg170775 said:
You are so right.. I just checked it, and if I get into Bootloader manually I see that the SYSTEM STATUS is Official
Even the Knox Warranty line is slightly different
KNOX WARRANTY VOID: 0x1 (4)
So, I guess I'll take the trip down to Samsung Centre, and as the Engineer in the chat confirmed, they'll repair for FREE, under Warranty
Also curious if you've got your phone sorted?? and If so, what did you do?
Click to expand...
Click to collapse
Unfortunately no. My phone is useable but getting worse. Luckily Im only a few miles from my closest Samsung centre so I'm going to take it in on Saturday
Me too going on Saturday to the Wembley centre (my nearest)
My phone is totally unusable and only boots into the bootloader.
Sent from my Nexus 6P using Tapatalk
Ok so i thought i'd post an update for you guys:
I took my phone in to samsung in Milton Keynes on saturday. At first they were'nt sure about the phone as it had a third party battery (the original failed at 13 months) and german firmware on it (offical, was the only way to get 5.1.1 at the time..). But they eventually took it in. They were busy, which is fair enough it was a Saturday after all, but gave the german firmware as an excuse not to test it that day. The girl told me quite clearly that they would have to reflash the correct firmware before they can test it, again, fine, it was busy.
When they took the phone, they took the sim and my 64gb memory card.I questioned this at the time but i was told it was fine. so OK.
Fast forward a bit and yesterday i get the email to say its fixed. YEY. So i visited the samsung store today to pick it up, only the find the sim and card missing. The guy i dealt with said he'd seen the card when it was being repaired. it was a 64gb sandisk Sandisk ultra, so red and grey - quite distinctive. He then heads ouyt back to speak to somebody and comes back out saying "you're not going to like this, but they've been disposed of".
REALLY? YOU THREW THEM AWAY?
Then he proceeds to point to the small print stating they are not responsible for sims or cards left in the phones. FFS. I asked for them back when i handed them phone over and was told it was fine and at no point was i shown this small print OR advised that they cant take them. Anyway he himself was quite helpful so it was hard to be mad with him. He's given me the number of head office and their branch code, so im going to ring them and see what i can do.
So, at this point the phone is fixed. It needed a new mainboard as expected and a new charging board as well - didnt expect that but it could have been damaged when they took the screen off. but, i have no sim and no memory card. The card can wait - everything is backed up so ive lost nothing but the card itself but it is the principal, here. Having no sim i had to go visit the three store in the hopes that they could provide another for me. They could, luckily, and my sim was registered and up and running as soon as i inserted it and turned the phone on so at least i have a working phone. Great service from Three. Samsung/carphone warehouse...not so much.
so that's where i am. Oh and they didnt reflash the right firmware on the phone, apparently they arent even allowed to do that. So the girl i dealt with on saturday wasnt right about that either.
James.Miller said:
Ok so i thought i'd post an update for you guys:
I took my phone in to samsung in Milton Keynes on saturday. At first they were'nt sure about the phone as it had a third party battery (the original failed at 13 months) and german firmware on it (offical, was the only way to get 5.1.1 at the time..). But they eventually took it in. They were busy, which is fair enough it was a Saturday after all, but gave the german firmware as an excuse not to test it that day. The girl told me quite clearly that they would have to reflash the correct firmware before they can test it, again, fine, it was busy.
When they took the phone, they took the sim and my 64gb memory card.I questioned this at the time but i was told it was fine. so OK.
Fast forward a bit and yesterday i get the email to say its fixed. YEY. So i visited the samsung store today to pick it up, only the find the sim and card missing. The guy i dealt with said he'd seen the card when it was being repaired. it was a 64gb sandisk Sandisk ultra, so red and grey - quite distinctive. He then heads ouyt back to speak to somebody and comes back out saying "you're not going to like this, but they've been disposed of".
REALLY? YOU THREW THEM AWAY?
Then he proceeds to point to the small print stating they are not responsible for sims or cards left in the phones. FFS. I asked for them back when i handed them phone over and was told it was fine and at no point was i shown this small print OR advised that they cant take them. Anyway he himself was quite helpful so it was hard to be mad with him. He's given me the number of head office and their branch code, so im going to ring them and see what i can do.
So, at this point the phone is fixed. It needed a new mainboard as expected and a new charging board as well - didnt expect that but it could have been damaged when they took the screen off. but, i have no sim and no memory card. The card can wait - everything is backed up so ive lost nothing but the card itself but it is the principal, here. Having no sim i had to go visit the three store in the hopes that they could provide another for me. They could, luckily, and my sim was registered and up and running as soon as i inserted it and turned the phone on so at least i have a working phone. Great service from Three. Samsung/carphone warehouse...not so much.
so that's where i am. Oh and they didnt reflash the right firmware on the phone, apparently they arent even allowed to do that. So the girl i dealt with on saturday wasnt right about that either.
Click to expand...
Click to collapse
i doubt you needed a new charging usb board. Place sounds shady.
Sent from my SM-N910C using XDA-Developers mobile app
dg170775 said:
Hi All,
I have a SM-N910F that I have been using as my daily phone for about 18 months. I have NEVER ROOTED.
Recently I started encountering lags, freezes and restarts. In general, the phone became unusable.
I factory reset the phone and set the whole phone again from scratch, but in a few days I'm back where I was.
If I restart the phone, OR power down, the phone does not start. I have to pull the battery out, and re-insert for the phone to start again.
I even tried Firmware Recovery via KIES but that too failed, and after that I'm beginning to see a new variant to my problem.
Now, the phone mostly boots into Download Mode, where I see the below:
Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910F
CURRENT BINARY: Samsung Official
System Status: Custom
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (0)
I'm a little worried about the above highlighted lines, as I plan to take the Phone down to Samsung (Samsung Chat confirmed that the phone is still in Warranty).
As I have never rooted the phone, I'm quite surprised why the phone is showing System Status as Custom. Is this something to worry about, or should it be fine and considered still under warranty?
Any advice would be great, as I really need to get this phone working normal again.
Click to expand...
Click to collapse
Hi, was there a definite solution? I have the same problem.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
Ahh welcome to the club, my Note 4 got the same errors now after > 1 year. Suddenly and without me doing anything wrong.
And nothing helped to repair it, no flashing of FWs or PIT files or anything. So - I guess a new mainboard would be the only solution.
Problem is, I am also Knox 0x1 - yes, I rooted the phone, and now I am worried that I won't get it repaired by Samsung on warranty.
Which would be an utter shame, since nobody can be blaimed for the faulty mmcs except Sammy.
So I rooted my note 4 910g on MM using Twrp and SuperSU 2.74 Beta. The problem is that it has started behaving weird with random freezes and bootloops. Formatting and Reflashing PIT, ROM, etc causes it to get stuck at Android is upgrading and it goes on for like 10mins and then the cycle repeats. Is my eMMC dying? Do help if someone can help me revive my phone somehow.
I know i shouldnt be hoping for much of a solution but still if theres hope then do post a reply.
I started experiencing this issue since last week. Out of nowhere, my Note 4 started to lag and freeze. At first I thought maybe it was the battery too, so I got myself a brand new Anker Battery. And hey, nope it's not a battery issue. Then I reformatted my phone, and yes, it was still lagging and freezing.
Fast forward to this week, last night, I got the mmc_read failed message. Shoot me.
Now I've been using the Wake Lock app and it's set to Level 4 (Partial Wake Lock). It's been much better with this App running. Of course, my battery takes a hit. But at least the phone is usable, as long as I don't restart the Phone.
My gf's phone is exactly the same as mine, Note 4, and we're exactly on the same firmware version. She has no issue at all. We've switched batteries as well and her phone works fine with any battery.
I never rooted my phone, and I've been using only the original, official firmware pushed by T-mobile. My phone is running the latest firmware (EQB1) released last month. The problem didn't start right after my phone was updated. Only since last week.
Now, I've been scouring the Internet and many say this is a hardware issue, but some say too that this is probably caused by the firmware. Does anyone now know better if this is a hardware or software issue?
I was going to get myself another Note 4 but then if this is a firmware issue, it could happen too to a new Note 4. If this is a hardware issue, then a new Note 4 may not get this problem.
There's also a conspiracy theory saying that Samsung purposely did this so as to force all Note 4 users to upgrade their phones. If this is a firmware issue, can we file a class suit? Sigh.
UPDATE 1:
I just came back from the Samsung Experience Center. I also talked with Samsung, T-mobile over the Phone today.
So basically, from what the guy over at the Samsung Experience Center told me, a few months ago, many Note 4 Sprint users had this exact same issue. Basically the firmware update caused the phone to malfunction. In the end Samsung replaced all the affected phones. I went there, talked to him, and initially I wanted him to reflash my phone but he then told me that this issue was basically a faulty firmware. Reflashing wouldn't really help because the firmware itself is faulty. The firmware could have affected (damaged) the hardware. That this exact same issue has happened in the past with Sprint users.
I then called Samsung hotline up and talked with, fortunately, a friendly and helpful rep who was willing to document everything and escalate the issue on my behalf. She told me that she would call me back in a few days to update me on how the case is going.
At this point, I'll just have to wait and see.
UPDATE 2:
And apparently I just learned that Note 4 in Europe and Sprint here in the US just received a latest firmware update around 300-400mb in size.
"The firmware update description reveals that it brings better stability and performance as well as optimizations for improving battery efficiency. This Galaxy Note 4 update also comes with the March security patch that has 73 fixes for Android OS vulnerabilities and fixes for a dozen vulnerabilities that Samsung found in its own software."
Fingers-crossed, hopefully this update will soon come to T-mobile and other carriers and fix our issue.
T-mobile recently released a firmware update for Galaxy Note 4 (EQC1): https://support.t-mobile.com/docs/DOC-28899
I'm wondering if anyone has installed this and can confirm if this firmware update has fixed the mmc_read failed issue along with the constant lagging/freezing problem?

S7 Edge - Freezing and random rebooting

Hey all,
I have a galaxy s7 edge that's 2 months old. It's randomly freezing which is forcing me to do a hard reset or rebooting. I have done a factory restart by the settings, I have done a factory restart by holding the power, home and volume up key and lastly I have done a smart switch emergency thingy-me-bob.
The phone has never been rooted or messed around with in that matter and was working flawlessly up until this point. It's running all the latest updates you can get OTA - My next step tomorrow is to go into store for them to essentially repeat what I have done for several months...wondering if anyone here has any ideas of anything else I could try? Hoping it isn't a hardware defect.
Cheers,
Tom
Had exactly the same issue. Ran it in safe mode and it still froze. Factory reset - still the same problem. Sent it off to Samsung and got it back a few days ago along with the usual note explaining that the fault had been identified, latest software had been installed and it had passed through quality control. Went through setup and within an hour it was freezing again. Not convinced Samsung did anything other than re-flash the firmware and send it back. I'm guessing that this is a hardware issue, as I have read many posts with people experiencing the same issue. It's going back tomorrow so they can try again, with a note in the box, politely asking them to dig a little deeper....
Did another factory reset and it's frozen while on the always on display svtren. Think I'll be leaving a note asking them to do a physical hardware check!
You have latest software?
As per the original post, everything is running on latest.
Any way, visited the 'Geek squad' who informed me that I had done a factory reset wrong *sigh* restarted it infront of me and would you believe it! crashed. They're now sending it to Samsung to look at who I assume will just flash it again.
Very very disappointed with the edge, compared to my OP3T it's so sluggish.
had the same problem. had to send mine to samsung. there was something wrong with the partitioning i think but in some way odin couldn't fix
Fingers crossed it's something like that is wrong with mine!
I have exactly the same problem.
I'm in aus, and bought the phone from HK, so I'm a bit reluctant to send it back to HK/China.
I've done everything... but still the same.
rockuman_ex said:
I have exactly the same problem.
I'm in aus, and bought the phone from HK, so I'm a bit reluctant to send it back to HK/China.
I've done everything... but still the same.
Click to expand...
Click to collapse
From what I have read, it sounds like a hardware issue. The guy are the store was an utter moron but he did say the harder it is to the fix the more likely they are to just give me a new phone. Once i get it back ill share what they've done and see if it can help fix your issue.
Mine does reboot from time to time. Once a day, once a week...
Sometimes reboots when it stands alone on charging, sometimes in my pocket. I just realizes when my smartwatch vibrates to advert lost bluetooth conection.
Lastest firmware. I´ll probably will send to warranty.
I just recently got the S7 Edge. Great phone I just hates when it does that.

Categories

Resources