I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.
Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.
Service Center in Slovenija
badtzo said:
Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.
Click to expand...
Click to collapse
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:
U should have done factory reset by stock recovery and bring binary count to 0 by that. I had same problm. Went to service centre there they told to replace motherboard which was almost costing very high. Luckily I had made everything on phone normal before going to service centre so I had done all in warranty《free》
Sent from my GT-N7100 using XDA Premium 4 mobile app
starlut said:
I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.
Click to expand...
Click to collapse
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .
zeeshanonlyme said:
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .
Click to expand...
Click to collapse
i tried to flash the stock rom. its not flashing the kernel. and, I don't know whats wrong with it.
I don't have warranty and I am stuck in it.
aNtRx said:
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:
Click to expand...
Click to collapse
Sorry to hear that, but they told you nonsense. If it's really SDS they have to repair for free. Ask a friend in your country who is envolved in legal things, a lawyer best.
One in general: As long as one can start eg. download mode, it is no SDS, mostly a software prob.
Related
I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
I'm experiencing something similar except i'm running AGAT's tFH13 rom and kernel.
Every time I get the phone into recovery or even download mode, the phone just reboots itself.
Out of curiosity I opened the mobile odin app and it gave me an error saying it could not detect the device model. -_-
bas85 said:
I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
Click to expand...
Click to collapse
Can you dump a logcat and attach?
(From ADB Shell)
Code:
logcat -d -f /sdcard/logdump.txt
Might help explain what's going on.
bas85 said:
I've done some research on this and haven't found and answer, so im putting it out there for you guys to get at me and let me know. I have been experiencing Rolling restarts on my phone. The phone will boot up fully, but randomly it will just restart it self. At times if I just push the power button, to turn of the screen, the phone will restart again. The phone also has an issue of staying in black and not coming back on, so I have to take the battery out in order for me to get it back to boot up.
Notes:
Im running EL29 Stock. Nothing special at all.
If there is a thread already created for this, I apologize, but ive looked and I couldn't find it.
Click to expand...
Click to collapse
That's pretty odd, I don't think I've ever heard of something like that happening unless there was something physically wrong with your phone.. have you ever tried to use Odin to reinstall a stock Rom? & out of curiosity do you have an antivirus app?
I did the Reflash back to stock through odin. Took it to sprint this morning though and found that it was a bad battery. So easy fix but annoying problem.
And with that being said, It did it to me again! Guess that wasn't the issue.
j7jman said:
That's pretty odd, I don't think I've ever heard of something like that happening unless there was something physically wrong with your phone.. have you ever tried to use Odin to reinstall a stock Rom? & out of curiosity do you have an antivirus app?
Click to expand...
Click to collapse
I have used Odin to reinstall a stock rom before. I do have an Antivirus app called Lookout. It might be something physically wrong with the phone at this point im not sure what to do.
*update* Just took it back to sprint and they replaced it for me for free. Went from black to white
I've been trying to flash it back to stock to take it to sprint but my phone just keeps rebooting even whilst in recovery mode. :-\
Sent from my cm_tenderloin using Tapatalk 2
bas85 said:
*update* Just took it back to sprint and they replaced it for me for free. Went from black to white
Click to expand...
Click to collapse
How long have you had your phone? I am having the exact same issues. My 1 year Samsung warranty expires on the 15th...
Was your phone rooted when you brought it in?
twoslo said:
I've been trying to flash it back to stock to take it to sprint but my phone just keeps rebooting even whilst in recovery mode. :-\
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I would say keep trying. Mine was doing that too but it finally held out long enough once to not restart on me. What I did was i just tapped the screen ever 10-15 seconds. Not sure if that did anythign or if I was lucky but It made it through.
MoMatt said:
How long have you had your phone? I am having the exact same issues. My 1 year Samsung warranty expires on the 15th...
Was your phone rooted when you brought it in?
Click to expand...
Click to collapse
I had my phone for less than a year. I had a sprint warranty and the Samsung 1 year warranty. Both covered this issue with no problem. I suggest taking it in if you cant find a solution to the problem. But if your rooted. Flash back to stock.
I was able to restore to a previous backup. From there i got Mobile Odin working and was able to flash the FH13 OTA, rooted though. I still can't get the power button to work and its still randomly rebooting but not as often. Still trying to get the phone to STAY in download mode to flash to stock(unrooted) with Odin.
twoslo said:
I was able to restore to a previous backup. From there i got Mobile Odin working and was able to flash the FH13 OTA, rooted though. I still can't get the power button to work and its still randomly rebooting but not as often. Still trying to get the phone to STAY in download mode to flash to stock(unrooted) with Odin.
Click to expand...
Click to collapse
You can possibly take the "risk" but I took mine that was a Rooted Stock version, and it passed their software test, so they gave me the new phone. Also if its rebooting as much or as fast as mine was, Its hard for them to even run a real test because the phone wont give them a chance to. Its up to you tho to make that decision.
Finally got the phone to stay in download mode and i was able to flash the Unrooted FF18 OC.
Reboots are fewer now but power button still doesn't work. I checked my account and my phone is still under 1 year warranty & i have the insurance. I'll be heading to sprint after work today.
Thanks for your tips and replies. :good:
Same issue. The power button on this phone is iffy. At least i think that's the problem
Swyped from a Galaxy S2 on CM10
update : they are replacing my phone because the power button is broken
It's gonna be a few days till I get the new one, tech says they are back ordered?
The stability and shutdown issues for me seem to be caused by a bad battery. Brought it into Sprint and they gave me a new one, no charge. Seems to have solved the problem.
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
machdown said:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
Click to expand...
Click to collapse
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
BCSC said:
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
Click to expand...
Click to collapse
I entered download mode and dont see flash counter anywhere. I got the warning screen were you have the option to restart or download.
Ya I entered recovery and did a factory reset but nothing. Really cant do anything with charging port broken.
I sent it in anyways for repairs. Hopefully they just replace it
I'm having the same problem with my Gs3 with CM10 4.2.2 running. Thought this would help.
Sent from my SPH-L710 using xda app-developers app
Hi friends!!
After my S4 decided to run away without insurance I had to revert back to my s2. It still had Hellybean on it so I upgraded it to PA 4.45 just to check it out on my phone. Then I went into the instructions on how to unlock the phone. I went to revert it back to stock ICS that it came with to do so and when I rebooted it gets stuck at the samsung logo that pulses. I can't get into recovery but I still can get into download mode but nothing works when flashed. I tried using ODIN for every stock ROM available and still nothing. I never bricked a phone before and this doesn't seem like one to me since the bricks I fixed before have never been able to go into DL mode without being jigged, Can somebody help me. I need this running asap for medical reasons. I'm a sitting duck without this phone if something should happen to me. I live alone and have no land line if I need to call 911.
ScottPomroy said:
Hi friends!!
After my S4 decided to run away without insurance I had to revert back to my s2. It still had Hellybean on it so I upgraded it to PA 4.45 just to check it out on my phone. Then I went into the instructions on how to unlock the phone. I went to revert it back to stock ICS that it came with to do so and when I rebooted it gets stuck at the samsung logo that pulses. I can't get into recovery but I still can get into download mode but nothing works when flashed. I tried using ODIN for every stock ROM available and still nothing. I never bricked a phone before and this doesn't seem like one to me since the bricks I fixed before have never been able to go into DL mode without being jigged, Can somebody help me. I need this running asap for medical reasons. I'm a sitting duck without this phone if something should happen to me. I live alone and have no land line if I need to call 911.
Click to expand...
Click to collapse
Are you trying to boot into recovery while you are plugged into a computer?
Sent from my SGH-T989
jrc2 said:
Are you trying to boot into recovery while you are plugged into a computer?
Sent from my SGH-T989
Click to expand...
Click to collapse
Of course not. But I think the problem may be that I didn't know that Kies was still installed in this computer.
And removing Kies didn't work either. I was talking to a guy that does jtag repair near me he said try that first. Gave me a pit file and it didn't help.
ScottPomroy said:
Of course not. But I think the problem may be that I didn't know that Kies was still installed in this computer.
And removing Kies didn't work either. I was talking to a guy that does jtag repair near me he said try that first. Gave me a pit file and it didn't help.
Click to expand...
Click to collapse
Here is something something that has worked for me twice. Use JOdin3 ( https://builds.casual-dev.com/jodin3/) Plug your phone in before going to the websute and put the TWRP tar file in PDA. Click start. It will say it needs to obtain a pit file. Click OK. Ignore the part about using in the download mode combo. It should bootloop your phone and you then might be able to unplug your phone and boot into recovery. I use this as a last resort but it has worked twice for me.
Sent from my SGH-T989
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
Hi, I recently bought this new phone (Galaxy A50) from the official Samsung Store (11/7). The phone came with a software version:
PDP: A505FDDU1ASBD
CSC: ASB7
Security Patch: 1 February 2019
After sometime, I decided to start rooting my Galaxy A50 following the steps in a thread on XDA (created by @geiti94). Unlocked my bootloader and rebooted to the system, I setup the phone without my Samsung and Google Acc, and I switched off the phone then entered the download mode. I put the TWRP Magisk Patched file at the AP section in Odin and unticked everything except Flash Lock. Warranty void (Knox tripped). Everytime I restarted the device, I have to boot rooted with Magisk (Recovery) or else I will lose magisk. It turned out to be true and bricked my device:
"Only official released binaries are allowed to be installed".
I then downloaded the stock firmware files (ASBD) from Sammobile.com and reflashed it back to the device. Success flashing stock without any problem then I set up the device, plugged in and went to sleep. I didnt know what did happen while I was sleeping and when I woke up, my phone had the OVERHEATING WARNING (device was hot) and the system was already switched off my device automatically. I took off my phone casing and I found out that my phone casing was wet. I didnt know where the water came from and I didn't even know when it got there. I'd never thought that the water could flow into the phone since it was very little. I switched on my device without hesitation. Right after it switched on, moisture has been detected in my usb port. I switched on the device and took out my sim card and ext mmc, I put it in front of the fan and let it sit for like 5 hours. The phone was okay. Phone rebooted normally and I didnt face any unusual behavior from my device.
Within 30 minutes of using the phone, I received Device Overheating Warning again, apps were closing and device was shutting down (physically the device wasn't really hot). It was warm. I let it cool and I received no more overheating warning. Suddenly, the device was being abnormal. It went to:
1. Screen locked itself and display lockscreen. I unlocked it back and it locked itself back. It happens frequently.
2. Screen locked itself and display lockscreen and the screen will on off like something was playing with the power button. It got crazier when I tried to charge the device, the 'display on off' went faster. Then, i could no longer use my power button to unlock since device didnt let me get to my unlock screen.
When it happened, I couldnt shut down my device using the normal way. I had to hold my power button and (-) volume button to restart my device. Device rebooted, 3 minutes and it went strange again.
I was frustrated and clueless. Went into safe mode and getting the same result. I tried reflashing the firmware again and it was being normal until i finished device setup then it happened again. I thought it happened because I tripped my Knox.
Tried different method. This time I downloaded and flashed stock firmware (A505FDDU2ASH3).
PDP: A505FDDU2ASH3
CSC: A505FDDU2ASH1
Security Patch: 21 August 2019
And same issues occured. This time:
1. From getting locked itself and display will 'on off', this time it eventually went locked itself (noticed 'screen lock sound') and nothing i could do to unlock it because the power button had no function! But I could reboot manually by holding (-) volume and power button! Stock recovery mode everything was okay. Display, power button and volume up and down button is okay. No issue in that mode.
2. Attempted factory reset and tried setting up again. Right after it displayed 'Phone is starting' it locked itself again. Reboot again. I quickly swiped my finger trying to not let it locked itself again. It worked and prevented the device from locking again. I realized that my UI didnt respond when I used the volume button to increase/decrease the volume. Power button only responded to lock screen and didnt respond to unlock it back but the device was still on.
Since Knox had tripped, I tried another solution. I rooted the device just like how I done it before. I still believed that it was firmware error not caused by any faulty in my hardware component. I installed TWRP w Magisk Patched, multidisabler, and flashed a stable custom kernel (SkyKernel V1.2 by @AlexGeek3) that worked w my device, and yes device worked normally. Magisk installed. Safety net verified. I disabled some pre installed Samsung Apps and Services (e.g. Find My Mobile and screen lock service) that maybe would be the caused. Just when I set up my Google Acc, the issues occured again. When I checked my CPU and battery temperature using kernel tweaker (installed alongside SkyKernel V1.2) and noticed that the temperature reading was so high (70°C-90°C) but device wasnt even hot. This had become very strange ?
Then I decided to bring it to the mobile repair shop. He said it may happened when I downloaded the firmware files using Mobile Data, so the files downloaded weren't accurate since the network is unstable and told me to bring it to the Samsung Service Center. Then I tried to get help from Samsung Official:
1. Chat through Live Support: He told me that Sammobile.com wasn't authorized by Samsung. He told me that maybe hardware faulty issues because it had contact with water. Told me to bring it to Samsung Service Centre.
2. Called Samsung Hotline: She told me it happened when device had been root. And nothing I could do to unroot it back and asked me to go to Service Center instead.
3. Called Samsung Hotline: He told me that it might occured since I downloaded the files using Mobile Data and even that I had successfully flashed the firmware, the problems existed because the downloaded files had corrupt. He told me to just go to official service centre and tell them to flash the official stock firmware and check if the issues persisted.
4. Called Samsung Hotline: He told me since device had been rooted, warranty was voided and there would be NO WAY TO UNROOT THE DEVICE. Hence, I would have to replace the motherboard to be able to use the device again.
Each time I called the hotline, I spoke to a different staff. I explained thoroughly to each of them the issues I was currently facing at the moment and how/when it started to occur. All of them had a different explanation and the same solution. I called them again & again because I wanted to find the most least solution I could find to the major solution to fix the device. I was trying to make sure if the issues still happen after clean flash install official stock firmware, only then I will take further actions to check on my hardware.
Concluded myself to bring it to the Samsung Service Center and flash the official stock firmware for my device. (60 Km away from my place). I called them a day before going to the SSC to ask about the process and cost to do it. Next day I went to the SSC. Cut it short, I explained to the staff from the beginning. I wasnt really satisfied because she didnt pay attention to what I was explaining. And because of that, she printed out the agreement and asked me to sign it. I read it patiently and I was confused when I looked at the Details of Problems section and my warranty status was still VALID but device stated that my Warranty was already voided ?
Problems: Phone can't switched on. Scratch on the side housing. Water damaged.
I looked at her again and asked her if she really confirm about the problems. She said that the technician will check the hardware and told me to wait an hour for them to check the hardware. She called me again within 1 hour and I was really disappointed by the fact that they said my hardwares were water damaged and the repair cost is 3/4 the price if I buy a new same device. If that would be the cost, it would really better if I just buy a new phone ? I disagreed for it and asked if they could reflashed the official firmware for my device. She said yes but my warranty status will be discontinued, and they would take no responsibility if the problem still occured. But if I agree w them to repair it and pay 3/4 for the replacement, my warranty will be extended ? such a an idiotic way to make your customer pay you such costs.
W/out further due I told them to reflash/clean installation full official firmware for my device and they kept repeating the same thing again that they took no responsibility blablabla and I just nah just do it la haih ? and ended the call.
Arrived SSC later after 30 mins, I thought that they had done the job. No. Another disappointment, most stupidest reason that I had to accept from them. They were telling me that if I flash the official firmware, my warranty will be voided and they take no responsibility for it. What the heck? I already allowed them to do so, and that was the reason why I came to the SSC, and even my warranty was voided because I had tried customization using unauthorized firmware for my device. I asked them to take a picture of my device hardware or maybe bring it to me because I wanted to have a look at it but they denied my request (That repair cost is to replace new motherboard, new usb charging port, new lcd display and new battery).
Exhausted, angry, and disappointed by them, I requested them once again to flash the official firmware and I didn't care about what would happen afterwards. They told me to wait a couple minutes until their technician completed the flashing process. Such an utter bull****, they told me that my device couldn't being detected by the PC since my USB Port was damaged. I took the device, left with frustration. I have wasted my time, energy and money and didn't even get what I wanted.
To sum up everything:
Samsung Service Centre:
1. SSC: Phone couldnt boot/switched on.
Truth:
But even until today I still can switch on my device.
2. SSC said the charging port had been damaged but until today I still can charge the phone. Its only couldn't be charged when it is switched on because device will detect overheating and stopped the charging progress.
3. SSC: Charging port is damaged so USB data transfer to the PC cannot be used. PC won't detect device.
Truth:
But still, up until this day I could still make a data transfer, flash firmware using odin.
4. SSC: LCD Display is damaged thats why it doesnt display correctly.
But recovery mode and download mode didnt have the same issues only. Issues happen when device boot the system.
Firmware:
1. Firmware wasn't downloaded correctly using Mobile Data.
2. Security services provided by Google and Samsung could be the reason.
3. Knox had tripped (e-fuse) and forced the firmware to crush itself causing damage to the system. (I am not sure abt this, based on what I had read)
4. Replace a new motherboard because the current motherboard could no longer be used after device has been rooted (?)
Hardware:
1. The water may have caused little damaged to the hardware.
2. Flex cable connectors (LCD Connector, Charging Connector, Power/Volume Connector) need to be replaced.
3. Check the CPU and properly apply a thermal paste and check if the problems solved.
Any help is really helpful and appreciated ???
that's one wall of text if i ever seen one.
post a very concise tl'dr at the bottom if you want people to help my man
who tf gon read this mf frfr ??
Hi,
A sensor will probably have been damaged, since the A50 does not have any IP protection in that case I cannot help you
hi guys
I need help. I have a galaxy a50 with firmware version as A505FDDS9CUI4(android 11) but recently after an OTA update I have started getting issue where in the device restarts automatically and sometimes even gets stuck in the booting process. So I thought of downgrading the device for fix but I am not able to downgrade as the firmware that I wanna downgrade to, is A505FDDS7BUB5(android 10) and the binary number for both the firmwares is different so I am getting error in odin. So if I root my phone and install custom recovery(TWRP) and flash custom rom, will it work? or will it get bricked in the process? is there any way that can fix this issue because as of now samsung has not recognised this issue officially and many other samsung device owners of A and M series are facing this issue. Any help would be appreciated guys. Thanks.