Database Develop

[Q] Stucked on the samsung galaxy s screen.

Stucked on boot screen (the one that we usually see first with white letters). I did factory reset but I am still stucked on Galaxy S boot screen. I heard the default galaxy S sound but did not see the big 'S'. When I press Volume down + Home + Power , I just see a big triangle which says 'Downloading...do not turn off target'. This means that I can go into the download mode.
I installed odin3 and installed .512 PIT file as well as JH2 firmware from samsung-firmwares website. Inside the JH2 zip file I see a file with extension .tar (I think this goes in PDA section of ODIN).
After connecting my phone with my computer, I see 0:[COM6] in Odin. Plz guide me from hereon. Any help will be much appreciated.
NOTE: I was using gscript o change system fonts. Probably deleted system fonts. Then, I restored back to system and since then phone would not start. Well, it starts but I am stucked on this screen.
I am using Samsung galaxy S vibrant (Bell, canada [GT-I900M])

I will not help because you didn't ask the right question. Please change the title of your thread to something more intelligible or no one will bother.

Bec07 said:
I will not help because you didn't ask the right question. Please change the title of your thread to something more intelligible or no one will bother.
Click to expand...
Click to collapse
Sorry...I will change now

...
Try the same combo but with volume up. Why do you want to connect to kies?

Bec07 said:
...
Try the same combo but with volume up. Why do you want to connect to kies?
Click to expand...
Click to collapse
I am trying to connect to KIES because I think i can reflash using test mode.
Yes..I tried that? Did wipe/factory reset..then rebooted....got the same screen again.
Thanks for replying
EDIT: when I go to recovery menu (Volume up + home + power) and then connect with USB...I can see my device listed by using 'adb devices' command in the cmd prompt.

OK....When I connect my phone to my computer via USB, I can see 0:[COM6] in ODIN. I can go into download mode. I have downloaded JH2 firmware (zip file from samsung-firmwares website). I have Bell Samsung galaxy S vibrant. Can I flash with ODIN.

hay buddy i had exact same problem and this post saved my life... here it is hopfully it will help u out if it does let me know
http://forum.xda-developers.com/showthread.php?t=984140

Stuck at Galaxy S logo!

Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared

Please Help!
- UPDATE: SOLVED!
Hi there, I'm having the same problem on my I9000B. Please help me.
This is my story, I had upgraded my 2.1 firmware to VIVO's 2.2 Froyo via KIES with the Kies Registry Patcher (used ZVV). Everything worked perfectly, but I wanted to root my I9000B so I made the terrible mistake of using CF-Root via Odin, (http://forum.xda-developers.com/showthread.php?t=788108) following the exact instructions. The kernel replacement (zImage file) was for the I9000 so I had the touchscreen problems. When the phone booted showed Samsung galaxy S GT-I9000B and then inmeadeatly the "B" dissapeared.
Because of my n000bness I tried to use the zImage file from this ROM (VIVO's) (http://forum.xda-developers.com/showthread.php?t=858483), by downloading my own .tar created file (with 7-zip) of the zImage file. Here is were things went down. I got the android - USB cable boot icon. I could not go into recovery mode but I could do download mode, so I re-flashed VIVO's ROM (the one published here) with Odin:
I used the 803 .pit file, Odin 1.3
I did not check re-partition
I selected the ROM as the PDA file and I left PHONE and CSC blank.
the ROM was downloaded to the phone and Odin did not gave me problems.
My problem here is that I get the black screen with vibrations from time to time on boot. This is exactly what happens:
The phone starts showing "Samsung galaxy S.... GT I9000B (at least shows "B")
I can get into recovery mode but the following appears:
Code:
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please us UI menu for format and reboot actions.
copy default media content failed.
Then I did a factory reset, succesfully completed, tried again flashing the ROM but with Re-partition box checked (as instructed here: http://forum.xda-developers.com/showthread.php?t=723596) but the same stuff happens.
Please tell me what to do! I know it was a stupid mistake trying to fix ony the zImage file, and stupider was using CF-Root on my non-compatible device.
PS: I can get into download mode with no problems
Code:
pda i9000bvjjpa
phone i9000bvjjpa
csc i9000bzwjp3

I have exactly the same problem
but i can go into recovery mode and download mode.
the galaxy screen is I9000 and my sgs is I9000B
any ideas?

A friend of mine has the same issue on his SGS. Both recovery and download mode working.

Have you done JUST like this:
Figueiredo81 said:
Guys... I´m in trouble... I´m on JPM and flashed CF-Root-JPM-v1.2-Busybox-1.17.1 but my phone was taking too long, like more than 20min at Galaxy S boot. I knew something did go wrong, removed the battery and I entered download mode again and re-flashed... Same thing! My phone is not getting past Galaxy S boot up picture!! I can't enter recovery mode but can enter download mode! Is there anything I can do to bring my phone back to life?! PLEASE HELP ME!
I already tried to flash new roms in odin. My device is recognized but odin hangs and does nothing...
I need some advice on this, did I kill a new phone?! I´m scared
Click to expand...
Click to collapse
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.

Thanks!!
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Margaliini said:
1. Enter your phone in dl-mode, but don't connect yet.
2. Open Odin, tag re-partition, auto reboot and f.reset time, make sure efs clear and bootloader -fields are NOT checked. select CORRECT PIT-file (2.1 ROMS usually 512, 2.2 ROMs many times 803, samfirmware always tells which one to use next to the dl-link of a ROM-file), enter your phone in dl-mode, plug, wait it to be recognized by Odin.
3. Click start, wait until Odin shows PASSED, unplug your phone, remove the battery for 30 seconds, enter dl-mode again, don't plug just yet.
4. In Odin, click Reset. Then select PDA, Modem and CSC files compatible with the PIT-file used in re-partition, plug your phone, make sure re-partition NOT checked and no PIT-file selected (once again, make sure you use correct PDA for the PIT you flashed). auto-reboot and f.res.time should be selected. Make sure efs clear and bootloader -fields are NOT checked.
4- Plug your phone and when recognized, click start. Wait to be passed. Now your phone will boot (or if not, boot manually) and should work just fine.
Edit: Try to put Eclair ROM, for example JM2, not jpa, and see if it works better.
Click to expand...
Click to collapse

Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.

Please, post the link or give me directions for the Claro's ROM. I am having the same problem here.
Thanks.

gtg2 said:
Well, the good news is that it appears that the "E:Can't mount /dev/block/stl10" error msg can be resolved.
http://forum.xda-developers.com/showthread.php?t=788850
This thread discussed this specific error message. For some reason, they're claiming that flashing JPC with 512 pit and repartition checked is doing the trick. I'm assuming this will result in data loss but I guess that's better than losing the phone entirely You should be able to flash to whatever firmware you want afterwards (assuming it works).
JPC:
http://www.multiupload.com/WB3104V8G0
Pass = samfirmware.com
512 PIT
http://www.multiupload.com/I5WICSBFJ1
Report back if this works for you.
Click to expand...
Click to collapse
worked here
thanks

thanks for the help i love you no homo !

Un Loko said:
Sir, you have saved my phone and my whole week. This is what I did:
With this method I tried the Vivo Brazil's 2.2 Rom again and did not work, same error, tried using both 803 and 512 pit files.
Then I downloaded an 2.1 firmware (JG9, which was the same that came with the new phone) from Claro Brazil that I found on google and flashed it with the 512 pit and worked perfectly. I had been strugling with this problem the las 6 hours and solving this was urgent because I'm going to vacation now.
Now I can re-update via Kies and return to Froyo were everything worked.
I will not try to do things like this in such a risky way (risky because I don't know)
Thank you very much.
Click to expand...
Click to collapse
JM2 with pit method is perfect. my "E: can't mount /dev/block/mmcblk0p1" problem has finally been solved.
Thanks

This worked for me.
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)

???I bought my Phone from CSpire but stuck on At&t Logo???
Samsung Galaxy s Showcase stuck on the At&t Logo...Will not let me go into Download mode??? Help please?

[Q] How to go back to standard firmware?

Hi,
was very interested in rooting my phone (Samsung Galaxy S) and putting a custom rom on it. I managed to put on Darky's latest rom last night. However it was giving me problems with the Android market (it crashed when it came to the installation part). Therefore, I want to get rid of all the modifications I made to my phone and go back to the settings how the phone was shipped to me.
How can I do that?
I already downloaded the original firmware (2.2.1) using this forum. It is a .tar file and I tried to flash it with Odin. Seemed to work at the beginning but there were still some elements, like apps, of the old Rom left. So I did the process again.
Now my phone starts up but after the boot screen I only have a black screen with the typical crash vibration patterns all the time. After flashing it again I get into the recovery mode showing errors.
Can somebody please tell me how to go back to my original firmware, without a custom rom, root access etc.?
I'm afraid that I will brick my phone now.
thank you
(I searched this forum but couldnt find anything related to my question)

Try a different firmware. Had the same issue when flashing a 2.1fw on an already 2.2 custom rom. Try a US 2.2 jpy. You can get any galaxy s firmware from (www samfirmware com).
Sent from my GT-I9000 using XDA App

thank you for the quick reply.
I am not 100% exactly sure if my procedure is right. Here is what I do:
1. Put your phone to download mode (hold down: volume down, home key, power)
2. Do not plug in your phone yet.
3. Start Odin3
4. Tick "Re-Partition", and also check that "Auto Reboot" and "F. Reset Time" have been ticked.
5. Click "PIT" button and select s1_odin_20100512.pit file.
6. Now, plug in the phone and wait until Odin finds it.
7. Click "Start" button... <Firmware update start...> <Get PIT for mapping...> appear. The phone will turn off and the screen indicates "Reset". Wait until Odin indicates "Pass".
8. Plug out your phone, remove the battery, put it back in and put phone to download mode again.
9. Click "Reset" button in Odin and untick "Re-Partition" box.
10. Do not select PIT file again. Just leave it empty.
11. I select here the downloaded firmware (2.2.1) in PDA. Everything else is blank (PHONE and CSC)
12. Phone installs and Odin shows pass
Now, the phone does not boot but goes into system recovery 3e showing an error message E: Cant mount /dev/block/st110
E: copy_dbdata_media:Cant mount DBDATA
After I select "reboot system now" the phone boots but gets stuck right after the Samsung logo disappears. then I only see a black screen and the vibration.
What am I doing wrong here?
thank you I really appreciate it!!

Follow instructions Block 2 method Odin and use the firmware you want .
http://forum.xda-developers.com/showthread.php?t=818556
jje

Help Galaxy s3 mini

Hello and i wish i can find solution for this
i bought GS3 MINI from friend and he flashed it now when the phone boot to the main screen to put the config the phone turns off immediately and boot again
when i tried to put it in odin mode i found at the bottom of the screen something HW REV 0x5 when i try to flash it with odin something appeares (movi create card session) with red line and there is no problem in odin i tried with alots of FW and it's the same problem
i tried to ERASE NAND ALL not working stuck at erase.... and unsuccessful.
PS : i can't go to recovery ..
custom binary download: yes (4 counts)
current binary:Samsung official
system status: custom
HW REV 0x5

Help help help !!!!!!!!!!!!!!!!!!!!!

6 Days with no help ?

Flash with PIT file and Re-partition box checked. PIT files are attached in the unroot/unbrick, flash stockrom, etc post

Chakapack said:
Flash with PIT file and Re-partition box checked. PIT files are attached in the unroot/unbrick, flash stockrom, etc post
Click to expand...
Click to collapse
i did everything without result

Can you take potos?
Resume:
1. You download the stock firmware?
2. Then, put your phone in Download mode (volumen down + menú + power)?
3. Put .tar.md5 file on PDA slot?
4. Put PIT file in Pit slot option?
5. Then, f.reset, re-partition, and auto reboot are checked?
6. When you connect your phone in download mode, there is cheked in blue the ID:COM space?
7. When you press start everything go good and the proccess end?
8. What appears when the phone auto reboot after all the process?
I got the problem of partition encrypted corrupted (something like that) but pressing the reset button works for me. Try agaun everything and tell us whats happend

1. You download the stock firmware?
Yes
2. Then, put your phone in Download mode (volumen down + menú + power)?
Yes
3. Put .tar.md5 file on PDA slot?
Yes
4. Put PIT file in Pit slot option?
Yes
5. Then, f.reset, re-partition, and auto reboot are checked?
Yes
6. When you connect your phone in download mode, there is cheked in blue the ID:COM space?
Yes
7. When you press start everything go good and the proccess end?
Yes and with success and when check the phone its looks like nothing happened
8. What appears when the phone auto reboot after all the process?
normal and when he boots to configure the phone turns off immediately and reboots

Man that sounds like a hard brick. If after all this process the phone still with a bootloop I think, its dead.
Sorry but I cant help you :/

Chakapack said:
Man that sounds like a hard brick. If after all this process the phone still with a bootloop I think, its dead.
Sorry but I cant help you :/
Click to expand...
Click to collapse
Thanks alots , atleast you replied

No problem. We are here to help!
Enviado desde mi GT-I8190 mediante Tapatalk

darkerthan said:
Thanks alots , atleast you replied
Click to expand...
Click to collapse
Probably don't work but if you get a bootloop after all this process, try power off the phone (remove battery) and then try to access to Samsung recovery and do a wipe data.
I'll sell this phone and when I did a restore with Odin, I got a bootloop after this process but restarting the phone and getting access to Samsung recovery and doing a wipe date, it work.
Try it

galaxy s10 stuck on an error has occurred while updating device software

hi all...i got a second hand galaxy s10 g973f/ds that was stuck on the screen an error has occurred while updating the device software.use the emergency recovery function in the smart switch pc software..
here are where the issues are starting..by going to smart switch app the app doesnt recognize my device..it says unsupported device.so i cant follow any suggestions found on this forum like selecting the more option and then emergency recovery function cos the phone isnt recognized..theres only an option to recover using recovery code but unfortunately i dnt have that code.the other problem is that by using odin i dont know the exact firmware file that was installed previously on the phone so when i try to flash with odin a ramdomly downloaded firmware it fails if i use modded odin or it gets stuck on recovery.img if i use not modded odin..
i have to say that i cant get to download mode by the pressing of any combinations of keys..the only screen that appears is the above mentioned error..even that apoears only when connected to power supply or usb through pc..otherwise if cable is disconnected theres no way of getting it on..
now i would appreciate anyone who can suggest a solution for my problem or if anyone can tell me if theres a way to get to know the original factory installed firmware through the imei or serial number of the phone..
i thank in advance anyone who would spend his her time to help me..

joyjuayasinghe84 said:
hi all...i got a second hand galaxy s10 g973f/ds that was stuck on the screen an error has occurred while updating the device software.use the emergency recovery function in the smart switch pc software..
me..
Click to expand...
Click to collapse
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.

s10 stuck on an error has occurred while updating device software
hi cealaska.tnx for reaching out..m sorry that i didnt showed up on the forum for so long and couldnt reply to the message you hv sent...i still couldnt fix my s10...ill try your method in a while and keep you posted..really appreciate ur effort in trying to help me..

cealaska said:
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.
Click to expand...
Click to collapse
no luck bro..phone is still stuck as it was before.. the first time that i tried to follow ur guide i did everything as u said but in odin i got an error message saying re-partition operation failed..that message ive got only the first time i tried to follow your guide..all the following times i get an error saying fail! (device info)
im completely lost..ive tried different odin versions including patched one..ive tried different firmwares but nothing..still stuck at that message..

Hi! I have a s20 that is in exact same state. Have anybody any clue what to do?

I was stuck on this error and couldn't turn off the phone. Tried all the possible button combinations.
This method worked for me on the first try.
Thank you!

cealaska said:
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.
Click to expand...
Click to collapse
I was locked on Note 20 ultra, your instructions works fine, thanks a lot, I love you ;-)

cealaska said:
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.
Click to expand...
Click to collapse
seems like partly working for me!
I have Samsung SM-M315F/DSN and I was stuck on EMERGENCY RECOVERY MODE and after applying your solution I guess I'm on a boot loop... keeps rebooting and nothing else!
what else can I do please?
::EDIT::
after trying many things, I went into safe mode and did a Wipe Data/ Factory reset and it worked!

cealaska said:
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.
Click to expand...
Click to collapse
A year later you saved my phone ! Thanks a lot

Don´t know why it doesnt work by me but i am the brick king or so. If ya realy fckd up the flash at odin won´t go over Partion in the BL to get there out again i can just put it out and it goes by it self on again when nothing help i had to use Reiboot for Android would be nice if someone can figuere out how the programm put it back out of the Emergency Recovery Mode. tool is free in the test version so you have just to brick ya phone btw did it on a SM-G973F D/S hope you are smarter and didn´t even have to read this not just cause of ma english skills
happend on android 11 with twrp on magisk 23 cause forgot the decrypt thing img

cealaska said:
Were you able to get it sorted out? Did you bring it to a Samsung Repair Center?
Look on the back of the phone and you will see the phone model number. Confirm that it is SM-G937F/DS so you will at least have the right firmware when you download it. It would probably be best to get the latest Android 10 firmware linked below. Download the latest Odin 3.14 if you weren't already using it.
You can download your firmware from here. I have the A70SM/DS and the original manual had Spanish on it and I was told it was the Latin America version. TCE is supposed to have the latest software patches at least for my A70. I do not know about the S10.
After your firmware is downloaded extract it to a folder. Copy the CSC to your desktop and delete the .md5 extension from the file. Use 7zip or PeaZip to open your CSC on your desktop and extract the PIT file. Save it in the original firmware (.tar.md5) folder. Delete the copied CSC from your desktop.
Open Odin with Admin privileges and connect the phone. Select all 5 of the downloaded files (BL, AP, CP, CSC and USERDATA). Select the Pit option and use the extracted pit from in your firmware folder. In the options menu select Auto Reboot, Nand Erase, Re-Partition, and F. Reset Time. ONLY USE NAND ERASE AND RE-PARTITION IF YOUR PHONE GETS PUT INTO EMERGENCY RECOVERY MODE. Start the flashing and wait for the phone to start up on its own. It might take up to 10 minutes on the first boot.
Click to expand...
Click to collapse
Fixed my phone!
I've been trying for days to fix my bricked phone that was stuck in Emergency Recovery Mode after a bad flash. The major points I learned is to try several different usb ports and cables (original cable is better), get the correct and region specific firmware (The Samsung s10+ G975F/DS is the same as G975F), keep trouble shooting and retrying many, many times after Odin errors/failures, and to use this provided guide above.
Samsung Smart switch didn't help but this post did. This information saved my phone! I couldn't find this information anywhere else after hours of searching. Thank you very much!
Other people may find this tip helpful:
Q: My device is in bootloop, I can't acces download mode or recovery, no combo works, how do I get out ?
A: You can try following:
- Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
- If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
- Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.

I have a G970F which got stuck at 8% while flashing Ubuntu Touch system image to the SYSTEM partition with Heimdall on a Linux laptop. I think my laptop USB hardware isn't as good as it used to be. Anyway, am stuck on the error screen shown in the photo. Note that in the upper left corner of the screen is red text which is partially obscured by the curved screen corner, it says something then "Level [3921]". I have had no luck entering Download mode again with button combo + USB cable.
The device was stock Android 12 then has the Ubuntu Touch BOOT and VENDOR partitions flashed to it before it got stuck flashing the SYSTEM partition.
Is it possible to enter Download mode somehow again to begin the unbrick process?

zpunout said:
I have a G970F which got stuck at 8% while flashing Ubuntu Touch system image to the SYSTEM partition with Heimdall on a Linux laptop. I think my laptop USB hardware isn't as good as it used to be. Anyway, am stuck on the error screen shown in the photo. Note that in the upper left corner of the screen is red text which is partially obscured by the curved screen corner, it says something then "Level [3921]". I have had no luck entering Download mode again with button combo + USB cable.
The device was stock Android 12 then has the Ubuntu Touch BOOT and VENDOR partitions flashed to it before it got stuck flashing the SYSTEM partition.
Is it possible to enter Download mode somehow again to begin the unbrick process?
Click to expand...
Click to collapse
same here with my galaxy a50... cannot enter into download mode not in recovery. samsung smart switch pc software says it cannot connect to device...

zpunout said:
I have a G970F which got stuck at 8% while flashing Ubuntu Touch system image to the SYSTEM partition with Heimdall on a Linux laptop. I think my laptop USB hardware isn't as good as it used to be. Anyway, am stuck on the error screen shown in the photo. Note that in the upper left corner of the screen is red text which is partially obscured by the curved screen corner, it says something then "Level [3921]". I have had no luck entering Download mode again with button combo + USB cable.
The device was stock Android 12 then has the Ubuntu Touch BOOT and VENDOR partitions flashed to it before it got stuck flashing the SYSTEM partition.
Is it possible to enter Download mode somehow again to begin the unbrick process?
Click to expand...
Click to collapse
Similar situation here with an Exynos S10e (G970F), but it was already rooted with TWRP and a custom ROM, though I couldn't boot into recovery.
Unfortunately, the Linux situation seems bad at the moment. The only thing that worked for me was to try and plug the device into a Windows 7 VMware with Odin there. I could power off the screen for short moment with Vol+Power, and then VolDown+Power to get into a "fictionnal" download mode (because the screen didn't change) that would allow me to start flashing things with Odin.
With Odin in the VMware, I flashed the BL and the CL from the latest stock ROM from samfw.com, and the patched vbmeta.img (in CP slot) at the second reboot with the vbmeta warning. I then flashed a custom AP (with the boot.img of my custom ROM repacked and lz4-compressed, but without the gigangtic system.img; full content was "boot.img.lz4 dqmdbg.img.lz4 dtbo.img.lz4 dt.img.lz4 vbmeta.img.lz4 vendor.img.lz4"). From there, I could finally boot into TWRP and flash the .zip of my custom ROM.

I wonder if this would apply to my issue here: https://forum.xda-developers.com/t/samsung-s10-bootloop-erase-fail-read-only.4260661/
Please check out the uploaded photos of the above link in order to match the problem and find a solution

I remember that I got the phone working shortly afterwards back in January, but I cannot remember exactly how I did it. I think I might have used a Windows computer with Odin to return the device to the stock OS. I think download mode was working while the error screen was showing. I recommend reading about flashing stock firmwares on Samsung devices before attempting to do it so one doesn't accidentally wipe IMEI.
I also recommend taking photos of the phone screen when it is displaying serial numbers, firmware version numbers etc... before experimenting with it.