Related
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
I have flashed my three mobile to the latest .184 release, and just before doing this I used flashtools to make a backup. Somewhat stupidly I went ahead and flashed without checking if my backup actually works, I have checked since and it just tells me to unplug and turn on debugging etc (they are both on).
Has anybody got an original three firmware they can upload in case I need it - since doing this I have also noticed problems with wifi tethering so it might need sending back
If no one can help (if anyone can it would still be appreciated), can anyone tell me if it will cause me problems getting my phone repaired.
Although I originally flashed the .184 update uploaded here I have since run a SEUS reinstall so technically the firmware is 100% official SE generic firmware. Will this mean it will be fixed as all they will know is that it is their software on.
I had some worrying news when I asked in a carphone warehouse repair center today, the engineer (I have doubts they actually hire engineers) told me if he finds I have changed the software he is required to inform SE themselves the phone details and have the warranty voided. This was after actually telling him that I had changed it though, and he might have been thinking custom - I also didn't explain the SEUS update that means it is completely official.
Anyone any advice? I definitely have a hardware problem that needs fixing so I am desperate now.
from what I remember the only difference was the bootscreen and the three app and a couple of games I doubt you will have any major problems. I'm pretty sure the main thing they didn't like with debranded firmware was you could set it to just use the Orange network which cost them more money, but now they are 3G only...
With WIFI tethering try changing the name of the hotspot I couldn't get it to connect at all, changed the name and it worked fine.
Thanks for the suggestion, I just tried renaming but it has the same problem. I can connect for 2 minutes then it stops working and needs turning off and on. It is identicle no matter what I do; after using SEUS or restaring the phone. I am pretty sure it is a hardware problem now (it seems unlikely to be software otherwise more people would have this exact problem). I'm also having problem connecting to wifi while out that I didn't notice untill I started using it more.
Ill give it a couple of days to see if anyone gets hold of the three firmware just in case (I don't want to give them a reason to try and screw me around, I like the plan and unlimited internet but their CS is abysmal sometimes), I will just go for it and send it back if not.
How long have you had the phone? I got mine switched over about a week after I got it because the camera had a problem. I have actually in general had some great customer service from them over the last couple of years they even just refunded me £40 of internet data usage because they did not explain it to me properly (One plan didn't start for a month apparently :/).
Good luck though hopefully they will just swap it over if they have some in stock. Make sure you take everything you got back in order to get an exchange.
Just over a week - got it on the 26th. The problem is I upgraded over the phone and had some problems then with overcharging, this is when I found out that the shops don't like dealing with phone customers and would not help me at all. Maybe they will be more accommodating for a hardware problem - or maybe if I refuse to leave until they behave like I am the one paying £40 a month to the company whos shop I am standing in I will get some service (Im actually getting prematurely angry lol).
Ill give the store a go first if I can't find the fw soon.
Thanks,
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
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?
My camera app(moto camera) has stopped working, it says: camera error, please restart camera(log attached).
I can still access my camera through google camera and other apps.
I checked about this error on Lenovo forums, Lenovo had to replace people's phone.
Im using BeanStalk 7.1 custom ROM with unlocked bootloader, is there any way I can claim my warranty to get a replacement and shove it in Lenovo's face.
Why even shove it in Lenovo's face? Okay, since your bootloader is unlocked and your warranty is void, all you can do now is buy another Moto G4 Plus. Can't claim back your warranty anymore. Sorry.
thebeonkid said:
My camera app(moto camera) has stopped working, it says: camera error, please restart camera(log attached).
I can still access my camera through google camera and other apps.
I checked about this error on Lenovo forums, Lenovo had to replace people's phone.
Im using BeanStalk 7.1 custom ROM with unlocked bootloader, is there any way I can claim my warranty to get a replacement and shove it in Lenovo's face.
Click to expand...
Click to collapse
i have 2 scenarios about this problem...
1-- On my another phone (not g4+),
Had same problem long ago: it usually shown something: "Camera error: couldn't connect to camera"
And it got fixed later on latest build...
You can now try first clear data/cache and give all permissions to camera... And then go for different ROM..
2-- this is about my brother's phone issue, this problem happened when phone fall down from height and camera hardware got damaged... Not 100% sure about this...
thebeonkid said:
My camera app(moto camera) has stopped working, it says: camera error, please restart camera(log attached).
I can still access my camera through google camera and other apps.
I checked about this error on Lenovo forums, Lenovo had to replace people's phone.
Im using BeanStalk 7.1 custom ROM with unlocked bootloader, is there any way I can claim my warranty to get a replacement and shove it in Lenovo's face.
Click to expand...
Click to collapse
I had the same issue when my mobile fell in water the camera would force close and finger print scanner option was also gone I didn't know what to do i just left it like that for some time and the issues was solved automatically funny I don't know how.
In EU is illegal to deny hardware warranty for software issues like unlocking the bootloader.
Unlocking is a feature advertised by manufacturer for the device, boost their sales and the code is provided by them, is not hacked illegally.
In US they (Moto) didn't get challenged in court yet but I bet they would lose.
Now, if the phone has fall or water damage (there are sensors inside that can prove that) then obviously they are off the hook for warranty.
thebeonkid said:
My camera app(moto camera) has stopped working, it says: camera error, please restart camera(log attached).
I can still access my camera through google camera and other apps.
I checked about this error on Lenovo forums, Lenovo had to replace people's phone.
Im using BeanStalk 7.1 custom ROM with unlocked bootloader, is there any way I can claim my warranty to get a replacement and shove it in Lenovo's face.
Click to expand...
Click to collapse
Its depend on your luck and the service center, if the people in service center are dumb they will not check whether bootloader is unlock or not.
Same thing happen to me when i got screen burn ,my phone was unlocked and rooted. I was confused whether I can claim warranty or not.So i re-lock my boot-loader by this method http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 then I went to service center ,funny thing is that I have to explain what is screen burn to them , then they said they will replace the display then I got my phone back in 40 days,
So i will recommend you to relock your bootloader and go to service center.
I was able to get my battery replaced under warranty after unlocking my bootloader for free. All I did was reload stock firmware and recovery using fastboot. Did the online repair and sent it out. Pestered them online on chat like every day after it was received about a status and it got fixed. My G3 is also unlocked bootloader but still shows valid warranty online.
Hi, my moto g4 plus device tells yhat "camera is busy" and it tells to restart the device. Even i restarted and even i flashed a stock rom on my device. But same issue. The flashlight option is missing from my phone(from the notification bar settings).... Even tried with rather third party camera app. Same issue... Can anyone suggest me for this issue???