Really sunk. Can anyone help? - Samsung Galaxy S20 / S20+ / S20 Ultra Questions &

Long and sordid tale, but here I go (apologies in advance for length):
* 2 weeks ago an OTA update was available and I initiated the download and update right before going to sleep. I wake up to a blue screen that says unauthorized software had been flashed and I'd need to take the phone to the carrier and could be charged for repair
* Completely uninitiated to ROM flashing, after googling, downloading Odin 3.14.1B (patched) and 3.14.4 along with the latest Tmobile firmware, I try to no avail to get the firmware flashed. I figure it's because I don't have USB debugging selected and have no way to get to the option. Holding the up volume and Bixby keys could not get me to the bootloader either. By chance try to restart the phone one last time and boom, it works!
* I enable USB debugging, I back everything up. Everything seems fine. A week goes by, I'm working in an app, it hard freezes, and in trying to restart it happens again.
* Luckily, I still have everything I downloaded, and this time it was a quick task to flash the firmware and get everything working again. Post flash, the bootloader worked and I took the opportunity to clear the cache. I thought I finally cleared out whatever problem I was having with a clean download and cleared cache.
* Another week passes and tonight, same thing. Working in an app, freeze, restart, and blue screen. Frustrated, but I knew the fix. I attempted the same thing, but Odin 3.14.1B hangs at initializing for 30 min. I stupidly disconnect the phone and close Odin with the intent of starting the process over. Now I can't even get to the download screen or bootloader and a new error message reads: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
* Smart Switch does not recognize a device and in attempting the recovery option there are no devices listed.
* In googling, I've found that if I immediately hold the up and down volume buttons right after restarting, my pc recognizes the device and Odin shows it as being added. I try flashing using the same ROM (G986USQU1ATCU), it gets pretty far and I'm encouraged, but then I get the following FAIL error:
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> quest.fv
<ID:0/003> testvector.fv
<ID:0/003> spunvm.bin
<ID:0/003> persist.img
<ID:0/003> carrier.img
<ID:0/003> dqmdbg.img
<ID:0/003> userdata.img
<ID:0/003> metadata.img
<ID:0/003> misc.bin
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 8868 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> aop.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> NON-HLOS.bin
<ID:0/003> dspso.bin
<ID:0/003> km4.mbn
<ID:0/003> storsec.mbn
<ID:0/003> sec.elf
<ID:0/003> bksecapp.mbn
<ID:0/003> tz_iccc.mbn
<ID:0/003> tz_hdm.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> uefi_sec.mbn
<ID:0/003> multi_image.mbn
<ID:0/003> vbmeta.img
<ID:0/003> vaultkeeper.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> super.img
<ID:0/003> dtbo.img
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And a message in red letters on the phone appears at the top left that reads: SECURE CHECK FAIL : super Image Extract failed. Googling this returns nothing.
* I download Android SDK along with tools package to try and start the phone in download mode to flash, but typing ADB Devices in the command line shows a blank "List of devices attached", even after killing and restarting the ADB server. I see "Samsung Mobile USB CDC Composite Device" in my computer's device list and this is the most updated driver. Attempting to load legacy Android ADB interface, Android composite ADB interface, or Samsung Android ADB interface results in an unrecognized device and still ADB Devices does not show any results. Dead end.
Having spent the last 8 hours on this, I'm at wits end. This may be the last time I purchase an Android device! Simply ridiculous that something like this could happen. I'm not reading the same problem anywhere else so it sounds like it's just me so possibly some sort of lemon.
Can anyone please help me? I'm really stuck and would be super appreciative. Thanks in advance!!

Only thing i can suggest is open odin as administrator and CSC file not HOME-CSC, home-csc doesn't wipe

Related

[Q] Bootloop after ODIN Flash [after Softbrick]

Today I finally got my USB Jig and successfully entered ODIN Mode.
I then flashed IMM76i on my Nexus...
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> bootloader.img
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
...disconnected it and there it is again.
That damn bootloop I already had.
Got any idea on how to fix this?
btw. I'm looking for stock Jelly Bean as a .tar file
why are you using ODIN?
learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Fastboot unfortunately doesn't work.
In general no key combination works which is why I bought myself a USB-Jig.
domimatik said:
Today I finally got my USB Jig and successfully entered ODIN Mode.
I then flashed IMM76i on my Nexus...
...disconnected it and there it is again.
That damn bootloop I already had.
Got any idea on how to fix this?
btw. I'm looking for stock Jelly Bean as a .tar file
Click to expand...
Click to collapse
Ok so you said fastboot did not work as to why you used the jig correct?
What was wrong with the device before you used the jig? Softbricked, hardbricked?
Even though odin flashed successfully does not mean it flashed everything correctly.
Can you get into bootloader? If so, try doing factory reset.
While in bootloader, see if windows sees your device....if so see if fastboot works now.
Sent from my Galaxy Nexus
My phone got soft bricked after an ota update to Jelly Bean.
This includes an endless bootloop aswell as that all key combinations (for fastboot, bootloader) are disabled.

[Q] s4 mini i9195 ODIN flash write failure

hi
i bought an s4 mini i9195 with fault :
"
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY : Custom
SYSTEM STATUS fficial
KNOX KERNEL LOCK :0X0
KNOX WARRANTY VOID :0X1
CSB-CONFIG-LSB :0X30
BOOTLOADER RP SWREV:2
WRITE PROTECTION :ENABLE
Firmware upgrade encountered an issue. Please selectect recovery mode in kies & try again"
when i flash pit file this message dispair and i've logo stuck with "set warranty bit kernel"
i can going to download mode vol- + home + power
but can't enter recovry mode vol+ + home + power it show " recovery booting ... set warranty bit recovery"
i've try de restore with many official rom up to the lastest rom.
with the lastest rom odin freeze on boot.img and take message "ODIN flash write failure "
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i tested with 4 file rom and odin stuck on aboot.img
all tested on many pc with many usb cable
what solution? is the hardware problem (emmc)
thx
Try to enter Download mod, and Cancel (volume down). Worked for me on I9195

I need help fixing my Note 10+

I have an AT&T Note 10+, N975U1. I tried to flash a US unlocked firmware onto it, but that kinda didn't work... Now I'm stuck on this page that says " An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software". I tried smart switch, but it wouldn't recognize my phone in the emergency recovery. I decided to try to flash the ATT firmware, thinking that doing this might fix it, well not really, I'm stuck and I have no clue what I'm supposed to do.
Log:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> quest.fv
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img
<ID:0/003> carrier.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 8720 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> aop.mbn
<ID:0/003> bksecapp.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> km4.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> sec.elf
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> storsec.mbn
<ID:0/003> uefi_sec.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> multi_image.mbn
<ID:0/003> dspso.bin
<ID:0/003> vbmeta.img
<ID:0/003> vaultkeeper.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> vendor.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> product.img.ext4
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EnderGopo said:
I have an AT&T Note 10+, N975U1. I tried to flash a US unlocked firmware onto it, but that kinda didn't work... Now I'm stuck on this page that says " An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software". I tried smart switch, but it wouldn't recognize my phone in the emergency recovery. I decided to try to flash the ATT firmware, thinking that doing this might fix it, well not really, I'm stuck and I have no clue what I'm supposed to do.
Log:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> quest.fv
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img
<ID:0/003> carrier.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 8720 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> aop.mbn
<ID:0/003> bksecapp.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> km4.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> sec.elf
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> storsec.mbn
<ID:0/003> uefi_sec.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> multi_image.mbn
<ID:0/003> dspso.bin
<ID:0/003> vbmeta.img
<ID:0/003> vaultkeeper.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> vendor.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> product.img.ext4
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to download the firmware you had before or you can flash again the same code but use CSC (Not HOME_CSC) and restore everything after. The trick is to get back to the download screen, and for that you need quick hands, and here is how...
Hold the power button and volume down for 7 seconds or so, as soon as the phone resets leave the buttons and hold the volume up button. You will be back to the download mode. Ignore the red exclamation mark on the screen. Flash away and you will be fine. You can't go from U to U1 or vice versa and keep your original partition. HOME_CSC can not be used in that case.
BigE said:
You need to download the firmware you had before or you can flash again the same code but use CSC (Not HOME_CSC) and restore everything after. The trick is to get back to the download screen, and for that you need quick hands, and here is how...
Hold the power button and volume down for 7 seconds or so, as soon as the phone resets leave the buttons and hold the volume up button. You will be back to the download mode. Ignore the red exclamation mark on the screen. Flash away and you will be fine. You can't go from U to U1 or vice versa and keep your original partition. HOME_CSC can not be used in that case.
Click to expand...
Click to collapse
OMG I have no way of thanking you, it really sucks that I lost all my information since I don't have a backup of it, I'll definitely change that ASAP. Thanks for this, and have a great day!
I had same problem last night. My samsung note 10 plus got stocked on "an error has occured while updating the device software" .
Initially, I tried using home csc but it got stuck on same page. I then decided to use csc and still got stucked too. Phone Battery is drained and I ave no idea wat to do.phone brand is AT&T unlocked version in Nigeria. I don't know of the Odin version used is the problem but I used the same Odin version to update my samsung Note 8 & there was no problem. Pls help!!!
---------- Post added at 09:17 AM ---------- Previous post was at 08:22 AM ----------
I tried flashing it again with odin and phone still not entering download mode bt I got info somewhere here that flashing of firmware can still occur if stocked on the error screen. The process was moving and after a period of time. Odin wrote failed. Wat to do now???
The firmware am updating to is N975USQU3CTE7.
Or am I using the wrong firmware???
DEREK1414 said:
I had same problem last night. My samsung note 10 plus got stocked on "an error has occured while updating the device software" .
Initially, I tried using home csc but it got stuck on same page. I then decided to use csc and still got stucked too. Phone Battery is drained and I ave no idea wat to do.phone brand is AT&T unlocked version in Nigeria. I don't know of the Odin version used is the problem but I used the same Odin version to update my samsung Note 8 & there was no problem. Pls help!!!
---------- Post added at 09:17 AM ---------- Previous post was at 08:22 AM ----------
I tried flashing it again with odin and phone still not entering download mode bt I got info somewhere here that flashing of firmware can still occur if stocked on the error screen. The process was moving and after a period of time. Odin wrote failed. Wat to do now???
The firmware am updating to is N975USQU3CTE7.
Or am I using the wrong firmware???
Click to expand...
Click to collapse
In order to go to download mode , when phone is on and stuck (telling you to use Samsung switch), you want to take the following steps:
1. Restart the phone: push power button and volume down for 7 to 13 seconds. Phone will start a reboot.
2. Now comes a quick hand feature... As soon as the screen changes to the Samsung logo, lift your finger from the power button, keep the volume down pushed, and add a volume up button.
3. You will end up in the download mode window. Ignore the scary red exclamation character, use Odin with the right firmware. Flash the full ROM , not just CSC .
4. Restore your phone, as you will have a fresh new start.
One word of warning. If you flash the user data of your carrier, you better remember your PIN code. The phone is set to identify a factory reset as a potential 'theft attempt'
Good luck
i am having a similar problem. i can reboot the phone from the exclamation point screen to the initial download mode screen. then, i have to push the volume up key to continue, and it goes right back to the smart switch screen. stuck in a loop. can anyone help?
agc87 said:
i am having a similar problem. i can reboot the phone from the exclamation point screen to the initial download mode screen. then, i have to push the volume up key to continue, and it goes right back to the smart switch screen. stuck in a loop. can anyone help?
Click to expand...
Click to collapse
Disconnect the USB cable when you reboot and get to the download screen, if you are keeping it inserted. If you do not, I have no clue why is dies it..
EnderGopo said:
I have an AT&T Note 10+, N975U1. I tried to flash a US unlocked firmware onto it, but that kinda didn't work... Now I'm stuck on this page that says " An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software". I tried smart switch, but it wouldn't recognize my phone in the emergency recovery. I decided to try to flash the ATT firmware, thinking that doing this might fix it, well not really, I'm stuck and I have no clue what I'm supposed to do.
Log:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> quest.fv
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img
<ID:0/003> carrier.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 8720 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> xbl.elf
<ID:0/003> xbl_config.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> aop.mbn
<ID:0/003> bksecapp.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> km4.mbn
<ID:0/003> qupv3fw.elf
<ID:0/003> sec.elf
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> storsec.mbn
<ID:0/003> uefi_sec.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> multi_image.mbn
<ID:0/003> dspso.bin
<ID:0/003> vbmeta.img
<ID:0/003> vaultkeeper.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> vendor.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> product.img.ext4
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey mate, I am also getting same error while trying to Flash Note 10+ firmware from BRI to TGY. Did you resolve this issue? I want to flash TGY firmware on SM-N9750 but getting this error so I had to revert to BRI firmware again.

I cannot do a hard reset or change rom of my boot looped(infinite loop in the phone logo) phone

I did put my Samsung Galaxy Tab 3 Lite SM-110 to charge and suddenly he begins a kind of boot loop.
Note: I did try so many things and had no way to me enter in the hard reset menu or in recovery mode(it is impossible by pressing buttons(believe me I tried every combination existing))
Note 2: The unique access possible is by download mode then, give me some solution that is by download mode.
Note 3: I did discover T110XXUANG2 is my PDA number based on the buy date 08/2014
Note 4: I did try every single one rom of my device(it had 5 based on my country) in each field(BL, AP, CP, CSC) and each one returns me the same error:
<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> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> obm.bin
<ID:0/003> DTim.Recovery
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Note 5: I did try to remove the DTim.Recovery of the rom with the 7zip but, when I remove it appears other error of another file and when I remove another one appears another one and that continue until over every file in the rom.
What checkboxes do you press in Odin?

T-Mobile S9 issues flashing to G960U1 firmware ...

I have tried flashing the G960U1UES9FVD1_G960U1OYM9FVD1_XAA downloaded from sammobile on two different computers and several versions of Odin, but every time I get
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> dqmdbg.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 5283 M
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Tried a patched Odin too (not sure if that would even help) and it just got stuck on SetupConnection. Have also been running Odin as admin, tried different USB ports & cables ... (one of the ports on my laptop is 2.0 still not working).
Current Android Build Number iS QP1A.190711.020.G960USQU9FVB2
I'm probably doing something obvious wrong, but I can't seem to find what that is & already spent a few hours trying to get this done!

Categories

Resources