[Q] Humble request from Epic noob - Galaxy S I9000 Q&A, Help & Troubleshooting

[Q] Humble request from Epic noob - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello guys,
Yes... I'm a total noob, I tried to root my phone with the wrong files and ended up bricking my phone.
My reason to root: wanted to be able to use the emulators / controllers on the market. If only I knew this was going to happen
On my attempt to reverse the situation, I did it... my phone stopped booting completely.
I figured since my phone does go onto downloading mode still, that I'd be able to return it back to normal once I educated myself a bit on the processes of flashing androids.
I have tried to find a thread similar to mine, and I have been unsuccessful to the point of utter frustration (I even considered going and getting a new phone).
Then I came across AllGamer's thread:
http://forum.xda-developers.com/showthread.php?t=1379650
I thought my search (of 8 hours by then) was done, that everything would be back to normal.
But somehow I have been unsuccessful to mimic his results on flashing the phone back to Stock.
I'm probably wrong assuming that the bootable files on the phone are missing since my stupid trials at the beginning of it all. Hence why AllGamer's instructions aren't doing it for my phone.
I have a Samsung Galaxy S GT-I9000m
This is my last resource (to which I have no right, but I figured I should try before calling it quits).
Can any of you help me fix my phone?

Did you try flashing using the three files method in ODIN? You need ODIN, a PIT File, and an original ROM that has 3 files (Phone, PDA, CSC) in it. Check the Re-Partition option and your phone should go back to the original rom.
Go to SamMobile dot com to find a Samsung ROM

As long as you have download mode then your phone is still alive.
Go to samfirmware ( or sammobile as it may have changed over now ) and get a zip file for you device which contains 3 files and a pit file.
MAKE SURE YOU GET A FIRMWARE FOR AN I900M NOT A I9000 OR AN I9000T!
Download odin and put the pit file in the pit box.
in PDA box put PDA file or it may be called CODE.
In MODEM put the MODEM file or it may be called PHONE
In the CSC box put the CSC.
make sure that repartition / auto reboot / auto F reset are ticked.
Any other boxes should be unticked.
Put your phone into download mode and connect it to the PC.
MAKE SURE YOU OPEN ODIN AND CLOSE ANY KIES SOFTWARE BEFORE CONNECTING YOUR PHONE!
a yellow box should pop up in odin saying COM XX
press the start button and let odin work its magic and voila! your phone is alive!
Good luck

Related

Issues with Flashing Galaxy Tab

Hello - It seems as though everyone is somewhat nice and knowledgeable on this board. I'm hoping that no one flogs me in the process of this thread.
I have a T-based Galaxy Tab and am trying to load a new ROM onto it. I've tried multiple times with multiple different ROMs but am not making really any progress. When I plug in the device to a wall outlet, the attached screen is displayed. This is the first time that I've seen this screen and I'm now hoping that this thing isn't bricked. Please help me bring this Tab back from the dark side.
I need to know which ROM to use and the appropriate PIT file. I also need to just understand how I get the device to be recognized by Odin again as it's not being recognized in it's current state. Thanks to all that will help me.
Jim

hi,
can you tell me which firmware files are you using to flash and the PIT files?

Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim

jimcansler said:
Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim
Click to expand...
Click to collapse
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT

Not wanting to be pessimistic here but after browsing the Galaxy S section I came across a thread with that image on your tab. You may have to contact Samsung and have the device replaced. http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode

Storm, Chow,
I think you may be right. I followed the instructions that Chow gave me and it failed. See attached. I still have the Tab attached to my pc and it still has the same image as original. I've attached my Odin screen so you guys can look at it and tell me if I'm doing anything wrong.
Jim

Hi,
I had that image many times, whenever my tab fails to install any new firmware.
did you reboot the tab after seeing that image
one more try:
after seeing the flash fail > hold the three button combination (power + volume down + home) for long time (may be more than 1 minute) until the tab is switched off and then use three button combination (power + volume down + home) to enter the download mode (you will still see the above image only). now connect the tab to odin and try flashing it.
if i remember correctly, my tab was connected to COM 8 when flashing but i think its USB port selection
this is how i recover my tab to working mode whenever a flash fails

Have you tried with Odin 1.31 with PIT 816 and JHA.tar selecting repartition?In the pic you are using the 1.71, right? I had something similar going back to JID from JJ4 and when I tried with the 1.31 it passed, cant be sure it wasnt just 'the one more try' or the old Odin but it worked.
Good luck
Sent from my GT-P1000 using Tapatalk

I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim

jimcansler said:
I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim
Click to expand...
Click to collapse
just install the JID without use any pit and do not select re- partition, keep using the 1. 31
Sent from my HTC Desire using Tapatalk

chowdarygm said:
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT
Click to expand...
Click to collapse
I quote.
I had that bad image on the screen for some time... If you connect to the PC you should find the TAB as connected in ODIN. If you flash JHA repartioning with the correct PIT, that for me was 9 and something if I remember, you should restore normal functionality. Try and let me know!

Can confirm.
Had this image several times while testing var firmwares.
Simply connect tab to odin and flash jha image with repartition.
This should fix it.
Sent from my GT-P1000 using XDA App

Guys, I think that he solved the problem using Odin 1.31.He already install the JHA and the unit is working.Pls stop posting without read.The issue can be related with the new Odin.Now he is concerning to install JID over a working unit...

MODEM file
Greetings,
Where did you guys get your MODEM file from? I only can see the PDA and CSC files on the samfirmwares.com site... :S

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?

Help!! Australian firmware update and got bricked

HELP~!!!! I bought a galaxy tab in Australia and it was unlocked. Then when I saw the forum post for firmware
It was the JJ3 version and download the Australian version P1000NUBJM2. I followed the step except I loaded the pit file inside the .tar instead of the P1_20100909.pit.
I unchecked the repartition button and it passed the installation and green button lights up. But my tab didn't restart after that !!! It's now in black screen!!!! Help~~~!!!
But it seems can connect to computer as i replug the tab, kies pops up and odin still works with the yellow ID:COM box.
And I didn't root it before flashing firmware, is it the reason? and how can i get it back to original factory setting??

First Calm down and Kindly Post the questions in appropriate forum Q/A forum is for questions
Second A detectable tab in ODIN and Kies is most likely NOT BRICKED
Third Read the guide for flashing your appropriate firmware before flashing it (or anything really). If you feel you are not able to do that take the Tab to someone who can and he/she can fix it for you. This is important if you feel you can't do it DO NOT DO IT.
Make sure your tab is well charged (charged fully is best).
Fire up ODIN.
Use the CORRECT PIT file for you firmware (each firmware has its own PIT file). Put the PIT file in the PIT box and check repartition and by default the other 2 boxes will be checked (DO NOT TOUCH ANYTHING ELSE).
Load the firmware PDA PHONE and CSC (or if its a single tar file load it in PDA). Start flashing.
Finally before doing all the I SUGGEST YOU SEARCH AROUND. You will find many guides that can get you out of this situation.

My tab is not rooted, but odin showed a successful box. It just didn't restart.
Is it because I didn't root? How can I recover from the update process?

[Q] Have I ruined my in law's phone? Can anyone help me please?

My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work. After looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on many times, I also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you

I was never a fan of EZ-stuff.
That said, think you can easily solve that flashing your phone with odin and a proper rom. At this point i am unclear about what bootloaders you have on your phone since you've tried a downgrade.
Without getting into further details (sorry, at work atm). You can get tutorials easy for all of this around this forum.
I'd get Odin, get a proper stock rom from samfirmware with bootloaders included and flash it fresh from start with that. Doesn't really matter if it's froyo or ginger as long as it includes bootloaders.
You'll be left with a working phone at this point.
From here, if you still want to try to unlock it, i'd flash a kernell that would get me root (like the ChainFire one) since i find this the safest and easiest way of getting root on your phone and do a backup of your EFS partition (preferably saved in your computer or wherever outside your phone). This is very important, if you lose of mess up with this part of your phone it will be a pain.
Now, there are several ways of unlocking this phone, the only one i found to be most reliable (but not the easiest one) is to manually edit the nv_data.bin file (located in your EFS partition in hexadecimal.
There's a tut right here
http://forum.xda-developers.com/showthread.php?t=761045&highlight=unlock

Thank you so much for taking the time to reply although you are working!!! Really appreciate it.
I'll try your suggestion but I don't know how to choose the right stock rom with bootloader from samfirmware. I went to the website and registered but don't really know what to do.
I know you are working so might not be able to help me, may be someone else?
Here's where I am. Update. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.

Download Jvt From sammobile. com, you need Odin on your PC (1.7 or 1.8) plus Samsung drivers. Read there flashing guides carefully, check you have download
Mode, battery charged > 50% etc
There is also a video on youtube which shows you how to upgrade to jvt.
Sent using TCP/IP

Sounds like you've got the boot-loop problem, which means that you most likely "soft-bricked" the phone. Don't worry, this isn't that big of a deal and can be fixed with relative ease. I agree with the posters above, a clean flash with Odin will probably fix your problem and get you out of the boot-loop.
I'll go into a bit more detail with some steps (feel free to correct me if I missed anything)
1. Download Odin 1.85 here.
2. Head over to Samfirmware.com and grab the latest firmware for the phone. I recommend Gingerbread 2.3.5 (JVT).
3. Make sure your computer has the proper drivers installed so it can communicate with your Samsung Galaxy GT-I9000. If you've flashed the phone before with your computer then you probably have the drivers installed, but here's a link for them just in case: Samsung USB Drivers
4. Enter download mode on your phone, depending on your firmware, it could be Vol down + power + home OR Vol up + power + home. Pull the battery out, pop it back in, and hold those three buttons until the phone turns on.
If you can't enter download mode with the 3-button hold method, then you might have to do so via ADB with the command "reboot download".
Getting into download mode is pretty critical, as you cannot progress further without it.
5. Once you're in download mode (should see a triangle with an Android shoveling stuff in it), plug your phone into your computer's USB port and open Odin. In Odin, press "Reset" on the right hand side. Odin should be able to detect your phone (this is indicated by a yellow box on the left side). I'm using a PC, so inside the yellow box I see something like this: 0:[COM9]. On a Mac it probably says something different, but as long as you see the yellow box appear then it's all good.
If you don't see the yellow box, then there's no communication between your phone and the computer, which means that you may have to reinstall the Samsung USB drivers.
6. With the contents in the firmware package that you downloaded from Samfirmware.com extracted, load them onto Odin accordingly.
PIT: use s1_odin_20100512.pit
PDA: JVT (sometimes the PDA is labeled CODE instead)
PHONE: JVT (sometimes labeled as MODEM instead)
CSC: use HOME-MULTI-OXAJVT (should be about 9.5 MB in size)
Since your father-in-law's phone was originally 2.3.3, you shouldn't have to alter the bootloader with Odin, so leave the bootloader field empty.
7. Once you've loaded up all the necessary files, make sure Re-partition and Auto-reboot is checked. Leave the rest of the checkboxes as it.
8. Press Start. This should initialize the flashing of the new firmware. After the phone has been flashed, it should reboot automatically and should hopefully be able to get past the Galaxy S black and white logo (aka. boot loop).
9. The phone should be in working order now. I used this method to unlock my SGS: SIM Unlock on the SGS. With this method, your phone needs to be rooted, so head on over to ChainFire's thread here to install his kernal which is already rooted.
Flashing firmware can be pretty scary since nobody wants to end up with a brick that costed $400 and it seems like so much can go wrong, but hopefully the steps I've provided helped. Good luck!

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

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!

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.

Database Develop

welcome