Development [AOSP-11] [UNOFFICIAL] [SW REV 1] Samsung SM-A125F TWRP - Samsung Galaxy A12

Mod edit : link removed and thread locked while waiting for twrp kernel source link.
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​Install instructions:
1. Download an arbitrary SM-A125F firmware zip package newer than 7 May 2021 on SamMobile.com, whose Android version is 11 (Android 10 based firmware no longer work at all)
2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages
3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)
4. If OEM unlocking is unseen to you, take software updates first
5. Also inside Developments settings, enable USB debugging
6a. Run an ADB command to disable dm-verity thru your PC (Or TWRP fails to boot, this isn’t done for my part, so my device is being boot looped)
6b. Sign your own vbmeta.img instead of the stock one, but of course you could still choose as fewer items to be verified as possible; but my own custom vbmeta.img will still be released for you, if you’re relatively new to TWRP
7. Download the TWRP image from my SourceForge project
8. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC
9. Hold <VolUp> to unlock OEM
10. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C
11. Press <VolUp> without holding to enter Download mode
12. Open Heimdall to flash the downloaded TWRP on the partition ‘‘recovery’’ with my TWRP image renamed to ‘‘recovery.img’’
13. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
14. Enjoy!

The Android 11 update is not yet available for my country, maybe soon it'll be available. Anyways can i ask whats working and whats not?

You should have posted the thread as development though, yet you posted it as a question Also thank you for your hard work in making this recovery!

Helix-one said:
The Android 11 update is not yet available for my country, maybe soon it'll be available. Anyways can i ask whats working and whats not?
Click to expand...
Click to collapse
Neither for my country, but you don’t need to pay attention to your regions, yes my TWRP build no longer works on Android 10 based firmware (told at my first step thanks?)

Do you have any screenshots of TWRP?

Helix-one said:
Do you have any screenshots of TWRP?
Click to expand...
Click to collapse
No, i’m still getting my vbmeta.img signed for my TWRP, when done, there will be snaps.

Can we get the vbmeta?

Sokue said:
Can we get the vbmeta?
Click to expand...
Click to collapse
Yes https://sf.net/p/twrp-samsung-a12, and flashed also with TWRP itself, but the device is still being boot looped

How did you disable dm-verity?

Mod edit : link removed and thread locked while waiting for twrp kernel source link.

Related

[GUIDE] STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential

[GUIDE] NOOB-Friendly STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential PH-1
Introduction: I know there are many threads already posted that answer how to install OTA on rooted devices but unfortunately they get lost in massive threads that are often not NOOB friendly. I do not claim to be an expert but I have spent a long time reading threads and found the method I will detail below the easiest for me to follow on a monthly basis. I will do my best to give credit where credit is due to the original authors but my apologies in advance if I miss anything.
Just to start the prerequisites I have are a Windows 10 PC, Essential PH-1, with Stock OS and stock unlocked Bootloader. I have tried using TWRP in the past but I found this method simpler. I don't know whether my instructions will work for you or not if you already have TWRP installed but I can let one of the experts respond and I will be happy to update the guide based on feedback.
Part 1 - Downloads
Start by downloading the following items and storing them locally on your PC if you don't have them already
Download the latest OTA Monthly build from here: https://www.essential.com/developer/current-builds Note: Just check off that you are looking for "Current Builds" and click "Submit Form" and then click "Download (OTA)" link beneath the newest release you want.
Download the newest stock boot image here from bmg1001's google drive Credit:bmg1001
(FIRST TIME ONLY) Download and install the Windows driver (if you don't already have on your computer) from here: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
(FIRST TIME ONLY) Download ADB tool (if you don't have already on your computer) from here: https://developer.android.com/studio/releases/platform-tools.html This link is directly from Essentials site here in their "Before Sideloading" section it is the link entitled "You'll need the latest ADB tool"
To continue you must have developer options USB Debugging enabled which I presume was already done previously if your phone is rooted but if not you must do so before proceeding.
To Enable Developer Options: Settings App> System> About Phone> Scroll Down to Bottom and tap 7 times on the "Build Number"
To Enable USB Debugging: Settings App> Developer Options> USB Debugging (Set to Enabled)
Part 2 - Sideload the OTA Update
DISCLAIMER: This method if done properly should not wipe any of your data, however I take no responsibility and it is always advisable to back up your data before proceeding with any updates if you wish. I will be honest that I have now done this several times and never had any issues.
Unzip the ADB tool (link above in downloads section is for "platform-tools") and save it to a folder easily accesible on your computer (for this demonstration I will use "C:\platform-tools")
Copy the OTA update file to your ADB folder i.e. "C:\platform-tools" and rename it "OTAupdate.zip" (it is not necessary to rename it, just makes this simpler for the guide)
Verify the checksum of the image. I use hashtab which allows you to right click on any file and click properties and see the hashes as a tab in the properties menu. The SHA-256 is listed right under the OTA download link just copy and paste it in to the hashtab to verify
Remove your PIN / Password before sideloading by going to Settings> Security & Location> Screen Lock> Set it to None (this probably isn't necessary I just do it as a precaution)
Plug Essential Phone into computer and make sure that it says USB Debugging Enabled
Open the folder "C:\platform-tools" in Windows File Explorer and hold shift and right click in the window and you select the option "Open Powershell window here" from the context menu (works in Windows 10 can't speak for earlier Windows versions). If you don't see it the first time Shift+right click on a different part of the empty white window and you should see it appear.
Verify your device is properly connected by typing
Code:
adb devices
and you should see your device listed
Type
Code:
adb reboot recovery
Note:If you're unable to use ADB to reboot into recovery, you can use the key combination for your device. While device is off to boot into Recovery mode, press and hold Volume-Up button while pushing Power button to boot.
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command:
Code:
adb devices
Then check that your device shows up with “sideload” next to its name
Run the following command:
Code:
adb sideload OTAupdate.zip
where OTAupdate.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
At this point you should have a stock updated essential device but without root. The remainder of this guide will use Magisk to restore your device to root.
Part 3 - Re-root your Device with Magisk
Copy newest boot image from here that you downloaded earlier to a folder directly on your phone. I personally put it in my "Download" folder on my phone so I can find it easily
Open Magisk Manager and click Install>Install>Patch Boot Image
Select the boot image from step 1 and then let Magisk proceed in creating a patched image file
Copy the file "magisk_patched.img" file that Magisk just created from your device back to the computer and put it in the ADB folder "C:\platform-tools"
Plug in phone and open powershell same as before (shift+ right click> Open Powershell window here)
Type
Code:
adb reboot bootloader
to reboot your phone into fastboot
Confirm your phone is in fastboot by typing
Code:
fastboot devices
Then check that your device shows up with “fastboot” next to its name
Execute the command
Code:
fastboot flash boot magisk_patched.img
Restart your phone and you are done! Don't forget to put your phone PIN/Password back if you disabled security in the earlier step.
You should now have a successfully updated phone with full ROOT access with Magisk. I know that this guide seems like a lot of steps but it really goes very quickly, I just tried to be detailed and NOOB-Friendly.
Hope this helps all of my fellow XDA members!! Please share any and all feedback. Thanks!
Full credit goes to this thread for helping me with everything: [GUIDE] Rooting your Essential PH-1
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
you know i just finished writing my own guide to do it after i had trouble with the sticky posts. for me, magisk couldnt find the stock boot so i had to pretty much redo it. i did most things with back-to-stock and fastboot. but now i really wanna try your method through twrp. i been using the patched_twrp_magisk_stock.img images which have twrp and magisk in the same image. using your method, in twrp, could i flash the ota, the patched_twrp_magisk_stock.img, switch slots in twrp, flash patched_twrp_magisk_stock.img again, then switch back to the original slot and reboot system? thanks!
this thread has the patched_twrp_magisk_stock.img images
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
@andypiznti
There's no need to manually switch slots. And no reason to flash the TWRP *installer* file twice. The first time it runs, it patches both slots.
IMHO, trying to control slots is what gets people into trouble.
I do pay attention to what slot I'm on before I start though. In TWRP, if you go to the reboot menu, it will tell you. But the way I flash, I stay on the slot I started with. The OTA will always flash to the opposite slot - which should be the inactive slot. Flashing the TWRP *installer* file just once, patches both slots.
Just wipe dalvik (and cache but there is no cache partition so it will error - just ignore the error) then reboot to system like we've done after custom ROMs for years.
The next boot, the bootloader knows to switch to the slot with the newest OS.
After a successful boot, when you return to TWRP, you'll see the slot is the opposite one from when you started. But you didn't need to do any slot switching.
Don't force things. Let the slots take care of themselves.
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
ktmom said:
@andypiznti
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
ok that answers a lot. thanks! the guide i made for myself had me flashing the stock image with bts. i was curious about the full boot after an update, i was thinking the same thing in that it might cause problems with magisk, but i also thought twrp would cause problems too. the reason i mentioned switching slots and flashing is the all-in-one img only flashes to one slot at a time, i believe.
heres my guide for reference, its kinda long. but these were the exact steps i followed and was successful. had to flash the img twice, kept rebooting into recovery if i didnt.
Applying OTA for Essential Phone when Magisk doesn't have stock boot
Boot to recovery with Magisk
Back up at least system and boot
Boot to bootloader with TWRP
Extract back to stock (BTS) for CURRENT INSTALLED VERSION, not the update BTS version
Once in bootloader, connect phone->old phone plug, SSD plug
Run flashallnowipe.bat, once bootloader reboots, select Start, unplug phone
Uninstall Magisk like a regular app
Do OTA->settings->advanced->system update
after reboot->reboot while holding volume down until in download/fastboot mode
***REMEMBER!! Flash on the opposite slot of the current slot
***so if im on slot a, flash slot b.
make sure to extract Essential_ADB_and_FASTBOOT.zip in BTS folder then->cmd-here.exe
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch to other slot
fastboot --set-active=a
fastboot --set-active=b
***Just to double check, REMEMBER!! Flash on the opposite slot of the current slot
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch back to orig slot
fastboot --set-active=a
fastboot --set-active=b
On the phone fastboot menu, select Start, unplug phone
Manager asks if you wanna install it, no, it downloads the wrong one, maybe works now?
Install Magisk Manager->https://github.com/ianmacd/MagiskBuilds
IT HAS TO BE THIS APK, Download any apk version from above github, install
when you open Manager, then download the newest apk, dont update image
Manager and Image update daily, ignore till next month OTA
Click to expand...
Click to collapse
hssxda said:
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
Click to expand...
Click to collapse
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I don't know what more I could do to make the point it's not necessary to work about slots in TWRP.
Click to expand...
Click to collapse
Well, all of your posts describing your method contains the word "slot" multiple times so it is obviously a relevant concern otherwise you wouldn't have mentioned it. My post did not contain the word even once...
I see no need to use TWRP. What advantage does it have?
ktmom said:
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
oh yes, definitely doing that next time. thanks!! i found this post thats exactly your method in a little less words.
https://forum.xda-developers.com/es...1-1-nmj20d-t3701681/post78194778#post78194778
Jeebus...
We didn't like the other 15 goddamn threads with the same topic...
XDA is cancer
what works for me at the time to flash the patched image was
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
note: i am on pie
thanks for the guide.
Really helped lots, thank you.
January update is out, who might like to patch boot.img with TWRP and Magisk?
kma_29 said:
January update is out, who might like to patch boot.img with TWRP and Magisk?
Click to expand...
Click to collapse
Go to the stock room thread
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
morphius88 said:
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
Click to expand...
Click to collapse
Thanks
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
jionny said:
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
Click to expand...
Click to collapse
Yep, I have it in the same Google Drive folder where the other month's images are posted.
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Sorry chalk that up to me not paying attention. I was looking for it after Jan but its actually the first one listed. Thanks!
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Hi one more thing, this is my third time updating and rooting via this method. The last two times worked flawlessly however this time I did update the OTA but when I try to reroot and go to adb devices I see my phone listed then when I reboot recovery it does however when I try fastboot devices my phone does not show and nothing happens, any help will be appreciated

How To Guide Unlocking the bootloader and rooting

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
UNLOCKING BOOTLOADER​1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. After holding VOL UP for 10 seconeds you should get in to the screen that will let you unlock the OEM so now just press VOL UP.
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
12. Check in developer options if oem unlocking is grayed out, if it isn't factory reset data and wipe chace partiton will have to be done.
ROOTING​1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds).
After the phone turns off, amedietly boot in to recovery (Vol + and POWER at the same time)
12. Make a factory data reset and whipe cache partition
13. Reboot in to system
14. Conect to interent during setup
15. Enable dev options by taping on build number 7 time. OEM UNLOCKING must be grayed out.
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing, go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
20. After flash reboot
21. Check in developer options if oem unlocking is grayed out, if it isn't the instalation process will have to be followed again
THIS IS A OLD METHOD OF INSTALLING TWRP
INSTALLING TWRP, I RECOMEND FOLOWING MY LATEST GUIDE
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
​INSTALLING TWRP OLD METHOD​# If you are not on the A125F or A127F you might have to do a crossflashing fimware operation
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
LAST_krypton said:
Code:
Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
Click to expand...
Click to collapse
LAST_krypton said:
Code:
# Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
UNLOCKING BOOTLOADER
Code:
1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. VOL UP for bootloader unlock
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
ROOTING
Code:
1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds)
12. After the phone turns of, amedietly boot in to recovery (Vol + and POWER at the same time)
13. Make a factory data reset and whipe cache partition
14. Reboot in to system
15. Conect to interent during setup
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
19. After setup reboot
INSTALLING TWRP
Code:
If you are not on the A125F model you will have to disable MTK Secure Boot and Secure Download and might also downgrade SW REV and then install A125F fimware
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
Click to expand...
Click to collapse
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
edward0181 said:
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
Click to expand...
Click to collapse
Ok sure, I will do it when I get time.
Cheers
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Rularick5 said:
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Click to expand...
Click to collapse
It is possible, and it is the only way for you to do what?. To flash A125F fimware on A125U you have to go through a really complicated method to succeeded, you would have to dismantle the phone and force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware. And forgot to mention, you have to go trought some litle pain with SBL aswel.
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Rularick5 said:
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Click to expand...
Click to collapse
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the i gues
Click to expand...
Click to collapse
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Rularick5 said:
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Click to expand...
Click to collapse
See here, https://forum.xda-developers.com/t/...ing-theories-and-issues-with-our-a12.4336999/
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
Click to expand...
Click to collapse
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
wiiddakidd said:
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
Click to expand...
Click to collapse
You donwload the same fimware your phone is running and copy the AP.tar.md5 fimware file to your phone. Install cannary version of magisk and patch the AP.tar.md5. Transfer magisk_patched-xxxxxxx.tar back to your pc and in odin flash it in AP slot.
wiiddakidd said:
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Click to expand...
Click to collapse
A guide for that, maybe some other day. It would require phone disasembely to force PRELOADER. And what error do you when flashing AP file?
Hello, long time forum lurker here but never posted anything before. I recently have been having a headache from several different AT&T phones all being restricted to the point where I can't do anything with them. I have an SM-A125U from att that doesn't have an OEM unlock option.
Through my Ubuntu computer I can run some basic adb and fastboot commands but nothing that actually helps me. Still though the fact that I can make the phone go to recovery and fastboot make me wonder if there is really nothing I can do about this. Frija also won't let me get a firmware file for my device.
Not totally sure how it works but somebody said AT&T encrypts the software so you can't access specific functions. I am just wondering is there anything I can do through adb or fastboot to fix this issue in any way, or if my only real option is to just buy a new unlocked phone or something?
I explained it here, if it still doesn't work then comment again here.
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
drcroc said:
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
Click to expand...
Click to collapse
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
LAST_krypton said:
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
Click to expand...
Click to collapse
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
drcroc said:
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
Click to expand...
Click to collapse
Make sure OEM unlocking and usb debuging have applayed. Boot in to system, reset developer options and then enable them back. After that enable OEM unlocking and usb debuging and restart. After reseting and booting back in to SYSTEM power off the phone and hold VOL + and VOL - at the same time. UNLOCKING MENUE should now be shown and you will be able to get in to it by VOL + longpress.

[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.)

How To Guide Unlock the bootloader and install GSI ROM

So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!
Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.
That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out
If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply
Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!
Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?
@TringQuack What's your current state with A53?
Running GSI? Stock?
ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock
@TringQuack How do I know if the build is compatible with A13?

How To Guide Rooting the Google Pixel 6a

Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.
Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.
Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen
binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.
You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.
Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?

Categories

Resources