I have been told by a service centre that my main board has a fault they wouldn’t/couldn’t tell me the exact fault!
Basically the device started randomly rebooting and sometimes would not even get past the splash screen.
I managed to get it stable in boot loader and re-flash the device hoping it was a software issue before sending to service centre.
My questions are what is the most likely cause of the above and is there anywhere where I could get the board fixed or buy a new one at reasonable cost as the service centre wanted £150 a bit daft when I can get a Kaiser for £200!
psionlover said:
I have been told by a service centre that my main board has a fault they wouldn’t/couldn’t tell me the exact fault!
Basically the device started randomly rebooting and sometimes would not even get past the splash screen.
I managed to get it stable in boot loader and re-flash the device hoping it was a software issue before sending to service centre.
My questions are what is the most likely cause of the above and is there anywhere where I could get the board fixed or buy a new one at reasonable cost as the service centre wanted £150 a bit daft when I can get a Kaiser for £200!
Click to expand...
Click to collapse
I've had 2 MDA pro's one got exchanged by t-mobile for a vario II cause i got fed up with it doing as you described. the other is still here and starting to exhibit the beginings of the same symptoms..
If you phone is doing as I'm about to describe then you'll get your answer shortly.
My phone after 10 month's wouldn't run the 802.11 wireless for any length of time and it didn't matter if i was just browsing, transfering files from main pc to it, or just leaving it on and idle to test connectivity. if i tried to transfer a file it would reboot after about 900k or less. then you couldn't get back into today screen without leaving the device off for sometimes up to 30 mins.
with a bit of testing , re-flashing with the latest firmware at the time directly from t-mobile i gave up and just resigned to bluetooth and making calls.
at least that was being stable. then finally it started dropping calls. and would reboot and stay off after it rebooted. if i pressed the power button same thing as when wireless was on. splash screen the off. Or splash screen, 2nd splash, WM version of an egg timer and then poof reboot to black off state.
leave the device off for 30 mins No problem boots right back up as if nothing had happened.
With a TON of reading and finally 1 article i read on a TOTALLY UNREALATED MATTER ( artlicle on this board about Wifi router ) if you leave the wireless on over a long period of time it will overheat. causing the device to shut down due to an internal protection circuit.
Your answer: The device has become thermally sensative. Since my phone started to do it with just phone calls i can't blame the wireless chip as it's seperate from the GSM receiver. ( see pictures of Universal Mainboard in this forum. ) Thusly where ever the sensor for temprature of the device is that shut it off after it reaches a certain internal temp, that is the cause as far as I can determine. And i Proved that to T-mobile after 10- months of having the phone and they even replaced it with 2 other handsets that did the same thing within HOURS of using the wireless to transfer files in excess of 1Mb in size. Thusly they had me write to the customer liason department and make my reuqest that way. I asked them for the Hermes ( Vario II ) even though it was a bit of a downgrade but it was as tehcnically close to the universal spec wise as they would have been able to offer at that time.
Hope this has helped and helps others, as I am convinced that the HTC Universal has batch's out there with faulty components that cause the devices to become hypersensative to heat and even under their OWN heat generated under normal use they power off as if the battery overheated or something onboard got too hot.
i have a N910C exynos version Note 4
history: my friend got it from dubai where her mother is working ( we're from Manila, PH ) and its dubai locked, we took it to tech for openline, after that everything seems fine, until it complety shuts down after 2 days...
problem: it cant boot up without a charger, but it does boot up if plugged, but then after few seconds it will reboot, the same process, will boot up then reboot...
Things we tried:
1. we tried to update it to latest lollipop, updated still have problems
2. we tried having a custom recovery ( philz touch ) it worked, but then i noticed it cant detect the percentage of battery ( its on 0% ) even though its charging while off
analysis:
1. software cant detect the battery percentage if not then 2
2. battery must be replaced if not 3
3. hardware problem
can someone make suggestions what to do, thanks
It's obviously 3.)
Contact a local Samsung repair center, or a certified repair center, and ask for a quotation.
Don't think it will cost you TOO much, like ~50-80 USD or so I think.
But that's a very-very rough estimation.
A new display with glass and all was 110$ for my Note 2.
But since I had insurance I only had to pay 10$ for it.
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
I am some what experience Android user. I installed several custom ROMs but the Optimized LineageOS 14.1-Beta5 I installed several days ago destroyed my phone. I was using the phone normally when all of the sudden it shutdown. I couldn't even go to a custom recovery. When I got home I tried installing Samsung firmware via Odin, but still phone couldn't boot up.
It is strange but when trying to load Odin mode, or custom recovery, or to try to load installed Android, phone sometimes gets random colored flashy lines and vibrations. Even thought my phone was dropped many times on hard surfaces, screen wasn't damaged. Looks like a hardware problem, but how can a custom ROM destroy hardware?
I tried to flash a firmware via Odin and I get <OSM> All threads completed. (succeed 1 / failed 0) but I can't boot into Android. Then I again tried to flash via Odin and I got stuck at <ID:0/008> system.img.ext4. Then after figuring out that this process is stuck I unplug cable. I again tried to flash another firmware and that was a success but I get "RECOVERY BOOTING..." in blue letter in upper left corner, with white Samsung Galaxy S4 logo.
I can't sideload a ROM since adb doesn't see my device.
http://prntscr.com/ecth8r
you really believe a rom can BURN your phone ?
Looks like a hardware fault to me.
Bro, it must be hw related. I had random slowdowns and had to restart device to properly use again. It was for months. Than my phone died, mobo / gpu, Dunno. These are hell of an old devices, and these parts last 2-3 years mostly. So contact a friend who has repair skills and go on. internals are around 30 bucks if I remember correctly. Drops, high humidity, vibration, all can Kill your phone in such a long lifespan,slowly, Silently. Im just a user but I can tell you that Nougat builds are the best roms that can be installed on your s4.
The fact that your phone died when you flashed that ROM is just coincidence.
If you buy and wear a new pair of shoes, and you somehow trip and break your leg or arm, do you blame it on the shoes?
Hardware damage due to custom ROMs is highly unlikely. People even overclock their CPU and GPU and it still functions properly.
Your phone simply reached the end of its life. GPU failure I'd say, because a malfunctioning screen has nothing to do with the phone's boot process. If it would a defective screen, your phone would still be able to boot, just that you would have distorted images.
The reason your phone boots into recovery and download mode is because those are very basic interfaces and they don't use the GPU.
The Android OS is more advanced and requires a GPU, which is why it won't boot. You can try flashing ROMs all you want, but the unfortunate truth is that your S4 is gone.
And it wasn't because of the ROM you flashed. Thousands of happy users of that same ROM, me included, can confirm.
Also, I want to mention that I'm not fanboying around.
I have been using custom ROMs since 2012 I believe, and have never had any serious hardware problems (fried CPU or anything) before. The only hardware problems I've had were bugs that made certain things (Bluetooth, GPS, Camera) not work properly, but those usually get fixed in future updates.
And in all those years I also haven't seen anybody say that using a certain ROM fried his device.
It is possible if you mess around with kernel settings (too high voltages or frequencies) to fry your phone. But I if that happens then it's pretty much your own fault, right?
Buy a new motherboard. It's fried. Very easy to swap out. If that doesn't work then your digitizer is shot. Better buy a new phone then. You can Change but better to start over.
Thanks everyone for you replies.
I will continue trying different things but GPU is probably damaged. It is shame that phone payed $700 3.5 years ago is dead...I will probably buy some Xiaomi.
Same issue. Using a damn slow Snapdragon 210 in a phone without any optimization. I'll wait for the next OnePlus or the next Sony X Premium.
About a year ago the battery started failing. I finally got it replaced 3 months ago. The new battery ended up being faulty (wouldn't hold charge) and I got it replaced a week later. This is when the phone started acting up. Random reboots when opening certain apps (camera, instagram stories, youtube). So I got the battery replaced again (for free). The issue went away for a week or so but it started acting up again. A week back the finger sensor stop working (maybe the connector got loose).
I'm thinking of sending the phone in to another repair place to check it up but I've got a feeling the phone is just not fixable. The Nexus was never officially released here (UAE) so there is no official support from the manufacturer.
Is it possible that the repair shop messed something up to cause the random boots? Either that or the phone is just dying. The repair place has refused to replace the battery again stating it's not a battery problem (it cost me $80 to get it replaced in the first place).
I've already reset the phone and that didn't make the problem go away.
Any possible solutions would be great cause I'm close to considering a replacement (OnePlus 6 maybe since Pixel is super expensive) even though I don't have the budget for it.
The phone isn't rooted and is running stock. I've only got 38 active apps so I run it quite minimal.
Android 8.1.0
Kernel 3.10.73-g309d642
Build OPM7.181205.001
Thank you.
EDIT: I'm open to the idea of rooting if it fixes the issues.
This sounds for me like the issue with BLOD - but partly. There is a case where the 4 big CPUs dont work any more like they should but the phone do not bootloop at the boot time but at random situations later.
This would probably help you much time going from shop to shop if you could test it out on yourself:
1. Flash TWRP 4-cores version recovery (unlock bootloader before that to work). But maybe also the regular version with all 8 core enabled could work. https://basketbuild.com/devs/osm0sis/osmods
2. Then use in twrp this zip file to set your android os from 8 to 4 cpu cores(from the same link i posted above): N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip
(full thread about that: https://forum.xda-developers.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515 )
If your reboots under load (your phone turns on the Snapdragon 810 BIG-cores to load the app) are then gone, then you know that the issue is on your big cores.