How To Guide Unlock bootloader and root A125U u3 - Samsung Galaxy A12

Requirements:
-Tested working on firmware A125USQS3BVA2
-A MTK bootloader unlocking tool, tested working with UnlockTool
-This is for A125U on binary 3 ONLY
Special thanks to @Boster27 for translate guide and test method
Steps:
1- Boot into Download Mode (vol+ & vol- & pwr) and flash this custom BL file BL_A125.tar with ODIN patched using the BL button. The device will reboot to an error screen, this is normal.
2- Boot into BROM mode using Test Points (picture attached, needs light dissasembly). Using UnlockTool or your MTK tool of choice, head to the Samsung section and select A125, then on the BROM tab, choose Unlock Bootloader.
After this the device should reboot into recovery and perform a factory reset automatically. In case it doesn't, go into recovery manually (vol+ & pwr) and perform a factory reset. After this the device should boot normally.
3- Once the setup process is complete, connect to Wifi and enable Developer Options to confirm that OEM Unlock is enabled and unlocked. Install the latest version of Magisk Manager and use it to patch the AP file for the corresponding firmware.
4- Boot into Download Mode, make sure the AutoReboot option is unchecked in ODIN, and flash the magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files. Then manually boot into recovery and perform a factory reset. After this the device should boot normally.
5- Once the setup process is complete again, connect to Wifi and enable Developer Options to confirm that OEM Unlock is still enabled and unlocked. Install the latest Magisk app and launch the app.
It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device.
And done! Phone is rooted on binary 3!

Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you

I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks

marioz17 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
Click to expand...
Click to collapse
link to these files please

mfeliu07 said:
I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks
Click to expand...
Click to collapse
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware

unruly1981 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware
Click to expand...
Click to collapse
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2

marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
thank u

marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
does it have the magisk_patched.tar ?

unruly1981 said:
does it have the magisk_patched.tar ?
Click to expand...
Click to collapse
You need to patch the AP from firmware with magisk app

Did you have to take the phone apart. or can you just use the software.

timandolly said:
Did you have to take the phone apart. or can you just use the software.
Click to expand...
Click to collapse
Need to take apart, but this phone is so easy to open

Would this work on the S127DL? The Tracfone Galaxy A12.

Wish39 said:
Would this work on the S127DL? The Tracfone Galaxy A12.
Click to expand...
Click to collapse
i need the phone to test but you can try if the phone can enter BROM mode with testpoint

marioz17 said:
i need the phone to test but you can try if the phone can enter BROM mode with testpoint
Click to expand...
Click to collapse
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.

Wish39 said:
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.
Click to expand...
Click to collapse
I want this phone to be my next project

mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
Did you add the ap ,modem and csc when you used the modded bootloader.

mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
I got the same how did you fix?

timandolly said:
I got the same how did you fix?
Click to expand...
Click to collapse
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset

timandolly said:
Did you add the ap ,modem and csc when you used the modded bootloader.
Click to expand...
Click to collapse
This after unlocking booloader

mfeliu07 said:
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset
Click to expand...
Click to collapse
Thanks for helping. I rooted 4 note 4s and they all finally give out so I am going to try a newer phone

Related

[GUIDE] Root galaxy A30 with magisk canary relaese 100% working

is guide tested on galaxy a30 a305f .
first we need to unlock the bootloader :
1. go to Setting>About>Software>Build Number and Tap on the build number repeatedly so that the Developer mode will turn on.
2. In the developer options, there is an OEM unlock option then enable that option.
3. enter download mode and press and hold volum up to unlock bootloader ! This will wipe your phone data entirely so make sure you have made a backup of important files.
now we can root this devices
we need :
1.odin 13.3.1
2.official firmware for your device
3.7zip ZS
4.magisk canary release or download from attached file
5.computer
1.download the firmware and extracted the files to your desktop
2.extract the boot.img.lz4 from the AP file
3.install the 7zip ZS , right click on boot.img.lz4 shoose 7zip ZS and extract the boot.img
4.copy the boot.img in your phone and install the magisk canary release
5.open magisk manager Install → Install → Select and Patch a File
6.select the file boot.img magsik will patche the boot image and store the output to [Internal Storage]/Download/magisk_patched.img
7. now copy the magisk_patched.img to you computer and reboot to download mode
8. rename magisk_patched.img to boot.img
9.right click on boot.img 7zip >add to archive and select format .tar
10.open odin unchek auto-reboot and select AP section and select the boot.img.tar and flash it .
11.We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode, and as soon as the screen turns off, immediately press Power + Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
12.In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
13.This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press Volume Up. After vibrate , release all buttons . phone will boot normal
14. After the device is booted up, do the usual initial setup.
15. install the magisk canary release again , it will ask you to install the zip click install , after a few moments the device will reboot .
16.Voila! Enjoy Magisk
this tutorial was tested by me and it work on my device !
this is my first thread
Please add the part that you need to press the volume up button everytime you reboot the device.
messi2050 said:
Please add the part that you need to press the volume up button everytime you reboot the device.
Click to expand...
Click to collapse
no just the first time , after that always reboot with root .
bleedboy said:
no just the first time , after that always reboot with root .
Click to expand...
Click to collapse
Perfect.
OEM Unlocking option is missing
I already in dev mode, but oem unlocking is unavailable
monaACE said:
I already in dev mode, but oem unlocking is unavailable
Click to expand...
Click to collapse
what about unlocking in download mode
bleedboy said:
what about unlocking in download mode
Click to expand...
Click to collapse
Any link?
How to enter download mode? Jold power and volume up button? ?️
Root Galaxy A30
I have try 6-7 times but it always failed. Any ideas. I have follow all the instructions but when flash with odin it fails
ValaTarot said:
How to enter download mode? Jold power and volume up button? ?️
Click to expand...
Click to collapse
volume up + volume down and put the usb cable
seekunto said:
I have try 6-7 times but it always failed. Any ideas. I have follow all the instructions but when flash with odin it fails
Click to expand...
Click to collapse
did u unlock the bootloader ?
bleedboy said:
did u unlock the bootloader ?
Click to expand...
Click to collapse
yes. It's give the following when trying to flash:
Initialization
Get pit for mapping
Firmware update start
NAND write start
Singledownload
Boot.img
RQT_CLOSE!
Complete (write) operation Failed
Failed
bleedboy said:
did u unlock the bootloader ?
Click to expand...
Click to collapse
Complete (write) operation Failed
hisam1987 said:
Complete (write) operation Failed
Click to expand...
Click to collapse
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
welcome enjoy ?
lazinezz said:
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
Click to expand...
Click to collapse
welcome enjoy ??
hisam1987 said:
Complete (write) operation Failed
Click to expand...
Click to collapse
try to flash the stock rom and repeat the instruction !
seekunto said:
yes. It's give the following when trying to flash:
Initialization
Get pit for mapping
Firmware update start
NAND write start
Singledownload
Boot.img
RQT_CLOSE!
Complete (write) operation Failed
Click to expand...
Click to collapse
flash the stock firmware with odin and repeat the instriction
Failed
lazinezz said:
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
Click to expand...
Click to collapse
I tried all the ways but still the problem
Thank you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
bleedboy said:
try to flash the stock rom and repeat the instruction !
Click to expand...
Click to collapse
I tried all the ways but still the problem
Thank you
hisam1987 said:
I tried all the ways but still the problem
Thank you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
I tried all the ways but still the problem
Thank you
Click to expand...
Click to collapse
try to flash only the stock boot img from your firmware ! after that flash the patched one .

Help on my TWRP bootloop phone

Hello, newbie here..
Need help!! My phone keeps booting to TWRP whenever I turned it on, connected it to PC, or even when I connected it to my charger.
It happened after I mistakenly uninstalled a system app (it is an app named Freeshare). I thought it was just a sharing app like MiDrop or ShareIt, but clearly that was a mistake.
Now I just can't seem to boot into the system, not even able to enter into the download mode.
I've tried a method that I found in here, like entering a code in TWRP terminal (it was "dd if blablabla", i forgot. Lol), to no avail.
Haven't tried to flash the stock rom or stock boot since I can't find any zip Stock Rom for my phone (my phone is Gome Fenmmy Note).
Does anyone have an idea or know how to fix it?
Thanks in advance
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Or did you flash TWRP to boot partition ??
TWRP needs to be flashed to RECOVERY partition.
If you flash TWRP to boot partition, your device will boot forever to recovery.
If yes, you need to flash the original stock boot.img
VD171 said:
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Click to expand...
Click to collapse
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
disegiooo said:
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
Click to expand...
Click to collapse
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
VD171 said:
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
Click to expand...
Click to collapse
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
disegiooo said:
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
Click to expand...
Click to collapse
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
disegiooo said:
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
Click to expand...
Click to collapse
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
VD171 said:
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
Click to expand...
Click to collapse
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
disegiooo said:
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
Click to expand...
Click to collapse
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script (if available).
Good luck
VD171 said:
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script.
Good luck
Click to expand...
Click to collapse
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
disegiooo said:
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
Click to expand...
Click to collapse
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
VD171 said:
It's same for all xiaomi devices.
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
If you don't know how to flash manually using fastboot, try MiFlash:
Click to expand...
Click to collapse
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
disegiooo said:
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
Click to expand...
Click to collapse
Good job, my friend
You are welcome.
God bless you too
About disabling preinstalled apps, try to perform this in command line:
pm disable-user --user 0 com.android.chrome​(Change com.android.chrome to desired package name to disable.)​

hardbricked realme 5 pro, No bootloader and No recovery

I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet
IS there any way to re unlock my bootloader ?
shrefeltony said:
IS there any way to re unlock my bootloader ?
Click to expand...
Click to collapse
Did you managed to fix it?
shrefeltony said:
I tried to upgrade my phone to Realme UI 2 with dirty flash but at first my phone get into a bootloop, I tried to reflash Vbmeta but it made it worse.
I tried this guide about unbrick : https://forum.xda-developers.com/t/...-to-stock-unbrick-and-fastboot-flash.3995285/ but not worked it just returned me to bootloop again.
I locked my bootloader accidently
My phone now only show this message and stuck till I press power button to turn off.
Is there is any way to flash stock ROM again with any tool ?
( MSM tool needs a username and password to work )
and I cannot find any QFIL files on Internet
Click to expand...
Click to collapse
ONLY ONEWAY TO FIX THIS IS FLASHING THE PHONE WITH EASY JTAG PINOUT METHOD
PrateekPanwar64X said:
Did you managed to fix it?
Click to expand...
Click to collapse
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.
PrateekPanwar64X said:
I did managed to fix my device. Pressed power button and both volume keys while connected to PC (when bootloader was locked) and saw Q_BULK in device manager > COM ports.
After then it was flashed with original ROM using MSM tool and done.
Click to expand...
Click to collapse
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )
iPonze said:
Hi @PrateekPanwar64X can you provide me the MSM tool that u used sir. I appreciate your help sir : )
Click to expand...
Click to collapse
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
oh hi! thanks for providing a zip file. btw, how much do you pay?
can u send me the source of the RUI 2.0 firmware you got and ill try to fix it
umm download platform-tools
- Clean wipe - Flash C.14 or latest firmware (No need if already there) - Go to custom recovery terminal and write setprop ro.separate.soft 19691 - Flash Realme UI 2.0 ozip - Reboot to bootloader - Download Realme UI 2.0 vbmeta and flash it using fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - Reboot to system
PrateekPanwar64X said:
Password of zip file should be 123
Although I don't have login credentials for msm tool. Paid to a telegram group to fix it.
Problem was I locked my bootloader myself with custom ROM [Following that warning while starting phone] and thought I'd bypass warning.
Click to expand...
Click to collapse
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.
maxzeroedge said:
Just a quick question, did you uninstall/delete the file later? And heads up for anyone using this zip. It seems to be a keylogger. In the zip under firmware, you can see all keypresses along with window it was pressed in, in a file called keylog.txt.
Click to expand...
Click to collapse
Oh, Thankfully I didn’t need it later as I learnt my lesson and never locked bootloader. If I want to reupload zip, How can I remove it?

Question HELP!!!!

I relocked bootloader and now phone won't boot past bootloader. It's only giving options to "start/ recovery/ restart bootloader/ power off" Phone is getting recognised in fastboot, but since I relocked bootloader I can't flash anything at all. Kindly help me what I can do for this mess. I tried using bootloader lock commands and it's saying bootloader already locked. I'm feeling helpless. Kindly help
First try and enter recovery and see of you can do a factory reset. Can you do that?
Andrologic said:
First try and enter recovery and see of you can do a factory reset. Can you do that?
Click to expand...
Click to collapse
Not entering recovery or anything! It's just stuck there. When I turn off and try to restart it again stays the same ie. On bootloader.
garvitkhatod said:
Not entering recovery or anything! It's just stuck there. When I turn off and try to restart it again stays the same ie. On bootloader.
Click to expand...
Click to collapse
I mean can you scroll with the volume up/down buttons to you see Recovery and push the power button to enter recovery like normal? If you can, try doing a factory reset from there. If that's not possible, try doing a RAW firmware install - but check if you can just do a normal reset first..
If adb works just try with
Code:
adb flashing unlock
or
Code:
adb oem unlock
If it doesn't work reboot to bootloader and try again.
Andrologic said:
I mean can you scroll with the volume up/down buttons to you see Recovery and push the power button to enter recovery like normal? If you can, try doing a factory reset from there. If that's not possible, try doing a RAW firmware install - but check if you can just do a normal reset first..
Click to expand...
Click to collapse
Even if I prees button on recovery it against reboots to same place. It's like an example infinite bootloop.
garvitkhatod said:
Even if I prees button on recovery it against reboots to same place. It's like an example infinite bootloop.
Click to expand...
Click to collapse
OK. Guessing you've locked the bootloader with a tampered boot.img without flashing stock boot back first. You should be able to use a RAW file to rebuild the firmware (your private stuff will be lost though).
Andrologic said:
OK. Guessing you've locked the bootloader with a tampered boot.img without flashing stock boot back first. You should be able to use a RAW file to rebuild the firmware (your private stuff will be lost though).
Click to expand...
Click to collapse
No I've flashed stock boot.img before and flashed afterwards. Can I still flash anything with bootloader locked?
garvitkhatod said:
No I've flashed stock boot.img before and flashed afterwards. Can I still flash anything with bootloader locked?
Click to expand...
Click to collapse
Yes I'm quite sure you should be able to flash a clean firmware with a RAW rom. Use the FTM flashall script.
This probably shouldn't be a how to guide and the title should be something more descriptive than "help"
A how to guide typically includes instructions, like this one:
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
The good news is that you can still flash a raw firmware with the bootloader locked.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
In the future, take the time to look at the guides here before jumping into anything that involves the system or bootloader unless you are absolutely sure you know what you're doing.
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Sir I Have Same Problem Please Help Me Out ..!
3rehaan said:
Sir I Have Same Problem Please Help Me Out ..!
Click to expand...
Click to collapse
Read. Stop posting in multiple threads and read. The answer is there.
twistedumbrella said:
Read. Stop posting in multiple threads and read. The answer is there.
Click to expand...
Click to collapse
Sir The Answer Is Didn't work for Me
Where Can I Find This File ..???
3rehaan said:
Sir The Answer Is Didn't work for Me
Where Can I Find This File ..???
Click to expand...
Click to collapse
twistedumbrella said:
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
It Says :
CONVERSION ONLY:
Make sure you unlocked the bootloader
Install Bootloader Unlock app
Launch app and follow instructions
But I Cant Unlock It My Bootloader Status Is Locked !
3rehaan said:
It Says :
CONVERSION ONLY:
Make sure you unlocked the bootloader
Install Bootloader Unlock app
Launch app and follow instructions
But I Cant Unlock It My Bootloader Status Is Locked !
Click to expand...
Click to collapse
CONVERSION ONLY
You're not converting.
twistedumbrella said:
CONVERSION ONLY
You're not converting.
Click to expand...
Click to collapse
How Can I Converting .. Please Guide Me ..??
twistedumbrella said:
CONVERSION ONLY
You're not converting.
Click to expand...
Click to collapse
I Am Waiting Sir Please Guide Me
3rehaan said:
I Am Waiting Sir Please Guide Me
Click to expand...
Click to collapse
Follow the guide just download the raw file you want and all the steps are the same.
Madbullben said:
Follow the guide just download the raw file you want and all the steps are the same.
Click to expand...
Click to collapse
Fastboot : error : CID () mapping the wrong XROM (0×1)

[Guide] TWRP and ROOT for A20e (A202f) [Updated]

My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!
[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek
does encryp work on this ? dont need to backup just hide data part if fone is stole
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.
SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp
Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before
OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?
I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.
fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?
lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.
Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)

Categories

Resources