Develop Bugs

The "I can't update to Mango, My phone is bricked" thread.

Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.

Ok, so my phone is now dead. I don't know what to do..
Carrier O2 UK
Phone Model HTC HD7
Updating from nodo to mango
Problem Description: I didn't get an error code. It froze on the update at step 8 or 9 (restarting the phone) and now will not boot. It vibrates 7 times and stays on the HTC logo screen.
Please help me
It was updating for over 3 hours.
---------- Post added at 12:30 AM ---------- Previous post was at 12:00 AM ----------
Please someone help me?

Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-

Carrier ORANGE CARAIBES
Phone Model HTC HD7
Updating from NODO TO MANGO
Error Code
Problem Description: Can't boot anymore. I don't even can turn on the phone :/ My first problem on windows phone!

Chasseur d'étoiles said:
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Click to expand...
Click to collapse
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.

derausgewanderte said:
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
Click to expand...
Click to collapse
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..

mdjmurray said:
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
Click to expand...
Click to collapse
a hard reset on mine worked by pushing down power button, camera button and both vol plus and minus at the same time while the phone booted. I unplugged the battery, plugged it back in and then get the timing right to push the buttons down. Good luck.

Dead HTC Surround..
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all. Hard reset won't work. Acts like the battery is completely dead and USB port doesn't work. No lights, no beeps.. dead. Ugh.
Never installed any hacks, ROMs etc. I was 100% normal updates. Very frustrating...
This was actually my third attempt to install the updates. Previous times it had froze I was able to do a hard reset and restore the backup.
Anyone have suggestions? I've pulled the battery and it hasn't made any difference.

bbrian said:
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all.
Click to expand...
Click to collapse
This happened to my Omnia 7 while doing the final restart. It got stuck on the 'Samsung Omnia 7' logo for about 15 minutes. I just hit the home button and it finished booting.....problem solved.

Ok. Did you guys forced the update or waited for the official notification?

i got a message on my cell about it so i upgraded i i got a sdamsun focus v1.4

Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
VoodooKing said:
Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Click to expand...
Click to collapse

tamcdonald said:
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
Click to expand...
Click to collapse
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully installed it.
I believe that nobody is meant to do the disconnect trick and its best to just wait for the official update notice.

It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
VoodooKing said:
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully it.
I believe that nobody is meant to do the disconnect trick and just wait for the official update notice.
Click to expand...
Click to collapse

tamcdonald said:
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
Click to expand...
Click to collapse
That's good to know. Now we know one of the causes for the error message. Mine is unbranded 000-88.

bricked focus
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?

Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}

depdereck said:
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Click to expand...
Click to collapse
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.

aggelosss5 said:
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
Click to expand...
Click to collapse
Is your phone still working after the update? What are the version numbers? You can check in Settings > About

VoodooKing said:
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
Click to expand...
Click to collapse
It gets stuck there for a long time longest i let it sit there before trying another reset was about 45 minutes or so. I got Zune to recognize my phone and start a restore but it stopped again at the phone restart and sat there for about 30 minutes. I had to exit out to leave work and head home. I also tried to recover the phone with the Windows Phone Support Tool but that timed out at the restart as well and gave me an error code of 800004005.

[Q] Sony Service Centre guys Failed. Can anybody HELP!!

Hi,
My Sony Xperia Arc S (LT18a) has been stuck in SAFE MODE, i.e. none of the apps installed explicitly from Google Store are showing up. Only the ones those are default with the handset are working. Apart from this, the phone is working perfectly fine.
Though, the Menu key isn't working at all.
About 2 weeks back, it started with flickering of the menu options as if the menu key has been stuck. So I restarted my phone and since than it is in safe mode.
NOTE: The phone was bought from US and is currently being used in India since around 1 year. Also, the phone was upgraded to ICS using Sony PC companion.
Here are the things that I've tried:
1. Taking the battery out for sometime and than trying rebooting.
2. Rebooting the phone with Volume Down key.
3. Rebooting the phone with Volume Up key.
4. Rebooting the phone with Back key.
5. Reseting the phone to Factory Settings
and ...
6. Taking it to SONY Service Centre.
NONE of the above has been a success.
The Sony Service Centre guys kept the phone for 3 days and I guess that they must have checked the hardware for any faults, but didn't reported any. They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode. And they don't know why. Moreover they told that USB cable is not detecting my phone, so it took them more time to flash it. Since they couldn't help further and they returned it back.
(The phone is getting detected by USB on my machine though)
Am I left with any other options that I could try? Any help would be great.

Somebody asked me to Try the Update Service executable from Sony website.. Will let you guys know if it worked.

I'm not sure about India's laws, but in certain countries, law says, that if the repair is not finished and problem still exists, you may proceed to file a complaint against them towards certain agency. As I said, I am not sure, if such things exist outside EU.
Now, if you said that Menu button does not work even after repair nor flashing firmware, then it is hardware level issue, which means you can not do anything about it.

Well, first of all many thanks for your reply.
The law do exists over here too, but since this was bought from US and I tried to get it repaired with the Indian service center; they might not consider it as case an International warranty (or support) kind of a thing.
My model is LT18a (a for America), where as their International version of Arc S is said be as LT18i. Not sure if I can file any complaint for this.
I'll check that scenario.
BTW, I think you missed it:
"They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode."
Someguyfromhell said:
I'm not sure about India's laws, but in certain countries, law says, that if the repair is not finished and problem still exists, you may proceed to file a complaint against them towards certain agency. As I said, I am not sure, if such things exist outside EU.
Now, if you said that Menu button does not work even after repair nor flashing firmware, then it is hardware level issue, which means you can not do anything about it.
Click to expand...
Click to collapse

Phone goes into Safe Mode only, if Menu button is pressed during boot. If you are not pressing it, it is hardware level issue, because it does detect the press, although not being pressed.

Well, I'll ask the Service Center guys to give it another try with the hardware thing (which might be the root cause of it), but was just curious to know how things became normal (for a while) when they flashed my phone?
Someguyfromhell said:
Phone goes into Safe Mode only, if Menu button is pressed during boot. If you are not pressing it, it is hardware level issue, because it does detect the press, although not being pressed.
Click to expand...
Click to collapse

BlindDreamz1091 said:
Hi,
My Sony Xperia Arc S (LT18a) has been stuck in SAFE MODE, i.e. none of the apps installed explicitly from Google Store are showing up. Only the ones those are default with the handset are working. Apart from this, the phone is working perfectly fine.
Though, the Menu key isn't working at all.
About 2 weeks back, it started with flickering of the menu options as if the menu key has been stuck. So I restarted my phone and since than it is in safe mode.
NOTE: The phone was bought from US and is currently being used in India since around 1 year. Also, the phone was upgraded to ICS using Sony PC companion.
Here are the things that I've tried:
1. Taking the battery out for sometime and than trying rebooting.
2. Rebooting the phone with Volume Down key.
3. Rebooting the phone with Volume Up key.
4. Rebooting the phone with Back key.
5. Reseting the phone to Factory Settings
and ...
6. Taking it to SONY Service Centre.
NONE of the above has been a success.
The Sony Service Centre guys kept the phone for 3 days and I guess that they must have checked the hardware for any faults, but didn't reported any. They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode. And they don't know why. Moreover they told that USB cable is not detecting my phone, so it took them more time to flash it. Since they couldn't help further and they returned it back.
(The phone is getting detected by USB on my machine though)
Am I left with any other options that I could try? Any help would be great.
Click to expand...
Click to collapse
Flash it with stock firmware using flashtools. if it is hardware error cant help. if not flashing always helps

[Q] Phone got stock with HTC logo screen

I updated to the latest firmware version to be able to use Insert Coin 5.0.1. The problem is that after doing that, my phone is only showing the HTC logo and the white screen.
If I plugged it into the PC it recognizes the phone and when I boot it even plays the music, it is like it is working but I can only see the HTC white screen with the logo.
I have tried to install a custom recovery, trried to get back to stock but the problem is that I didn't have USB debugging enabled so ADB will never recognize the phone.
Is there any way to bring the phone back or did I just turned into an expensive paperweight?
Edit 1: My sister in law just called me and I was able to accept the call. At least that shows the phone is working, is just the stupid logo screen won't go away.
Edit 2: i went back to the previous firmware version, but the same issue remains. I don't know what else to do, any ideas please help!

I guess it doesn't matter anymore. I ended up buying a new M8 on Amazon...
However, if someone knows how to fix my problem, I would really love it to at least sell the one that went bad.

pinktheater said:
I guess it doesn't matter anymore. I ended up buying a new M8 on Amazon...
However, if someone knows how to fix my problem, I would really love it to at least sell the one that went bad.
Click to expand...
Click to collapse
what model is your phone ? you can RUU back to factory settings. all you need is the MID / CID and Software version (.401 / .521 / .502 /.1540 ...etc)
theirs also a bunch of stock nandroid backups here >> http://forum.xda-developers.com/showthread.php?t=2701376

qhsusb_bulk no download mode no recovery no bootanimation

Can anyone help me with this problem?? I tried many ways but there isnt anything possible. The community either ignores me or gives me a simple answer. Can anyone just give me a suggestion of what i cant do?

You can't do anything with it by the looks of things, it's gone.

me too.....

On the same boat but mine is being recognized by my PC.

Same here... some extra info.. but still broken.
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).

tacua said:
It happened yesterday. I have the H812 Canadian version. It just was suddenly, I wake up and pull it from the charger, read some mails during breakfast, go to work and then the screen didn't turn on. Holding the power button did nothing.
- Pull the battery, put it back, nothing.
- Then maybe I though maybe the phone didn't charged properly overnight and the battery died. I plug the charger and the battery logo pop-up 2 seconds later it boot up on the LG animation logo. It goes stuck loping there.
- After 30 minutes, holding power button did nothing, pull the battery. Always on the charger put the battery back and it immediately went to Recovery Mode and at the end showing "fastboot mode". What!!! I thought this phone bootloader is locked.
- I unplugged for the power and put in on the computer and it was recognized as "Marshall phone". I tested "fastboot devices" command and it was recognized. Well it could be recovered if I had a image that I could applied.
- I tried to applied a previous download KDZ "H81210H_00.kdz" even that my phone was already on "v10n". But fastboot didn't liked the kdz file format.
- Previously also I did a backup of the system partition but also the format is incorrect for fastboot.
- So no available files that I could apply on fastboot.
- I removed the usb and battery put it back. Black screen. Nothing.
- Plug the phone without battery on the USB and for my surprise the computer still recognized as "QHUSB_BULK" but not recognized driver. Which reading around, I understand is a Qualcomm low level mode to start up programming a device, but no information of how to do it.
- To go back fastboot, I had to simultaneously plug the USB and insert the battery at the same time. Sometimes even the fastboot gives an error that could start. Which it makes me think the phone ROM has a major corruption and it's booting on the emergency bootloader.
So, I didn't have time to keep playing around to see if I could do anything else. I drove to a Fido store and drop it to send it to LG for repair.
This is my first brand phone out of Nexus, I'm really disappointed with LG (actually this will be the case with any major Android brand phone).
- First there used to be a way to recover the current KDZ, now they closed the path.
- Later, only offers unlock boot loader on one model that is not in north america.
- No fastboot recovery images. Zero, nada.
So, many times I had bricked my Nexus phones by tweaking and playing around, and it always there is a way to recover it. The LG G4 brick itself on my pocket and I feel helpless to try to recover it. Even my wife iPhone's I have been able to restore them by downloading the full recovery image.
I'm seriously thinking resell my LG G4 as soon as it's back and go back to Nexus phones (5X).
Click to expand...
Click to collapse
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449

Done that
mb_guy said:
Look at the Canadian Thread in the general section, there are some direct links to kdz's there.
Here you go
http://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449
Click to expand...
Click to collapse
I had lurked this forums for 3 year now, and until now I signed up to post my experience. So yeah, I have looked on this forum and other sites for the correct KDZ. If you look careful on that post (as I did) that latest full LP version KDZ is 10h, which already have it for a while. However when this happened to my phone, it was already on 10n which is the version I expect to find somewhere to be able to recover my phone. Recently, I see that is available version 20e but that is already MM, I want to observe how it behave on the community before I decide to go there.
No matter what is the case, the phone was sent for repair. I think mine when under the worst case scenario of the so much mentioned bootloop. So much, that it even opened the bootloader and show me the fastboot prompt, although that the Canadian version is locked.
For my experience with the Nexus, they come with two bootloaders, the normal that can be updated locked and unlocked and a emergency bootloader that is available when the device is almost bricked and the normal bootloader is borked. Finally there is a low level manufacturer flashing that use the OEM SOC application to put the initial ROM. In the past I have been able to play with the Rockchip and the Nvidia Tegra 3, applications at that level. So those devices are simple "unbrickables". Low level Qualcomm (QHUSB_BULK) flashing is barely mentioned on the net, no process detailed, no application available so far that I can find.
My experience with LG so far is like buying a PC with installed OS, no recovery CDs, no website to download the recovery, no access to the BIOS, no "normal" human soul is allowed to create a full backup of the HD without going on a major hackaton with not assurance that what you get will work in future case of emergency. If something happens to the OS when you are out of warranty... you are royally screwed.

Guys try the oven method it may work. Some are saying it lasted 24 hrs others say its still active. It may be dangerous but worth a shot since no one else is taking action on this fix.

Also my phone was just rooted. At that time I wasn't trying to do anything with modifying but just using instagram.

[HELP][ISSUES][SM-A505F/DS] My Samsung Galaxy A50 is corrupted ??

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.