Develop Bugs

Can't boot into recovery mode... Bricked?

I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.

You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your problem
Click to expand...
Click to collapse
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.

OK, found this which seems to indicate I may be able to salvage data. Thanks for pointing me in the correct direction. :good:

I've got a followup question, if you don't mind. I've followed the instructions in the referenced article and Odin is reporting the following:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
I went to lunch, so I don't know how long it's been on the NAND Write Start!! but it's going on about 2.5 hours from when I clicked start and the process started going. The top left box is white and outputs SBL2. Should I continue to wait or start thinking something is broken/hung at this point? TIA!

Just updating the thread in case I can (a) solve the problem and (b) folks find it useful.
I have tried Odin 3.07, 1.87 and 1.83 to no success. They all seem to fail in about the same way, either at sbl2.mbn or at NAND Write Start!!. Waiting anywhere from 10-30 minutes doesn't seem to change anything. I've tried different cables and USB ports. I don't have another computer to try. Currently researching whether I should try to include the PIT file and if doing so will result in data loss.

wnoonan said:
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.
Click to expand...
Click to collapse
Well if that's the easier option, send me the S3 lol.

bilgerryan said:
Well if that's the easier option, send me the S3 lol.
Click to expand...
Click to collapse
Well, at some point you cut your losses. At this point I've spent the better part of 7 hours trying to get the phone recovered in some fashion. Multiple versions of Odin. Multiple USB cables. Multiple USB ports. Currently installing the Samsung USB drivers on another PC to try it all from there. I'll admit it, I'm not a cell phone developer (I'm a data center guy, want to know how to setup DFI, why you use FabricPath, what ACI is, why you use a pVC, how to setup OTV, etc. I'm your guy). I don't know the in's and outs of what a PIT file is, what it means when the phone just sits there at NAND Write Start!! and does nothing, and I can't seem to find an answer. Every article I can find seems to indicate I'm doing exactly what I'm supposed to be doing, but nothing works. I'm certainly open to ideas, but so far I'm not getting anywhere really.

And FWIW, I just fired up Odin3 v1.85 up on a totally different PC, with yet another totally different USB cable (so I'm not 0 for 2 on PC's, 0 for 3 on cables) and it's the same result. Starts the firmware update, sbl2.mbn goes, the next message is NAND Write Start!! but no progress is made and in the top left box, it's simply white with "SBL2". Clearly something isn't write, but just as clearly I'd be danged if I can figure out what it is.

bilgerryan, a question if you don't mind. You said "Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin." I have to confess, I have no idea what ND8, MK3, MD4, etc are, but at the QBKing77 link he mentioned a TAR file at a hotfile.com location, but that link appears to be dead. So I subsequently (after doing more reading in more threads) went here to grab what I presume is a valid TAR file, which I then extracted into a MD5 file. Odin seems to find it to be valid, but again it never seems to update. Any ideas? TIA!

OK. If anyone else happens to run across this thread, here are the things I attempted:
cf auto root chainfire - didn't work. It actually seemed like it was trying to copy, but would stop about halfway and never finish.
Tried the following ROM's. None of them would get past the NAND Write Start:
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
Tried multiple PC's, cables, ports, you name it.
Currently the phone won't even power on anymore. Not sure if the battery is just dead (tried another old battery, same result) or if the phone is just outright dead.
If this happens to you and you can figure out how to recover, you're a better man than I. Near as I can tell it's pretty much a total loss when this happens.
HTH.

[Q] Soft bricked Note 2 I317m

Hi guys. I'm trying to fix this phone for my brother. He said he went to factory reset and wiped his phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I put it in ADB mode to show more of the messages. I never flashed anything from ADB)
So it looked like he managed to wipe his systems so I downloaded Odin, installed the drivers and got the stock firmware from sammobile for his model. When I tried to flash it fails. I am not sure what I can do from here. Is the phone done? The previous forum threads were suggesting turning on USB debugging but the system isn't even on the device anymore for me to enable it.
I was thinking maybe I can flash it through recovery but I didn't find anything on google that said I could do that.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUDNH2_I317MOYADNH2_I317MVLUDNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance. Any help would be greatly appreciated.

So I tried flashing a custom recovery both through Odin (get failed message) and through recovery (get cant mount /cache and /cache recovery)
So is this phone bricked?

any news? I have exactly same problem.

Same problem here, my friend's N7100 Hong Kong Version is dead just like this.
Stock 4.4.2 rom, not rooted, same message in recovery mode and Odin.
Please help!

Same here, stock recovery can't mount anything, ODIN mode can't flash anything, I think it is EMMC brick bug. N7105
Kicking myself for not copying a recent backup to external SD (it is on now inaccessible internal SD). Would be good if I could flash a decent recovery with some tools to try to get the internal SD card mounted, but I think nothing can be flashed at this point.

My SGH-i317M 16GB with Telus also suddenly failed to boot, and failed to flash using ODIN as well. After sent to several shops, including one which can perform JTAG flashing, confirmed that the eMMC is damaged.
This is not a simple software bug in eMMC, but a hardware failure, which requires to spend several hundred dollars in part and labour to replace the eMMC (embedded MMC 16GB NAND flash memory).
According to my weeks long research in the internet, this seems like a eMMC IC manufacturing problem on 16GB Note2 models in early release phones back in 2013, but not affecting 32GB model.
There are several users reporting that they used non-Samsung charger to charge the phone, including me, who use car charger. Poor quality charger somehow can shorten the life of the eMMC 16GB IC, and the phone will either slowly has storage corruption in this 16GB storage (which stores mount points /system, /data, /user). Unluckily this storage memory also stores the bootloader, recovery screen, charger percentage, Android OS, as well as user data + apps.
For me, it first reporting data issue by showing "I'm Lucky" button after booted up, which I though it resolved by factory reset without realize this is an early symptom of eMMC damage/failing. After 3 weeks, it stuck in boot screen, but manage to go to recovery screen, and neither Samsung Kies nor ODIN can write to the eMMC storage. This is later confirmed by a technician who has JTAG equipments/software that the eMMC is not writable at all, and needs to be replace.
The Android app that you can found on internet for the "fix" is actually a workaround, which will do a write test to identify bad block in eMMC storage which failed, and prevent the phone from using those areas to store any data. This app doesn't fix the hardware failure, which needs to be physically replaced. Theoretically, it can be replaced with 32GB eMMC IC but I don't find anyone posting the picture or model of the 32GB eMMC for SGH-i317M, as well as nothing for international model - i7100. If you are DOS users who used a floppy disk before, this is alike a dirty floppy disk with bad block, which the chkdsk utility can mark the FAT area for bad cluster to prevent DOS to write any data into those area. It is near impossible to repair the floppy disk to recover the bad cluster, unless replacing the disk.
For those who read this post early, and their phone is early release, and using the bad eMMC IC, I will advice to root it and install custom ROM which can boot from external fast microSD card, in addition of not using car charger and only use Samsung charger. This should prolong the time of eMMC lifespan
Hope this clarify for all users who has a failing eMMC chip, and be proactive about it

possible hard brick gt n7100

Hi everyone,
I ve been using a note 2 gt n7100 for 2 years .Since i ve got in my hands it was rooted with custom rom.Everything was fine,as i always was reading the instructions of every forum out there.
Its been a week that i ve installed a cyanogen build rom 6.01 ,my phone was working properly and i had no problem till yesterday that i ran out of battery and since then my phone is stuck at rom logo.
It cant even enter recovery mode ,only download mode .
In the download mode i can see my device name and my phone appears in ODIN.
But i cant write nor a stock rom,or bootloader or recovery even using pit files that i fould in the internet.
it is stuck oin download mode.
Can y give me any advice someone?
Is it hard brick?

what messages do you have in Odin?
it seems like SDS

yaro666 said:
what messages do you have in Odin?
it seems like SDS
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Rimotomos said:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to take out sim & sd before flashing.

malyshbo said:
Try to take out sim & sd before flashing.
Click to expand...
Click to collapse
i already did.
i also tried to flash only pit file ,only recovery,only bootloader and always the same
I tried to flash all above again with pit file together but again fail
------
my samsung appears as gadger serial in devices.is this a problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried HEIMDALL frontend and i get same fail about the pit file

seems your problem same as me bro. ran out of battery and cannot even enter recovery ( actually can but cannot go further such as flash rom or restore nandroid. ) dont panic. get another battery to test. i also panic when try anything but only download i can enter. at the end, i found my battery is totally dead after i try another battery. so buy new battery and phone back to normal.

fonblets said:
seems your problem same as me bro. ran out of battery and cannot even enter recovery ( actually can but cannot go further such as flash rom or restore nandroid. ) dont panic. get another battery to test. i also panic when try anything but only download i can enter. at the end, i found my battery is totally dead after i try another battery. so buy new battery and phone back to normal.
Click to expand...
Click to collapse
unfortunately,new battery didnt work

SM-T110 Stuck on Boot Loop

Hello All,
I have a Samsung Galaxy Tab 3 Lite (SM-T110). Recently, the phone crashed, and now stuck on boot loop. I tried to access the Recovery Mode to Clear Cache and perform Factory Reset, but the device keep rebooting with Samsung Logo. If I access the Download Mode, it works. I'm unable to find the official/stock ROM, and don't think a custom ROM will work without custom recovery.
I need assistance to get the device running again (Hopefully without clearing the data) ..

Flash TWRP using Odin 3.07 or newer:
https://drive.google.com/open?id=1yPxGpaMGSPHNckZ-UUISpqUWARNBCLC2
Select file in PDA, and UNCHECK AUTO REBOOT, exactly like in the image. After it finish upload image, hold power button. After successfully reboot, hold power + volume up + home till you get recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, you can flash ROMs using recovery. Just put zip on SD CARD, insert it on tablet and chose to see External SD CARD files, when press install.
Note, if you stuck in recovery, you need to flash stock recovery and start again .. .
Make sure you reboot tablet from stock recovery to unstuck it.
Here's stock recovery:
https://drive.google.com/file/d/1iSkrzZgTxjYNgyGsBeyWZZeMOGuoUnOn/view?usp=sharing
If you still don't rescue it, use this tutorial.
Download links are in description
https://www.youtube.com/watch?v=e7o3e6Km640

adryyy said:
Flash TWRP using Odin 3.07 or newer:
https://drive.google.com/open?id=1yPxGpaMGSPHNckZ-UUISpqUWARNBCLC2
Select file in PDA, and UNCHECK AUTO REBOOT, exactly like in the image. After it finish upload image, hold power button. After successfully reboot, hold power + volume up + home till you get recovery.
After that, you can flash ROMs using recovery. Just put zip on SD CARD, insert it on tablet and chose to see External SD CARD files, when press install.
Note, if you stuck in recovery, you need to flash stock recovery and start again .. .
Make sure you reboot tablet from stock recovery to unstuck it.
Here's stock recovery:
https://drive.google.com/file/d/1iSkrzZgTxjYNgyGsBeyWZZeMOGuoUnOn/view?usp=sharing
If you still don't rescue it, use this tutorial.
Download links are in description
https://www.youtube.com/watch?v=e7o3e6Km640
Click to expand...
Click to collapse
Flashing T110.TWRP.2.7.0.1.tar.md5 didn't work .. Odin gives "Failed" .. Tried the video, fails also ..
When I try to flash the TWRP, I get the logs below on the Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110.TWRP.2.7.0.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I started to believe this is a hardware malfunction .. Could be fried ROM

Did you tried to flash full ROM? You have a Youtube link in my post.

What is your country? I found my Stock ROM from a site (i don't remember) Maybe I can send you a Stock ROM!

Secure Check Fail: Flash Error SM-G9860

I tried to install a new firmware from Sammobile with odin on my SM-G9860. I deleted my Samsung account before, but not my google account. However, after the flash process, I get Security Check Fail: dtbo (9)
this phone has been flashed with unautorized software & locked. Call your mobile operator for additional support. Please note that repair / return for this issu may have additional cost.
Is there a solution to my problem
Thank you

Have you tried to reflash by going back into download mode?

Yes, I can return to download mode with the plus and minus buttons and the USB cable.
View attachment 5110515
And when I restart
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to flash the original firmware e.g. I get AP in Odin Fail
FRP is enabled, not allowed to download non-frp boot binary
View attachment 5110545

Knolle100 said:
I tried to install a new firmware from Sammobile with odin on my SM-G9860. I deleted my Samsung account before, but not my google account. However, after the flash process, I get Security Check Fail: dtbo (9)
this phone has been flashed with unautorized software & locked. Call your mobile operator for additional support. Please note that repair / return for this issu may have additional cost.
Is there a solution to my problem
Thank you
Click to expand...
Click to collapse
Which FW did you attempt to flash? The only FW you can flash on an SM-G9860 is Hong Kong, Taiwan and China.

I use Odin v3.14.4 and i have uses G9860OZS2BTI8(TGY)
https://www.sammobile.com/samsung/g...e/SM-G9860/TGY/download/G9860ZHU2BTI8/386039/
From the 5 files i can only Update BL and CP:
BL_G9860ZCU2BTH6_CL19350423_QB33763291_REV00_user_low_ship_MULTI_CERT.tar
CP_G9860ZCU2BTI8_CP16839570_CL19705706_QB34403288_REV00_user_low_ship_MULTI_CERT.tar
from the other 3 Files i get Error
if i use the AP file i cet a error: <ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8343 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> super.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

is my Handy damage? i dont found any Solution?

Try with smart switch Emergency mode.

The Windows version of Samsung Smart switch reports the connected device is not supported.

Knolle100 said:
is my Handy damage? i dont found any Solution?
Click to expand...
Click to collapse
Your SM-G9860 is the China variant, correct? Did you use a VPN to install Google Services? I would remove any Google related services/apps before flashing. Here's an article which may help.
https://www.comparitech.com/privacy-security-tools/blockedinchina/android/

yes, this is a China Variant (CHC) buy from tradingshenzhen.com. but what does that mean for my problem? I had previously installed Google without any problems. I had problems with the Samsung health app that does not work without a China secure account. That's why I tried to install the Hong Kong (TGY) firmware. Without success as can be seen. Instead, I now always get the error message due to the activated FRP.

Knolle100 said:
yes, this is a China Variant (CHC) buy from tradingshenzhen.com. but what does that mean for my problem? I had previously installed Google without any problems. I had problems with the Samsung health app that does not work without a China secure account. That's why I tried to install the Hong Kong (TGY) firmware. Without success as can be seen. Instead, I now always get the error message due to the activated FRP.
Click to expand...
Click to collapse
There's a conflict due to China’s Security Policy regarding Google Services. These steps will deactivate FRP which is causing the error.
Go to Settings.
Tap Accounts or Users & Accounts.
Select the account type, which in this case would be Google.
Tap the email address.
Tap the menu icon (three vertical dots) on the top right-hand corner.
Tap Remove account.
Confirm by tapping Remove account again.
Uninstall all Google Apps on your device then attempt flashing the TGY FW.

The phone no longer starts in the operating system. I only get into recovery or download mode. So I can't adjust my account.
I also cannot install an alternative recovery like TWRP because of the OEM boot lock.

Knolle100 said:
The phone no longer starts in the operating system. I only get into recovery or download mode. So I can't adjust my account.
I also cannot install an alternative recovery like TWRP because of the OEM boot lock.
Click to expand...
Click to collapse
You're screwed, a bricked device isn't worth much. MAYBE Samsung can offer tech assistance over the phone but that's doubtful, you'll likely need to send it in for repair. Unfortunately the China variant of the SM-G9860 is the worst.

Yes, that's the way it is, I contacted the dealer and asked for a solution. If I'm unlucky, this has been my greatest damage in recent years that I have caused myself.

Knolle100 said:
Yes, that's the way it is, I contacted the dealer and asked for a solution. If I'm unlucky, this has been my greatest damage in recent years that I have caused myself.
Click to expand...
Click to collapse
Try flashing your original firmware and go through the same process with your new firmware but remove your Google account.

Firmware can no longer be flashed, not even the original one.
The error message FRP is enebled, not allowed to download non-frp abl binary always appears

tradingshenzhen just sent me to the XDA forum. If all else fails, I have to send the device to China and there will be costs. Somehow I still can't believe that there is no solution. I have had so many devices that have gone through flash processes of any kind without any problems. But the S20 + is a stubborn goat.

It is weird that it started the flash and FRP is active. It shouldn't have started.
I mean it first checks if the device has google account, if there is the flash will not start but in your case the flash started and finish 50% and couldn't continue the full flash.
You can try to flash the "combination rom"
https://samsungfirmware.net/samsung-galaxy-s20-plus-5g-sm-g9860-repair-full-firmware/
https://androidfilehost.com/?fid=4349826312261811315
https://samsungcombinationfile.com/samsung-sm-g9860

I need A Binary U2 File. the last firmware that was installed on the phone is G9860ZCU2BTH6 However, I cannot find a combination file.
When I use this Rom [up_vnROM.net]_COMBINATION_FAC_FAQ0_G9860ZCU1ATB8, the following error message appears:
When I use this Rom [up_vnROM.net]_COMBINATION_FAC_FAQ0_G9860ZCU0ATA6 the following error message appears:

I think I need a current (CHC) firmware which has no problem with the FRP. So newer than (CHC) G9860OZL2BTH6 from September 6th, 2020
However, since I tried the latest TGY (G9860ZHU2BTI8) from October 4th, 2020 and the security gate was activated, all other firmware versions are older and it would therefore be a downgrade. As far as I know, a downgrade does not work with the manufacturer recovery. However, a TWRP does not work because of the OEM lock.
Either there is an FRP disable program via Odin or a firmware that is FRP enable.