Related
Hello lovely people.
Not long ago, my wonderful Samsung Galaxy S2 dropped dead. Before I send it in for service, I would LOVE to get the data on the internal storage back.
The phone does not get hot while charging, and nothing else whatsoever makes it show sings of life.
Is it possible to swap out the internal storage chip from the motherboard, and place it on an another identical phone, and retrieve the data that way?
Any sort of tips for businesses that would do something like this is welcome!
As you can guess, I learned to back up my stuff the hard way. My last clockwork backup was 20 days ago. Precious 20 days ago
probability = 99,99% yes ... a SD-card no matter of where it was before. have good luck
psytr0nic said:
probability = 99,99% yes ... a SD-card no matter of where it was before. have good luck
Click to expand...
Click to collapse
And the deadly .01% is if the damaged part is the internal memory itself.
:good:
While emmc chip got like 20 important pads to solder (out of even hundred, when most are there being N/C) it is still BGA. A ****ass small BGA covered with glue. That would require someone really experienced with reworking such things. I do not know the prices but I would be prepared to pay even 100$ or more for such job, done right.
That from HW level. From SW+HW look: in theory there should be no trouble with properly swapped emmc ic from other phone. But you shall not forget about the said 0.01%, maybe more - reworking such chip might have influence on its content (I might be wrong) + GS2 had the emmc hardbrick bug - how did it die?
Please let us know how did it go.
Oh and btw - there must be companies working on such data recovery with proper HW to wire up to the unsoldered chip with sort of socket or other hackaround - I'd lookup there.
Max specified operating temperature of an eMMC is about 85 °C, there's no telling what happens above that... So whatever way you use to re-connect your eMMC, make sure it is not by soldering!
Of course it is possible but you need highly expensive tools for it to solder of the chip. it is BGA it's not just like a transistor..
It does have hundreds of micro balls under the chip. Did you try adb shell already? Or is it really 99% dead.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You may find a company that can do it but it will cost A LOT of money. Because you need special tools for it.
Something like this
You best bet would be to try to use a heat gun on the main board. Just heat it up for a few seconds and cool it down to zero as quick as possible. Maybe the bga is cracked because it got hit by the ground when you accidentally dropped it. By heating it up you may temporarily fix this crack(will also cause slightly damage to the chips) in the soldering. So you can back it up and sent it back. I think it will void the warranty, but you have to decide for yourself what to do. Try to get back the data or get a new working main board from Samsung (if you sent the phone back they will just replace it with a new one most likely).
Bga soldering crack
0,1% of chance .. playing with Samsung EMMC chip = bye bye phone . look around forum or elsewhere 100% of bricked is due to it .
Question : what make you confident to say that your internal memory is good ?
to remind : it is also your phone flash chip which manage boot sequence and all . don't forget it .
Max specified operating temperature of an eMMC is about 85 °C, there's no telling what happens above that.
Click to expand...
Click to collapse
Of course it is possible but you need highly expensive tools for it to solder of the chip
Click to expand...
Click to collapse
every time I tried with hot air , I removed chip with missing pads cause of glue under chip which make hard to remove .
why not to give a try ? have good luck
You best bet would be to try to use a heat gun on the main board
Click to expand...
Click to collapse
Those are options you have instead of paying hundreds of euro's to a company that can recover it if it isn't the nand/emmc itself that is the dead part of the phone.
Of course i recommend him to go to a professional company and let them do recover it. Because they will do it the proper way but like i said before it cost you a lot of money.
So your best bet would be to try it yourself or just sent it back to Samsung for warranty.(by trying yourself i don't mean to solder it off because thet will not work out good. It will probably kill the chip, just try to reflow the mainboard and maybe you have luck.)
I know about glue in the corners of bga based chips in HP & Acer and other brands in laptops and such but didn't know that phones had that too.
But glue under the chip, never seen that before. And btw you cannot remove a bga soldered chip with a heatgun you need ir so that the whole surface under the chip gets loose. And you need to cover up all other components or they will get loose too or fry
Acer bga soldered chip -> glue in corners (this is not nand or emmc, its the chipset & cpu/gpu)
http://i.imgur.com/aIHNu.jpg
Irda soldering
http://www.youtube.com/watch?feature=player_detailpage&v=RrA-trDZPNs#t=170s
Recovering data from snapped Galaxy s2 motherboard
Hi everyone, i really need some help
My galaxy s2 motherboard has snapped (around the long thin bit) with all other parts of the motherboard still intact. I really need to recover all of the data. The data has sentimental value and cannot be replaced. Is there any chance of recovering the data either through chip extraction and onto new board? Can the existing motherboard be fixed?
All i keep hearing is that it is too difficult, the motherboard is multi-layered and would be impossible to fix. I am reluctant to take this as an answer. Is there anybody out there that has a solution for recovering all the data? Who would i go to? who do i pay? Ive contacted samsung and they say it is impossible, when questioning them why it is impossible they state tit would cost too much and they cannot do it.
Please help. thank you.
EMMC reball and some other tips
Hey guys,
I know this thread is a little bit old but I'll try to give in my 2 cents maybe someone here may find it helpful
So I come from background where I do around 20 bga reballs per week, so I do know a thing or two I guess about this although my knowledge on Samsung platform is relatively low compared to an iphone logic.
So to begin with replacing the emmc chip alone is not enough as you'll need a programmer box which connects to a jtag interface which is able to rewrite the initial files like bootrom to the emmc. You can find these boxes at any prominent gsm repair shops; boxes named such as RiffBox or Z3X Samsung box are the best I found recently.
Having said that before any repair is attempted by mainly removing the flash chip it is imperative to try to resurrect the phone using these said boxes, to try to find whether or not the NAND chip is actually detected. As one may have simply installed a ROM which is not compatible with the phone and all that is required is to rewrite the bootrom files. If the NAND (basically the same name as a flash chip) fails to be detected then obviously something went wrong and it either could be the NAND is burnt inside, or the NAND has some cracks under its critical ball pins or even may be a problem that the main power management chip inside the phone is failing from supplying usually around 3V to power up the NAND.
The emmc chip at least found in a samsung is a 14 by 14 pins which only about 1/3 of it's pins are critical, the rest are dummy and do not worry if they eventually get removed, while removing the chip or cleaning the board after desoldering prior installing the new chip.
Some tips on reworking:
Always cover critical glued components like CPU + POP (package on package) RAM, baseband processor usually XGOLD found in Samsung.
Clean surrounding chip glue before attempting to remove by giving around 250C of heat and with a needle scratching the glue around
Do not exceed more than 350C to remove the actual chip to prevent more damage to the built in tracks inside the motherboard.
Last and not least a schematic for your phone would always be a lot of help to help you detect what voltages are missing on bootup to make sure that the boot up sequence is starting fine and also the relative points of each pin under a chip while knowing which pins are critical and which are dummies, or NC (not connected)
If you need any help you can always message me and I'll try my best to answer your questions.
Regards,
Ryan
solder with care
Solder with care mate, else it will be totally gone
psytr0nic said:
0,1% of chance .. playing with Samsung EMMC chip = bye bye phone . look around forum or elsewhere 100% of bricked is due to it .
Question : what make you confident to say that your internal memory is good ?
to remind : it is also your phone flash chip which manage boot sequence and all . don't forget it .
every time I tried with hot air , I removed chip with missing pads cause of glue under chip which make hard to remove .
why not to give a try ? have good luck
Click to expand...
Click to collapse
The glue in samsung is very easy to remove you just need to heat the board up to 250C and gently scratch the glued area with a needle. Do not worry on the removed pads as 1/3 of the pads under the EMMC are not connected and therefore not needed. Always clean the chip from the glue and use leaded solder for best shiny connections.
If you need any help you can always message me and I'll try my best to answer your questions.
Regards,
Ryan[/QUOTE]
Can you please explain more about JTAG.., types and the connections, how to get files for the different phones, where can we get the software etc. Thank you.:good:
richie16171 said:
If you need any help you can always message me and I'll try my best to answer your questions.
Regards,
Ryan
Click to expand...
Click to collapse
Can you please please explain more about JTAG.., types and the connections, how to get the files from different phones, where can we get the softare etc. Thank you.:good:[/QUOTE]
You will need special programmer boxes like riffbox to be able to rewrite the bootloader. JTAG is a dedicated space on the board where the riffbox will communicate with the phone.
AnArChYm said:
Can you please please explain more about JTAG.., types and the connections, how to get the files from different phones, where can we get the softare etc. Thank you.:good:
Click to expand...
Click to collapse
You will need special programmer boxes like riffbox to be able to rewrite the bootloader. JTAG is a dedicated space on the board where the riffbox will communicate with the phone.[/QUOTE]
Thank you., what about the riffbox connections? Which pin to connect what and is it common to all devices?
richie16171 said:
You will need special programmer boxes like riffbox to be able to rewrite the bootloader. JTAG is a dedicated space on the board where the riffbox will communicate with the phone.
Click to expand...
Click to collapse
Thank you., what about the riffbox connections? Which pin to connect what and is it common to all devices?[/QUOTE]
Edit: I already got the site. And everything is explained in forum there. If anyone wants.. you can find here http://faq.riffbox.org/showcat.html
Would like the learn how to reball
AnArChYm said:
Hey guys,
I know this thread is a little bit old but I'll try to give in my 2 cents maybe someone here may find it helpful
So I come from background where I do around 20 bga reballs per week, so I do know a thing or two I guess about this although my knowledge on Samsung platform is relatively low compared to an iphone logic.
So to begin with replacing the emmc chip alone is not enough as you'll need a programmer box which connects to a jtag interface which is able to rewrite the initial files like bootrom to the emmc. You can find these boxes at any prominent gsm repair shops; boxes named such as RiffBox or Z3X Samsung box are the best I found recently.
Having said that before any repair is attempted by mainly removing the flash chip it is imperative to try to resurrect the phone using these said boxes, to try to find whether or not the NAND chip is actually detected. As one may have simply installed a ROM which is not compatible with the phone and all that is required is to rewrite the bootrom files. If the NAND (basically the same name as a flash chip) fails to be detected then obviously something went wrong and it either could be the NAND is burnt inside, or the NAND has some cracks under its critical ball pins or even may be a problem that the main power management chip inside the phone is failing from supplying usually around 3V to power up the NAND.
The emmc chip at least found in a samsung is a 14 by 14 pins which only about 1/3 of it's pins are critical, the rest are dummy and do not worry if they eventually get removed, while removing the chip or cleaning the board after desoldering prior installing the new chip.
Some tips on reworking:
Always cover critical glued components like CPU + POP (package on package) RAM, baseband processor usually XGOLD found in Samsung.
Clean surrounding chip glue before attempting to remove by giving around 250C of heat and with a needle scratching the glue around
Do not exceed more than 350C to remove the actual chip to prevent more damage to the built in tracks inside the motherboard.
Last and not least a schematic for your phone would always be a lot of help to help you detect what voltages are missing on bootup to make sure that the boot up sequence is starting fine and also the relative points of each pin under a chip while knowing which pins are critical and which are dummies, or NC (not connected)
If you need any help you can always message me and I'll try my best to answer your questions.
Regards,
Ryan
Click to expand...
Click to collapse
Hi Ryan,
My son's galaxy s3 i9300 was inadvertently given a spin in the washing machine. When I realised what had happened I took it apart into its various components and put it in rice for a week. When I switched it on everything worked except the cell phone signal. From what I can gather the eMMC chip has been damaged and no software can fix it. I don't have it with me now but I think IMEI and baseband is unknown. The EFS folder is empty or corrupt.
Stumbling across your post I was interested in the fact that you seem to be an expert in re-balling. My son has since got a new phone and since I am a basic amateur in phone repair (for family and friends) I have been toying with the idea of replacing the eMMC chip on the s3 after watching this video:
http://www.youtube.com/watch?v=s38vQxXv0GE
I don't mind if I buy the chip and it doesn't work I am more intent on gaining the experience and going through the stages. Do you think this is a good idea and do you have any tips or things I can research on the topic?
Yiannos
---------- Post added at 07:30 AM ---------- Previous post was at 07:14 AM ----------
Sorry I meant this video:
http://www.youtube.com/watch?v=ds04BTVL8i0&feature=youtu.be
yiannos50 said:
Hi Ryan,
My son's galaxy s3 i9300 was inadvertently given a spin in the washing machine...
Click to expand...
Click to collapse
Hi,
If the imei is available (null), it could be the case that it needs repairing rather than actually chaging the eMMC chip , however you'll need a special tool to do this, which honestly do not know which exactly is as I'm more into hardware repairs rather than software.
Another possible issue could be that the phone can also have corrosion around critical components, ie around the main baseband supply, which is stopping from the baseband switch on, thus no signal or any radio communication from starting up. It would be best to have a microscope and inspect each part of the board for bad components, rather than rushing to the eMMC replacement.
It's very important to read this post very carefully and understand it as it is not easy to be done, but it is very much possible. And find a lot of youtube videos before even trying so you'll be more familiar with the process and different techniques.
Anyways for the most interesting part
Basically the eMMC chip is a 14 by 14 bga, ball grid array chip which is fairly easy to reball comapred to other complex ones, like baseband processor or the main application processor, You'll also be needing a reballing stencil to put the balls on top of the solder pins, and solder paste to paste the solder onto the holes and a hot air gun to melt that solder into balls. (Basically the solder paste will melt between those holes inside the stencil and will form nice silverish balls.
The chip also has got a lot of not connected pads (aka dummy pads) so do not worry when removing the chip as you'll be more then likely to lift pads from the board especially if this your first reball job.
First of all, you'll need to clean the surrounding glue around the chip by using around 200C and with a needle scrape off the glue, be very gentle not to scrape any tracks or board layers.
Then to remove the chip from the board use around 350C (always ramping up the temp), very important to use kapton tape around the surroundings to reduce heat stress. Personally I use the following temperatures: (do not use any nozzle with the heat gun as the chip is large and you need the heat to dispersed all over the chip)
1st min 180C full air
2nd min 280C full air
4th min 350C full air until the surrounding components turn silverish and are easy to lift, at that time get a very sharp needle and gently (very gently) start to pry up with ease the chip from one side, until it is fully lifted.
Then you'll need to clean the board, basically put flux and with a fine tip soldering iron clean the pads gently until all underfilled glue is no more remaining and the pads are nice and shiny and set the board aside.
If you'll buy a new eMMC chip most probably you'll have it reballed from the supplier. If not pre reballed, you ll need to reball it using a reballing stencil and solder paste.
Finally align back the eMMC chip over the board in the correct way, always note where is pin A1 and solder it back by ramping up heat again, same process as removing the chip.
The last process is all based on software, basically you'll have to copy the bootloader from a good working S3 phone to this one, as the new eMMC chip is empty of data, and obviously without the bootloader so the phone wouldn't be able to switch on.There is a process somewhere on the net how this is exactly done.
Ryan
Ryan,
Thanks a million for setting me on the right path. I'll let you know what happens.
Yiannos
Data recovery - Siemens A31
Hello everyone,
this thread seems to be what I've been looking for. My Siemens A31 got some water from a torrential rain while it was on. When I got to removing the battery, the phone was already off. I dried all accessible parts but I did not have the necessary torx screwdriver, so some water stayed inside. It was Friday evening and I got the screwdriver no earlier than on Monday. There was some corrosion in the phone, of course. It could not be turned on and subsequent cleaning with alcohol and even ultrasound improved only the look of the main board, but not its behavior. The only sign of life was that it seemingly recharged the battery while connected to the charger.
I have asked several repair services and people and I am quite confused whether it is possible to recover the data by soldering the memory chip into another A31, a functioning one of course. Last time, I asked a laptop service and I was told it is impossible, not just because of the difficulty of soldering a BGA chip. They told me it would not work because the phone would get blocked due to IMEI mismatch! This was surprising for me. If it is true, it implies that the IMEI is stored in both the flash memory and some other chip. I was unable to find any evidence for such a claim on the Internet.
Can anyone tell me if the target phone with replaced flash memory will actually work, assuming the memory is functioning? The video referred to by yiannos50 suggests it may really work. Anyone else has tried it? Two people in this discussion were about to do so.
Hi,
Just curious is anybody can suggest some avenues for repair. A friend of mine gave me their GT-I9505 which had a broken screen. They apparently were aware of the issues with this phone and upgraded to an iPhone 6, but didn't tell me about this until after I'd bought a screen replacement and had already encountered the issue.
I replaced the screen but now have issues with the device showing "No SIM Card". Sometimes the device also has difficulty charging. The device also seems to get very hot, and the SIM issue appears to occur around high heat.
To try to fix this I have:
Tried different SIMs
Verified correct operation of the top proximity sensor
Verified the device is an authentic Samsung and the IMEI is not listed as stolen
Reflashed firmware with ODIN
Tried Cyanogenmod 11
Used CPU Tuner to underclock the processor to 600mhz and 2 cores
Replaced the MicroSD & SIM Card slots
Tried to reflow the solder contacts on the mainboard with a hair dryer. No idea how effective this really was
Added a piece of plastic to apply pressure to the SD/SIM slot connector (used a cut up bank card)
Examined the battery and found it flawless. Replaced it anyway
Tried copper tape on the rear cover to act as a heatsink
Tried applying arctic silver thermal paste to the chips that come in contact with the body of the phone
Nothing I've tried has really had much of an impact. The device is not under warranty.
Is there anything else I should try? This does appear to be a very common issue but answers seem few and far between.
I've read about people believing its a mainboard issue, only to replace the mainboard and have the same issue occur again?
critenau said:
Hi,
Just curious is anybody can suggest some avenues for repair. A friend of mine gave me their GT-I9505 which had a broken screen. They apparently were aware of the issues with this phone and upgraded to an iPhone 6, but didn't tell me about this until after I'd bought a screen replacement and had already encountered the issue.
I replaced the screen but now have issues with the device showing "No SIM Card". Sometimes the device also has difficulty charging. The device also seems to get very hot, and the SIM issue appears to occur around high heat.
To try to fix this I have:
Tried different SIMs
Verified correct operation of the top proximity sensor
Verified the device is an authentic Samsung and the IMEI is not listed as stolen
Reflashed firmware with ODIN
Tried Cyanogenmod 11
Used CPU Tuner to underclock the processor to 600mhz and 2 cores
Replaced the MicroSD & SIM Card slots
Tried to reflow the solder contacts on the mainboard with a hair dryer. No idea how effective this really was
Added a piece of plastic to apply pressure to the SD/SIM slot connector (used a cut up bank card)
Examined the battery and found it flawless. Replaced it anyway
Tried copper tape on the rear cover to act as a heatsink
Tried applying arctic silver thermal paste to the chips that come in contact with the body of the phone
Nothing I've tried has really had much of an impact. The device is not under warranty.
Is there anything else I should try? This does appear to be a very common issue but answers seem few and far between.
I've read about people believing its a mainboard issue, only to replace the mainboard and have the same issue occur again?
Click to expand...
Click to collapse
Hi mate,
Some times the no sim card error may be related to Imei problem or EFS being corrupted ( my case) check your imei dial *#06# see if the imei number match the one behind the battery
I am having a similar problem and the IMEI does not match, what can i do to solve this?
MAX 404 said:
Some times the no sim card error may be related to Imei problem or EFS being corrupted ( my case) check your imei dial *#06# see if the imei number match the one behind the battery
Click to expand...
Click to collapse
Found that the IMEI reported by *#06# consistently matches the one behind the battery, even when the no sim fault occurs.
I don't have an EFS backup, but with EFS Pro I was able to perform a backup, format the EFS, and restore from the backup. I also did its fix permissions routine, but it didn't change anything. So I don't think its an EFS problem.
MegaMike604 said:
I am having a similar problem and the IMEI does not match, what can i do to solve this?
Click to expand...
Click to collapse
EFS Pro. Better if you have an EFS backup.
critenau said:
Found that the IMEI reported by *#06# consistently matches the one behind the battery, even when the no sim fault occurs.
I don't have an EFS backup, but with EFS Pro I was able to perform a backup, format the EFS, and restore from the backup. I also did its fix permissions routine, but it didn't change anything. So I don't think its an EFS problem.
EFS Pro. Better if you have an EFS backup.
Click to expand...
Click to collapse
Mate the problem is you maybe doing a backup of something corrupted .....so you basically are putting back whatever "bad" was there again...
MAX 404 said:
Mate the problem is you maybe doing a backup of something corrupted .....so you basically are putting back whatever "bad" was there again...
Click to expand...
Click to collapse
So I've flashed the following two files with ODIN 3.07, no change. First tried one and it seemed to work, but after it faulted I tried the second, and had it fault again.
http://www.4shared.com/zip/ZG0QtCq_ba/I9505_efs.html
http://www.4shared.com/zip/Z1yKu1Upce/I9505_modem_patch_File_for_Unl.html
That should've rewritten the /efs and baseband?
critenau said:
So I've flashed the following two files with ODIN 3.07, no change. First tried one and it seemed to work, but after it faulted I tried the second, and had it fault again.
http://www.4shared.com/zip/ZG0QtCq_ba/I9505_efs.html
http://www.4shared.com/zip/Z1yKu1Upce/I9505_modem_patch_File_for_Unl.html
That should've rewritten the /efs and baseband?
Click to expand...
Click to collapse
Hi Mate
Every EFS is unique it has your imei information among others , flashing a different efs could had fix it but in the other hand you may have a different imei information...
anyhow as I said error may be related to Imei problem or EFS being corrupted ( my case) in your case it may be a hardware issue....
Guys, care to help me out here? I have this i9505 in front of me. It was brought to me because it would randomly stop playing audio. I noticed that this audio issue only happens after the device wakes up from sleep. No sound at all after wake up from sleep. And Video Playback (SdCard and YouTube) stutter goes along with the problem. Here's what I did to get rid of this issue:
- Factory reset in Samsung Stock Recovery; didn't help.
- Flash stock tar.gz via Odin; didn't help. (Yes, I used the correct one matching my model)
- Flash CM to rule out issues with Samsung specific software/drivers; didn't help
So I concluded that there must be a hardware issue. Since the device looked pretty worn out and sticky, I though maybe dust or something else like a liquid could've destroyed the internals. I dissassembled it but to my surprise it looked very clean. So I reassembled it. Plot twist; now it wouldn't boot anymore. It passes the Samsung splash screen and gets into the Bootanimation. But within seconds into it, it reboots. This goes on and on and on unless I take out the battery. I know what you're thinking, but listen; I disassembled/reassembled almost 70 devices, almost half of which iPhones (Yes, I keep track of it, since I charge people for my work) and chances that I messed up something are very low. Not saying impossible, but you get the point. I exclusively change parts. Dispalys, middle frames, backcovers, batteries, microphones, cameras, microsd/sim trays, you name it*. Anyway.
Now, no matter what I do, I can't boot into the OS. Download Mode, Recovery, be it stock TWRP or CWM just work fine. When I format the internal storage via TWRP/CWM and boot up the device on stock, no folders are created on it. But when I flash a custom ROM, be it TW, CM or AOSP/A, I sometimes get into the OS and the standard Android folder structure is created. But the device is then pretty much unresponsive. I can barely navigate the OS before it shuts down again.
What could be the issue here? What could I have damaged during reassembly to cause these issues? But on the other hand, the S4 has a fairly simple architecture and I use an ESD pad, ESD wrist straps and only use plastic tools to pry off connectors. I even watch the humidity in my room for the record.
I gave this guy a replacement Nexus 5 already after he brought his S4 to me. That's what I usually do when I can't tell how long a "repair" could take. If it turns out that I caused the problem, of course he'll get to keep the device.
EDIT: I forgot. I have some spare parts for the i9505 and replaced one at a time to rule out malfunctioning hardware. So far I replaced every part except mainboard (Sim/SdCard Slot), Display and any cable connected to these two parts only to end up with the same problem.
nitrous² said:
Guys, care to help me out here? I have this i9505 in front of me. It was brought to me because it would randomly stop playing audio. I noticed that this audio issue only happens after the device wakes up from sleep. No sound at all after wake up from sleep. And Video Playback (SdCard and YouTube) stutter goes along with the problem. Here's what I did to get rid of this issue:
- Factory reset in Samsung Stock Recovery; didn't help.
- Flash stock tar.gz via Odin; didn't help. (Yes, I used the correct one matching my model)
- Flash CM to rule out issues with Samsung specific software/drivers; didn't help
So I concluded that there must be a hardware issue. Since the device looked pretty worn out and sticky, I though maybe dust or something else like a liquid could've destroyed the internals. I dissassembled it but to my surprise it looked very clean. So I reassembled it. Plot twist; now it wouldn't boot anymore. It passes the Samsung splash screen and gets into the Bootanimation. But within seconds into it, it reboots. This goes on and on and on unless I take out the battery. I know what you're thinking, but listen; I disassembled/reassembled almost 70 devices, almost half of which iPhones (Yes, I keep track of it, since I charge people for my work) and chances that I messed up something are very low. Not saying impossible, but you get the point. I exclusively change parts. Dispalys, middle frames, backcovers, batteries, microphones, cameras, microsd/sim trays, you name it*. Anyway.
Now, no matter what I do, I can't boot into the OS. Download Mode, Recovery, be it stock TWRP or CWM just work fine. When I format the internal storage via TWRP/CWM and boot up the device on stock, no folders are created on it. But when I flash a custom ROM, be it TW, CM or AOSP/A, I sometimes get into the OS and the standard Android folder structure is created. But the device is then pretty much unresponsive. I can barely navigate the OS before it shuts down again.
What could be the issue here? What could I have damaged during reassembly to cause these issues? But on the other hand, the S4 has a fairly simple architecture and I use an ESD pad, ESD wrist straps and only use plastic tools to pry off connectors. I even watch the humidity in my room for the record.
I gave this guy a replacement Nexus 5 already after he brought his S4 to me. That's what I usually do when I can't tell how long a "repair" could take. If it turns out that I caused the problem, of course he'll get to keep the device.
EDIT: I forgot. I have some spare parts for the i9505 and replaced one at a time to rule out malfunctioning hardware. So far I replaced every part except mainboard (Sim/SdCard Slot), Display and any cable connected to these two parts only to end up with the same problem.
Click to expand...
Click to collapse
It's clearly hardware damage. Some component on your motherboard. The audio problem is/was also hardware related. No software would cause that. My conclusion based on your info is that the motherboard already was damaged. Sound problems are usually a damaged motherboard. So the disassembly probably made it worse. Just bad luck. Maybe reheating/reflowing the audio chip will fix it. If not then buy a new motherboard and charge him that.
Yeah, was also thinking about a reflow. But it's strange that everything works. Download mode, recovery and I can mount and access every partition in TWRP/CWM. Let's see. I'm not sure if I'm gonna charge him. It sounds obvious on first sight that I caused it, sure. But I haven't given up hope yet.
Gesendet von meinem LG-H815 mit Tapatalk
Hello everyone,
I have a problem with my Samsung Galaxy S5 and I was hoping to find some help here.
When I got up this morning I unplugged my S5 from its charger. However, it was turned off which is usually not the case as I usually don't turn it off. After trying to switch it on for several times and failing with it, I asked Google for help.
What I found after some research was a hint that it might be a problem with either the battery, the charging cable or the mainboard that has been damaged/burned.
Long story short, after some testing (tried a new battery and charging cable) and going to two different repair shops, it turned out it probably is the mainboard. (I'm writing 'probably' because I don't trust those shops 100%. I left my phone at the second shop for about 2.5 hours though, for error diagnostics).
Nevertheless, what I want your help with are these three questions:
1. If there really is a problem with the mainboard, how can I find it all by myself? Is there a way to tell it apart? And is there a way of telling which (more or less) exact part/entity of the mainboard has been damaged?
2. Let's say the mainboard is damaged. Is it possible to fix it? And by fixing I don't mean to just replace the mainboard, but really fixing it. (Ofc I know it might depend on the part that has been damaged, this is why I asked Question #1).
3. Assuming there is no (feasible) way to repair that mainboard. How can I possibly save the data stored on the internal memory? Is there any Software available that can still read the storage? Or do I have to physically move the memory chip to a functioning mainboard, e.g. by soldering?
Any help is appreciated. Thank you in advance!
Eclipsian said:
Hello everyone, I have a problem with my Samsung Galaxy S5 and I was hoping to find some help here...
Click to expand...
Click to collapse
My personal opinion would be that one or both of the following may have happened.
1) Bad Charger - Chargers can go bad without any warning that resulted in your battery going dead.
2) Bad Battery - Also can just go bad suddenly or over time.
The motherboard of your device has a type of regulator that will only allow a certain amount of voltage/amperage to pass on to the battery. It's extremely rare for a proper charger to kill a motherboard (unless jumper cables were involved LOL!).
Your best bet is to replace both the battery and the charger but, this is only a suggestion/recommendation.
I wish you the best of luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I wish you the best of luck!
Click to expand...
Click to collapse
Thank you very much. Unfortunately using a new battery and a new charger didn't solve the problem. And my charger is still in use for my backup phone, which is a Samsung Galaxy S2, and it's still working fine.
So it appears it really narrows down to some physical damage on the board.
After some more reading I found out that professional data recovery uses eMMC adapters for their SD card slot, as eMMC is downwards compatible to MMC. Unfortunately those adapters come at a cost of 85-230$, which of course is still cheaper than paying for professional data recovery, yet too expensive for having no actual clue how it even works. I still didn't figure out what the data will look like once I get access to the memory chip. Will I have to use an android emulator to get to the data? Will I have to use some special recovery tool to read the memory? Or is the eMMC already formatted in such a way that Windows can easily read it?
Anyway, what I'll try now is the cheapest method that came to my mind: mounting the eMMC on some sort of USB stick, that I found on aliexpress for 5$+shipping (it's called "USB3.0 eMMC 153 169 U disk PCB NS1081 main controller without flash memory for recycle emmc emcp chips").
I hope this will suffice to read the memory, somehow.
Any comments on this?
Eclipsian said:
Thank you very much. Unfortunately using a new battery and a new charger didn't solve the problem. And my charger is still in use for my backup phone, which is a Samsung Galaxy S2, and it's still working fine.
So it appears it really narrows down to some physical damage on the board...
Click to expand...
Click to collapse
Unfortunately Motherboards can go bad suddenly too but, there's a few options.
Option 1) You can try buying a USB JIG from eBay for $3-5, it's a tool designed to force your device into download mode. It isn't guaranteed to work but if it does you can flash the firmware. If it doesn't then you only lose $5.
Option 2) You can see if there's a friendly and helpful individual at an official service center for your device for a JTAG service. Though it isn't guaranteed to work but, some may do it for nothing while others can charge up to $50 +/-. The fees are all individually determined by them. Some have the JTAG service there while others require it to be shipped to another shop to repair them and then ship it back to you.
Option 3) You can always purchase another compatible motherboard and put the new one in your device. This is an option you can do yourself if you're careful.
These options/suggestions are the best that I can think of at this time and I hope one of those will work out for you.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
Yesterday, I used the phone like normal(little bit of listening music and media etc) and drained the battery, so it shut down. Connected the charger fairly later and it started charging. In a few hours switched it on and saw that there was this white stop sign on the notification bar. Figured it might be a matter of a reboot since things like that happen from time to time. When rebooted in the morning the sign was still there.
I tried all the firmwares from Sammobile available for the region and nothing got it away, tried LineageOS and then used SmartSwitch to restore the thing.
I also got to the ServiceMode using dial code:
Code:
*#011#
and it says there that:
Code:
MIPI DEVICE FAIL. DEVICE MID=0x20c, PID=0x008
Googled a bit and it seems that the easiest way to fix this is changing the motherboard.
Some more background if it matters: the device asks for a sim pin and hasn't been dropped. Just happened out of the blue.
Solved
Hi again,
I managed to fix the issue. Seems like this is a common problem but I didn't find anything on why it happens or is, just some sites I personally haven't heard before had some same content how to fix the J500M but the same chip was faulty on the J500FN.
What I did was: re-heat the chip shown on the pictures a bit with a hairdryer that had a really small radius(kinda like put a cone on it because didn't want to heat the whole board up). And that seemed to do it. It probably will break again, since it was and is still faulty and for that reason broke on the first place. Also if you're advanced enough you can try to solder it, but that seems to be for the professionals really.. One little connection in the wrong place and you fry the damn thing!
The safe bet is to replace the motherboard(which I don't currently have money for) but that does the trick for me now. Also if your warranty still lasts you might wanna take it to the Samsung Service shop where they should replace or re-solder the chip safely onto the mainboard for free. Or change it alltogether.
What also sealed the deal for me was that the grille that was on the opposite of the chip what was faulty had this weird burn-mark thingy on it, so thats why the whole thing happened..
The pictures of the faulty component: Thegsmsolution.com
I hope that anyone who struggles in the future with this (or in the past and still hasn't found a way to fix it) can fix it now.