Simply stated, I am seeking a way to make this device a dependable phone, as I am stuck with it at the time being. I loved my original GNex, but what Verizon keeps sending me is garbage.
I have had quite a strand of bad luck with this device. I am averaging a warranty phone about once every six weeks. I have actually tried talking to Verizon about exchanging the phone for one of equal or comparable value, and they won't do anything. I am convinced that these certified like new devices are junk.
Issues that keep causing me to warranty the phone are:
- Charging Issues
The phone quits accepting a charge. I have replaced the battery.
- Phone Locking Up
Recently, while using apps, the phone has developed a habit of where it locks up, and the quits accepting input. It's like it goes to sleep, but it doesn't wake up. The only way to get it to function is to remove and reinsert the battery.
- Phone turning off on its own
Self Explanatory
- Radio Failure within the device
I'm not against rooting the device, I have kept them stock, and wouldn't know what to get, I just want to do something that will make this a dependable device and possibly solve any problems I may be having. They seem to be reoccurring problems with each handset they send me Any tips would be greatly appreciated as I have another one due to arrive tomorrow!
I don't think these refurbished headsets go through much, if any, testing before they are re-issued. What I would suggest is to begin with flashing a factory android image via the boot loader. There are plenty of guides to doing this. This step will ensure that any problems that you may be experiencing are not software related. A stock image reflag should do the job for the most part, but if you find yourself looking for more you can flash an alternate ROM, these won't solve any issues that you may still experience in a stock ROM however.
A friend recently sent me her "retired" Galaxy Note II. She replaced it because at some point the screen stopped turning on altogether, but she still wanted me to see if I can salvage it somehow. I've tried, with no luck, and searches on the topic don't seem to suggest any solutions other than the fact that it may be a hardware issue. While I can accept this possibility, I'm really hoping that it is not the case because at this point I don't think it would be worth investing the time and money to buy the parts, learn how to replace them, and attempt it. If anyone has any ideas I'd be very grateful. Here are the symptoms:
The display NEVER turns on. It is in a constant state of pitch black.
The sounds are working fine. When I get an email, for example, it notifies me.
The hardware button works
The software buttons do not work
Upon connecting the device to a monitor, keyboard and mouse, the monitor works, however the keyboard and mouse do not. (I use the same monitor, keyboard and mouse with my Galaxy S4 and they all work fine.)
Touch interaction with the screen is working properly. Using the monitor, I am able to use the device, but it is very tricky, as it is simply a matter of trial and error. I tap on a black screen and have to look on the monitor to see if I hit my target.
The device is on the stock TouchWiz that came with it, and is not rooted. Since I am pretty sure that doing any mods without a working display would be more difficult than I could tolerate, I opted to take an OTA instead, despite the fact that it may make rooting and flashing ROM's impossible in the future. I hope I didn't screw myself by doing that but I had to make an executive decision. Here is what I've tried so far:
Factory reset
Update to the latest software (Android 4.3)
Pulled battery, held power button for 10 seconds while battery was out, replaced battery and powered device on.
I'd greatly appreciate any suggestions. Ideally, here is what I'd like to happen: get the display to turn on and restore functionality to the software buttons. This may not be possible without replacing some hardware components, which as I mentioned is not an option, but if it is I'd really like to give it a shot. Thanks in advance for any suggestions.
My initial guess would be a digitizer failure...
A phone drop or water damage can easily render a phone dead...
You have the option of replacing the screen and digitizer at a cost of about $225.00 for the needed parts...but it's still no guarantee that the fix would be 100% successful...
My honest opinion is this...
Given the unknown history of the device...you are taking an expensive chance in attempting a repair...
And given the age of the device....the repair if performed by a qualified repair service would push the cost very near to the overall value of the device...
For the same dollars spent...you can obtain any number of working devices and save yourself the hassle...and the unknowns associated with a repair that will likely work...but again may not...
You are of course free to attempt the repair...but....
The skill level needed to perform a "proper" repair of the device is high...and you would need to study up on the process extensively before cracking open that case...
If I were in your situation...the choice would be to sell the device for parts....and put that cash back into a working device...
Others will chime in I'm sure with their recommendations....but I would choose to move on...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
My initial guess would be a digitizer failure...
A phone drop or water damage can easily render a phone dead...
You have the option of replacing the screen and digitizer at a cost of about $225.00 for the needed parts...but it's still no guarantee that the fix would be 100% successful...
My honest opinion is this...
Given the unknown history of the device...you are taking an expensive chance in attempting a repair...
And given the age of the device....the repair if performed by a qualified repair service would push the cost very near to the overall value of the device...
For the same dollars spent...you can obtain any number of working devices and save yourself the hassle...and the unknowns associated with a repair that will likely work...but again may not...
You are of course free to attempt the repair...but....
The skill level needed to perform a "proper" repair of the device is high...and you would need to study up on the process extensively before cracking open that case...
If I were in your situation...the choice would be to sell the device for parts....and put that cash back into a working device...
Others will chime in I'm sure with their recommendations....but I would choose to move on...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
Thanks for the reply, and sorry I didn't see it sooner (I always forget to subscribe to threads). I figured this was probably not a fixable problem (at least not easily/economically fixable). But I wanted to see if there were any quick fixes I could try, and it sounds like there aren't. With that said, if anyone does want it for parts I'd let it go for a reasonable price (considering the damage and lack of functionality) through Swappa. (Sorry if I'm not supposed to make these kinds of offers here, if that is the case I'll gladly remove it.)
Hello everyone! This is my first thread and I know it's the right site to ask this. (sorry for my english)
I bought this "suspicious" i9190 in Budapest 2 years ago. Since then it has been impossible to use it regulary.
Constant rebooting and freezes are part of its daily routine. As well as stopped apps and processes messages in a ridiculous way.
I have tried millions of ROMs, officials and customs, all kind of wipes and restores. I have even tried the eMMC brickbug apps looking for damaged chips or internal memory: Nothing, the phone is perfectly fine.
But here are some facts that may be relevant to find the problem:
- The phone came with the IMEI number scrached in the back of the battery.
- I've been using the phone for hours and hours perfectly fine as long as no update is performed and the Sync option is off.
- Doing the above I have even downloaded and used some little apps with no problems.
- When the major apps are installed, like Facebook and Instagram the phone begins to die, popping more and more "stoppped working" errors.
- The processes that fail the most are the google type but, in general, every single existing process has failed in this 2 years.
- I have noticed that when you start the phone for the first time after a wipe or a new ROM, it is better to create a new google account than using an existing one because the existing one, I think, will start updating everything while the new one will not. Anyway, using a new google account collapses the phone sooner or later.
Sorry for the long post, fellas. But I wanted to give you all the possible info I have about this phone.
Hoping for you can help me fix this issue... Have a good day.
Galaxy S4 mini GT-I9190
I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"
IronRoo said:
I'd guess at a hardware issue in the radio and related circuitry as you seem to get the issues when apps that send/receive data frequently are in use. Though it could be anything. You probably need to get it checked by an authorised Samsung repair centre ......... if your phone is not too "suspicious!"
Click to expand...
Click to collapse
Thanks for your reply! Do you have an idea why they scratched the IMEI number? Maybe that could take me to where the exact problem is. Here is a photo of the back
http :// imgur. com/Sa0ptSm
Sorry for the link, my account still cannot post outside links
I was going to say they scratched the IMEI number probably because it was stolen so that it could not be tracked, but it is quite easy to see the number so that is probably not the reason. One place I used to work at the test department used to scratch the bar codes on faulty PCB's so that they cannot be scanned back into the system by mistake (if the fault tag comes off, etc) as that computer system did not prevent scrapped boards from being re-entered. So I would guess this may be the case with your phone, but of course we can't know for certain! But based on this and all tests of different ROMs etc you did I suspect it is quite likely the explanation.
What I would do is look for the same model that has a cracked screen on ebay etc so it's cheap to buy then swap the PCB's from the cracked phone to your good screen (swap everything to prevent the possibility of the boards not working due to different revision numbers, as has been reported when replacing the power boards on our phone). You can also buy a repair kit for a few dollars on ebay with screwdrivers, pry tool etc
http://www.ebay.com/itm/10-In1-Repa...et-for-Mobile-Phone-iPhone-6-5s-/281869038536
If the PCB on your phone was scratched to show it was faulty then taking to a repair shop is probably a waste of money, unless then run an assessment for free before they repair it.
Hope you can fix it for a few dollars!
not sure if this helps but that I actually managed read off the IMEI code correctly and it turns out its a turkish registered phone, I can PM you IMEI code if you want, also its not reported stolen (but i am guessing its most likely is), anyways thats all I was here to say, good luck.
Lemme start off by saying I've got a SM-N910P that's getting the fabled eMMC_write failed error.
Because of its intermittent behavior, it REALLY seems possible it's due to a corrupt file or sector of memory somewhere. Can't say for sure but I'd love to try everything I can, which leads us to...
I know of these portions of software that can be flashed(?) onto a phone:
ROM
modem
kernel
bootloader
EFS?
Pit (re-partition)
Am I missing anything at all? And most importantly... I know (think) these items, if flashed, have to match up to each other. Like, bootloaders matching roms matching kernels, etc... the hard part is figuring out what matches what in an attempt to flash and reformat and wipe as much as possible. It seems to vary what a ROM comes with- some with, some without bootloaders or kernels.... I dunno how to tell for sure??
Anyone got any insight on how to collect and complete these things? Pick any rom, doesn't matter... it's on PK1 at the moment, but had taken the official PL1 update before i flashed PK1 back onto it. It will boot sometimes, but always eventually crashes. If it has to be rolled back to LP, it is what it is lol.
I'm aware of wake-lock bandaid, and other odd suggestions that do not fix this issue. Cleaning house as much as possible just might work- and if it does, someone could be a hero. There's HUNDREDS of devices suffering out there after MM came out.
I may have chosen a bad title LOL. If anyone reads this.... A huge help would be just to know for certain all the components and what they're called that I can completely wipe and replace. If it helps, I have 3 more of these phones exactly same model and carrier that are active use phones at my disposal (sorta...my wife, my brother....lol).
If I understand correctly, there's an EFS ...partition?...that I must preserve? Kinda like the phone's identity, but complicated. If I could back that up, how much closer could I get to a full, complete, 100% wipe of the phone's internal memory? If ya see where I'm going with this....I believe there's data stuck somewhere that's corrupt and causing this eMMC issue. Lemme know if I'm just completely ignorant and wrong tho lol.
Thx for looking, anyone.
There's lots of theories of what's happening, that's true. But I think evidence points directly to the eMMC.
You can find how to videos on YouTube for replacing eMMC chip on main board or just main board replacement. There are many places on Amazon and eBay to buy main board replacement for Note 4.
I asked my local uBreakItiFixIt for an estimate on main board replacement. They don't stock eMMC or main board but gave me a $10 labor quote for board replacement that I would bring in myself.
There was a poster that was trying to localize the issue through a developer online. Sent his phone to him to flash the recovery, claiming the partition was corrupt but he got his phone back with same issue. I do believe many happy ending threads in our forum are incomplete.
There was a thread in another site that had numerous phones exhibiting eMMC failure that were Odin flashed with PIT loaded, repartition with PIT, nand erase all and stock tar loaded all at once and I don't think there was a happy ending anywhere to be found where reports after flash were followed up.
That suggests it's not corruption but component failure. And also suggests this shouldn't be happening with normal flash or update. I think the update places a burden on weak components is where the correlation to update is coming from.
From my own experience, only few issues have happened that a reboot wouldn't fix. Twice over the entire life of my phone- picked up on launch day as a pre-order and kept in continual service since-, I've had to Odin TWRP because the phone wouldn't boot into recovery from system boot, when commanded.
The times I've flashed ROM again or wiped cache and dalvik-cache and rebooted were mostly my doing that caused unexpected results. I also crashed marshmallow twice early on while modifying stock and wasn't sure how I did that but all in all, I think I'm to blame for mistakes rather than the phone or OS updates. My phone has remained healthy but I've also replaced the battery frequently.
How's your battery? If you can Odin stock tar successfully, I'd try it again but only with a fresh battery. I'm suspicious of replacement battery's shelf life if ordering a replacement battery has it arriving with very low capacity. Research has shown batteries last longer for users when they're stored at 50% capacity and maintained at that capacity. But they're low drain batteries but imagine they could have made in bulk when Note 4 was first manufactured. If left to drain and not maintained, you may not get a year's worth of normal use from that battery. The original battery received new with these phones were notably failing at 12 months. Also depends on use. Others may fail sooner; they're rated at 500 full charge and discharge cycles. Depending on use, they may not last as long as rated or get the cycles used up prior to a year. They can become erratic and unstable at that point, whenever that is.
Nonetheless, if you want to try procedure I described earlier, a post is linked below for reference. Consider also that the more you flash a failed or intermittent eMMC, you're more likely to induce its demise to permanent or persistent failure; unusable.
https://forum.xda-developers.com/showthread.php?p=70181377
As far as EFS partition, I wouldn't try to restore a backup if replacing eMMC or main board. Phone should activate easily if you're a Sprint subscriber. Just Odin stock tar.
Sent from my SM-N920P using Tapatalk
Hi Guys,
While back, I was experimenting with my phone with different ROMS and I started getting this ERROR where the phone shuts off and when turn on the screen goes to DOWNLOAD MODE and shows an error MMC_READ FAILED .
"Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: Off
KNOX WARRANTY VOID: 0x1 (0)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A4, P1
SECURE DOWNLOAD : ENABLE
UDC START"
So, I flashed the Stock Firmware through ODIN, however, the error is still there.
To use the phone, I have to take out the battery for few minutes and then reinsert it again and hope the phone boots up, Sometimes it goes to the DOWNLOAD MODE with this error and sometime it won't start up and sometime it does.
The phone does not restart when I try to do a restart it just shuts down.
Can someone please provide a proper Solution for this.
Thanks,
Asim Waqar said:
Hi Guys,
While back, I was experimenting with my phone with different ROMS and I started getting this ERROR where the phone shuts off and when turn on the screen goes to DOWNLOAD MODE and shows an error MMC_READ FAILED .
"Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: Off
KNOX WARRANTY VOID: 0x1 (0)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A4, P1
SECURE DOWNLOAD : ENABLE
UDC START"
So, I flashed the Stock Firmware through ODIN, however, the error is still there.
To use the phone, I have to take out the battery for few minutes and then reinsert it again and hope the phone boots up, Sometimes it goes to the DOWNLOAD MODE with this error and sometime it won't start up and sometime it does.
The phone does not restart when I try to do a restart it just shuts down.
Can someone please provide a proper Solution for this.
Thanks,
Click to expand...
Click to collapse
Replacing the phone is the only solution. The problem will only get worse in the future, until the phone is completely unusable.
Sent from my SM-N920P using Tapatalk
LMMT said:
Replacing the phone is the only solution. The problem will only get worse in the future, until the phone is completely unusable.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I'm waiting for Note 8 to release then I'll move to that phone. For now I don't wanna waste money on any other phone and need to find a way to Fix this phone. Because I believe it's a software related issue that caused internal files to corrupt.
Asim Waqar said:
I'm waiting for Note 8 to release then I'll move to that phone. For now I don't wanna waste money on any other phone and need to find a way to Fix this phone. Because I believe it's a software related issue that caused internal files to corrupt.
Click to expand...
Click to collapse
I agree with lmmt. But did you see thread on T-Mobile thread. About wake lock app! Helping prolong using phone until you get new one.
I have no idea if it works. Just suggesting looking.
I seem to fix this issue by flashing a DR. Ketan NOTE 7 Custom ROM which I was using previously, the phone is working fine for now.. so just gonna use this ROM till I can get my hands on Note 8 or Note 7r as they are going to be half the price.
aaron74 said:
I agree with lmmt. But did you see thread on T-Mobile thread. About wake lock app! Helping prolong using phone until you get new one.
I have no idea if it works. Just suggesting looking.
Click to expand...
Click to collapse
Hy There,
Using App Wake Lock is the best option these days on this issue. Using it for last three days and phone is working as previous. No issue at all. I am thinking for flashing set from flashing device i/o Odin flash tool. This may forcefully reinstall any ROM or stock firmware. Today will taking the risk for 10 grands. Lets see what happen next. Will share the progress when all done.
Peace !!!!
Had the same error pop up. Did all the recommended fixes (new battery, wake Locke, etc.) and the phone finally quit after the new battery fully did charged. Tried like hell to get it to boot. No joy. Seems to be a common issue.
Had a glimmer of hope today when I plugged it in and the charging battery display popped up, but my dumb ass couldn't leave well enough alone and I unplugged it and held the power button to start it up. Nope. Fully dead again. Going to leave it plugged in and see if any life is left. Would really love to get some data off the internal memory.
And no, trying to Odin into it provides no results. Windows just sees a dead device and cannot communicate with it.
***Edit***
I've seen some posts saying that this may be related to updated firmware. I can say that in my specific case I have very old firmware and haven't updated to 6.01 as many suspect caused the failure. Pretty sure this is flat out hard ware failure on behalf of Samsung.
dh350nwo said:
Had the same error pop up. Did all the recommended fixes (new battery, wake Locke, etc.) and the phone finally quit after the new battery fully did charged. Tried like hell to get it to boot. No joy. Seems to be a common issue.
Had a glimmer of hope today when I plugged it in and the charging battery display popped up, but my dumb ass couldn't leave well enough alone and I unplugged it and held the power button to start it up. Nope. Fully dead again. Going to leave it plugged in and see if any life is left. Would really love to get some data off the internal memory.
And no, trying to Odin into it provides no results. Windows just sees a dead device and cannot communicate with it.
***Edit***
I've seen some posts saying that this may be related to updated firmware. I can say that in my specific case I have very old firmware and haven't updated to 6.01 as many suspect caused the failure. Pretty sure this is flat out hard ware failure on behalf of Samsung.
Click to expand...
Click to collapse
Have you tried removing battery and letting it sit without battery for a while? May take hours, longer or just minutes. Remove the battery and try later if it doesn't boot.
There's a chance you might get a boot to transfer some data from internal memory. I believe the battery pull plus cooling may increase likelihood of boot. IMO, an A.C. register blowing cool air on it or forced air from a fan may be better than fridge or freezer; the condensation should be avoided.
Ultimately you likely need a repair. Samsung Support may be offering eMMC replacement for $75 USD but turnaround may take a week or more.
Sent from my SM-N920P using Tapatalk
samep said:
Have you tried removing battery and letting it sit without battery for a while? May take hours, longer or just minutes. Remove the battery and try later if it doesn't boot.
There's a chance you might get a boot to transfer some data from internal memory. I believe the battery pull plus cooling may increase likelihood of boot. IMO, an A.C. register blowing cool air on it or forced air from a fan may be better than fridge or freezer; the condensation should be avoided.
Ultimately you likely need a repair. Samsung Support may be offering eMMC replacement for $75 USD but turnaround may take a week or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
holding the power button for 30+ seconds or repeatedly for 10-15sec at a time without any power source has the same effect, if not better. the technique is called "static discharge"
it's an old fix for BIOS issues on old laptops
Sterist said:
holding the power button for 30+ seconds or repeatedly for 10-15sec at a time without any power source has the same effect, if not better. the technique is called "static discharge"
it's an old fix for BIOS issues on old laptops
Click to expand...
Click to collapse
Many Thanks for your rlp, i have tried each and every method but all in vain, got repair @ 20$ it run flawless for max 3 days then he turned off permanently . They suggest me to change it's motherboard, it will cost 80$ with no warranty. As i already spent 20$ so i decided move on to NOTE 5.
I Sold Note 4 for its LCD Panel at 100$. Now Enjoying NOTE 5 Dual with 7.0 Nougat.
Peace ...
ahsanbutt1989 said:
Many Thanks for your rlp, i have tried each and every method but all in vain, got repair @ 20$ it run flawless for max 3 days then he turned off permanently . They suggest me to change it's motherboard, it will cost 80$ with no warranty. As i already spent 20$ so i decided move on to NOTE 5.
I Sold Note 4 for its LCD Panel at 100$. Now Enjoying NOTE 5 Dual with 7.0 Nougat.
Peace ...
Click to expand...
Click to collapse
I would say that was a bad idea because
1. slower cpu
2. replacing battery = repair center visit (and it's probably already seen a lot of use!)
3. no sdcard slot
4. no IR blaster
Asim Waqar said:
Hi Guys,
While back, I was experimenting with my phone with different ROMS and I started getting this ERROR where the phone shuts off and when turn on the screen goes to DOWNLOAD MODE and shows an error MMC_READ FAILED .
"Could not do normal boot.
ddi : mmc_read failed
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910P
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: Off
KNOX WARRANTY VOID: 0x1 (0)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A4, P1
SECURE DOWNLOAD : ENABLE
UDC START"
So, I flashed the Stock Firmware through ODIN, however, the error is still there.
To use the phone, I have to take out the battery for few minutes and then reinsert it again and hope the phone boots up, Sometimes it goes to the DOWNLOAD MODE with this error and sometime it won't start up and sometime it does.
The phone does not restart when I try to do a restart it just shuts down.
Can someone please provide a proper Solution for this.
Thanks,
Click to expand...
Click to collapse
This is 100% Hardware Issue not Software. Easy Fix! To get proof yourself:
1. Disassemble the phone, Re-Solder the IC: U3002 Section (Under the SIM and SD Flex) works 100%. "ddi...Error" gone for mine & still now Ok (two weeks running), except a little Lagging & Restart detected some times. I just ignore them
2. After just Disconnecting the SIM & SD Card flex from MB also worked as reported some other devices! (Flex Issue???)
Another interesting thing is, most of those phones goes to QHS_USB Download mode when Restarted and bricked! 10 Seconds of Battery removal solve the issue too....
Anyway, none of the above solutions are guaranteed. I Just identify the real problem, real solutions depends on real Exparts.
Thanks.
Hello, I have this exact issue going on with my phone. Here's the rundown to how it started. (Btw, this is a non-rooted Note 4)
I was using the phone as normal and it was pushing for the G1 Firmware update, but I had delayed in order to run a backup of my stuff. A few days went by, and the 2 days before this started the phone began lagging heavily, and then would reset itself a few times. Then I made the mistake of accidentally hitting the update button. It ran its update, and came back and said the update failed.
Since then, I have been experiencing the exact issue that OP wrote about, whereas I can get it working briefly to recover some internal storage information, but that's about it. Any ideas?
celticpride said:
Hello, I have this exact issue going on with my phone. Here's the rundown to how it started. (Btw, this is a non-rooted Note 4)
I was using the phone as normal and it was pushing for the G1 Firmware update, but I had delayed in order to run a backup of my stuff. A few days went by, and the 2 days before this started the phone began lagging heavily, and then would reset itself a few times. Then I made the mistake of accidentally hitting the update button. It ran its update, and came back and said the update failed.
Since then, I have been experiencing the exact issue that OP wrote about, whereas I can get it working briefly to recover some internal storage information, but that's about it. Any ideas?
Click to expand...
Click to collapse
Move on to the note 8. I've been with the note 4 since launch day and the emmc read fail is exactly y it's time to move on. I'm on my 3rd note 4 because of the emmc read fail and was just waiting for the note 8. Anything you find online to help with this is pretty much bs as this is a internal mem failure. The N4 is such a great phone and I wish Samsung didn't F it up up like this. Sorry, but grab what data you can off it. I didn't get that chance the second time this happened.
I have run into a similar issue with my phone, and was looking for some advice. It started with my phone running really really slow, and it would freeze when typing. Eventually i would turn it on and get the weird mmc_read error. After resetting it a couple times,m it would boot in the Welcome Samsung screen, and get a continuous force close of random thing and it will not stop. I installed the Samsung drives and was able to pull up my phone, but the folder is empty. Does this mean my phone deleted everything on the phone? I had pulled the sd card soon after it started messing up, but the internal memory was nearly full, and was wondering if there was another way to attempt to get my information off of the device.
thanks in advance
Hi!
rassel2k said:
This is 100% Hardware Issue not Software. Easy Fix! To get proof yourself:
1. Disassemble the phone, Re-Solder the IC: U3002 Section (Under the SIM and SD Flex) works 100%. "ddi...Error" gone for mine & still now Ok (two weeks running), except a little Lagging & Restart detected some times. I just ignore them
2. After just Disconnecting the SIM & SD Card flex from MB also worked as reported some other devices! (Flex Issue???)
Another interesting thing is, most of those phones goes to QHS_USB Download mode when Restarted and bricked! 10 Seconds of Battery removal solve the issue too....
Anyway, none of the above solutions are guaranteed. I Just identify the real problem, real solutions depends on real Exparts.
Thanks.
Click to expand...
Click to collapse
did you change the charging jack or just removed it from the motherboard? can you charge your phone in both turnet on and off state? can you boot the phone into recovery mode or download mode if you want to or they don't work anymore?
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try.
https://youtu.be/jLPHWtb0StI
It is a fix that has to done for the hardware. Replacing the emmc chip costs more for this model at this time. Check out the simple DIY permanent fix from the below article.
https://androidforrookie.blogspot.com/2020/02/100-fix-for-mmcread-failed-error-in.html
mpadhu said:
It is a fix that has to done for the hardware. Replacing the emmc chip costs more for this model at this time. Check out the simple DIY permanent fix from the below article.
https://androidforrookie.blogspot.com/2020/02/100-fix-for-mmcread-failed-error-in.html
Click to expand...
Click to collapse
This tutorial helped me solving the issue, strangely, it worked. But after studying the problem, clearly it can be solved with a heat gun and a bit of soldering knowledge. Thanks tutorial maker!
arnookie said:
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try.
https://youtu.be/jLPHWtb0StI
Click to expand...
Click to collapse
I did and it is the solution But I broke one flatcable from the screen and the digitizer is not working anymore. my stupid fault. Lucky the screens are inexpensive on ebay and Aliexpress. But which one is good? they say Burn Shadow AMOLED LCD , Is this bad?
Some advise?