How To Guide [FULL DEFINITIVE GUIDE] Installing 'Custom ROMs' (GSIs) without TWRP on Samsung Phones - Samsung Galaxy A52 5G

11th Feb 2023
THIS GUIDE DOES NOT REQUIRE ROOT, BUT WILL WIPE YOUR EXISTING DATA! MAKE SURE TO HAVE A BACKUP.
Now before you start commenting that GSIs are not the same as Custom ROMs, please read below.
Spoiler Alert: There are probably not going to be any true Custom ROMs for the A52 5G for quite a long time. Due to the fact that Samsung's RIL system (the thing that makes your SIM/LTE/Mobile Data work) will not work on anything other than the Stock ROM, many developers have basically seen no point in developing even an official TWRP recovery for the phone. The above is true for all Samsung 5G Snapdragon-based devices. Using a GSI circumvents the RIL issue since all it does is sit in the system partition.
Therefore, your best bet if you really are intent on messing with your phone is to use GSIs. While some may argue that using GSIs for use as a daily driver comes with its issues, but I have been using mine with PE13+ for a few days now and everything functions as normal albeit while needing some workarounds (see POST-INSTALLATION section at bottom after installation).
You might be asking, why not use TWRP? The A52 5G does not have an official (or stable) TWRP yet. You can check this thread to be updated on the progress of the unofficial port! This guide is relatively simple, however, I have tried to make it as thorough as possible to help those who are just beginning on their GSI journey.
IT IS RECOMMENDED TO READ THROUGH THE GUIDE AT LEAST ONCE BEFORE UNDERTAKING ACTIONS!
----Your Warranty is Now Void (unless you live in AU or UK I guess)----
I am not responsible to any damage that comes from following this guide. While I have tried to keep information here as accurate and precise as possible, your mileage may vary. Be Warned!
This guide is tailored towards Windows devices and Samsung phones for target installation. Please seek alternatives to Odin such as Hiemdall if on Linux.
-----------------------------------------------------------------------------------
GUIDE:
Installing the PixelExperience+ GSI is recommended while using this guide as I cannot give any post-installation help to those using other GSIs.
General Commands for GSI Installation here:
Generic system images | Android Open Source Project
source.android.com
PixelExperience+ Stable GSI Download:
GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
Script and patches for building PHH-Treble Pixel Experience - GitHub - ponces/treble_build_pe: Script and patches for building PHH-Treble Pixel Experience
github.com
Prerequisites:
- An Android Treble-Enabled device. Use this app to check. Any devices launched at and after Android 10 should work.
- Windows system.
- Extraction software such as 7Zip or PeaZip.
- ADB and fastboot on computer, if not can download from official Google Android SDK. Make sure to add the platform-tools folder to PATH.
- Samsung Odin software (at the time of writing, the attached is the latest version).
- Stock Firmware for your phone model to completely reset if needed. Use this link to download yours. Make sure everything is correct before downloading!
- Your preferred GSI .xz file or .img
- Know which keys to press for your SPECIFIC Samsung model for Download Mode and Recovery Mode.
If your Samsung device already has fastbootd, boot into fastboot and skip straight to step 8!
Your Samsung device should be plugged into your computer from now on, with USB debugging enabled.
1. From the stock OneUI ROM, boot into Download Mode by holding VOL UP and VOL DOWN simultaneously when off or rebooting. Alternatively, you can run `adb reboot download`.
2. TURN OFF AUTO RESTART IN ODIN (options tab), AS RESTARTING TO STOCK ROM WILL WIPE CUSTOM RECOVERY!
3. If you are on an A52 5G, download the fastboot-recovery.tar file attached. If the file is missing, go to this thread and download the tar file. Otherwise, use this link and follow instructions to patch your model's recovery.img file. Then convert it back into a tar file for flashing.
4. Choose the patched recovery tar file. This is enables fastboot, as modern Samsung devices don't have this feature enabled. USE AP SLOT in ODIN TO FLASH.
5. Once flash is complete, hold VOL DOWN and SIDE KEY to exit Download Mode, then immediately change to VOL UP and SIDE KEY when screen goes black.
6. Press the VOL UP and VOL DOWN buttons to select the fastboot option once in Android recovery.
7. Press SIDE KEY to boot into fastbootd.
8. Run `fastboot devices` in Windows Terminal or Command Prompt to ensure the device is recognized.
9. If your GSI came in a compressed file (.xz, .zip, etc.) extract it with your program of choice. You should be left with a .img file. Rename this file to system.img. All of this should be done in your downloads folder.
10. Navigate your command prompt using `cd` to your Downloads folder. In my case, it was `cd C:\Users\User\Downloads\`. Your username might be different.
11. Run `fastboot erase system`.
12. Run `fastboot flash system system.img`. This might take a few minutes to complete. If you get an error about system partition size, scroll to the bottom of this article and run the command to free up space.
13. Once complete, run `fastboot -w`. If this returns an error, do not retry and proceed to the next step. If it ran successfully, skip to step 17.
14. Run `fastboot reboot`. Immediately after the screen goes black, hold the VOL UP and SIDE KEY buttons together until you reach Android recovery. If you fail to reach Android recovery, you may have to return to step 11. Worst case scenario, you may have to go to the PANIK GUIDE to completely reset, then go from step 1.
15. Use VOL UP and VOL DOWN to select 'Wipe Data/Factory Reset' and use SIDE KEY to confirm. Then repeat the process for 'Wipe Cache'.
16. After wiping data, use VOL UP and VOL DOWN to reboot (should be the first option in Android recovery).
17. If you ran `fastboot -w` without an error, run `fastboot reboot` and enjoy your newly flashed GSI! Make sure to check the POST-INSTALLATION section for some fixes.
POST-INSTALLATION SPECIFIC TO PIXELEXPERIENCE:
These are some quality-of-life improvements for your experience that I had to painstakingly test lol. If you have any of your own, make sure to share them with me in the comments!
1. Under-screen fingerprint sensor not working.
FIX: Go to Settings -> PHH Treble Settings -> Misc. -> Under-display fp color. Switch to the colour it was on your stock ROM (should be white for most Samsung devices). For some reason, PE13+ will only let you register fingerprints when the color is green. If you want to modify your fingerprints, switch the display fp color back to green. When done, return it to your stock ROM's colour.
2. Camera app features are extremely minimal.
FIX: Go to the GCam Hub to find the best app for your device.
3. No alternate refresh rate (or stuck at 60HZ)
FIX: Go to Settings -> PHH Treble Settings -> Misc. -> Force FPS. Choose the one you want.
4. Fingerprint sensor not working with Night Light.
FIX: There's no working fix yet. However, you can work around this by downloading a task automation app such as Tasker (paid) or Automator (freemium) to toggle the Night Light automatically when you are on the lock screen. Search online for a specific fix for your specific app. For starters, you can use 'toggle night light with <your automation app>'.
KNOWN UNFIXABLE ISSUES:
If you know any fixes that have worked for you, make sure to share them in the comments!
1. Face Unlock does not work on the A52 5G. It may or may not work on your device. IMO, it's not a deal breaker since I the fingerprint sensor is faster and more convenient in 99% of cases.
PANIK GUIDE:
If all hope seems lost and you somehow mess the phone up, wait until the next bootloop. When the screen goes black, press VOL UP and VOL DOWN immediately until it enters Download Mode. Then flash stock firmware through Odin. Use All files available in the stock firmware folder to their corresponding slot in Odin. Use the CSC file, NOT the HOME_CSC.
CONCLUSION:
Well, hopefully that just about sums up everything you need or wanted to know about the A52 5G and tinkering with the OS. If you need any more information just leave a comment on the thread and I'll try to get back to you.

---

Reserved.

---

Reserved.

---

Reserved.

---

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I followed the steps, install the file fastboot a52 5g by odin, reboot into recovery, install img gsi, it seems that it gives a size error but it is installed. I follow these steps of course, unlocked booloader, fasboot mode fastboot erase system fastboot flash system system.img gives size error but does it install?. Finally the fastboot -w command and reboot but it stays rebooting. I have android 13 a52 5g. I put images fastboot delete-logical-partition product_a not working for me

---

For some reason, attempting to erase the system partition results in error:
Erasing 'system' FAILED (remote: 'unknown command')
fastboot: error: Command failed

---

Worked like a charm. Thank you very much. I now have something else to play with my a52 5g. Will try with other gsi's.

---

markpanget1 said:
Worked like a charm. Thank you very much. I now have something else to play with my a52 5g. Will try with other gsi's.
Click to expand...
Click to collapse
Hello, what rom did you use? Well, I tried pixel, cdroid and it gives me a partition size error. I have the a52 5g android 13

---

ped1609 said:
Hello, what rom did you use? Well, I tried pixel, cdroid and it gives me a partition size error. I have the a52 5g android 13
Click to expand...
Click to collapse
Pixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.

---

markpanget1 said:
ÇPixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.
Click to expand...
Click to collapse
markpanget1 said:
Pixel experience plus. Did you erase the system properly? Try to check if fastboot drivers is properly installed. I do get some error but i just proceeded with every steps.
Click to expand...
Click to collapse
I follow all the steps, install the recovery with odin, enter recovery, then fasboot mode where fasboot devices recognize it with a number, then fastboot erase system, this is where fastboot flash fails system system.img partition size error, I hit fastboot delete-logical-partition product_a but it does nothing.

---

ped1609 said:
I follow all the steps, install the recovery with odin, enter recovery, then fasboot mode where fasboot devices recognize it with a number, then fastboot erase system, this is where fastboot flash fails system system.img partition size error, I hit fastboot delete-logical-partition product_a but it does nothing.
Click to expand...
Click to collapse
Im sorry, i'm not an expert on this, im afraid i cant answer your question about that except if i experience that error, maybe i can find a workaround with myself , then maybe i can help you. Maybe later i'll try to flash my phone again with gsi and record it all and share it with this forum.

---

markpanget1 said:
Im sorry, i'm not an expert on this, im afraid i cant answer your question about that except if i experience that error, maybe i can find a workaround with myself , then maybe i can help you. Maybe later i'll try to flash my phone again with gsi and record it all and share it with this forum.
Click to expand...
Click to collapse
Thanks, maybe it's a PC problem, I'll restore them to the factory and try.

---

Hello, I already managed to install gsi pixel plus, partition errors too large, pixel on the a52 5g with android 13. 1 root method a525g with android 13, use AP_A526BXXU3EWD2 according to your model to place it in the mobile memory 2 install magisk, patch the ap will create a file on the mobile pass it to pc, 3 open Odin, reinstall the official rom but with the patched ap, when you start the mobile, please install the magisk app again as it is removed, When you open it, you will be root. 4 then go back to odin to install the fastbootd-recovery file in the ap box as the tutorial says above. 5 when you install the file enter the recovery as it says above press power and volume down at the same time to exit odin and quickly when it exits black screen volume up and power to enter recovery. 5 when you enter recovery and you are in fasboot mode, this is where it gave me trouble normal cmd didn't work. Download platform-tools, create a folder called rom a52, inside the plattform -tools folder I opened cmd the commands i used and it worked, 1 fastboot devices to indicate that it recognizes it, 2 fastboot delete-logical-partition product this worked 3 fastboot erase system 4 fastboot flash system system.img 5 fastboot -w 6 fastboot reboot and reboot into the new pixel system, Sorry if it's too long but I had a hard time solving the partition size.
Más información sobre este texto de origen​Para obtener más información sobre la traducción, se necesita el texto de origen
Enviar comentarios
Paneles laterales​
https://translate.google.es/saved
https://translate.google.es/contribute

---

ped1609 said:
Hello, I already managed to install gsi pixel plus, partition errors too large, pixel on the a52 5g with android 13. 1 root method a525g with android 13, use AP_A526BXXU3EWD2 according to your model to place it in the mobile memory 2 install magisk, patch the ap will create a file on the mobile pass it to pc, 3 open Odin, reinstall the official rom but with the patched ap, when you start the mobile, please install the magisk app again as it is removed, When you open it, you will be root. 4 then go back to odin to install the fastbootd-recovery file in the ap box as the tutorial says above. 5 when you install the file enter the recovery as it says above press power and volume down at the same time to exit odin and quickly when it exits black screen volume up and power to enter recovery. 5 when you enter recovery and you are in fasboot mode, this is where it gave me trouble normal cmd didn't work. Download platform-tools, create a folder called rom a52, inside the plattform -tools folder I opened cmd the commands i used and it worked, 1 fastboot devices to indicate that it recognizes it, 2 fastboot delete-logical-partition product this worked 3 fastboot erase system 4 fastboot flash system system.img 5 fastboot -w 6 fastboot reboot and reboot into the new pixel system, Sorry if it's too long but I had a hard time solving the partition size.
Más información sobre este texto de origen​Para obtener más información sobre la traducción, se necesita el texto de origen
Enviar comentarios
Paneles laterales​
https://translate.google.es/saved
https://translate.google.es/contribute
Click to expand...
Click to collapse
Oh, that's what i forgot to mention, i'm already rooted with latest magisk long before i performed gsi flashing.
Good for you bro! congrats!

---

markpanget1 said:
Oh, that's what i forgot to mention, i'm already rooted with latest magisk long before i performed gsi flashing.
Good for you bro! congrats!
Click to expand...
Click to collapse
Thanks, I've tried 2 gsi but it has little pixel brightness, cdroid, I'll try lineage and evolution to see if the brightness is corrected.

---

I see mention of the Snapdragon variants. Does that mean the bootloader doesn't need to be unlocked to flash GSIs? I have the U1 variant

---

lowridincrew said:
I see mention of the Snapdragon variants. Does that mean the bootloader doesn't need to be unlocked to flash GSIs? I have the U1 variant
Click to expand...
Click to collapse
You need to unlock the bootloader to flash GSI, yes.

---

C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.063s]
sending sparse 'system' (256443 KB)...
OKAY [ 6.929s]
writing 'system'...
OKAY [ 0.890s]
sending sparse 'system' (258773 KB)...
OKAY [ 6.679s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (255920 KB)...
OKAY [ 6.754s]
writing 'system'...
OKAY [ 0.714s]
sending sparse 'system' (258109 KB)...
OKAY [ 6.957s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (259589 KB)...
OKAY [ 6.674s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (258310 KB)...
OKAY [ 6.678s]
writing 'system'...
OKAY [ 0.726s]
sending sparse 'system' (259101 KB)...
OKAY [ 6.910s]
writing 'system'...
OKAY [ 0.671s]
sending sparse 'system' (259985 KB)...
OKAY [ 6.582s]
writing 'system'...
OKAY [ 0.617s]
sending sparse 'system' (259396 KB)...
OKAY [ 7.228s]
writing 'system'...
OKAY [ 0.616s]
sending sparse 'system' (260673 KB)...
OKAY [ 6.939s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (260774 KB)...
OKAY [ 6.919s]
writing 'system'...
OKAY [ 0.695s]
sending sparse 'system' (245741 KB)...
OKAY [ 6.211s]
writing 'system'...
OKAY [ 0.672s]
sending sparse 'system' (206734 KB)...
OKAY [ 5.591s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 96.193s
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Creating filesystem with parameters:
Size: 629145600
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 2400
Label:
Blocks: 153600
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/38400 inodes and 4936/153600 blocks
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 10.502s]
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (11752 KB)...
OKAY [ 0.284s]
writing 'cache'...
OKAY [ 0.102s]
finished. total time: 10.932s
these are my fastboot logs, when I perform "fastboot reboot" I got an endless bootloop, I followed all steps and everything worked fine until this, any help please?
EDIT: I tried also to perform a factory data reset from recovery instead of "fastboot -w" command, nothing changed

---

Shiina_ said:
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot flash system system.img
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.063s]
sending sparse 'system' (256443 KB)...
OKAY [ 6.929s]
writing 'system'...
OKAY [ 0.890s]
sending sparse 'system' (258773 KB)...
OKAY [ 6.679s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (255920 KB)...
OKAY [ 6.754s]
writing 'system'...
OKAY [ 0.714s]
sending sparse 'system' (258109 KB)...
OKAY [ 6.957s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (259589 KB)...
OKAY [ 6.674s]
writing 'system'...
OKAY [ 0.687s]
sending sparse 'system' (258310 KB)...
OKAY [ 6.678s]
writing 'system'...
OKAY [ 0.726s]
sending sparse 'system' (259101 KB)...
OKAY [ 6.910s]
writing 'system'...
OKAY [ 0.671s]
sending sparse 'system' (259985 KB)...
OKAY [ 6.582s]
writing 'system'...
OKAY [ 0.617s]
sending sparse 'system' (259396 KB)...
OKAY [ 7.228s]
writing 'system'...
OKAY [ 0.616s]
sending sparse 'system' (260673 KB)...
OKAY [ 6.939s]
writing 'system'...
OKAY [ 0.641s]
sending sparse 'system' (260774 KB)...
OKAY [ 6.919s]
writing 'system'...
OKAY [ 0.695s]
sending sparse 'system' (245741 KB)...
OKAY [ 6.211s]
writing 'system'...
OKAY [ 0.672s]
sending sparse 'system' (206734 KB)...
OKAY [ 5.591s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 96.193s
C:\Users\user\Downloads\PixelExperience_Plus_arm64-ab-13.0-20230503-UNOFFICIAL.img>fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Creating filesystem with parameters:
Size: 629145600
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 2400
Label:
Blocks: 153600
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/38400 inodes and 4936/153600 blocks
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 10.502s]
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (11752 KB)...
OKAY [ 0.284s]
writing 'cache'...
OKAY [ 0.102s]
finished. total time: 10.932s
these are my fastboot logs, when I perform "fastboot reboot" I got an endless bootloop, I followed all steps and everything worked fine until this, any help please?
EDIT: I tried also to perform a factory data reset from recovery instead of "fastboot -w" command, nothing changed
Click to expand...
Click to collapse
Hello, that happened to me, above I put how to install..it seems to be installed but not.

---

ped1609 said:
Hello, that happened to me, above I put how to install..it seems to be installed but not.
Click to expand...
Click to collapse
Hi! Thanks for your reply, I just tried following your guide but nothing changed, still in bootloop
EDIT: I tried using another PixelExperience GSI and it worked, so I guess that I solved, thanks