Database Users

[Q] Vega stuck?

Situation:
Advent Vega running r6 Modaco ROM by Paul
Ubuntu 10.10 desktop PC in case it's needed
Tried to activate the USB Host Mode, as I wanted to plug a USB stick
It had been done before flawlessly.
The device came to a black screen with a prompt: "Starting Fastboot USB download protocol".
The device is unresponsive. Powering off the device and turning it on again brings only the same black screen with the prompt.
I've read somewhere that it's not bricked, but I certainly can't bring it to work. Has anyone encountered this issue?

Re-flash original rom from recovery. Power off and fully charge. Then hold down the back button for 2 sec then power for 2 sec then back for 2 sec. You also need to install the recovery drivers from the advent website. Not sure how that goes with ubuntu. Good Luck

First of all, thanks for your help.
Sigh. I've tried putting the device in Recovery mode (with a timer to count the seconds for every press) and the same Fastboot screen appears.
The lsusb command doesn't return any changes after plugging the Vega either, so I can say the computer is blind to the device. I have another Android device which is recognized flawlessly.

It took me a few attempts to get my device into recovery. Just keep trying with the device plugged in to your pc, eventually i got a unknown device in hardware manager. I then had to install the recovery drivers to get the device to show up.
I dont use ubuntu so cant tell you if its any different.

Oh,, it is. Nobody programs drivers for Linux, and Advent is no exception. I guess I can try and... compile the Windows ones?
For what it's worth my device is not recognised no matter where I plug it, so adb is out of the question.

Using a windows pc would be the easiest. Advent only likes windows for the time being. Sorry i cant help any further, i am not a Linux user.

Then I'll try tomorrow in college. Thanks for your help!
...Forgot to ask: Has anyone had the issue I'm reporting and successfully solved it after flashing?

I've never heard of a Fastboot prompt before, however, as far as I know, getting in to recovery should always be possible.
1) Get the screen on (doesn't matter what is on it).
2) Make sure it is unplugged.
3) Hold power for ~7 seconds until the screen turns off.
4) Plug it in and wait for the charge light.
5) Plug in the USB cable.
6) Hold back.
7) While holding back, press power for 1 to 2 seconds and release (keep holding back)
8) Within 2 seconds you should hear the PC's found USB noise (the screen will not turn on)
9) Once you hear the PC's USB connect noise, you can release back, install the nVidia driver (not ADB driver) and run the FW updater.
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.

rpmccormick said:
PS: I think devs would actually be interesting in getting it in fastboot mode. I wonder how you did that.
Click to expand...
Click to collapse
I *think* I got that prompt because my device was already in USB host when I intended to toggle USB host. However, it's kind of disheartening to hear that the issue is new...
Shall I post a picture of the prompt?

Here is a (regrettably very poor, I'm no photographic whiz and the college lightning conditions are horrible) picture of the Fastboot prompt I receive.
{
"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've tried to enter Recovery mode today in one of college's computers (Windows XP). The device was recognized as "Nvidia ANdroid Fastboot device" after executing the recovery mode operation successfully. I was prompted to install the drivers, which I did, I was warned that they were unsigned, but on executing the Advent updater I had the following output:
Pressing Enter leads to the console closing and no changes have been done on the device: I'm not told that the image has been installed or anything, the Fastboot screen is still there, and powering on and off does bring me to the same than before.

Hi - I'm now in the same situation with the Fastboot error and no recovery no matter what I try.
Have you been able to boot to recovery / flash your Vega or is it still sitting with the error message ?

I'm going to try again today (Free day, no college )

A re flash will sort it out. I done it 5 times in the past 2 days to test CWM. Just count 2 seconds back button, 2 seconds back and power and 2 seconds back button alone again and it will be in recovery. I do it every time first time. It's just a matter of getting used to it. Then plug the vega in and it will recognise it, you will see by starting the original 1.08 firmware again, the vega screen is blank, no back-light.

I couldn't do it yesterday, but it worked today. I am now on stock 08 and I'm very happy. Thanks for all the help!

Help recovering Samsung Galaxy Note 3 contents

Hi all, I have a Samsung Galaxy Note 3 and I dropped it on the floor. On the outside, the phone is fine but when I try to restart it, it gets stuck on the splash screen as per this picture
{
"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"
}
So, I researched XDA forums and someone suggested pressing the Home+Power+Volume up. When I do it, it just enters a loop vibrating every 10 secs (approximately) with a black screen as per this picture
Continued researching XDA forums and found another post telling me to try pressing Home+Power+Volume down to enter an emergency menu. I did so and got the following screen with 2 options (Continue or cancel). I chose continue
When I pressed the volume button up, it showed me the following screen, and stayed there for at least 10 minutes
This reminded me I tried to install a new ROM about 2 years ago (this was my first Android phone), didn't work, but the phone worked well until I dropped it, 2 years after I tried installing a new ROM!
So, I tried repeating the same steps, but this time cancel it. It was stuck in the splash screen again.
In the meantime, I got myself a new phone and the only thing I want to do is to recover the pictures and videos I had in the Note 3.
When I connect the Galaxy Note 3 to my laptop using the original cable, when it's stuck on the splash screen, the laptop doesn't recognize the device and therefore doesn't read the content. The same applies if I press Home+Power+Volume up or Volume down.
What are my options? Is it possible to recover the phone maintaining the contents? Is there a physical device I can use to recover the data (ie. dismantle the phone and read the "hard drive" directly)?
Any help will be very appreciated. Many thanks in advance!

It seems a hardware problem, 'cause it occurs after a shock.
But, before going to panic or to pay a repair, you can try to extract the battery (though maybe it was already got off the phone on the fall).
Wait a minute or so, then re-connect the battery, restart the phone and pray...
Try again the Recovery mode : the home >vol up>power buttons (press Power as the last button). If you enter recovery, make a Factory reset.
If not Recovery, go to download mode, as your 3rd photo. Flash a STOCK firmware, this will not change your Knox.
It is all I can say about. Maybe another more expert member can give you better advice.

Still no joy
aftnoon2 said:
It seems a hardware problem, 'cause it occurs after a shock.
But, before going to panic or to pay a repair, you can try to extract the battery (though maybe it was already got off the phone on the fall).
Wait a minute or so, then re-connect the battery, restart the phone and pray...
Try again the Recovery mode : the home >vol up>power buttons (press Power as the last button). If you enter recovery, make a Factory reset.
If not Recovery, go to download mode, as your 3rd photo. Flash a STOCK firmware, this will not change your Knox.
It is all I can say about. Maybe another more expert member can give you better advice.
Click to expand...
Click to collapse
Hi afternoon2 - thank you for your help. I have removed the battery and restarted the phone 1 million times. Unfortunately, it never progressed beyond the splash screen.
When I go into recovery mode (Home+Power+Volume up) it goes into vibrating cycle but never displays anything on the screen as described.
Any other suggestions folks?

even with it doing all that, can you hook it up as a us b device to get your data?

gad42000 said:
even with it doing all that, can you hook it up as a us b device to get your data?
Click to expand...
Click to collapse
Hi gad42000 - thank you for the suggestions. Nope, when I plug in the phone via USB I can't see the phone on the laptop and therefore can't access any of the folders.
Is it possible to read the "hard drive" via some other hardware?

If it's a hardware problem (which I also believe it is) what can I do to recover the data?

I would in your shoes .
Install Samsung USB Drivers .
Change USB Port and change USB cable .

JJEgan said:
I would in your shoes .
Install Samsung USB Drivers .
Change USB Port and change USB cable .
Click to expand...
Click to collapse
Hi JJEgan - thank you for the suggestion. I have installed the Samsung drivers via Kies and the cable is brand new. How do I change the USB port?

I think he means try different USB ports on the computer.

audit13 said:
I think he means try different USB ports on the computer.
Click to expand...
Click to collapse
Hi audit13 - thanks for clarifying. Do you have any other suggestions on how to retrieve data?

Recuva if you can connect .
Or a Data Recovery Service may help but expensive .

dquelhas said:
Hi audit13 - thanks for clarifying. Do you have any other suggestions on how to retrieve data?
Click to expand...
Click to collapse
What do you mean by "data". Your media, photos, etc, or the apps data?
My advice is to enter download mode, flash through Odin stock firmware and see what you get. Pick up the know how in the "General" forum of this device.
If success, you will not lose your media data.

If you can get the phone recognized by the computer, you could flash twrp, boot into twrp, mount the data partition, and copy the data to the computer.

JJEgan said:
Recuva if you can connect .
Or a Data Recovery Service may help but expensive .
Click to expand...
Click to collapse
Hi JJEgan - thank you for the suggestion. Any chance I can dismantle the phone and read the drive (ie. like the ones you connect hard drives to and mount as a USB)?

audit13 said:
If you can get the phone recognized by the computer, you could flash twrp, boot into twrp, mount the data partition, and copy the data to the computer.
Click to expand...
Click to collapse
If the computer read the device, then he can recover not only the media but also the whole device by flashing it's latest firmware via Odin!

Marvino. said:
If the computer read the device, then he can recover not only the media but also the whole device by flashing it's latest firmware via Odin!
Click to expand...
Click to collapse
Apart from what flashing the firmware wipes .
<Hi JJEgan - thank you for the suggestion. Any chance I can dismantle the phone and read the drive (ie. like the ones you connect hard drives to and mount as a USB)? >
NO its nand memory .

Marvino. said:
If the computer read the device, then he can recover not only the media but also the whole device by flashing it's latest firmware via Odin!
Click to expand...
Click to collapse
A phone maybe recognised by a computer but that does not automatically mean Odin can be flashed.

I think i broke my Redmi

I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?

1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)

Danoz88 said:
1. Deep flash cable is to open the edl mode (not fastboot) and yes the screen is black in edl (download mode)
2. Make a clean flash and try it with qfil
3. You can find videos on youtube how you can fix redmi 4 prime hard bricks (complete guides)
Click to expand...
Click to collapse
ok new problem, i plug the deep flash cable and it says hardware malfunctioned repeatedly
this one scared me and the device cannot charge
i'm thinking about test point method but i have to wait ordered small torx driver on monday

UPDATE:
After using test point. nothing changed except the device ID number is weird
{
"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"
}

How is it displayed in fastboot mode? Deepflashcable also doesn't worked for me because I read that on the newer rom's the edl mode is blocked so no chance with dfc anymore (thanks xiaomi...). It only reboots if I tried everything (commands,dfc,file..).
I had to flash an older version first via fastboot mode. After this I was able to reboot into edl mode with 0 problems. And I never tried the test point methode, not the right tools.

cant goto recovery, cant go to fastboot, test point tested 2nd time and its work.. flash success
but the screen still blank.
if i plug my usb cable to laptop its onlt shows MTP and green led light

I Know How To Fix This...
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
---------- Post added at 04:29 AM ---------- Previous post was at 04:23 AM ----------
rs168 said:
I bought my first redmi ever that is used phone and the previous owner said "its stuck on Mi logo after updating SU"
I tested the device first with these conditions
1. plugged to charger and its charge properly (led is on)
2. cannot go to recovery or power on (had to use deep flash cable to get into fastboot)
3. used deep flash cable, Quacomm shown and installed properly
4. Flashed the image. its says success but i accidentaly look at most bottom window. its says "flash_all_lock.bat"
5. unplugged the cable tried to turn on, it doesnt work
help me .. did i miss something here?
EDIT:
1. plugged to laptop, it says usb malfunctioned unlike before
2 is it normal if i get into fastboot using deep flash the screen show nothing?
Click to expand...
Click to collapse
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .

amangupta711 said:
First Go to miui Fastboot page. Read the instructions and do as said till decompressed the file. Then Just connect your Phone while in Fastboot mode and enable adb and fastboot driver by double clicking on both respective bat files on your pc. Then Just Double click on [flash_all_except_data_storage.bat]. Your phone will reset and restart. If any problems contact me at [email protected] .
Click to expand...
Click to collapse
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same

Try this!!!
rs168 said:
nope, cannot go to fastboot or recovery
flash succeed with test point method but the screen went blank after tried to power on the device
EDIT: forgot to mention, flashed with global stable, china stable , china developer.. the result still the same
Click to expand...
Click to collapse
Hold power and vol down button for 20 sec.

amangupta711 said:
Hold power and vol down button for 20 sec.
Click to expand...
Click to collapse
it has been said.. nothing

How to bypass fastboot low battery warning / FAILED (remote: Warning: battery's capacity is very low)

Hello Everyone I'm writting this post to hoping that This would help many people. Because I didn't find any proper solution for this on the internet.
Scenario: Suppose you flashed wrong file or did something wrong and somehow you bricked your device in such a state where your device will only go to fastboot mode stable or unstable fastboot mode ( fastboot restarts itself after few seconds).
Means your boot/recovery all destroyed. Luckily your bootloader is unlocked. So you felt realx thinking that you can flash recovery/boot from fastboot to fix your device. Then you flashed an image through fastboot and saw an warning like " FAILED (remote: Warning: battery's capacity is very low)".
{
"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"
}
Thats when the problem begins .
It's because before device got bricked it had very low charge. And without boot or recovery image your device don't know how to charge itself. So weather if your device is in fastboot or edl 9008 don't expect it to charge itself. And by fastboot rule it won't accept any file if it has low battery.
For exactly below 3478mV any file writing is unacceptable.
I found a solution on XDA How to fix the 'Low Battery' fastboot loop . Basically it's a fastboot script which restarts bootloader in a continues loop to charge it in the mean-time of reboot to fastboot.
Code:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
I mean no disrespect to that post, The way it was trying to do it maybe it make some sense but not much.
Because like others I have run this script for several hours for several times and got no result. I was running this script on laptop then i thought maybe laptop is not giving proper output delivery. Then I tried with my desktop back usb port but no good.
Instead for running this script so long that in those thousands reboot my device surely lost some of its lifetime early and it corrupted my internal partition which I've discoverd after fixing my device.
Ok then the next option I had was opening the backshell which I don't want. Tried customer service they denied because of unofficial device. Local shops failed also they tried to open back shell but I didn't let them.
So your'e basically doomed like me because Brands like realme doesn't provide any flash tool/flash tool credentials for free. And remote unbrick is very much costly.
Solution:
After trying many things I found an App on play store Called Bugjaeger Mobile ADB - Develop & Debug via USB OTG.
Requisitions :
1. NO Root Required
2. App itself
3. Good OTG cable
4 Proper USB cable
5. Nothing else
For stable fastboot user:
First download the app in a device which support OTG connection. plug in otg cable.
Now connect your device to other device via OTG in fastboot mode. Now press on < > This icon and type your command like you do In pc
for example "fastboot flash recovery" after recovery give a space and click on attachment icon in the top right corner then select your file. Then run the command .
Boom you have successfully ignored fastboot low battery warning. Enjoy.
For unstable fastboot users:
I have calculated that my device was restarting in every 5 secons. could be different for you.
So what I did. Before going to fastboot mode the app show some AD.
so first disable it by adding private DNS like dns.adguard.com or better turn off wifi/mobile data.
Then suppose you want to flash recovery so make copy of command 'fastboot flash recovery" this will save 2 seconds and keep your file in your root directory so it will also save time. After everything set hit flash As soon as possible.
My recovery size was 98 mb and It had only 2 seconds to push it to the device. It said " sending recovery ok- writing failed" so you better use good cable.
Means it was able to successfully sent the file but didn't got image writing status because your device got turned off. But don't worry.
sent the img file was all the things we needed. I tried it 2 times and it works.
If it is unclear please watch the video to how to use this app
Tips:
1. Never do any risky task with low battery .
Conclusion : I'm not responsible if anything goes wrong with your device. I shared it only thinking that this will save many people from hassels.
Thank you.

So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?

mike_san said:
So you need a second device via OTG to fix the unstable bootloader?
My case is that the phone works perfectly, IMEI wifi calls etc, recovery works aswell but fastboot is broken.
Restarts after 2 or 3 seconds while holding the button, If release the phone will just boot normally.
This happened right after trying to lock the bootloader again coming from realmen UI 2.0 beta
Any thoughts?
Click to expand...
Click to collapse
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?

Bishnu840 said:
Yes seccond device will ignore low battery or any other warning.
in 2-3 seconds your device get detected in fastboot?
did you checked that in device manager of windows?
Click to expand...
Click to collapse
I've to run; adb reboot recovery, then in stock recovery I can run 9008 qualcomm state and it is detected by windows.

I has the same problem, but only with recovery flashing. For other partitions flashing works correct.
I just deleted recovery:
Code:
fastboot erase recovery
Аnd the problem is gone.
Now i can flash it:
Code:
fastboot flash recovery recovery.img
Device: Oukitel k7 power.
Sorry for bad englich.

An error has occurred while updating the device software

Hi!
So my phone is stuck with the "an error has occurred while updating the device software" and that screen only shows when i charge my phone with wall brick. If i try to connect my phone with usb to pc nothing happens.
Even if i try to enter download mode. Any suggestions what I can do?

Try using the power button for a hard reboot.
If it got a low battery % you could let it discharge until shutdown. Generally this isn't practical.
Just another reason I don't allow updates...

blackhawk said:
Try using the power button for a hard reboot.
If it got a low battery % you could let it discharge until shutdown. Generally this isn't practical.
Just another reason I don't allow updates...
Click to expand...
Click to collapse
The phone is "dead" the hard reboot wont help. I get the error screen when i put in the charger, if i connect it to the pc nothing happens and the screen is just black. Doesn't matter if i try download mode, recovery mode or just hold the power button.

Chekhn said:
The phone is "dead" the hard reboot wont help. I get the error screen when i put in the charger, if i connect it to the pc nothing happens and the screen is just black. Doesn't matter if i try download mode, recovery mode or just hold the power button.
Click to expand...
Click to collapse
You could try pulling the battery connector... hard reboot.
If that doesn't work, it's bricked.

blackhawk said:
You could try pulling the battery connector... hard reboot.
If that doesn't work, it's bricked.
Click to expand...
Click to collapse
The battery connector?

Chekhn said:
The battery connector?
Click to expand...
Click to collapse
The connector to the battery itself.
A true hard reset.

blackhawk said:
The connector to the battery itself.
A true hard reset.
Click to expand...
Click to collapse
I have managed to connect the phone to the pc, but the new issue is when i try to start Odin the phone just restarts instantly.
{
"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"
}

Chekhn said:
I have managed to connect the phone to the pc, but the new issue is when i try to start Odin the phone just restarts instantly.
View attachment 5395719
Click to expand...
Click to collapse
Was Odin working before?
Check Windows Event Viewer for error messages. Latest version and drivers? Roll back or update drivers as needed.
Try another port.
I have zero experience with Odin. If you can't solve it and no one else responds to this thread, start a new thread for this issue. Lots of help here for that! Google search as well with XDA in the search parameters.

Chekhn said:
Hi!
So my phone is stuck with the "an error has occurred while updating the device software" and that screen only shows when i charge my phone with wall brick. If i try to connect my phone with usb to pc nothing happens.
Even if i try to enter download mode. Any suggestions what I can do?
Click to expand...
Click to collapse
Once again check with your PC driver manager. Please confirm it's shows unknown driver or samsung device...if it shows unknown driver, then it happens only connected on bricked phones

Just happend to me too, Odin got stuck when flashing vendor.img (S10+, SM-G975).
For anyone getting here during research, THIS was my life saver:
How To Fix "An Error Occurred While Updating The Device Software" On Galaxy Smartphone? - SamsungSFour.Com
How To Fix "An Error Occurred While Updating The Device Software" On Galaxy Smartphone?
www.samsungsfour.com
tl;dr: after installing the tool (windows, I used it in a W10 sandbox VM on my linux host; make sure to pass the USB device into the VM!)
1) Connect the phone, make sure upper right hand dropdown lists it.
2) Ignore the "Please select your device" drowdown, leave it at "SC-01C". S10 Series isn't in there anyhow.
3) Select "SoftBrick Fixer"
4) Press "Hijack it!"
5) Phone should reboot and be in DL mode again
6) Flash again from ODIN with a GOOD cable and a DIRECT connection to the Host!
HTH.

PokeRekoP said:
Just happend to me too, Odin got stuck when flashing vendor.img (S10+, SM-G975).
For anyone getting here during research, THIS was my life saver:
How To Fix "An Error Occurred While Updating The Device Software" On Galaxy Smartphone? - SamsungSFour.Com
How To Fix "An Error Occurred While Updating The Device Software" On Galaxy Smartphone?
www.samsungsfour.com
tl;dr: after installing the tool (windows, I used it in a W10 sandbox VM on my linux host; make sure to pass the USB device into the VM!)
1) Connect the phone, make sure upper right hand dropdown lists it.
2) Ignore the "Please select your device" drowdown, leave it at "SC-01C". S10 Series isn't in there anyhow.
3) Select "SoftBrick Fixer"
4) Press "Hijack it!"
5) Phone should reboot and be in DL mode again
6) Flash again from ODIN with a GOOD cable and a DIRECT connection to the Host!
HTH.
Click to expand...
Click to collapse
thank you so much you saved my life, you're a good man

Doesn't work on S20 FE