yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Palinamarne:
Hello I would like to share a solution I have found :

Update ABI references using a script (create_reference_dumps.py) with the command:

$ANDROID_BUILD_TOP/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libcrypto

Example path:

python /home/android-14.0.0_r15/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libcrypto

Once the previous process has been executed and completed, I have successfully compiled Android 14 android-14.0.0_r15 again on Ubuntu 20.04.5-LTS

Details of my environment:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=14
PRODUCT_INCLUDE_TAGS=com.android.mainline
TARGET_PRODUCT=aosp_lynx
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-2a
TARGET_CPU_VARIANT=cortex-a55
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-165-generic-x86_64-Ubuntu-20.04.5-LTS
HOST_CROSS_OS=windows
BUILD_ID=UP1A.231105.003.A1
OUT_DIR=out
============================================

This solution has allowed me to compile AOSP 14 for example for a Google Pixel 7a(aosp_lynx) (which I have not tested yet)

View attachment 6034012

Today I will try to compile a virtual device aosp_cf_x86_64_phone-userdebug (it will take several hours)

I hope it can help, if you need more information do not hesitate to contact me.
[Android Builders Collective] Palinamarne:
Hello ,

I would suggest that you try some Ubuntu distribution to compile AOSP. At least in my experience it was the one that brought me the least complications and the best results.

Description: Ubuntu 20.04.5 LTS

I guess that for your Pixel 6 Pro you must choose: 'lunch aosp_raven-userdebug'

I remember that in the past I have made an image for Pixel 6a and I have used bluejay.

Please , see the differences with my environment.

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=14
PRODUCT_INCLUDE_TAGS=com.android.mainline
TARGET_PRODUCT=aosp_raven
TARGET_BUILD_VARIANT=userdebug
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-2a
TARGET_CPU_VARIANT=cortex-a55
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-165-generic-x86_64-Ubuntu-20.04.5-LTS
HOST_CROSS_OS=windows
BUILD_ID=UP1A.231105.003.A1
OUT_DIR=out
============================================

Let me know if this help.
[Android Builders Collective] SuperITMan:
The output I've sent is from the command create_reference_dumps.py -l libcrypto.

Here is my config:

% lunch raven-user
============================================
Commands from vendor/google_devices/raven/cmds-for-envsetup.sh:
export BUILD_ID_raven="UP1A.231105.003"
unset PLATFORM_SECURITY_PATCH_raven
============================================

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=14
PRODUCT_INCLUDE_TAGS=com.android.mainline
TARGET_PRODUCT=raven
TARGET_BUILD_VARIANT=user
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-2a-dotprod
TARGET_CPU_VARIANT=cortex-a76
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-2a
TARGET_2ND_CPU_VARIANT=cortex-a76
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.6.1-arch1-1-x86_64-Arch-Linux
HOST_CROSS_OS=windows
BUILD_ID=UP1A.231105.003
PLATFORM_SECURITY_PATCH=2023-11-01
OUT_DIR=out
============================================

I don't see real difference between your configuration and mine.

My machine has 4 CPU and 32GB of RAM.

My issue is that the following command does not work on my machine

$ANDROID_BUILD_TOP/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libcrypto

I get the following error:

error: external/hardened_malloc/androidtest/Android.bp:22:24: module "HMallocTest" variant "linux_glibc_common": data_device_bins_64: cannot find 64bit device target. Targets: map["android":["android_arm_armv7-a-neon"] "common_os":["common_os_common"] "linux_glibc":["linux_glibc_x86_64" "linux_glibc_x86"] "windows":["windows_x86" "windows_x86_64"]]

I'm building GrapheneOS.

Thanks for your help.
[Android Builders Collective] Palinamarne:
Hello @SuperITMan

Sorry for the delay in my reply.

So we are talking about Graphene OS and not AOSP: I would suggest if you can try with TARGET_PRODUCT=aosp_raven.

Here I have seen another solution in the following link:

https://forum.unity.com/threads/major-bug-in-android-14-breaks-building-aosp-for-debian-ubuntu-users.1506443/

Hope help.
[Chromebooks] Kliper23:
I have a Dell Chromebook 11 3120 that needs an RMA shim. I've been unable to find the RMA shim file to download and install. Dell doesn't seem to have it available on their site.

Does anyone happen to have the RMA shim for the Dell Chromebook 11 3120 or know where I could download it? I'd really appreciate any help or links anyone can provide. This Chromebook is my main device for school, so I'm eager to get it up and running again properly.

Please let me know if you can help me out with locating the RMA shim download.
[General Questions and Answers] Rottytops:
So I'm getting this "Can't load Android System" after about 7 minutes on the boot screen.

Gives me the option to "try again" which yields the above result again, or to factory reset.

I managed to run my battery down to 0% hoping that losing power and restarting might somehow change things, it doesn't.

Since id rather keep/backup/access my storage, resetting my phone to a factory reset situation is not an option right now. Here are more details about what my options are:

Volume+Up and Power gives me bootloader options

Volume+Down is non functional. Apparently ASUS make sub-standard quality hardware (This device is ASUS ROG Phone 6 512GB Global), and my Volume Down button started losing use a month and a half ago. So using this button is not an option for me.

From the Bootloader menu, I get the option to Boot System which just repeats the Boot pattern, Restart, which is still the same, power off, which self explanation, and finally Boot into Recovery.

Booting Recovery gives me these options:

Reboot

Reboot to bootloader

Enter Fastboot

Wipe Data/factory reset (with no option to only wipe cache, it's either nuke it all or nothing)

Run graphics test

Power off

Fastboot seems to be my only option to do anything. Problem is my device is unmodded. I believe USB Debugging was not enabled. But I don't know what my options are.

My goal is to access my Internal Storage. It doesn't matter how. Either I get back into my corrupt Android system, or copying my storage to a flashdrive or something through otg.

Can anyone help me or point me in the right direction?

I haven't had to use adb since 2017 so my knowledge is rusty and I don't know what commands will help me. Googling the issue also said some people used OTA update flash to fix their problem, but I also don't know where to go or where to start for my device specifically.

Can anyone help me with my storage problems?
[General Questions and Answers] user0u:
Here's the link to asus update.
[General Questions and Answers] Renate:
Did you have ADB enabled? Can you get through while it's stalling?

If you are lucky it's only the Android subsystem that is broke.

adb devices
adb shell
stop
ls -l /sdcard/
[General Questions and Answers] alecxs:
Reboot to bootloader = fastboot
[General Questions and Answers] user0u:
I don't know much about Asus flashing but apparently there's a flash tool that can be used without unlocking the bootloader. I would suggest looking for its latest version since that thread is a bit old.
[General Questions and Answers] Rottytops:
That kind of tool seems like flashing whatever image will wipe my storage. But it's a nice tool to have if resetting to factory conditions doesn't actually fix the device, but for now internal storage recovery is more important than restoring the device. Which is why I'm so hesitant to move forward with any fix
[General Questions and Answers] Rottytops:
Probably not? This was an unmodded device. I had dev options enabled for small tweaks, but USB Debugging was not enabled.

I have prior adb experience from old devices which is why I even know fastboot commands could be an option, but I have no knowledge where to actually begin.

I've never had experience with ADB experience without USB Debugging so I don't know how far fastboot can help me, and I have no experience with using ADB commands to do anything storage or side loaded related.

What I do know from googling my "Can't load Android" is that some people manage to force push OTA updates, but I don't know where to Begin specifically for my device since the tutorials I dig up specifically mentioned rooted devices, which I don't have, and can't perform dive I didn't have my bootloader unlocked or OEM unlocking enabled
[General Questions and Answers] alecxs:
then fastboot is of no use

if you don't have Apply update from ADB / Apply update from SD card entry in recovery menu, you cannot install updates. your data is lost.

edit: try this firehose programmer with edl client. if you can dump partitions, there should be a way to apply the update offline.

ROG Phone 6 / 6 Pro (AI2201) Repair to bootloader package:

Download: Link 🔗 Steps: 1. Only works on EDL mode. 2. Run script 0-8475_update_image_EDL_fh_loader.bat 3. Update Official OTA package in recovery or install UserRAW in bootloader Thanks ASUS Taiwan, @EdwardWu6688 , and don't use it for...

xdaforums.com
[General Questions and Answers] Rottytops:
Solved my issue, managed to get back all my data. This time for sure I'm gonna back up more than just my music
[General Questions and Answers] V0latyle:
What did you do to fix the problem?
[General Questions and Answers] Rottytops:
Sure, I realize people in the future will Google their issue and potentially come across this thread:

Pretty simple, but took some time, allow me to over-explain

"holding down the power button for a really really long time"

Because everyone loves a story...

My original idea/hypothesis of running the battery to zero to force a total power reset that I mentioned as my 1st procedure in my opening post, because I refused to believe my system could just corrupt on a completely unmodded device, so I kept trying. Just to repeat what the issue was, Hold the power, ROG logo video plays, but doesn't have its sound that it's supposed to, then reports that Android is corrupt and you have to factory reset or keep trying.

The problem is, whether ASUS is incompetent at making hardware (I say this because my volume button is non functional after 6 months, and my ROG Kunai controller's shoulder button is also non-functional after its first day of use, just a garbage manufacturer in my limited experience), or the fact the phone has a 6000 mah capacity, 0% doesn't necessarily mean 0%.

I digress, all I did was boot into the Bootloader because in the Bootloader menu I noticed the phone doesn't go into sleep/screen off, so I wrapped a shoelace around the power button, and let my phone sit for days well after the screen turned off, hoping this would eventually force/drain the battery to a true 0% state instead of just reporting as 0%

Basically that's it... I had an idea that I needed the phone to drain to 0%, but I underestimated that 0% wasn't Zero enough.

It took several days, more than I would reasonably expect.

I had the shoelace wrapped for a night, plugged in the charger, checked, Android reports corrupted

I had the shoelace wrapped for 2-3 days, charged and checked again, Android still reports corrupted.

Then I wrapped a final time, busted out my old phone so that id have something to use in the meantime, and leave the ROG alone for a week with the power button tied down.

Surely... SURELY the battery should be as drained as it possibly could be by now. And yes, I know discharging a battery to absolute zero could possibly kill it for good. Anyway, plugged it in, get the red charge light, but no reaction after 15 minutes on the charger.

Then another 15 minutes, still power does nothing.

Finally about 40 minutes after, battery indicator turns on, says 0%

Hold the power boots up with the ROG 6 logo. This time with sound, which a huge sign that something had changed.

Then the phone turned off. Wait until 0% became 1% and tried again. Successfully booted back into system.

About 2 hours to get back to 100% on a 20 watt charger.

So that's it... If you encounter someone in the future that has a similar problem, maybe suggest that the battery that says zero percent, just isn't zero percent enough yet
[General Questions and Answers] Rottytops:
Now I'm thinking about just moving all my data to a flash drive and sell my ROG 6 to some willing sucker, because the ROG Phone 6 and ROG Kunai have both have had button death and my experience with the brand had been soured. 3 out of the 3 hardware from that brand had not been meeting expectations.
[General Questions and Answers] V0latyle:
I'm going to go ahead and recommend that no one try what you did. It sounds like a good way to ruin your hardware and destroy your battery. I'm not terribly familiar with Asus devices but I imagine that it may have been possible to flash an OTA update to get your phone running again.
[General Questions and Answers] darky_omdb:
I don't want to roast but Asus is trash at all they make the most terrible things

its been 8 or 10 days im trying to root my phone and I give up today i think Asus doesn't let user enable the OEM and unlock the boot loader to be able to flash ROMs but u should just ota update and use your phone like before but becarful the most YouTube videos and guide are fake and they are not working for all users and all regions to root (that's how I broke my device) and there's also alot of percentage that u could break the device
[General Questions and Answers] Rottytops:
That's why I said in my wall of text that I knew it's a battery killer for anyone reading.

Also on this device, especially with bootloader locked, USB Debugging disabled, fastboot options, even sideloading with adb is extremely limited. And Fastboot commands would not work, even fastboot devices just to check if my device was responsive did not yield results. (yes I had ASUS and Qualcomm USB drivers installed)

My options were Factory Reset, or risk cracking the back glass for pin shorting to force EDL (there are no button/USB combinations to boot EDL on this device), sending my device in for "repair" where they would have wiped the data anyway, and regards to dumping through EDL, my Windows device wouldn't be about to hold the data I wanted to dump, since my Windows device is a Windows tablet from 2014. I had that tablet (I don't own a PC anymore) for the sole purpose of using mods and hacks on portable devices like Android phones, 3DS, PS Vita's, etc...

But those tablets of those days came with like 16GB of storage with Windows 8.1 taking up 10GB of that storage. To dump my phone I need about 410GB

With the tools I had for this particular phone, my options were limited.

Since I couldn't confidently remove the back without any issues, I couldn't unplug the battery ribbon cable, which is why I resorted tying the power button down to eventually kill the battery or capacitors of any residual charge.

If I wasn't locked out of Fastboot, or if the back was metal, or was a Samsung phone or something else, I would have had more options and try other things.
[General Questions and Answers] Rottytops:
Google searches and YouTube videos not yielding useful results is the only reason this thread existed in the 1st place.

Thankfully since the Snapdragon 805 (maybe the 810 I'm going by memory), it's been nearly impossible to truly brick your device. All Snapdragon SoCs back to a certain model come with a hidden EDL boot option that allows to flash compatible stock images. Sometimes that boot option is harder to access on some devices than others, but it's there. On may Chinese devices you have to short some pins on the board, but as long as you can put your device in that mode, you can push a stock image that will repair and reflash all your partitions. There seems to be very little exceptions in my experience as I've bricked every device I've owned up to 2019 and I've recovered from said bricks Everytime.

What changed after 2019 is any Android device I've owned had come with a locked bootloader and I was locked out of rooting, so I couldn't destroy anything, or I was discouraged from rooting/rom flashing in the first place. Custom roms often don't come with the software or drivers necessary to make certain features of gaming phones to work.

But yes, this phone and the Kunai controller is my 1st introduction into ROG brand/hardware so I didn't know to expect lockdowns, bugs, and faulty hardware, but now I know.
[Sony Xperia 5 III] Gustx:
Looking for lastest rom files for Xperia 5 III. is there a place they are kept?
[Sony Xperia 5 III] Mr Hughes:
You should be able to download the latest rom files via Xperifirm https://xperifirmtool.com/xperifirm-v5-6-5

Instructions are on the site.
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
Proudly Presenting RisingOS for Samsung Galaxy A71 [SM-A715F]
​

What is RisingOS?

RisingOS is a Open Source Aftermarket Android Operating System that aims to deliver unique and refreshing android experience. With a variety of AOSP mods.

Based on Android 13 | September 2023 | with a Splash of LineageOS

Screenshots :

Only for Reference ! Actual Device may differ a bit from demonstration !
​

Your warranty is now void.

I am not responsible for bricked devices, dead SD cards,

thermonuclear war, or you getting fired because the alarm app failed. Please

do some research if you have any concerns about features included in this ROM

before flashing it! YOU are choosing to make these modifications, and if

you point the finger at me for messing up your device, I will laugh at you.

Thanks for your understanding ! :)

What is Working ? :

Audio.​

Bluetooth.​

Calls and VoIP via bluetooth.​

Camera.​

Fingerprint.​

GPS.​

Lights.​

Mobile Data.​

Mobile Calls single and dual sim.​

Call record.​

NFC.​

OMX.​

SELinux is Enforcing.​

Sensors.​

Screen-OFF FOD.​

Storages, Internal and External SD cards.​

WiFi.​

Screen Mirroring.​

Bugs ! :

Camera apps that use the CameraX framework produce around 70mb JPEGs, try different GCAM. FIxed ! check new release !

VoLTE/VoWIFI (due to there is no implementation for samsung devices) that's common.

Requirements :

Unlocked bootloader.

Ensure to be on the latest OneUI 5.1. A715FXXUADWH4

Installation Guide Via SD card (TWRP) :

Use the recovery form download

Copy the latest ROM/GAPPS to your external SDcard.

Install > Select ROM

Wipe data and cache, redo same steps for GAPPS/Magisk.

Enjoy.

Credits :

@haky 86 for his works on Samsung A71 & A70 devices .

@Simon1511 for his works on Samsung QCOM devices.

Well of course Me @khalil30 ! for building this masterpiece LOL 😂.

Source code

:

https://github.com/Haky86?tab=repositories

Download :

Rom link : Google Drive

Download your own flavor of NikGapps (your experience will depend on what package you choose !)

"it's time to choose !" Gman

Gapps : NikGapps

This Rom is Unofficial Release, So do not Expect Updates !
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] ZG_DEV:
Nice rom, mate

Thank you !
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] vc_1455:
how did you install it? I did it with TWRP and NikGapps and it doesn't go beyond the "rising" logo
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] ZG_DEV:
Didn't install Gapps at all :)
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
it's mentioned that you have to change the /data file system to ext4 ! read again 1er post !
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] vc_1455:
So the ROM already includes GAPPS?
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] vc_1455:
In which section of TWRP is this done? 🤔
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
no you have to download your own gapps

follow this video ! the video is just to show you the way to change the /data file system ! you have to check EXT4 !!
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] conghuykrb:
How do I make the status bar fit my phone's camera?
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] roma1141:
Hello! This is a very good gsi firmware, the best!

USB DAC does not work, turns on and off constantly, flashed Prime Kernel, this did not give any result. Can anyone tell me the essence of the problem?

Thanks a lot!
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
the correct value for the camera cutout overlay is not available in this rom

first, it's not a gsi ! it's a full AOSP based rom

for USB DAC i will check it, but never use Prime Kernel , it will crash the fingerprint use
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] conghuykrb:
Why i don't have transparency effects on notification center like in the picture
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] roma1141:
Thank you very much for your answer! I didn’t know that it wasn’t gsi firmware, I’m ashamed :)

But this is excellent firmware, and very fast, only one thing upsets usb dac. Thank you!
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
you have to set that from the settings. the photos are only for demonstration purposes
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] conghuykrb:
A
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] conghuykrb:
Where is it in setting?
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] Legofan:
also yeah, for bugs

the screen flickers if you leave it idling for a long time
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
New release !

Everything is fixed !

no need for the ext4 data change anymore, just use the recovery in the download link
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] khalil30:
soon i will release android 14 RisingOS 2.0 once it's stable to use , please no eta ! thanks
[Samsung Galaxy A71 ROMs, Kernels, Recoveries, & Ot] vc_1455:
specifically, which gapps did you install to make it work properly?
[General Topics] zoxk:
To make it easier, use Zarchiver

1. You must go to folder "Photos"

2. You might need to find the folder "Screenshots"

3. Delete it and take a screenshot with the scroll bar.

This is how i fixed the bug, I do not know anything regarding other phones.
[Introductions] zur1el:
Hello, I'm happy to be here. Need something to learn here.. thanks for your support XDA.. :)
[Introductions] shibaa987:
Hello @zur1el Welcome to XDA.

If you need anything, search box on XDA forum is your first friend. You will get almost everything with the help of that.

Keep going. :)
[Samsung Galaxy S7 Questions and Answers] scopus:
hey i have s7 exynos with latest official android 8 and not sure if should install a rom as battery life most important for me. Will installing like lineage os20 improve my battery life or make it worse?
[Samsung Galaxy S7 Questions and Answers] ze7zez:
It all depends on how and what you use the phone for.
[Samsung Galaxy S7 Questions and Answers] ethical_haquer:
Look at these.
[Android Software Development] ethical_haquer:
View attachment 6114405

Galaxy Flasher

A GUI for Samsung Flash Tools

Thor and Odin4 are flash utilities for Samsung devices, like Odin.

Unlike Odin, they support Linux! (and only Linux, currently)

Galaxy Flasher is a GUI (Graphical User Interface) for Thor and Odin4.

For more info, check Galaxy Flasher out on GitHub.

Also feel free to ask questions below!

Disclaimer:

Currently, Galaxy Flasher is in an Alpha stage. There are known (and probably unknown) bugs. Also, it was just completely re-written, so the readme is still in the process of getting updated.

A list of missing features and know bugs in the latest release can be found on GitHub.

Galaxy Flasher Links:

GitHub, Original XDA Thread

Thor Flash Utility Links:

GitHub, XDA

Odin4 Links:

XDA

Credits:

@TheAirBlow for posting Odin4 to XDA, and for creating the Thor Flash Utility.

@A Cool User for his contributions, and for starting the port to GTK4 on his own.

@Not_Rich for continuing to test out new versions and suggest improvements.

@ethical_haquer, for Galaxy Flasher.​