Develop Bugs

[Q] Can Odin screw up a flash?

This happened to me twice, same computer with Windows 7 64 bit. Both the phones were SGS with JG4 by default and both didn't have 3 button combo working, whenever I try to flash Odin gets stuck at "Set Partition" and I take the cable out it gets stuck at "Phone - ! - PC" screen.
I am sure I am selecting the files correctly(PIT was 512, CODE in PDA, CSC in CSC, MODEM in PHONE), this is in attempt to install JPC on the phones. I also select "Re-partition" apart from the 2 other checkboxes.

You cannot select any flash files while you tick re-partition.
The phone needs to do a power cycle after it has been re-partitioned.
Did you get to download mode by using ADB?
Odin cannot screw up your flash, only you can.

So what should have I done? I got into downloads mode via ADB.

Actually you do not need to repartition unless you previously used 513.pit.
Start Odin.
Plug in the phone.
Type in CMD "adb reboot download"
Select flash files.
Download.
Any other way the flashing process will hang.
Do just as described.

Aren't you supposed to use pit 803 when flashing to JPC? Wouldn't recommend flashing JPC anyways.

803 is for P1000, thou it works with I9000 too.

Richthofen said:
803 is for P1000, thou it works with I9000 too.
Click to expand...
Click to collapse
Yeah I know that, but isn't the problem here that he's using the 512 pit with JPC which doesn't work?

Richthofen said:
You cannot select any flash files while you tick re-partition.
The phone needs to do a power cycle after it has been re-partitioned.
Odin cannot screw up your flash, only you can.
Click to expand...
Click to collapse
can you explain that? i always thought you can tick the repartition option during normal flash. i have never read that you have to repartition in a "separate cycle" and i did i several times (possible it got stuck then, i'm not sure anymore)! not that i want to question your knowledge, i am just wondering ...
jackiechan8 said:
Yeah I know that, but isn't the problem here that he's using the 512 pit with JPC which doesn't work?
Click to expand...
Click to collapse
obviously it does!

So even if I get my 3rd replacement phone without 3 button downloads mode, I can flash a firmware in it?

Richthofen said:
You cannot select any flash files while you tick re-partition.
The phone needs to do a power cycle after it has been re-partitioned.
Did you get to download mode by using ADB?
Odin cannot screw up your flash, only you can.
Click to expand...
Click to collapse
How will the phone boot after you tick re-partition + insert just a .pit file and then flash? I mean, what kind of boot it should do?
Should it boot to android so I can use adb to get into the download mode or does re-partition result the phone--!--PC screen in the first power cycle? My phone has the "3-button disabled" thing so I'd rather not brick my phone.
I know you said it should still be able to boot into the download when that p--!--PC screen is shown even if it doesn't boot into the download mode under "normal" conditions.

Aanrii said:
How will the phone boot after you tick re-partition + insert just a .pit file and then flash? I mean, what kind of boot it should do?
Should it boot to android so I can use adb to get into the download mode or does re-partition result the phone--!--PC screen in the first power cycle? My phone has the "3-button disabled" thing so I'd rather not brick my phone.
I know you said it should still be able to boot into the download when that p--!--PC screen is shown even if it doesn't boot into the download mode under "normal" conditions.
Click to expand...
Click to collapse
i guess the repartitioning does not affect the bootloaders just the /system /data/ /dbdata /cache etc. partitions. also you can always just untick the reboot option and directly flash afterwards without a reboot...

jodue said:
i guess the repartitioning does not affect the bootloaders just the /system /data/ /dbdata /cache etc. partitions. also you can always just untick the reboot option and directly flash afterwards without a reboot...
Click to expand...
Click to collapse
Richthofen precisely says that the phone should be shut down and battery should be removed after flashing with just .pit file. So you shouldn't directly flash it afterwards.

Can't get out of ODIN mode

I tried to install TWRP, but I had some problem with that. After I tried couple of time I stack in Downloading mode.
Now I can't get out of odin mode, no mather what I do.

Make sure that the recovery is compatible with your phone
Or
Try to download ofw riginal firmware of s4 mini
And flash it

yahiahedna said:
Make sure that the recovery is compatible with your phone
Or
Try to download ofw riginal firmware of s4 mini
And flash it
Click to expand...
Click to collapse
I tried both but dosn't helped.
Sent from my HUAWEI G6-U10 using Tapatalk

Hold the power button it will end the download mode.
Have you flashed the right TWRP or FW to your phone The S4 mini are have different Versions.
9190 / 9192 / 9195 and the newer Device 9192 I and 9195 I.

bierma32 said:
Hold the power button it will end the download mode.
Have you flashed the right TWRP or FW to your phone The S4 mini are have different Versions.
9190 / 9192 / 9195 and the newer Device 9192 I and 9195 I.
Click to expand...
Click to collapse
Thanks.
I finaly find right TWRP for my device 9195I, and I finaly start TWRP but now I have new problem.
I tried to install LineageOS, but I get an error:
"could no detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory"
I tryed to add a photo but I don't know how??
Any idea where is the problem?

Try to reboot from TWRP to Recovery
Than install the ROM
Make a backup!
Reboot into recovery
Wipe data (You may get a "staus 7" error if you fail to wipe.)
Install the Current ROM
Optionally install Gapps
Boot phone into normal mode

bierma32 said:
Try to reboot from TWRP to Recovery
Than install the ROM
Make a backup!
Reboot into recovery
Wipe data (You may get a "staus 7" error if you fail to wipe.)
Install the Current ROM
Optionally install Gapps
Boot phone into normal mode
Click to expand...
Click to collapse
I tred but the problem is the same.
"could no detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4 mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory"

OK, go complete back to Stock, flash the ROM with Pit.file and than try again to flash TWRP and Los 14.1

bierma32 said:
OK, go complete back to Stock, flash the ROM with Pit.file and than try again to flash TWRP and Los 14.1
Click to expand...
Click to collapse
Pit file?
Where can I get it?
How to flash?
Thanks.
Sent from my HUAWEI G6-U10 using Tapatalk

Install samfirm https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Download a multiple firmware, in side of CSC.image you find the pit.file.

bierma32 said:
Install samfirm https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Download a multiple firmware, in side of CSC.image you find the pit.file.
Click to expand...
Click to collapse
As you sugested I downloaded stock firmware for my device" I9195IXXU1AQA7.....tar.md5", but I don't find any pit file.

Copy the CSC.img to a sperate Folder, unzip the image and than you have got the Pit.file.
https://www.pocketpc.ch/attachments...galaxy-s7-s7-edge-g930f-g935f-unbenannt5.jpg?
Under Pit you must select the the file and actived the Repartion Option.
Samfirm
https://www.pocketpc.ch/attachments...-galaxy-s7-s7-edge-g930f-g935f-unbenannt1.jpg
Odin
https://www.pocketpc.ch/attachments...amsung-galaxy-s7-s7-edge-g930f-g935f-odin.png

bierma32 said:
Copy the CSC.img to a sperate Folder, unzip the image and than you have got the Pit.file.
https://www.pocketpc.ch/attachments...galaxy-s7-s7-edge-g930f-g935f-unbenannt5.jpg?
Under Pit you must select the the file and actived the Repartion Option.
Samfirm
https://www.pocketpc.ch/attachments...-galaxy-s7-s7-edge-g930f-g935f-unbenannt1.jpg
Odin
https://www.pocketpc.ch/attachments...amsung-galaxy-s7-s7-edge-g930f-g935f-odin.png
Click to expand...
Click to collapse
Thank you for you help, but I finaly managed to install stock firmware, install TWRP recovery and lineageOS.
The problem was "hidden.img.ext4" file in stock firmware. After I delete this file, there was no more problem with installation.
Thanks again.
Best regards.

Reset Screen Lock Without DataLoss- Latest Samsung Devices

Hi. I want share important thing with you. Some of Samsung devices support reset screen lock with programmators (z3x, octoplus etc.) when FRP/FAP is ON.
But most of devices are not supported by this boxes. Only way is COMBINATION FILES. Just flash Combination file (make sure REV number is same with your device firmware- see it on Recovery mode) with Z3x box (or any tool), and uncheck (IMPORTANT!!!) CACHE and PIT sectors. Then press Flash button and your device will be opened with data in it. You can transfer your files to your PC and reflash phone with format all data, or reset FRP, flash only AP, and then TWRP, and delete this files:
/data/system/gesture.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
Then your device will be opened without screen lock and data in it. You also can do it with Odin. Delete .md5 extension from Combination File, open it with Winrar and delete Cache and Pit files from archive. Then rename it with .md5, and flash with Odin (AP).
Note 1. Devices that have encrypted internal storage not support this way. If you have such device, then your phone will be start with Pin code after you flash it with comb files. Just flash official firmware(AP) and device will be back previous stiuation(Screen lock).
Note 2. If you flash whole comb file with CACHE and PIT all off your files will be deleted permanently! Be careful!
Good lock! I'm sorry, Good Luck!

Anyone tried the above successfully? does it work on xiaomi phones?

s_m_a_s_h said:
Anyone tried the above successfully? does it work on xiaomi phones?
Click to expand...
Click to collapse
I tried this method with one exception: removed userdata.bin as well from the binary, on J710MN ZTO with U4 Combination file. First attempt i removed both the pit file and the cashe binary. Rebooted with an error message "dencryption failed". I could hear a sound from the PC that indicated the phone was connected and it made a chime even with the lock still on. I reflashed Stock rom with no CSC and system booted like previously with a pattern lock. I went back to. Second, I reflashed same combo file but I put back the userdata binary now it went through with no lock but no data is to be found. So now i'm most likely F'ed. I will reflash stock and see what happens lol

Glitching and boot looping on splash screen

I am suddenly faced with glitching on splash screen, while the SAMSUNG GALAXY TAB displays when you switch on, it dims a bit, glitches ( shows lines on the screen ) and reboots continuously. I have reflashed stock firmware, cleared cache and wiped everything with no results. On TWRP recovery, the device works with no problem. I am currently charging it to 100% since I've heard it can be battery related.
Any help would be appreciated.
Regards to all.

in recovery, connect USB cable and do from PC:
adb shell cat /proc/last_kmsg > last_kmsg.txt
Click to expand...
Click to collapse
and send it here via attachment

gellmar said:
in recovery, connect USB cable and do from PC:
and send it here via attachment
Click to expand...
Click to collapse
Sorry to sound stupid, but can it be done from stock recovery or do I have to flash TWRP ? Also, is it run from CMD from Windows 10 ?

Ok got the file....how do I attach it? I've been a member here for years and never been able to attach files

@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak

drowsy1982 said:
@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak
Click to expand...
Click to collapse
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.

gellmar said:
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.
Click to expand...
Click to collapse
I can do Nandroid Back up from TWRP, but what's the next step ?

Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?

drowsy1982 said:
Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?
Click to expand...
Click to collapse
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.

gellmar said:
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.
Click to expand...
Click to collapse
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?

drowsy1982 said:
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?
Click to expand...
Click to collapse
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.

gellmar said:
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.
Click to expand...
Click to collapse
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.

drowsy1982 said:
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.
Click to expand...
Click to collapse
This is a dying NAND flash. Given that TWRP dumps efs as raw image, this is not a just filesystem issue.
I told you what to do in PM.

FIXED !
Followed the below guide, creates a generic EFS folder and then install an stock firmware.....ta daaaaaaaaa !!
http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/

How to Root Your Samsung Galaxy A10 + Install Twrp

READ EVERYTHING CAREFULLY!
1.Your phone warranty will be void after this tutorial!
2.Any small mistake and your phone is bricked/bootlooped!
3.All of your data will be lost so back it up somewhere
Click to expand...
Click to collapse
(Fixed the tutorial my bad.)
Click to expand...
Click to collapse
Hey Guys Im Back! Thank you for the support and how it blew up. I have tested this on Android 10 UI 2.0 and it works better then ever!
Also installed lineage os : https://forum.xda-developers.com/galaxy-a10/development/rom-lineage-os-a10-a105f-t4078093
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download TWRP and 2 other important files
1.Dial *#1234# and it will show the AP and some others, focus on AP paste it on google and get the download for it
2.After downloaded move the AP to your download folder in your android device
3.You will get a magisk_patched.tar after its been offically converted
4.Get the twrp for a10
Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.After you got everything open the .tar archive and extract vbmeta.img, boot.img and you should already have recovery.img on your Desktop
6.Grab all the 3 .img files and archive them into a .tar using 7zip, Now continue to step C,
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find Desktop.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!

i notice thread title says exynos only.. u do know they are all exynos including a102u and a102u1 right?

Oh. Alright thanks for telling me.

Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.

Cupcake 1.5 said:
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Click to expand...
Click to collapse
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:

cmz6996 said:
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
Click to expand...
Click to collapse
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.

Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Oh! Im happy to hear that!

Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?

cmz6996 said:
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
Click to expand...
Click to collapse
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.

Cupcake 1.5 said:
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Click to expand...
Click to collapse
Alr thanks.

Can you upload it to Mediafire? Mega marks a "temporal error"...

Kyua said:
Can you upload it to Mediafire? Mega marks a "temporal error"...
Click to expand...
Click to collapse
At me it works?

Works on a105m?

Axeggus said:
Works on a105m?
Click to expand...
Click to collapse
Yes

i receive message that i running samsumg not official firmware after odin install recovery.tar

not work
cmz6996 said:
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download Your firmware and TWRP
1.Go in your calls app and dial *#1234# Then You will receive some details about your AP, CP etc. look at the AP then download the firmware by searching it on google and (download it from sites like sammobile etc)
2.After you got your firmware connect your device to your pc after its connected send the entire firmware to the device in the Downloads folder
2.1. Install Magisk Manager
3.After you're in magisk manager press on install (first one) then press install again then press Select and Patch a File
3.1.Chose the firmware you saved on the Downloads folder
3.2.After you tap on it it should've already started modifying it
4.After it finished go back to your pc and move the magisk_patched.tar back to your desktop (It should be located in Downloads)
5.From the magisk_patched.tar extract boot.img and vbmeta.img to your desktop
5.1.Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.2.After recovery.img(TWRP) has been downloaded move it to your desktop
5.3.Select all those three items(vbmeta.img,recovery.img,boot.img) right click then Find 7Zip then press add to archive
5.4.Rename the Archive name to recovery.tar and make sure the archive format is .tar
6.After the Archive has been downloaded follow the steps in C
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find recovery.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
Click to expand...
Click to collapse
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)

andrea2o18 said:
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
Click to expand...
Click to collapse
You installed the wrong fir.ware check your right firmware.

BlueFolks said:
i receive message that i running samsumg not official firmware after odin install recovery.tar
Click to expand...
Click to collapse
Be cause you modified the firmware ignore that message

have you fixed the storage reduced to 16gb problem?

I have a Samsung galaxy sm-a10. I've tried everything here, even combination files. The error I ALWAYS get is 'failed flashing ROM... OEM lock'
Of course I have unlocked OEM in developer options, but still I get this error in the bootloader.
Any ideas?