Database Develop

Please help!!! Phone stuck after installing image 1.6 during V4.2.1 Cyanoen installat

Okay i was installing V4.2.1 and after i installed the image 1.6 i turn on the phone and it shows me an imgae of like a black rectangle and an arrow. I try pressing Home + power but i still get the same thing.
Help please!

85Mario85 said:
Okay i was installing V4.2.1 and after i installed the image 1.6 i turn on the phone and it shows me an imgae of like a black rectangle and an arrow. I try pressing Home + power but i still get the same thing.
Help please!
Click to expand...
Click to collapse
Tell me what happens when you press home + power then alt + l when the screen comes up. .. and when that screen comes up does the g1 screen come up first? Cuz I think otherwise it might be a guaranteed brick :/

okay i gott itt to go to the menu. but i try to apply the v4.2.1 and it always aborts it =/

Try the Q&A forum next time.

I go to the menu. flash the 1.6 recovery image. Change Cyanogen to update. Try to flash it but it gets aborted

don't know about cy updates but it sounds like your may have a bad file. Have you installed this update before using the "same file"? if not you may try just redownloading the update.

really neeed helpp with this. Tried installing the v4.1.9999 and it still aborts

bummer. I'm not sure what all the prerequisites are for cy mods.. Hopefully someone else can jump in here to help ya :/

Think he may have aborted installation during the radio flash portion of the HTC archive.
From Cyanogen's OP:
cyanogen said:
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
Click to expand...
Click to collapse
That's not exactly the way it went for me the 2X I've done this, so maybe this is what happened...IDK?
I've had to reboot manually (Home+back) out of recovery following phase 1 of the flash to initiate the start the Radio flash portion. This may confuse some as it's not listed as a step.
Just to be sure, place fresh copies of dream_devphone_userdebug-ota-14721.zip and cm4.2.1 in /sdcard prior to doing this. Use an external card reader if necessary.
1. Get into recovery
2. Wipe (optional but recommended, problems=include step 2)
3. Flash dream_devphone_userdebug-ota-14721.zip
4. If phone does not reboot automatically, reboot manually (Home+back) out of recovery and release buttons immediately
5. Let Radio flash (you see the image of the box with the arrow and the eprom chip)
6. Wait for screen to go completely black then hold "Home" button until it reboots back to recovery console.
7. Flash CM4.2.1
I noticed 4.2.1 took an unusually long time to load on initial boot, so be patient.
If this has nothing to do with your issue, sorry for wasting your time. Hopefully this helps somebody eventually.

85Mario85 said:
really neeed helpp with this. Tried installing the v4.1.9999 and it still aborts
Click to expand...
Click to collapse
There are 2 things you could do, use cyans file, and make sure you flash the HTC image first, as his update file is a partial update without the google experience (read apps)
This is taken from Cyans OP in his thread and edited for you, please follow the instructions properly.
Note: You need cyanogens recovery image 1.4 or better for this process, as it lets you chose files named other than update.zip
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc (ignore since i don't suppose you have anything to backup at this moment)
2- Download: http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image. This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download cyanogens ROM. http://n0rp.chemlab.org/android/update-cm-4.2.1-signed.zip
4- Mount your phone and place BOTH 1.6 Image and cyanogens ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
(ITS VERY IMPORTANT THAT YOU HOLD THE HOME BUTTON, BECAUSE IF IT THE HTC ROM BOOTS, YOU WILL HAVE TO RE-ROOT YOUR PHONE)
8- Apply sdcard:choose zip *Pick cm-4.2.1-signed.zip* from the list.
9- Reboot!
OR
download daveid's full update from http://www.megaupload.com/?d=80FXE36J or http://www.mediafire.com/?dnljdtndwnv
and just flash normally.
Oh and to mount your sd card to transfer the rom images to it from your computer when in recovery (Alt-X), use this command (in recovery, on your phone)
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Finally, as someone else mentioned, please post in the right section.

how did u get ur phone to go back to the menu because the same thing happened to me

Sorry for may bad english !
I have the same problem. After flash rom OTA 1.6 of HTC, now i lose the recovery cm-1.4.
{
"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"
}
When boot in recovery, it look like before hack root, we can't update the other file, exception "update.zip".
When i type "su" in terminal, it return "permission denied".
-I tried to update another rom but i didn't run.
-I tried to flash another recovery by Fastboot but not success.
-I tried to flash another SPL but not success.
-The last hope, i tried to re-hack root by DREAIMG.nbh but not success too.

Okay I had the same problem and know how to fix it.
1. Download 1.5 Cupcake here
2. Copy the file to the root of your SD and name it Update.zip
3. Boot recovery and press Alt + S to install Cupcake
4. Now that you`ve got Cupcake download Flashrec here
5. Make sure that you allow installing non market programs on your phone.
6. Open Flashrec after installing it and click backup recovery!! VERY IMPORTANT, didn`t do it the first time and it didn`t work.
7. After backup is finished you download the recovery given by the program
8. When the download is complete you select flash recovery.
9. Reboot, and flash your Custom Firmware again.
IMPORTANT!: All of the 1 click rooting procedures are putting the Flashrec.apk file and a recovery image on the SD card, installing Flashrec and then using it to flash the new recovery image. You WILL NOT have internal root access after this procedure (it only allows us external root access from recovery)
10. I installed the full version of 4.2.1 which was linked on the previous page of this thread, and it installed the right radio, spl and hboot.
So everything is normal again, thank god. Ow after i installed the full version of 4.2.1 it didn`t work but i had the recovery back and root so i installed the oldskool 4.1.1.1 and it works.
Good luck and this took me 5 hours to find out!

Edj87 said:
Okay I had the same problem and know how to fix it.
1. Download 1.5 Cupcake here
2. Copy the file to the root of your SD and name it Update.zip
3. Boot recovery and press Alt + S to install Cupcake
Click to expand...
Click to collapse
After this step, i have this result:

Omg! Exact same thing happen to me!
Please fix this problems for us if possible

Android 4.4 Wakelock

Hi,
since Android 4.4 (Android Revolution HD 41.0) I get a huge amount of wakelocks, my phone hardly goes to deep sleep mode.
See screenshot below:
{
"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"
}
I already tried reflashing the rom, tried a different kernel (Elemental X, latest version), but those things don't help.
Anyone having the same problems? Or found a solution?

Hi.
Stop double posting
Sent from my HTC One using Tapatalk

xcrazydx said:
Hi.
Stop double posting
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry, my connection failed and now it's posted twice.

any solutions?
I'm having the same problem on stock 4.4.2 with Sense 5.5, wlan_rx_wake keeping my phone awake even after factory reset with nothing installed, just google apps updated, on 4.2.2 i used to get about 45-48 hours with medium usage, nothing extreme, now the same way i don't get over 30 hours, it's killing me! here's a screenshot from BBS

maybe try disable cloudprint (found in settings towards the bottom). can take a little time for it to disable when you turn it off. may/may not make a difference.
i read this and seems to make more sense
http://rootzwiki.com/topic/16134-kernel-wakelock-wlan-rx-wake/
mainly the second post. hope its of some use..

Thanks for the response, and i will try both options and post the results after.
Sent from my HTC One using XDA Free mobile app

I think it's fixed now, don't know if batteryguru did the job or theWifiFixer app, i tend to believe that WifiFixer did the thing with this setup in "Service" and "Advanced" settings.
Sent from my HTC One using XDA Free mobile app

Best solution
after a lot of searching somebody posted this and this fixed the problem better than wifi fixer or anything else, it's a response from HTC Support.
"got an email from HTC support, which I will copy. so far, my battery is back to normal.
I totally understand your concern on this matter with the battery drainage of the phone, and I will be more than glad to assist you.
I ask you to please go to All apps > Settings > Battery or Power, and disable Fast boot. Then, please go to All apps > Settings > Developer options, and enable USB debugging. After doing this, please perform a Cache reset. This process will delete unwanted and temporary files from your phone. It will not mess up your personal files. Just follow the instructions on the attached file.
COPY OF ATTACHED FILE:
Power the phone off.
Press and hold the Volume Down button and then while still holding the Volume down, press the Power button as well.
You will get a menu giving you options such as: Fastboot, Recovery, Clear Storage, and SIMlock
Navigate to “Recovery” using volume buttons, then press power to select.
The screen will change to display a phone on its back, with the update symbol above it. Momentarily it will change to an image of a phone with a red triangle and exclamation mark.
Press and hold volume up then press the power button for about 3seconds. You will see something very similar to the example shown below.
e:can’t open /cache/recovery/command
e:/ failed to mount /sdcard (no such file or directory exists)
e:/ failed to mount /sdcard (no such file or directory exists)
e:/ failed to mount /sdcard (no such file or directory exists)
A new screen will give you options like Reboot system now, Wipe Cache partition, and Wipe Data/Factory Reset.
Navigate to “Wipe Cache” the volume down button and select with Power.
Navigate to “Reboot Phone” with the volume buttons and select with power."
Hope it helps people that have the same problem.
Here are the results:
View attachment 2733159 View attachment 2733160

[GUIDE] SIM-unlock your i9305

Hello guys (and girls) and welcome to (probably) my first guide
!! Be aware, I have tried the following procedure and am using S5 Elite Lite ROM by MaHo_66 !!
To start the unlocking procedure, first see if your device is actually sim-locked by inserting another sim-card from another provider and see if it asks for a code. If it asks, press on dismiss. Now, the actual steps:
Take a note of your CSC and MODEM with the help of Phone INFO.
Download from my GDrive I9305XXALI5_I9305EVRALI5.zip and copy it to either an USB OTG drive or to a MicroSD card (if you have one).
Make sure you have a custom recovery installed. Boot into it with the VOL UP+HOME+POWER button combination and make a nandroid backup of your current ROM. Make sure to do it on the MicroSD if you have one.
Go and do an advanced wipe and only wipe the following partitions: Cache, Dalvik Cache, Data and System.
Now install the zip file you previously copied on either an external USB OTG drive or on the MicroSD card.
While the rom is booting, search around on XDA for the aforementioned CSC code and a suitable modem for your BACKED UP rom.(The ZIP file I provided you will have changed the modem and CSC, so make sure you noted the CSC and modem before)
After the rom is done booting, skip the set-up wizard and the network lock screen. Now, go to the dialer and type *#197328640#
Here, go this way: [1] UMTS > [1] Debug Screen > [8] Phone Control > [6] Network Lock > [3]Perso SHA256 OFF > and wait for around 30 seconds. If you see at the Network Lock screen 4 options, you are good to go.
Press on the menu button (device) and tap on Back. Then, choose [4] NW Lock NV Data INITIALLIZ. After about 30 seconds, you should see PERSO_NV_INIT is SUCCESSFUL. From this point , you are unlocked. You can use any sim card in the device. If you have a third carrier sim card, test it out.
Reboot the phone and enjoy your unlocked phone. NOT SO FAST.
Reboot back to recovery and do an advanced wipe (the following partitions: Cache, Dalvik Cache, Data and System). Restore your nandroid backup now. Don't reboot the device to system, but go and flash the MODEM and CSC. Now, you are ready to reboot back to system and enjoy your KitKat or Lollipop ROM.
{
"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"
}
12.
Go to UMTS-COMMON-NV REBUILD and then tap Erase only Backup, then after it is done head back and tap on Make Back-up. You are all set now in case you restore the NV again by mistake, the simlock status will remain OFF.
The sim-unlocked devices do not really exist, they are just unlocked from the factory after a NV backup. If you restore the default NV, it simlocks it.
Click to expand...
Click to collapse
That's it. Now you are SIM UNLOCKED, have your device the way it was before and with a backed up NV in case something goes horribly wrong. Special thanks to @LucasBass for his thread, to RCS&RDS for their internet, and to Enel Energie Muntenia for not failing on me.
P.S. I didn't find the zip somewhere, so credits to @lamahgra for lamahgra-rom.v1.4-lite. All i did was download I9305XXALI5_I9305EVRA5_EVR.zip and extract&replace the system folder, the baseband.bin, boot.img and hidden.img and edit CSCVersion.txt and SW_Configuration.xml.

Must try that..

How can I do step 12 after I've restored my lollipop rom?

@Vvaheed, @singhdhirendra28, @Geofftey, @ZoranAncev, @newstead01, @senpdy:
Ladies & gentlemen, please be aware that this thread is for the Samsung Galaxy S3 LTE (aka GT-i9305). If you posted due to post #4 please be aware that the account of the user who posted that is already disabled.
I don't intend to ask why you need the codes or ouvertly publish IMEI's.

Thread cleaned!
Be aware that if you share your IMEI this can be used by other users and your device turns into a ded piece of hardware.
NEVER SHOW YOUR IMEI!

did not work for me
i just tried this now, it did not work for me
it had some "could not map..." error
Thank God i had a Backup, the process left my phone without an OS

Audi Android Tablet

Hi friends
how to entry in recovery mode on Audi Android Tablet, Rear seat enterteiment ?
{
"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"
}

igorgts8 said:
Hi friends
how to entry in recovery mode on Audi Android Tablet, Rear seat enterteiment ?
Click to expand...
Click to collapse
Hi did you found a solution for this problem?

Turn off the device.
Hold down the Power button and the Volume Down (or Up) button at the same time.
Press them again and again until the screen starts.
After loading, you'll see a screen with options like "reboot system now" and "wipe data/factory reset."
Now, use the power button, volume up and down, and the "wipe data/factory reset" option in the "recovery mode" to move around and choose it.
Select "Yes" to confirm, and then let the phone do its thing.
When you are done, choose Reboot system now.
When you turn on the Audi AG Audi tablet again, everything will start over.

Any joy here to report? I can confirm stesps above are correct and I have done the same recovery but the tablet sits on the pre-screen without the Audi rings starting on my desk. It took ages to do the factory reset/ wiping /data and cache... I tried to "root" the tablet so hopefully not fully dead. The eMMC is a BGA so really painful to try and recover the old way with a complete image flash. Maybe JTAG ports on the Pegatron board?
Looking at a firmware update there is a referenced in the build.prop a reference to the factory reset partition:
#factory reset protection partition
ro.frp.pst=/dev/block/mmcblk0p13
which isnt mounted during normal operations so no way should have a root attempt damaged this. I would assume that this would just recover all the necessary files and overwrite them durin the normal recovery operation. Question is, is there an issue with build.prop so factory reset doesnt get to find this location?
When I run the recovery procedure it finishes correctly and provides the option to reboot as per the Audi instruction.
All I can do from a PC now is use sideload as the tablet doesn't get to the Audi rings so true ADB isnt running :-(
Did the tablet need to go into the car to fully recover?
Does anyone know with the Android recovery main menu "forced recovery" does?

spyderboyant said:
Any joy here to report? I can confirm stesps above are correct and I have done the same recovery but the tablet sits on the pre-screen without the Audi rings starting on my desk. It took ages to do the factory reset/ wiping /data and cache... I tried to "root" the tablet so hopefully not fully dead. The eMMC is a BGA so really painful to try and recover the old way with a complete image flash. Maybe JTAG ports on the Pegatron board?
Looking at a firmware update there is a referenced in the build.prop a reference to the factory reset partition:
#factory reset protection partition
ro.frp.pst=/dev/block/mmcblk0p13
which isnt mounted during normal operations so no way should have a root attempt damaged this. I would assume that this would just recover all the necessary files and overwrite them durin the normal recovery operation. Question is, is there an issue with build.prop so factory reset doesnt get to find this location?
When I run the recovery procedure it finishes correctly and provides the option to reboot as per the Audi instruction.
All I can do from a PC now is use sideload as the tablet doesn't get to the Audi rings so true ADB isnt running :-(
Did the tablet need to go into the car to fully recover?
Does anyone know with the Android recovery main menu "forced recovery" does?
Click to expand...
Click to collapse
Update... I re-flashed the APP partition I had from another tablet that has root and then re-run the update via recovery so tablet is back.
The issue is the rooting process I used (kingoroot) only half did the job. Tablet looks to be rooted when booted into fastboot:: fastboot getvar secure & getvar unlocked
(bootloader) secure: no(bootloader) unlocked: yes
BUT, I can only boot the correct BOOT.IMG found on the update SD cards. If I change one byte in the update image I receive on the screen of the tablet
???.img verififcation failed twice in BootAndroid!! Contact care!
To me, this means the bootloader flag for unlocked is set but not being read and hence the SELINUX secureboot check is still being used :-( Hence you cannot load any "adjusted" bootloader images :-(
The only "oem" switch I can find for the tablet that loads is "fastboot oem lock" to lock the bootloader. When I try and lock the bootloader again, nothing happens, the flag stays set at (bootloader) unlocked : yes. There isnt any "fastboot oem unlock" command. Analysis of the bootloader image I have from another rooted tablet doesnt show many obvious commands for the oem switch..
Very strange.
When also in fastboot mode the bootloader image shows as 6Meg?? whereas its based on Tegra which has the boot loader split across two partitions of 4Meg each on the eMMC: mmcblk0boot0 and mmcblkboot1
Without a truly unlocked bootloader I think I am stuffed.
Any ideas?
APX mode is available from the bootloader "forced recovery". Maybe this is the only way by re-flashing known "virgin" bootloader partitions?

Hi @spyderboyant, how did you manage to get into the recovery ? I have 2 of those tablets with forgotten password and I can't get into the recovery to factory wipe them...

Power off tablet, then while pressing and holding the power button down to power on the tablet constantly press the left volume button quickly. Keep pressing this volume button with power button depressed and it will bring you to the "fastboot" menu (the bootloader image). Then release the power button and stop pressing the volume button when you see this menu. Then select via the volume buttons the "Recovery Kernel" and press the power button. The tablet will look like it reboots but will show an android image. Depending on the firmware on the tablet you can either press the "power" button to get to the recovery menu or "hold power + press right volume button" to proceed to the recovery menu... You should now be in the "Android System Recovery <3e> menu..." Scroll down to "wipe data/factory reset" and press enter and there you go....
**IMPORTANT** This wipe can take anywhere from 10minutes - 45 minutes+ ****
BE PATIENT.. LET IT FINISH
If above doesnt work. Install Android Debug Bridge (ADB) and connect to the tablet from a PC with a micro USB cable. You need to enable Android Debugging (settings/about tablet/press "build number" seven times). Then under developer make sure "USB Debugging" is enabled and connect tablet to PC and "trust" your PC. Then from a command prompt in the folder with adb tools installed issue the with "adb devices" command to make sure you can connect to the tablet.
PC>adb devices
List of devices attached
2ps53qtnDvxxJPx1K device
If you can see the tablet then you are good to go... Issue "adb reboot recovery" and you get to the screen with the android image... Again either press power button OR hold power button and press "right" volume button to proceed.
Make sure you use a decent micro USB cable as some are only power and you wont be able to connect to the tablet.
good luck

[GUIDE] How to Unlock the Samsung Galaxy A70 Bootloader

Hello fellas;
In this topic, I'd like to show you how to customize this device, from unlocking the whole bootloader into flashing a proper AOSP port.
Setting Up Environments for Windows Users​
Microsoft Windows.
Samsung USB drivers, click here to download and install them.
Odn Flash Tool, download it from the attach files.
Spoiler: How to Flash VBMETA Using Odin Flash Tool
Download the vbmeta.tar.gz (if you didn't done it yet).
Reboot the device into downloading mode (Vol Up + Vol Down + Power + connected USB).
Open Odin Flash Tool and inset the vbmeta.tar.gz into AP field.
Once you're ready, click on Start to flash it, the whole device will starts automatically once you see "PASS" on Odin screen.
Spoiler: How to Flash Recovery Using Odin Flash Tool
Download the recovery.tar.img (if you didn't done it yet).
Reboot the device into downloading mode (Vol Up + Vol Down + Power + connected USB).
Open Odin Flash Tool and inset the recovery.tar.img into AP field.
Once you're ready, click on Start to flash it, the whole device will starts automatically once you see "PASS" on Odin screen.
{
"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"
}
How to Customize Your Samsung Galaxy A70​
Spoiler: How to Unlock the Whole Bootloader
Go to Settings.
Tab on Connections.
Select your WiFi connection, then insert the password (otherwise OEM unlocking option won't appear).
Tab to About phone.
Then tab on Software information.
Tab many times on Build number, untill you see “Developer mode has been enabled“ appears on your screen.
Now back to the main Settings page, then click on Developer options.
You should able to see the OEM unlocking option, if it is gray enable it.
Reboot the device into downloading mode by Volume Up + Volume Down + Power + connect the device into the USB port.
Choose Volume up long press: Device unlock mode.
Press on Volume up Unlock bootloaedr (may avoid warranty) option.
Reboot the device, and check the OEM unlocking option again .
Congrats, your bootloader has been unlocked.
Spoiler: How to Reboot Into Recovery on OneUI 3.x Firmware
Samsung has changed the kaylayout maps by OneUI 3.0, so to boot into recovery just do this;
Press on Volume Up + Power buttons + the device must be connected into USB port, release the buttons once Samsung bootlogo appers during boot.
Congrats, you're in recovery.
Spoiler: How to Flash AOSP Port Using LineageOS Recovery
Reboot by pressing on Volume Up + Power buttons + the device must be connected into USB port, release the buttons once Samsung bootlogo appers during boot.
Tab on Apply Update > Apply from ADB.
Do the same for GAPPS.
Now do a rest by Facotory reset > Format data/facotry rest.
Reboot, enjoy the fun.
Spoiler: How to Flash AOSP Port Using TWRP Recovery
Go to Wipe > Advanced Wipes.
Select the following partitions: Dalvik / ART Cache, Cache, System, Vendor and Data.
The confirm by Swipe to Wipe.
Back to the main page, then click on Advaced > ADB Sideload.
Check on Wipe Dalvik Cache and Wipe Cache, then Swipe to Start.
From PC, open a terminal application and do this;
adb sideload drag_the_rom.zip
Press enter to start flashing.
Do the same with the GAPPS, reboot and enjoy the fun.
It's recommened to go to Wipes > Format Data > YES (do this only if you came from stock rom, otherwise it will not boot).
Spoiler: How to Flash Magisk
Use LineageOS recovery for this operation, it's more efficient.
Download the latest Magisk from this link.
Reboot into recovery.
Tab on Apply Update > Apply from ADB.
adb sideload drag_the_Magisk-v25.2.apk
Press Enter to start flashing, wait a few seconds untill process done.
Reboot into the whole rom.
Download the latest Magisk application manager via Internet.
Install the proper modules to pass the CTS, benefits from the ramdisk.

reserved
Don't quote, I'm reviewing the guide.