Hi, I have a friend who currently has
Android Recovery System <2e> on his droid. Wanting to know if there's a way to change from that to Amons? Also, while using the <2e> any zip he tries to install comes up with the error E: Can't open /cache/recovery/command
If he scrolls down to Apply sdcard: update.zip he gets:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification fialed
Installation aborted.
This happens when trying to open .zip's such as Evil Eris 2.0 or any other zip. I have Amon's recovery and these zips work fine for me.
Any and all help is appreciated. Thanks in advance.
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
No files/names have been changed. If I could get Amon's recovery I could mod his phone for him. I have Amon's and do not have this issue. It is prbably something I am not doing due to being unfamiliar with the recovery he has. Basicaly I think all I really need is a way to get his recovery to read Amon's and I'm good.
andrew8806 said:
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
Click to expand...
Click to collapse
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
If his phone is rooted just download rom manager from the market, open it, scroll all the way to the bottom and hit flash alternative recovery.
That should do it.
.mak said:
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
Click to expand...
Click to collapse
I change the name of update.zip and it always fails to verify.
I've gotten into the habit of running all kinds of ROMs and sometimes they just blow up. Usually a reboot suffices but the last crash caused my phone to only bootloop and I couldn't get into recovery anymore, thankfully download mode still worked. This will focus on how to get your phone back to life, provided you can access download mode.
Steps this guide will walk you through:
Calm down a bit
Get everything you need to fix your phone
Do the magic
Boot your phone
Rejoice
Step 0: Backup
I can't stress this enough. Once you've really bricked your phone there's a chance you might not be able to access the data that's on there anymore. So, if there's stuff on your phone you care about, just backup it from time to time.
Step 1: Calm down
There's a myriad of exercises you can do to calm down, meditate, go for a walk/swim/jog, go to the gym, whatever works for you. Just chill out for a second because being in a completely panicked state is not going to help you to recover your phone.
Step 2: Get the tools in place
We need a few tools to fix your phone:
Heimdall version 1.3.1. DO NOT download 1.3.2 it has issues with uploading large files
Windows: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
Mac: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.3.1-mac.dmg
Debian AMD64: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_amd64.deb
Debian i386: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_i386.deb
Heimdall package of 2.3.6/XWJVZ: http://www.mediafire.com/?3v35chw9a8a2wmw
CFRoot for 2.3.6/XWJVZ: http://download.chainfire.eu/130/CF-Root/SGS/CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
Once you've downloaded everything:
Install Heimdall (run the installer)
On Windows the link I provided also includes the GUI
For Mac and Linux the link I provided only includes the command line binary, we don't want to use the GUI for this
Extract the Heimdall package of 2.3.6.tar.gz to a directory, you should end up with the following files:
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
firmware.xml << delete it, we're not going to need it
modem.bin
params.lfs
Sbl.bin
s1_odin_20100512.pit << delete it, we're not going to need it
zImage << delete it, we're not going to need it
Extract the CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip, this contains only one file: zImage, put it next to Sbl.bin
If the Heimdall installer asked you to reboot your machine but you didn't, do it now. That will make sure the drivers are loaded.
What we've done right now is set up your machine so that it's ready to flash your i9000 back to a Samsung release of Gingerbread. The astute reader might notice I'm telling you to delete the zImage (kernel) from the Heimdall package. This is true but we're replacing it with the one from CFRoot so you can flash a rooted stock instead of first flashing stock and then flashing CFRoot on top. Some people advice against this approach but it has never caused me issues.
Step 3: Do the magic
Now we're actually going to flash your phone. We're going to do this from the command line because the Heimdall GUI is a bit twitchy when it comes to flashing without a PIT-file. The command line has no such issue and will just download the PIT from your device and use that.
Windows:
Find out where Heimdall was installed (probaly %PROGRAMFILES%\Heimdall)
Copy all the files (zImage, Sbl.bin and so forth) into the directory where the heimdall executable is located
Go to the location of cmd.exe, right-click on it and select: Run as Administrator
Now cd to the directory Heimdall was installed
Issue a dir on the commandline to verify all the files (heimdall.exe and the rest) are there
Mac / Linux:
Heimdall was probably installed into /usr/bin so all you need to do is open a Terminal of your choice and see if running the heimdall command results in heimdall output or a command not found.
Open a Terminal
cd to the location of zImage, Sbl.bin and the other files from Step 2
Flashing:
Use the 3-button combo to put your phone into Download mode: Volume Down + Home + Power and connect your phone over USB to your computer.
Windows, issue the following command:
Code:
heimdall.exe flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
Mac / Linux, issue the following command:
Code:
sudo heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
If all went well you should get output similar to this:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
IBL+PBL upload successful
Uploading SBL
100%
SBL upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Your device will now reboot. If it doesn't and stays at a black screen, just pull the battery, put it back in and turn it on.
Step 4: Boot your device
Just let the phone boot but don't unlock your SIM-card / use it. Once it's is done booting for the first time just shut it down and now boot into Recovery Mode: Volume Up + Home + Power.
From here you can go into the Mounts and Storage section and then into the Mount USB menu. Now your phone will make it's storage available over USB so you can recover files you've lost or upload a zip-file to flash a new ROM.
Step 5: Rejoice
Your phone is now back into a workable state with a fully functional Recovery so you can now start flashing your fancy ROMs again.
A few pieces of advice:
Before you flash anything else: data/factory reset and wipe your cache
Before you flash anything else: flash CM 9.1.0, twice. The first time will upgrade your Recovery to 6.x but will then bootloop so you need to flash it again.
If you want to flash a JellyBean ROM, flash CM 9.1.0 first. If you don't and try to upgrade from Gingerbread (2.3.6) to JellyBean in one go you'll probably end up with an invalid IMEI (no idea why this happens, it just does)
Good luck!
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
ERROR: Failed to confirm end of file transfer sequence!
IBL+PBL upload failed!
Ending session...
Rebooting device...
Click to expand...
Click to collapse
Please HELP me
What do I do from here??
battznz said:
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Please HELP me
What do I do from here??
Click to expand...
Click to collapse
That one is in my experience either caused because you supplied a PIT-file or because you've got a funky version of Heimdall.
how about when the phone can't get to download mode :/
usb jig?
microMXL said:
how about when the phone can't get to download mode :/
usb jig?
Click to expand...
Click to collapse
try solutions in My Android Solutions
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
SpartanWarrior said:
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
Click to expand...
Click to collapse
try download from My Android Collections
Phone stuck in bootloop, possible corrupt internal memory?
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.[/QUOTE]
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks
mars777jd said:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
Click to expand...
Click to collapse
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hi,
I tried EzBase Rescue, with the following result:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
-- Wiping data...
Formatting /data...
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
I will try the resurrection kit...
mars777jd said:
Hi,
I tried EzBase Rescue, with the following result:
I will try the resurrection kit...
Click to expand...
Click to collapse
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
mars777jd said:
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
Click to expand...
Click to collapse
you can try http://depositfiles.com/files/ro6fnlr38 or http://depositfiles.com/files/zay0if5x7 for Darky and a solution from My Android Solutions for
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
microMXL said:
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
Click to expand...
Click to collapse
usb jig can only work when USB slot is not damaged or misaligned , check usb connection problems in My Android Solutions or read this thread
mars777jd said:
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks[/QUOTE]
Same happens to me. Any idea on what's going on?
vindikleuk said:
it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"?
Click to expand...
Click to collapse
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Well what happened is this:
I saw this phone going cheap on eBay by someone who said that they "had tried flashing a custom ROM, and now the camera won't work due to a memory error." I had successfully flashed CM7 to a Nexus One, so I wanted to see if I could fix it.
I don't know what ROM he tried to install, but at that point the phone still booted. I could use the phone and all functions that didn't need free memory (ie camera). I went into settings, and, like I mentioned, although there was a micro-SD card the phone reported "0.00B free of 0.00B Internal" and "Please insert an SD card" for external. I thought it may have been a problem with the SD card, so I formatted it on the computer. Same result.
I then proceeded to flash a known trusted stable ROM to the phone. I opted for CM9 with CWM for I9000. This is where I first ran into problems. I was using fastboot at the time, and always, after flashing anything I would get these results (see pics.) So I downloaded Odin, and after trying several different things from various wiki's and guides on xda and other sites, I believe I have successfully wiped any existing OS, and any custom recoveries.
The phone's model is GT-I9000. The SSN is I9000GSMH. I also have the IMEI and S/N. From my understanding, it was originally locked to Vodafone, and was unlocked by the previous owner.
So far I have tried flashing:
CM9
DarkyRom_10.2 Resurrection
ezbase gb
SGS_Rescue_kit-13-1-2012
plus a few different individual pda, csc, bootloader files.
I am again going to try DarkyRom_10.2 Resurrection, once I can get Odin to recognize my phone.
Is there any thing else I can try? Or should I try to sell my phone for parts?
I really appreciate everyone's help
Thank you so much
mars777jd said:
Is there any thing else I can try? Or should I try to sell my phone for parts? I really appreciate everyone's help
Thank you so much
Click to expand...
Click to collapse
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
xsenman said:
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
Click to expand...
Click to collapse
OK, I will try that, do you know where to find those?
mars777jd said:
OK, I will try that, do you know where to find those?
Click to expand...
Click to collapse
in My Android Collections
i am new to this forum so i want to apologies if my problem is simple to the most experienced members.
After automatically updating my samsung s8 (greek version) my phone never booted.
Now i have it in Android recovery screen and the samsung service told me i have to delete my data (my phone still has guarantee ). The problem is that i have important data that i need to backup and i need a way to backup my bricked phone!!!
the message at the bottom of the screen is
#fail to open recovery_cause (no such file or directory)
support single-sku
file-based OTA
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm verify verification failed..
E:[libfs_mgrlis_dt_compatible():firmware infowas not valid '/proc/device-tree/firmware/android/compatible : no such file or directory
I am thinking updating with sd card my firmware, i am not sure how to do it, where to find the file and if this will erase my data.
The most important for me is not to lose data (sms, pictures, voice recording, viber, whats app and messengers)
i also found software that says can backup data from bricked phones but i am not sure which is good. did anyone used any of these???
Please any help will be valuable to me
panoszam said:
i am new to this forum so i want to apologies if my problem is simple to the most experienced members.
After automatically updating my samsung s8 (greek version) my phone never booted.
Now i have it in Android recovery screen and the samsung service told me i have to delete my data (my phone still has guarantee ). The problem is that i have important data that i need to backup and i need a way to backup my bricked phone!!!
the message at the bottom of the screen is
#fail to open recovery_cause (no such file or directory)
support single-sku
file-based OTA
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm verify verification failed..
E:[libfs_mgrlis_dt_compatible():firmware infowas not valid '/proc/device-tree/firmware/android/compatible : no such file or directory
I am thinking updating with sd card my firmware, i am not sure how to do it, where to find the file and if this will erase my data.
The most important for me is not to lose data (sms, pictures, voice recording, viber, whats app and messengers)
i also found software that says can backup data from bricked phones but i am not sure which is good. did anyone used any of these???
Please any help will be valuable to me
Click to expand...
Click to collapse
Flash official firmware with odin and on the csc section use home csc your files will remain then
kpwnApps said:
Flash official firmware with odin and on the csc section use home csc your files will remain then
Click to expand...
Click to collapse
thank you for the answer
please can you give me a link with instructions, never done it before
is it safe for my data?
where can i find the official firmware
Yes its save.
Download the firmware download too from here:
https://www.google.com/amp/s/forum....l/tool-samfirm-samsung-firmware-t2988647/amp/
When done open samfirm and write on modelbox your s8 model number. Then on Regionbox write VGR. When done select the auto option and binary nature. Uncheck CRC32 and hit Check Update. It should display a logic value, if thats the case tap on download.
After you downloaded the firmware, extract it somewhere. Open your browser and go to this: https://devsjournal.com/download-odin-tool-for-samsung.html. Download the latest odin then extract it.
Now open odin. Select BL and choose the extracted firmware file that starts with BL wich you downloaded from samfirm tool. Then select AP and use file wich starts with AP. Now the same with CP.
Now most importantly. Click CSC and select HOME_CSC file. Not the normal CSC one. When done. Boot phone in download mode with home+power+vol.down button in same time. Connect phone with pc or laptop and click start in odin.
DO NOT TOUCH THE OPTIONS OR PIT TAB