(SOLVED)Soft Bricked 18200N - Galaxy S III Mini Q&A, Help & Troubleshooting

(SOLVED)Soft Bricked 18200N - Galaxy S III Mini Q&A, Help & Troubleshooting

HI I have a Samsung galaxy s3 min GT-18200N (i think that is the value edition) I had rooted it and I tried to install TWRP with Odin. It said it went ok but when I try to boot it it gets stuck on the first screen (The words "Samsung Galaxy S3 Mini GT-18200N" written in white) It does not move on to the next samsung logo screen.
I can access download mode but not recovery mode. I tried using odin to flash firmware found on sammobile.com it said ok but it still wouldn't boot to anything but download mode.
Please can anyone find any way to un-softbrick my device. Thanks
Note: I can't get SDK tools to work on my PC
If someone could find a package that I could flash using odin that would be ideal.
Edit Thanks everyone anyway but i managed to fix it

Hey. How did you fix it?. Same Problem here with stock firmware.

I don't know what the problem was the first time. Maybe it was odin or perhaps the firmware was dodgy. I just went back onto sammobile.com and tried another firmware from sammobile and it un bricked it. Just try another one and avoid ones specified for carriers. [e.g don't use Germany(Vodafone)]
In case you don't know how to flash the firmware here is the process
1 download and unzip the firmware, it should be a .tar.md5 file
2 start odin
3 click AP (PDA on newer versions)
4 select your .tar.md5 file
5 it will say "checking md5" or something
6 after about 10 minutes it will say "leave cs"
7 now connect your phone(in download mode)
8 odin will say "added"
9 check re-partition is not checked in options tab
10 click start
11 after about 5 minutes it will finish and the phone will reboot.
Like I say I don't know what went wrong the first time after trying a different download it worked. Try the above again with a different download and see if it un bricks your phone. If not then say what went wrong and I'll try to find another solution

Related

[Q] Samsung Tab P1000 not powering on

hi i have a Samsung Tab P1000 and now its not powering on after i forced to switch off from downloading mode,because I'm trying to update from Froyo 2.2 to gingerbread 2.3.3 but after following the instruction from opening the odin, putting the pit file and PDA file and i click the start its only showing the setupconnection.......please help me.....thank you

did you try to charge it? If not do that and flash again.

yes....i tried to put in charge and it showing like this in the photo but if i remove from tha charger i cannot powering on and the icon will disappear.....

i tried to flash again may tab using the odin it showing pass but its not continue to reboot......now its totally off

Samsung gtp 1000
cabansagarchie27 said:
i tried to flash again may tab using the odin it showing pass but its not continue to reboot......now its totally off
Click to expand...
Click to collapse
hi guy i ve the same problem, pls i just need to know if is an hard brick or just a soft.
I ve read many trhead on forum and i ve seen that if is hard brick i must use resurrection program but i cant find no link.
pls some one can post me? tnx

cabansagarchie27 said:
i tried to flash again may tab using the odin it showing pass but its not continue to reboot......now its totally off
Click to expand...
Click to collapse
That diagram you had is the same thing as the download mode. So treat it as such and flash your rom and kernel normally and it should work. I had the same problem before. To be sure, tried the following thread. Go to the 3rd post in this thread and follow the installation instruction. It will work. http://forum.xda-developers.com/showthread.php?t=1382055

I get that every now and then too. I reinstall the drivers (included with Kies), and reboot the computer. After that it will work.

Froyo to Gingerbread -- Please be extra careful when flashing
cabansagarchie27 said:
i tried to flash again may tab using the odin it showing pass but its not continue to reboot......now its totally off
Click to expand...
Click to collapse
Does ODIN still recognize your Tab? If you are upgrading from froyo to gingerbread, you may need to load new PIT file as well as new dbdata.rfs.
If ODIN still recognize your Tab, try to download your choice of firmware again with PIT file included. I'll attach a working PIT for you.
Note: Please extract the attached file to get the .PIT file and put it on PIT field on ODIN along with your choice of firmware you are flashing.
Once you are done and reboot, mostlikely you'll be in a boot-loop stuck at SAMSUNG screen. Now reboot to download mode again, then flash the DBDATA.rfs.tar I attached on the following post in PDA field on ODIN:
http://forum.xda-developers.com/showpost.php?p=23348040&postcount=121

i dont have the icon

wakak make sure you got the proper Samsung driver installed!

[Q] When flashing with BVJVC my phone became stuck on boot screen

Hi guys, since I had this problem I have flashed darkys rom because I know it works and needed a working phone but I still need help flashing BVJVC as I wish to have my stock orange rom back.
The problem is that when I download BVJVC from sammobile.com (formerly samfirmware.com) I then load up odin and load the JVC_JV6_JV3.tar file into PDA (it's just the one file) and put my phone (Galaxy s i9000) into download mode, plug it into my computer and click on start. It all seems to go well, no errors showing in odin and when complete my phone comes up with some kind of status 7 error (I can't remember the exact thing it said) and just sticks on the samsung galaxy s screen (the one the phone boots up from)
I have also tried using check fus downloader, selecting Orange UK and it downloaded the same rom, it too failed. And I'm not sure what to do with the zip.enc2 file as I just unzipped the normal zip file and used the .tar file within that. Not that it's important.
Please can you help as I really would like my stock rom back and to be able to update via kies again.
Thankyou in advance.

[Q] My Galaxy Note(SHV-E160L) is bricked...

before writing, I'm so sorry for my pooooor English.
I live in Toronto, Canada. I bought my Galaxy Note(SHV-E160L) from Korea, so change sim card from LG U+ to Rogers.
but when I sleep, Note encounter Unlimited Reboot.
so I try to repair in 3-way.
first, Factory reset. but I could make Download mode only, couldn't make Recovery mode.
so I try Samsung Kies Recovery mode, but Kies show me binery Error.
last, I want to use ODIN, but ODIN show me Error Message, too.
"Complete(write) operation failed"
What this means?
If it can't be repaired, I must send my cell phone to Korea.
I'm very embrassed...
please help me!!
and Merry Christmas for you

Is it sticking on factoryfs.img in ODIN ? this usually means its bricked which kernel where you on when you did the factory reset ?
I had a similar issue last week, stuck in odin, everything failing, I was convinced it was bricked, I manage to repair it by (no joking here) flashing a million wrong things in ODIN.... But DO NOT TRY THIS lol
try to flash a safe kernel through ODIN, and then see if it bring back recovery, then you can wipe and flash a new rom (hopefully)
otherwise there is the pit file method to revive from a brick, which works well, but loses around 3gb of internal sd space

hello
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.

Thanks for your reply
hanzo777 said:
hello bro...
try this method:
download a stock gingerbread rom then go into download recovery, flash it with odin, root your phone.
from here you can install any custom rom, this is how i do when i got bootloop.
Click to expand...
Click to collapse
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..

Sigea said:
Thanks, but when I use ODIN, ODIN got a trouble..
when It start to flash, ODIN shows error message (Complete(write) operation failed)..
so even I can't try another Kernel Files..
Click to expand...
Click to collapse
Perhaps should follow closely the guide for using odin from Dr ketan should help:
http://forum.xda-developers.com/showthread.php?t=1424997
1. Installation
- Download stock ROM (should start with a GB rom), and extract it to .tar file
- Download Odin, open it
- select PDA tab and point to ROM file. Leave Re-partition, pit, CSC, Phone tab unticked.
- Switch off device, Put in download mode (Vol down + Home + Power)
- completely close kies, Anti virus if running
- Connect device to PC
- ID com port shud turn yellow (not shown in image)
Now hit Start
----
see how it goes.

Same problem as OP
Hello guys,
unfortunately, I have the same problem with my 32GB SHV-E160L as OP. Little backstory:
I bought the GNote in Korea and brought it back to my country. I successfully rooted it with one of the guides here on XDA (Tegrak kernel, no OC whatsoever). No problems so far, the phone worked for weeks and I was able to do what you can do with rooted phones. One day while surfing the net it just crashed and was stuck in a boot loop. This is where I am now.
I tried:
Go into tegrak recovery. result: It gets stuck on samsung logo, funnily the phone would establish a usb connection if plugged in (as if in download mode)
Reset from Kies. result: After beeing told by Kies to go into download mode, instead of flashing the new software it gives an error message in Korean about missing binaries (see attachment)
Flash from odin. result: the dreaded red box with "fail" appears after the NAND write command
Now, after doing my research here on XDA I found out that my emmc might have damaged partitions and I need a PIT file. Here's where I'm stuck.... I can't find a PIT file for my 32GB note, only for the N7000 or the I717. And I don't want to mess things further up... so if anyone here could provide me with a PIT file, or tell me how to fix the phone through other means I would be really grateful
Thanks in advance....

You should ask hg42 if he can make one - in his thread I read that he did this before even for other devices.
So try a pm or post in his thread. Good luck

Note 5 Stuck on boot screen and won't open Recovery mode !!

So I recently tried rooting my phone ( Samsung Galaxy Note 5 SM-N9208 ) using custom firmware through Odin but when it had finished installing on to my phone it was just froze on the boot screen (saying "SAMSUNG Galaxy Note5 ... POWERED BY android"). I tried all kinds of ways like try and turn it off and on using the reset method (Volume down + Power key) but that didn't work.
I even tried to put it in Recovery mode but it just just puts me on the same boot up screen (saying "SAMSUNG Galaxy Note5 ... POWERED BY android"). The phone can be put on downloading mode but I tried to install the stock (orginal) firmware for my phones model (SM-N9208 ( duos ) ) but in Odin it just says "Fail". My Phone is still stuck on the boot screen and I don't know how to fix it and I think that if I take to to a repair shop they might say that trying to root your phone damages warrenty and not try to fix it. PLEASE HELP !! :crying:

Hey mate.
This happened to me.
1st I downloaded the stock firmware zip for my country there is a thread in general for all firmwares.
2nd unzip and flash AP file in AP section of Odin.
Wait for it on flash then you'll be good to go.
Sent from my SM-N9208 using Tapatalk

Which country firmware did you use?
Which country firmware did you use?

It worked ! Thanks
I actaully did finally use this method but I had to use Taiwan firmware as there is not English one but I don't think that matters, thanks :good:

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