Develop Bugs

[Q] PURE Heimdall Stock GingerBread Upgrade

All the current upgrade methods involve ODIN or don't explain the heimdall version in depth..
I HAVE NOT TRIED THIS YET - waiting for confirmation from someone who knows more than me.
Heimdall 2.3.3 Update v0.9 - UNTESTED
1) Back everything up. Titanium etc..
2) Download the new Stock 2.3.3 file, as found in Overcome 2.0beta http://www.multiupload.com/F6D7U1RUHD
2) Extract GB-stock-safe.zip into a folder.Go into the folder.
3) Now extract the GB_Stock_Safe_v1.tar file into another folder.
3) Copy the gt-p1000_mr.pit and the correct modem.bin into the extracted GB_Stock_Safe_v1.tar folder. So all the required files in one place now.
4) Plug Tab into computer and go to Download mode. (You can do this, by shutting/powering down your Tab. Once shut/powered down, hold down the Volume Down button and the Power button together until Download screen appears) or much easier if you have adb
Code:
adb reboot download
5) (Once in Downlaod mode) From the command line, run this function from the folder where the GB_Stock_Safe_v1.tar file was extracted, and you copied the gt-p1000_mr.pit and modem.bin file.
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
6) basically the movinand.mst and hidden.rfs files are still in the folder but not referenced.
Is this correct !? Can someone confirm or deny please?
I'll update this post with corrections

Just used these instructions to take a stock Froyo Galaxy Tab to Gingerbread stock version (Overcome restock v5) using only Linux.. and then to CM7.
I installed the deb package from the Heimdall web site and installed it into my Ubuntu 10.10 install. Worked like a charm. Thanks a bunch for posting this. Saved me trying to mess around with Windows.

[Q] Help with building stock kernel

I would like to learn how to build stuff for my tmobile s2. I figured I should try to build the stock kernel first to get my hands dirty. I have been following this guide here: http://forum.xda-developers.com/showthread.php?t=1442870
Unfortunately it is for the Epic Touch 4G, but I think a lot is similar. I have several questions regarding building a kernel for the T989:
1) How can I extract the initramfs from a stock boot.img?
2) The guide from the link above tars a zimage file. Does this need to be boot.img for the T989?
Thanks.

Below I have posted what I have done so far in trying to compile a kernel for the T989, in case anyone else is also learning like me.
I am using Ubuntu 10.10 32-bit
1) Download T989 source code from here: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T989 (download the T989 version for TMobile)
2) unzip SGH-T989_GB_Opensource.zip
3) extract SGH-T989_Kernel.tar.gz
4) next you need to get a version of the initramfs. I got it off of my phone using clockworkmod backup (boot.img file) and following this guide to extract the initramfs: http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows
5) Download arm toolchain here (I use version 2010.09): https://sourcery.mentor.com/sgpp/li...09-51-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
6) extract toolchain
7) Setup cross compile script (run before doing compiles) (change CROSS_PATH for your setup):
cross-compile.sh:
BINVERSION=arm-2010.09
export ARCH=arm
export CROSS_PATH=~/android/toolchains/${BINVERSION}/bin/
export CROSS_NAME=arm-none-eabi-
export CROSS_COMPILE=${CROSS_PATH}${CROSS_NAME}
export CC=${CROSS_NAME}gcc
export CXX=${CROSS_NAME}g++
export LD=${CROSS_NAME}ld
export STRIP=${CROSS_NAME}strip
PATH=${CROSS_PATH}:$PATH
8) Compile script (modify CONFIG_INITRAMFS_SOURCE to point to your initramfs) :
source ../scripts/cross-compile.sh
cd kernel
make clean
make mrproper
make msm8660_celox_usa_tmo_defconfig
make modules
make -j5 CONFIG_INITRAMFS_SOURCE=../initramfs
9) The kernel image is in "arch/arm/boot/zimage"
10) *** Question: How do I make the zimage "odin" compatible
This is still not complete (Steps 10 is unsolved). I need to make the build image odin compatible.
If anyone knows of a kernel building guide that exists for the T989 please post here.
Thanks.

You should pm the devs that posted their kernels in the dev section. Im sure they would love to help. Even exchage google talk or google + with each other to get quicker answers.
sent from the Dark §¡3€

I noticed you hit up the e4gt thread so I came here to see If I can help. If you have Irc I can walk you thru It all the way. I lost all my data today so my machine is down for building. im on freenode #evervolv ...

interloper, thanks for the kind offer. Please let me know when your machine is up and running. Hope to hear from you. Thanks again.

This is the script you want to use to extract the initramfs http://forum.xda-developers.com/wiki/Extract_initramfs_from_zImage
It works for the E4GT without modification so it should work for you guys without modification.

dtm_stretch,
Thanks for the extract script. The script does not work when I try to extract the initramfs from a boot.img I got from doing a backup with clockworkmod. It only manage to extract two empty folders: "dev" and "root"
However, the script does work when I tried it on a zImage I built myself. With the kernel I built I used the initramfs provided at: https://github.com/bubby323/anomaly_kernel_platform_SGH-T989/tree/master/initramfs
I know I can use the initramfs at the github but I really would like to learn how to get it myself so I can apply to other phones later. The knowledge is more important to me.
Thanks.

I was able to extract the initramfs from the boot.img (cwm backup of my phone) using the tools at this site: http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows
Now my only problem is making a odin compatible (flashable) kernel from the compiled zImage. Is it as simple as renaming zImage to boot.img and then put it in a tar to flash with odin? The only reason why I am not certain is my zImage is only about 5megs while the boot.img is 10megs. It seems like the boot.img is a disk copy of the flash partition for the boot on the phone. Do I need to use dd to copy my zImage into boot.img?
I know I make no sense. Hopefully with this last step I have it all down (at least for creating a kernel, rom is next). Please help a noob. Thanks.

datzstr8 said:
I was able to extract the initramfs from the boot.img (cwm backup of my phone) using the tools at this site: http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows
Now my only problem is making a odin compatible (flashable) kernel from the compiled zImage. Is it as simple as renaming zImage to boot.img and then put it in a tar to flash with odin? The only reason why I am not certain is my zImage is only about 5megs while the boot.img is 10megs. It seems like the boot.img is a disk copy of the flash partition for the boot on the phone. Do I need to use dd to copy my zImage into boot.img?
I know I make no sense. Hopefully with this last step I have it all down (at least for creating a kernel, rom is next). Please help a noob. Thanks.
Click to expand...
Click to collapse
Sorry for not replying sooner, but if you want to create a flashable tar in terminal
Code:
# cd /where/your/zimage/is/located
# tar cvf whateveryouwanttocallyourkernel.tar zImage
or you can just use a zip that already flashes a kernel and swap out the zimages.

I was able to successfully build my kernel and flash it to my phone. I needed to use mkbootfs and mkbootimg to combine my zImage and ramdisk to make boot.img. I will post a tutorial up in the development section and will link it here when I am done. Hopefully it will help all the noobs like me get their feet wet. Stay tuned.
update:
here is the link to the guide: http://forum.xda-developers.com/showthread.php?p=22941057#post22941057

ODIN .tar
I advise all of you to learn bash scripting. With bash scripting or pearl you can automate this entire process. Also create a cheat sheet text document with long but common commands, git command reminders and things like that. These commands should create your ODIN .tar file. First cd to the directory the junk is in then:
Code:
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage boot.bin recovery.bin param.lfs sbl.bin > myOdin.tar
That makes the tarball
Then:
Code:
md5sum -t myOdin.tar >> myOdin.tar
That does the MD5 sum
Then:
Code:
mv myOdin.tar myOdin.tar.md5
That sign the tarball with the MD5 sum
You should be able to ODIN that .tar. Now, for the first command you can replace whatever files you want tarred with what I put. If you only want the modem.bin specify that only, etc.
Another word of advice is to find helpful helpful Nautilus scripts to ad to the right click context menu for time saving simple operation. Google it and you find several good resources. Also, if you look, there are Nautilus scripts that can be added to zip and sign .zip and .apk files to make that faster and easier.
Be careful out there and good luck.

How to Make an Odin .img Tar File...?

Hello,
I'm just wondering how I can make the .tar file with the recovery.img file in it and flash with Odin? Does anyone have a guide to how to do this? I recently downloaded the latest recovery from Clockworkmod website, but don't know what to do from there. I know how to flash with Odin of course, but don't know how to make the .tar file with the recovery.img file in it. I tried to (NOOB) rename the recovery file I got from cwm website to "recovery.img" and put it as a .tar file using 7Zip, thinking it would work, but didn't work. So I'm guessing there's another way, I'm sure I can figure it out with a good guide. Thanks!
P.S: Only reason why I want to know how to do this is because there's no actual place to my knowledge where I can update my cwm recovery automatically, but if anyone knows an automatic way of updating cwm that would be a big plus. Thanks.

you could use rom manager. As long as your device is rooted, Rom Manager will download and flash your recovery for you.
or...
You can also put your recovery file on your sdcard so that the path would be /sdcard/recovery.img Then using either adb shell or terminal emulator, the command would be
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

lordmorphous said:
you could use rom manager. As long as your device is rooted, Rom Manager will download and flash your recovery for you.
or...
You can also put your recovery file on your sdcard so that the path would be /sdcard/recovery.img Then using either adb shell or terminal emulator, the command would be
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
Oh yeah I know about rom manager, I just want to know how to make the file so I can, in the future update my cwm recovery version. I use Rom Manager to flash the recovery and do what I want in the recovery, that's not an issue, just updating it to a later version if one comes out is why I want to know how to make the file. I tried to download the latest cwm from Rom Manager, but when it gives me the devices list to download, the Galaxy S3 is not there.

A day or two ago I opened rom manager and it prompted me that there was an update for my recovery downloaded it and flashed it no problem

You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.

DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
Ah thanks! I downloaded that tar file and updated successfully! I will try that command guide out and see if it works. Thanks again! :fingers-crossed:
lordmorphous said:
A day or two ago I opened rom manager and it prompted me that there was an update for my recovery downloaded it and flashed it no problem
Click to expand...
Click to collapse
Hmm...that's really weird..I never got such a message.
EDIT: Tried the command guide, and it didn't work unfortunately, but it does show the recovery.tar file, won't let me open saying it is damaged. On the cmd it tells me: 'tar' is not recognized as an internal or external command operable program or batch file.
The recovery.tar file is made though, but can't be opened. Any tips?

Thr toolkit posted lets you do that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

is 6.0.1.2 much better than the version from the toolkit?

No I'm saying that the toolkit Lets you make img files into Odin flashable tar files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

drakeymcmb said:
No I'm saying that the toolkit Lets you make img files into Odin flashable tar files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes you're right! Thanks a lot. Made one using a recovery image downloaded from cwm website, makes tar file and everything, worked when flashing with Odin. Thanks again.

DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
To do the same thing in windows, you need to use Cygwin.

what is the toolkit u guys are talking about? Is there a link?:silly:

http://forum.xda-developers.com/showthread.php?t=1746665
I think this is the one they are referring to.

mrhaley30705 said:
To do the same thing in windows, you need to use Cygwin.
Click to expand...
Click to collapse
I happened to have Cygwin installed so I used it to tar the image, but you could probably use 7-z

DeathKoil said:
You are in luck, I needed a ODIN flashable tar of CWM 6.1.0.8 yesterday, and I made a flashable tar.
http://forum.xda-developers.com/showthread.php?p=30494477#post30494477
I run linux, and I"m not positive how to make your own ODIN flashable .tar from a .img file in Windows, but on Linux the commands are as follows.
Download the recovery from the CWM website.
Rename the file from <WhateverItsCalled>.img to recovery.img
Open a terminal window and get to the folder that recovery.img is in.
Type in the following command without the quotes: "tar -H ustar -c recovery.img > recovery.tar"
You will not have an ODIN flashable file called recovery.tar.
To flash it, open ODIN, make sure your phone is in download mode and ODIN sees it. Click on the PDA button, choose recovery.tar, hit start. The phone will reboot when its done.
Click to expand...
Click to collapse
I'm also running Linux, but my computer seems to have problems communicating with my S GS3 (T999V). It doesn't help that I'm new to linux, but where do you get a driver for the gs3 for linux? Also, if I were to package a ROM into a .tar or .tar.gz to be flashed with Heimdall, what do? just unzip my rom, repackage as .tar.gz and try with heimdall?

I stall out on flashing recovery image. Here's what I get. I'm using a tar where I manually swapped in the recovery image on my own.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
Click to expand...
Click to collapse
And it just stalls. The screen of the phone appears as if nothing happened. I don't see the progress bar or anything.
Odin shows the first blue bar of the progress bar but it never goes beyond that.
Any help?
EDIT - it worked fine using one of the tars from this thread. - http://forum.xda-developers.com/showthread.php?t=2015369 - So what am I doing wrong when substituting a recovery image on my own?

[Q] Extract Boot.img from Stock ROM

Hi guys, I would like to extract boot.img from a Stock ROM without the need of installing it on my (Galaxy Note 2 T-mobile). All I found on the internet is how to extract it from an installed ROM.
So I would like to:
1. Extract the boot.img
2. Then flash it through ODIN to my custom ROM (Jedi Master 14)
Thanks in advance and please help me :crying:

Why would you do that?
Hastily spouted for your befuddlement

I don't know how you going to use boot.img to fix your problem. But the .md5 rom files are just zipped files. unzip and you will find the boot.img file. Are you sure that this will fix your problem?
Are you trying to change your boot image?

Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.

Thanks a lot. Thats exactly what I am looking for.
Sent from my SGH-T889 using xda app-developers app

Darkshado said:
Use a tar archive program (7-Zip, Winzip, Winrar, PKZip, this format is pretty universal) to extract what you need from the official Samsung ROM images. (Check out sammobile.com if you haven't already, you will need to register.)
You might get some error message about the end of the archive, that's normal and due to the presence of the MD5 hash at the end of the file, which most programs will be able to work around nonetheless.
Repack the relevant file with a *nix tar binary, or under Cygwin on a Windows machine. (YMMV, but those are the two only ways I've managed to have the files work with Odin.)
Reboot phone to download mode and flash with Odin as usual.
Done.
Click to expand...
Click to collapse
and how do we do?
i flash the file without pepacking it so i can t bot, kernel error!
I'm really annoyed if you can explained to me how do we do it
thx

How to go back to official firmware

Hii. I am ankit.
I have downloaded custom rom and twrp recovery.
Now i want to get back to stock rom and stock recovery in my phone.
And also wants to use official updates of phone's software.
Can anyone help?

1.Download the odin
2.Download rome orginal a50

Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.

Syndamia said:
Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.
Click to expand...
Click to collapse
Sorry sir but I don't know how to use linux.
Could you tell me easy way.

_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .

_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/guide-how-to-downgrade-to-android-9.4096323/ Same procedure, just use newest Android version.

Watch this video How to Flash Samsung Galaxy ROM ( Firmware ) with ODIN

Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.

SudanTmz said:
Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.
Click to expand...
Click to collapse
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom

peter couniaz said:
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .
Click to expand...
Click to collapse
After that could I use knox services like secure folder etc.

_Ankit_Chahar said:
After that could I use knox services like secure folder etc.
Click to expand...
Click to collapse
Yes you should be able to use secure folder after going back to official firmware .

kisvagen said:
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom
Click to expand...
Click to collapse
And if for example, I want to go back to Android 9, which is binary 5 and my A50 is Android 11, binary 7, is there any way I can ignore the binary or something?