Question Stuck in boot loop after firmware flashing attempt, please help - Samsung Galaxy A32 5G

1. I forgot to do the oem unlocking for the bootloader
2.i tried to root my phone with odin3
3.my phone was softbricked with the light blue error screen that had a waring in english,koren
4.I tried to flash a stock rom potentially of the wrong kind of A32 and the wrong CSC
5. Now the phone no longer turns on unless plugged to a computer, which makes the screen turn on and off continously. The screen is completely black when on for half a second.
What are my options in fixing my phone? If the correct CSC is needed, how do I discover it with a frozen phone such as mine?

If the device does not boot, you probably flashed the wrong firmware and corrupted the bootloader. Unfortunately there is nothing you as the end user can do to recover your device. Seek professional repair.

Related

FRP lock = In between a rock and another rock

My phone began lagging last night so I gave it a restart. The shut-down animations were normal but when the phone turned back on, it gave me the dreaded FRP LOCK curse. I went through many forums and videos and I was able to take the lock off via FRP Hijacker, but now I am stuck at the download mode. If I try booting the phone on with the stock recovery, the Samsung Note5 splash screen stays indefinetly (soft brick). If I try booting the phone with a custom recovery, I get a message in purple text saying "Recovery image signature check fail. Reboot to avoid Warranty bit set" and it will keep bootlooping. Currently, I am not sure how to continue if I cannot get to the recovery mode and flash a ROM. So basically, I am stuck at not being able to flash a rom, nor being able to get into recovery mode successfully without a brick or bootloop. Any help is greatly appreciated.
Edit 1: USB Debugging is turned on as well as OEM Unlock
you need to use odin and downgrade to a stock 6.0 tar file..or use a conversion tar file taking you from n920p to n920f..or n920c ...ill upload the files everyone needs after work today...

I need some help with a sm-g930f that wont boot ANY stock rom. Just boot loops.

So im trying to fix a freinds phone. He said it randomly shut off and started bootlooping on the samsung screen. So I flashed the same firmware using odin. It succeded restarted and still does the same exact thing?
No matter what I do I cannot get this damn phone to boot up. After holding vol down and power to soft reset it goes to a screen with a triangle and says installing update then to no command. If i soft reset then hold vol down and home with power download mode will come up. I cant get this phone to go into recovery the combination just brings me to the triangle screen. Maintenance mode wont even come up the triangle screen shows instead. I have knowledge of odin and flashing. Ive been flashing since the motorola cliq lol But this is making me scratch my head...Any ideas?
I want to add that when it freezes at the samsung logo the logo corrupts and gets black lines through it then restarts several seconds after?
Are you flashing all 4 firmware files with Odin or just AP?
Of course I am. I even went ahead and flashed another "non carrier" firmware to see if it made a difference and no luck.
BL
AP
CP
Home_CSC, I flashed the CSC when flashing a different firmware.
By the books and nothing seems to get this phone booting.
Have you tried just normal CSC? Home_CSC keeps data, it's basically acts as an in place upgrade rather than a fresh image.
If you're having issues you'll want a full clean wipe which means using CSC.
When trying a new firmware I flashed the "CSC" because it contains the pit file. So yes I have and that didn't work either.
The phone gets to download mode which tells me its not a brick. Still says "samsung official". FRP lock is off.
And just waiting it out doesn't work? Flashing from a custom Nougat ROM to stock Oreo was like 10+ minutes on the Samsung logo for me.
No as I said in op it always freezes at the Samsung logo over and over and over again.
My best guess is the system partition is corrupt and is un-repairable or the hardware was defect from the factory...but the phone has been In use for 2 years flawlessly...besides that it still boots up Odin(download) mode....so... Does anyone have any idea wtf is going on with this phone? Because anything I do just won't boot it normally. I can't root it and try a custom rom because "OEM unlock" isn't enabled. So WTF?
Please does anyone have any idea what is going on here?
I had some luck with getting it to the bootloader by using odin to flash the corresponding BL file. Then I flashed a combination file obtained from hardreset. But I am still stuck bypassing the FRP lock myself. Either I flash stock rom or firmware with ADB. It always get an error cllose to the end. Or the flash finished and the warning message is still there and I couldn't get pass the google authorisation stage.

[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.

Bricked LG G6 H870, tried it all

Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.

Hard Bricked a Samsung

Hello there, short story, flashed with odin 3.12 the stock firmware a SM-531F Grand Prime, and the power got cut in the middle of the phone flashing, after i restarted the phone, he ran in Emergency Donwload mode, requesting kies recovery, i tried to reflash the firmware, but odin said is failed, i though if i restart one more time will be fine, and from this point, the phone have absolute 0 life, is not booting, is not vibrate, no light, doesn't make connection even with the pc, what should i do? as i think the phone is still locked up in that edl session, exist a test point method or something? i really need to revive this phone.
I know there is a solution, thins thing could happen on any samsung, did someone faced the same problerm?
Did you try to flash the stock rom again?
Just try flashing stock ROM again.

Categories

Resources