A51 black screen - Samsung Galaxy A51 Questions & Answers

Hi, i unclocked the bootloader and flashed updated to Android 11 on my A51 few weeks ago and everything was going fine until yesterday i plugged it into charger and after a few minutes when i tried to unlock the phone, the screen doesn't show up. eveything's black. i tried forced restart method and other possible methods but none worked. the display only shows samsung logo while restarting and while in recovery and download mode but once it restrats completely, turns black again. i thought relocking the bootloader will do the job so i go to download mode and select LOCK BOOTLOADER( i didn't know if it was correct as i have 0 knowledge regarding these). and then it's stuck in download mode and no methods worked to get outta it.after a few hours, several while vertical lines and then blue dots(in the corner and surrounding the fingerprint sensor) start appearing on the screen and increases gradually with a break. however, i was able to install the custom firmwire (android 10) {although samsung officially released android 11 on A51s} using odin and then wipe the phone completely but now it restarts and then back again on the black screen. what can i do now? thank you

Related

My Galaxy Tab 7.0 plus (GT-6200) suddenly died, help please!

The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.

[Completed] My SM-G925F (Vietnam) Keeps Rebooting and Hanging after October Update on MM

Dear Support Team,
Please note that I am facing this issue since 1.5 Months, after update by samsung official. My Phone automatically downloaded update and install the update of October 2016. After that my phone turn itself off and keeps rebooting.
Rebooting Types:
1. Reboot properly come upon HomeScreen, when I try to unlock homescreen It goes again hang first then reboot.
2. While rebooting itself it stuck on Samsung S6 Edge and Andriod Logo.
3. While Rebooting itself Samsung logo came and again screen off and reboot.
Note: In all rebooting case my SM-G925F Vietnam Country's Phone. LED Light Blinks White Color, Some times White Light blinks Like On...Off...On...Offf, and Some time White LED Notification Light Keep on.
In this way I tried multiple times pressing 3 buttons (V-Up+V-Down+Power) Same time it get off from stuck and white led off and Phone Starts Properly. and Sometime I try to go Recovery Mood by pressing (V-up+Home+Power) buttons, and try to Reboot to bootloader, then my phone comes alive properly.
I tried rooted successfully one time also, and tried also Install Stock Firmware from Samsung-firmware latest one also.
and I am unable to install any other old update of Marshmallow because my Phone says B:4 K:2 CheckFail.
Please help me.
Regards,
Ali
[email protected] said:
Dear Support Team,
Please note that I am facing this issue since 1.5 Months, after update by samsung official. My Phone automatically downloaded update and install the update of October 2016. After that my phone turn itself off and keeps rebooting.
Rebooting Types:
1. Reboot properly come upon HomeScreen, when I try to unlock homescreen It goes again hang first then reboot.
2. While rebooting itself it stuck on Samsung S6 Edge and Andriod Logo.
3. While Rebooting itself Samsung logo came and again screen off and reboot.
Note: In all rebooting case my SM-G925F Vietnam Country's Phone. LED Light Blinks White Color, Some times White Light blinks Like On...Off...On...Offf, and Some time White LED Notification Light Keep on.
In this way I tried multiple times pressing 3 buttons (V-Up+V-Down+Power) Same time it get off from stuck and white led off and Phone Starts Properly. and Sometime I try to go Recovery Mood by pressing (V-up+Home+Power) buttons, and try to Reboot to bootloader, then my phone comes alive properly.
I tried rooted successfully one time also, and tried also Install Stock Firmware from Samsung-firmware latest one also.
and I am unable to install any other old update of Marshmallow because my Phone says B:4 K:2 CheckFail.
Please help me.
Regards,
Ali
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried kies/smartswitch emergency firmware recovery ? That should return your phone to stock
Good Luck
Sawdoctor
Dear I have tried Kies it said no phone connected found. It shows and connected in ODIN app. But not showing in Kies.
Smart Switch have only option to transfer data from old phone to new phone. Otherwise there isn't any option to firm in mobile.
Please guide me.

Help required S7 DUOS [SM-G930FD] hanging during update after flashing stock ROM.

I have been given an S7 SM-930FD [Dual Sim] that was supposed to be bricked. It wouldn't boot into anything but I have successfully got it into download mode and been able to successfully flash a stock ROM downloaded from Sammobile [several times] with no errors. Each time I have used the full set of AP,CP,CSC files and the previous owner is not sure what ROM it was on or what he tried to install. I have tried different versions of the firmware for this model for various android versions and regions simply to try and get it to boot, but without success. I have tried HOME CSC and CSC files too.
But each time it starts to install the update / reboot it hangs. Either when it installing the update on the blue screen with the robot and its "erasing" - small rotating symbol just stops and nothing happens OR it loads to the GALAXY S7 normal boot screen then hangs.
When it hangs it will only respond to one key combination Power + Vol Down. It then "switched off" and will not reboot in any mode. When I say "switched off" I mean the screen goes black. However if I then connect the charger, it won't show the charging symbol UNLESS I leave it for a few hours and the battery goes flat. It will then charge and I can boot into download / recovery mode but normal boot starts installing the update and it will hang all over again. On one occasion it hung with and black screen and blue flashing light but again no key combinations worked and I had to wait for the battery to drain.
Also tried Smart Switch Emergency Recovery. Even with the drivers freshly installed it does not recognise the phone, it does accept the model number during initialisation, but once the S/N is entered it comes back and says it can't find the model, S/N or IMEI in the database!
I have researched the web for hours and watched every relevant youtube video and tried their suggested key combinations etc and they just don't work.
So I'm hoping someone can help me resolve this frustrating situation, not least because of the delays between attempts!
Presumably as I can consistently get it into download mode there is a solution out there somewhere???????
What am I doing wrong? Should I be looking at a custom ROM or trying something else?
All help appreciated.

Need help after failed rom install

I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.

[sm j730f] Bootloader fail and TWRP boots into black screen

Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.

Categories

Resources