[Q] unauthorised software found by technician - Galaxy Note 3 Q&A, Help & Troubleshooting

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

Related

i337M Abrupt Signal Loss

Hi everyone,
So about five days ago I was in the middle of using my Galaxy S4 (I think I was playing a game or something) and all of the sudden my cellular signal dropped out completely—from 4 bars to zero with a little X in it. There it's remained ever since.
My first thought was that I ought to reboot the thing and see if that would solve anything. The answer was no.
My second thought was that maybe my contract was up (as that was due to happen this month), and rather than auto-renewing, they kicked me off. Weird, but possible. But that's not it: I phoned up my provider and they said that all systems are go, there are no outages, your account is active for a week still, and even past that contract expiry I'll just get bumped to month-to-month and never experience a blip in service. So that's not it.
So then I put my SIM in another unlocked phone, and lo-and-behold, it connects just fine. So clearly the problem is with my phone.
My i337M is running Liquid Smooth 2.9 and KToonSez' kernel. I decided to make a nandroid and flash back to stock ROM/kernel. Still I could not connect to the network.
I can only think of two potential problems. First, I unlocked the phone myself via FastGSM.com's tethered USB method. It was a Bell-locked phone, and I'm on Rogers. This was accomplished back in July, and since then, there haven't been any issues to speak of (i.e., the unlock worked flawlessly). I tried to see if those unlocks ever expire, and couldn't find any reason why they ought to. I personally don't think it's that, but I mention it out of interest in being thorough.
Second, I messed around with my phones NVData a few weeks back to enable the AWS network via this method. I didn't experience any signal problems after doing so. Again I mention this out of interests of being thorough. Could that have had something to do with it? I suppose I could try flashing back my original NVData, but honestly I don't see why that would suddenly kick in now since I did it weeks ago originally.
Any thoughts? This is really bizarre, and it sucks being without connection.
I was also thinking of flashing back to stock and going to a Bell shop to see what happens when I put a tester SIM in.
It sounds to me like it's hardware related. Don't see anything you've done that would have caused it. I'd flash back to stock and if it still persists I'd file a warranty claim.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi, thanks for your reply.
An additional thought's occurred to me: I lost signal at or about the same day I setup Android Device Manager to allow for remote lock/wipe directly from Google. That couldn't possibly be responsible for signal loss, could it...?
Currently flashing back to stock, and I'll unroot/restore kernel/restore NVData and make it look factory, and see what the store says about it. Hopefully I don't have to pay for another unlock at some point.
Okay, this is very messed up. Nobody has any idea why my phone isn't getting signal. I can scan for networks and everything shows up, but in any case with any SIM it says "unable to connect to network". It doesn't matter what ROM I'm on. I flashed back to stock and updated to latest using KIES of all things, which found a firmware/modem/baseband update, and still no dice. I don't know what to do with this thing except take it to an unlocking store that might be able to figure something out for me, but it'll cost me. This is messed, I've never had to get someone else to look at my tech for me.
Okay, so the situation is that it most probably is a hardware failure related to the radio.
I am a Rogers customer who bought the phone from a guy from CraigsList who apparently got it from Bell. I went into Bell and explained the situation, and they scanned the IMEI and printed me out a proof of purchase of the guy's name and told me I should take that to the Bell service centre, and it doesn't matter if I'm not the guy. I also had them check to see if he reported the phone stolen; it turns out he did not—though it should be known that if he had done so, then that could have very well been the reason I wasn't getting signal from anyone, as all providers across Canada apparently share their blacklists with one another now (including the little guys like Wind/Mobilicity).
So now I am in the process of making it look like it's never ever been hacked before: I shall restore my NVData, unroot, and update everything using KIES, and then perform a factory data reset. I'm also on the hunt to figure out what the heck the "flash counter" is and whether or not I need to reset that, but perhaps since mine is the i337M Canadian variant, I don't need to worry about that. (Any advice on restoring my phone to factory condition would be welcome, thanks.)
Edit: Figured out TriangleAway and everything associated. I'm all stock now and ready to bring it back to the factory.
MAJOR UPDATE: PROBLEM IDENTIFIED
So I got my phone back from the factory today. They reported that everything is 100% a-ok on the hardware/software side of things. The radio IC is NOT blown as was suspected.
You know what they said? The problem is on the network. I have a story to tell that I think people should hear, as I've learned something very valuable today and people need to learn this lest they get conned themselves.
Today I phoned in Rogers again, armed with new information, to ask what's up. They ran the IMEI number, and this time... it's come up on the blacklist.
It wasn't there last week. In fact, it wasn't even there an hour ago. It actually only appeared there as the clock ticked past midnight Eastern time... as that is EXACTLY 90 days from when the phone was reported missing. It took them a long time to track down this information.
To reiterate, I did not steal the phone. I bought it from a guy on Craigslist who had it brand new in box with the screen-protector sticker still on the front of it. I checked it out, tried it, and unlocked it myself and have been using it since July without issue, until a week ago.
There is the trouble of, why now? Why only now does the IMEI come up blocked? What the senior rep at Rogers thinks happened was that the guy had it delivered to his house, didn't sign for it, kept it in box, reported it as "undelivered", and flipped it to me for cash. Insurance has meanwhile hooked him up with a new phone, and the factory kept my phone in the "we're looking for it" pile for the requisite 90 days, after which they officially publish its IMEI as "blacklisted". That would explain why it worked for a while but doesn't now; and this 90-day TO THE DAY period is the same for Rogers as it is for AT&T apparently (which is where the rep used to work for 10+ years).
I am in possession of stolen property. I've little hope of recuperating my losses. I've been advised to file a police report, and I think I will actually, given that I've got a receipt with the "anonymous" guy from Craigslist's name on it which I had printed out from Bell after they scanned the IMEI number for my factory warranty receipt. This phone will officially never work in Canada, as there is no way for it to be removed from the blacklist. I've been very unfortunate in this case, and it's a real shame.
People should take note: If buying a phone, ALWAYS do it in-store and have the IMEI number run first to check and see if it's on the blacklist. Next, have the phone transferred into your name so that the IMEI and you are officially linked, and the guy can't report his gear stolen or lost. That should suffice in most cases... except in the case of insurance fraud, which is my case, where there is a 90-day delay period in the IMEI number being added to the blacklist (which is why it didn't come up on the blacklist last week when I had the Bell rep run it in-store for me). Another point of interest is that in my case, I found it was possible to lose service BEFORE the number is on the blacklist—assuming the Bell guy didn't run the number wrong last week.
So f**k me. All I can do is try to hack the number, I guess, or find a way to spoof the IMEI.
Edit: Unf***ing believeable—I somehow reenabled data and texting by messing around with QPST. Calls still not happening, though.

[Q] Galaxy S4 Sensor issues

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?

[Q] How many of you returned your Note 3 and got a problem free replacement?

My note 3 has had lots of problems. Reboots and crashed quite frequently. After the firmware update it seemed better for a few days but now its back to freezing and rebooting all the time.
Did anyone out there have these problems and then exchanged your Note 3 for a new one that was trouble free?
Did your replacement have all the same problems?
I don't know if I should try to get my money back and get a different phone. This is very frustrating.
My One was having a problem of power switch,replacement came &working fine I love this phone,first one was made in Vietnam but replacement came Made in Korea...
If you haven't tried a factory reset (back things up) give it a shot. Cleared up my final issue. I had my replacement on order and it arrives today. Won't be needing it.
I did a factory reset. During the initial setup after the factory reset the phone restarted once in the middle of me typing in my gmail account info.
Will nothing help Lord...nothing?
:crying:
Oh and it says: (this is directly after a factory reset..nothing has been installed yet..no apps...nothing)
Security Information
An application attempted to access system......
Replacement
Snugglesthemonkey said:
I did a factory reset. During the initial setup after the factory reset the phone restarted once in the middle of me typing in my gmail account info.
Will nothing help Lord...nothing?
:crying:
Oh and it says: (this is directly after a factory reset..nothing has been installed yet..no apps...nothing)
Security Information
An application attempted to access system......
Click to expand...
Click to collapse
hi,
I took my phone back to Tmobile after 6 days due to issues. They gave me no problems.
This is exactly the same issue I have been having with my Note 3. Freezing up and constant restarting. It's been factory reset twice and even flashed. Nothing has worked. Can someone please help? I desperately need a replacement because I can't even use it for even a few seconds before it freezes up and goes into a reboot loop. I still have several months left on the one-year warranty. Can someone tell me how I can get a replacement from Vietnam? The website is entirely in Vietnamese and no other Samsung center will help. I've tried US, Australia and our own local center (Trinidad and Tobago), and even Amazon and the seller I bought it from. I'm now thinking of trying the UK. So far no one wants to help me and I am now at a loss. I just want to know HOW to communicate with the Vietnam manufacturers to get a replacement. I'm desperate.
See your identical post .

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 SM-G935FD always Auto Restarting[urgent help needed]

In big problem.
My S7 edge is now automatically restating in every 10seconds.Practical I cant use it. I booted in same mode still restarting. I flashed stock Nougat and marshmallow stock ROMs still its restarting. Even in recovery screen(TWRP or Default) its getting stuck and restarting.
Only in Download mode it is not restating.
Please advice any ideas, since I am already on void warranty my $500+ phone is simply got useless.
Thanks in Advance
Tony Tomson
Maybe your power button is jammed?
When i checked, Power button is pressing and releasing. Power button is functioning actually, I can enter to Recovery, Download Mod and I can lock screen using power button. Or any other method to verified power button?
tonytomson said:
In big problem.
My S7 edge is now automatically restating in every 10seconds.Practical I cant use it. I booted in same mode still restarting. I flashed stock Nougat and marshmallow stock ROMs still its restarting. Even in recovery screen(TWRP or Default) its getting stuck and restarting.
Only in Download mode it is not restating.
Please advice any ideas, since I am already on void warranty my $500+ phone is simply got useless.
Thanks in Advance
Tony Tomson
Click to expand...
Click to collapse
My S7 Edge did the same thing I reset it to factory settings empyrion I went in and did safe mode I tried resetting it and not installing any applications it seems that my ROM had gotten corrupted or something for no reason there was definitely a hardware problem. Never could figure out what it was I had insurance with Verizon and because I had cracked the screen barely three months prior before the problem began they stuck me with the $200 deductible to get it replaced. if you got insurance you will probably have to send it in but what mine was doing was it started just lagging then it just got to wear it wouldn't do anything it would freeze up and just reset and it would continually do that even when no programs installed except the factory setting and it would reset until the battery died I don't know that's exactly what you're experiencing but mine was in a constant Loop of reset it didn't get water damaged or anything the only thing I can figure is it had the 7.0 nougat update when it began doing this hope that helps you out sorry for the run on I'm talk texting I'm with the S8 now I haven't had any problems I'm just wondering if they've actually supported that I hadn't heard any other people having the same problems but mine surely did right after I got the update Android 7.0 on Verizon good luck bud
Sent from my SM-G950U using Tapatalk
YES!!!..........Its exactly what you described. It started in the beginning like get slow>freeze with in 1 min>restart......But now after installing stock ROM back, its now directly restarting like a loop....Only difference we could use/see mobile for 10-20sec.....with in that time, it will restart again.
Unfortunately I dont have insurance.
If its hardware problem, samsung will rectify with accepting payment??
My S7 Edge did the same thing recently....no fix but to send for replacement. I reset it to factory settings. I went in and did safe mode. I tried resetting it and not installing any google apps. Seems that my ROM had gotten corrupted or something for no reason there was definitely a hardware problem or corrupted data in the OS or ROM. Never could figure out what it was. I had insurance with Asurion and Verizon but because I had barely cracked the outer screen 3 months prior (digitizer and oled where fine....was just outter guarilla glass which people complain about due to having no tempered glass to fit it correctly. So i had gotten the skin type scratch protector and one 2 foot drop onto asphault not even 2 weeks after receiving the object...pebble cracked it on the edge. Three months the problem began with freezing amd resetting finally b4 giving up and making a claim. ASURION stuck me with the $200 deductible to get it replaced because they said the drop/crack caused the malfunction though it worked perfectly for the 3 months...even had full sensitivity at the cracked area. If you got insurance, i imagine you will have to replace it. I did ad i saw no other choice and it ticked me off them sticking me with the deductible of full 200. Leave the cracked screen on hell. Just fix what they didnt fix when they got it to refurbish it initially. Have gotten at least 5 poorly refurbed phones that didnt last a year that was passed off as GOOD AD NEW. Mine started lagging then it just got to were it wouldn't do anything but cycle reboots. It would freeze up and just reset and it would continually do that even with no google or verizon account setup or apps. Only installed the factory settings which included the preinstalled bloatware. Phone would boot, then reset, boot and would reset again...continuous loop until the battery would die.
I don't know if that's exactly what you're experiencing but mine was in a constant Loop of reset. T here was no water damaged or anything other than a drop months earlier, an update, and i had recently moved some apps to the ext Sd card (which that should have been resolved at factory reset) cause i removed the micro sd card incase it was conflicting in someway from priorly having apps installed onto it.. the only thing I can figure is it had the 7.0 nougat update when it began doing this. Hope that helps you out. Sorry for the run-on sentences. I tried clearing up my grammar and punctuation...at least look a bit edumacated.? I had been talk texting.
Currently, I'm with the S8 now. I haven't had any problems so far. Dont like the default samsung voice input that it resets to constantly. But i am sure the S8 has more support for the new OS THAN DID s7. Phone companies are notorious to slack on support for models even 1 year old. Minimal support at best. You might get 2 Android OS updates. Not likely though. Pushing the new big thing each year and forget about the loyal customers that have chosen to spend out money with said co. rather than their rival. After the N7 hand grenades. Time that Samsung start supporting their phones updates a bit better. I'm really of the opinion that sufficient testing and support wasnt given towards the s7 the 7.0 OS. New OS updates Always buggie when first released. I hadn't heard any other people having the same problems as we did but i havent looked. Verizon claims no issues from the update. I question all retailers truthfulness on such issues. It a business and i see hoe much they mark up their retail products. 5 time the cost of internet prices many times.
Do report back pleas e. Sorry so winded....wanted to give all my thoughts and details of my exact experience. Hope you can fix it cheaper than i did. The s8 is sure to have more samsung support for a longer time. Nag them if you are settling with insurance. They can give you a new phone vs. Refurbed if they want to make u satisfied.
Good luck brother. Many blessings.
Sent from my SM-G950U using Tapatalk......tattd
Sent from my SM-G950U using Tapatalk

Categories

Resources