yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] Rich_Flex:
i havent found a firmware yet. will get back as soon as I do
[Android Stick & Console AMLogic based Computers] fastvan67:
Fabulous
[Samsung Galaxy A12] tyler4709:
i am trying to flash a gsi but i dont have a custom recovery so i was wondering if there is one for the a125w model
[Redmi Note 12 4G] stevenf00:
Hi,

In Redmi note 12 4g, there are 2 models. One support NFC (topaz) and another non-NFC support (tapas).

https://miuirom.org/phones/redmi-note-12-4g-nfc (Topaz)

https://miuirom.org/phones/redmi-note-12-4g (Tapas)

The chipset is snapdragon 680.

Is possible to install Topaz ROM into Tapas?

Any idea and what is the risk?
[Redmi Note 12 4G] jaimebo:
I have exactly the same question, please let us know your outcome if try :)
[Redmi Note 12 4G] stevenf00:
Hi, I am not able to try since I have only 1 phone. It is too risky. Unless there is sponsor. :)
[Redmi Note 12 4G] ahusni96:
Hi everyone,

I've tried flashing topaz's rom to a tapas device. It does not able to flash it because of mismatched hardware error from the flashing program.

I can still flash back to tapas's rom after the attempt.
[Redmi Note 12 4G] stevenf00:
Thank you for trying out. Greatly appreciate that.
[Redmi Note 12 4G] tahanaqvi:
have anyone else tried it ? i will try the same topaz into tapas and will share the results here
[Redmi Note 12 4G] K.Hatake:
I am wondering why you would want to convert the Topaz Rom into Tapas when there are already Tapas Roms available online.
[Redmi Note 12 4G] nabitô99:
Tôi đã flash rom topaz cho mô hình tapas của mình và thành công ( rom tùy chỉnh không chính thức) . Mọi hoạt động đều bình thường chỉ NFC không hoạt động ( đó là điều kiện tự nhiên và không ảnh hưởng gì )

Moderation Edit: English Translation

I flashed topaz rom for my tapas model and it was successful (unofficial custom rom). Everything works fine, only NFC doesn't work (it's a natural condition and doesn't affect anything)
[Redmi Note 12 4G] MinaAlex:
I want flash topaz andonisa ROM on tapas device becus there is no andonisa ROM for tapas.

is it possible ?
[Redmi Note 12 4G] Ahmedmirza5252:
Can I flash linageOS version 20 (unofficial) of topaz device in tapas

Can I flash this ROM in tapas variant does it support tapas. 🔗 https://sourceforge.net/projects/rn...e-20.0-20230801-UNOFFICIAL-topaz.zip/download
[Redmi Note 12 4G] Claroooooooo:
Hi, please tell us if this ROM is working fine with your tapas device if you tried it. thank you very much!
[Redmi Note 12 4G] WolfWindowsTech:
LineageOS works perfectly for my RN12 ( tapas )
[Redmi Note 12 4G] miloskrsikapa:
I'm writing this from Tapas device, I used topaz roms and flashed them succesfully to the device, they work flawlessly
[Redmi Note 12 4G] alim1976:
Я прошил на свой "тапас", Hyper OS от "тапаз",все работает без проблем
[General Topics] endlessdeath:
Mouse acceleration comes from libinputreader.so being hard coded to having a pointer acceleration of 3 with no way to change it. In order to change it on a rooted device you need to edit your libinputreader.so file and make a magisk module out of it.

On my LE2115 running LOS 19.1 this file can be found in /system/lib64/libinputreader.so.

Based on your luck one of the three methods should work for you:

1. Just straight up use the magisk module I made. This will ONLY work if your AOSP build is similiar enough to mine, if not it may very well send you into a bootloop. (I will upload this file later when I finish this within the week.)

2. Get a hex editor and search for the following bytes in your own libinputreader.so file - (will finish later adding bytes to search for). put the modified file in a magisk module and flash it to your phone, follow this guide here: https://topjohnwu.github.io/Magisk/guides.html

3. If all else fails you could do what I did originally to find this information- build the AOSP yourself from a linux desktop, edit the input.aidl file that holds the pointer acceleration value, one with no acceleration, another with acceleration, and view the differences between the 2 files spat out in a hex editor. change the corresponding values in your own libinputreader.so to disable mouse acceleration.
[General Topics] YUVA DeV:
Hi dude got there? Plz help me with this by step by step instruction
[General Topics] endlessdeath:
OH DAMN I didn't think anyone else would actually be interested so I didn't bother finishing this- Here's the upload: flash that with magisk and 1 of 2 things will happen:

1. your phone will bootloop and magisk will after bootlooping a few times probably auto disable all modules to rescue you from the bootloop

2. your phone will not have system wide acceleration when connecting a mouse.

If flashing this fails you I don't remember the bytes to search for and don't really have the time atm to go through it but both files are attached, you can examine them in a hex editor to see which ones were modified and download your own libinput.so from your phone and modify it appropriately and it will most likely work.

If you've tried that and you still need help you can add me on discord, endless5045. Good luck

P.S the website wouldn't let me upload the .so files so they were renamed to .so.modifieddeletethistrailingfilename.txt and .so.deletethistrailingfilename.txt. Please delete the extra extensions so they look like "libinputreader.so"
[General Topics] felipemessersmith:
Thank you for sharing this information about mouse acceleration and the methods to modify libinputreader.so. Please note that using these methods may have risks to best budget, so proceed with caution and make sure your device is rooted and you have the necessary knowledge and expertise to handle these changes.
[Android Apps and Games] quro13:
View attachment 5968141

Update 18/Mar/2024: Add notification before redday, and Ovulation day forecast.

Update 30/may/2023: Add supported Android OS from Android 9 to newest. Fixed some bugs.

Monitor the menstrual cycle of girls

View attachment 5911657 View attachment 5911659

View attachment 5911661

Girls can follow by yourself, or your family, your man do it for you.

Just add the begin date for every period and you will be able to know the day of next period comes, based on the history of last 6 months.

This application does not collect any personel data or share it to anyone.

App contain small Ads in some screens.

App will have function that sending notification before the day, in the future, updating.

Download from Playstore: https://play.google.com/store/apps/details?id=com.qrrr.qgirllog
[Android Apps and Games] quro13:
UP
[Google Pixel Watch] v1ru5879:
Recently encountered an issue where I was able to get the watch factory reset and wiped then I was able to start the setup process and it started an update, but now its stuck on the multicolor G logo. I have a feeling I will need to do an update with a hacked up cable and ADB. Anyone else experience this?
[Google Pixel Watch] Joshsha:
I don't have too much experience, but the 4 pins at the top of the Pixel watch are just USB, so you should be able to use a hacked up cable to try flashing the stock firmware via fastboot, that is, if you can get a copy of the stock firmware.
[Google Pixel Watch] v1ru5879:
So I found a solution by total accident. I isolated it to after the setup when it updates and restarts it would get caught in that boot loop and never actually boot. I was trying it again for about the 10th time after factory resetting which would allow me to at least get to the setup screen and continue forward. So it was on last step of the setup where it downloads the update and pushes it to the phone when I got up and answered the door because my buddy had called to say he was pulling up. Without knowing I walked away with my phone and it must have lost the connection because when I came back the watch was functional and got through that initial boot that it kept getting caught up on. In the watch app I now had a notification that the watch needed to update with the option to download and install. I was hesitant to do so but it worked.
[Fire TV General] Pedro-SA:
Sorry for not organizing the post properly but I would like to share something new, as I didn't find a dedicated post I decided to talk about it in this one, the Launcher Manager can easily remap the Fire TV Stick buttons, despite the video being in Portuguese (my native language ) is easy to understand when looking at the images, it can even be watched without audio.

Mod edit: Self promo YT link removed.
[Fire TV General] Badger50:
Thread closed since the topic already exists here. And please refrain from sharing personal social media links as stipulated in XDA Rule #5:

Spoiler content hidden.

-Regards: Badger50
[ASUS ZenFone 8] Ponso00:
Can't use the official unlock app from asus to unlock the bootloader. Just got this zenfone 8, and I successfully unlocked the bootloader on another zenfone 8 about a week ago, why did it work then but not now? I saw someone else posted about this same error with the rog phone 6 last week.
[ASUS ZenFone 8] blackbile:
Maintenance on Asus server from 2. may ,,,
[ASUS ZenFone 8] MDV106:
A week ago? I've had this phone since the start of the month and still cant unlock the bootloader with each daily retry
[ASUS ZenFone 8] Ponso00:
Wow this is bad. If asus doesn't give us an estimate for when this is done soon I might have to return this and buy a Zenfone 9. But will that have the same issue? I hope not
[ASUS ZenFone 8] jstys92:
The same issue is currently happening on the zenfone 9 (and all asus phones that I'm aware of) with no concrete fix communicated by the support team.
[ASUS ZenFone 8] Joheee:
Still the same issue on my Zenfone 9. Would it ever be fixed? If not, is there another way to unlock the bootloader?
[ASUS ZenFone 8] ZachRayT:
Has anyone been able to solve the issue?
[ASUS ZenFone 8] ZachRayT:
In a call with Asus support this morning, they told me they are no longer supporting the Asus Unlock Tool. Someone might want to call them again and double check just in case.
[ASUS ZenFone 8] ZachRayT:
It should be noted that the customer support guy could be wrong, because at first he didn't even know what I was talking about
[ASUS ZenFone 8] bnsmb:
Hi

I just got a confirmation from the ASUS suppprt that the unlock tool is still supported and only the server used by the unlock tool is currently down

regards

Bernd
[ASUS ZenFone 8] MDV106:
ASUS removed the unlock tool from their download site. Not sure what this means, but from what I gather they plan to reupload it in the 3rd quarter of the year.
[ASUS ZenFone 8] Dr.Axelbauer:
Interesting...Thanks for the news here...I am trying to get Lineage OS running on my new Zenfone 8 (ZS590KS)..Is it possible to get it running without unlocking the bootloader. Or is there any other way to unlock the bootloader?

Currently I upgraded to Android 13 and did all the checks within the Lineage OS installation tutorial...
[ASUS ZenFone 8] MDV106:
No and No. You need to unlock the bootloader to do anything of note to this phone. That is why mine is currently used as a browser and nothing more. I use my old phone for everything else.
[ASUS ZenFone 8] Dr.Axelbauer:
Give it a try! That might be cool if it works. No the Tool is not available anymore. The Asus Servers are down and hence there is no way as far as I know to unlock the device. I think (but I don't know much about android stuff) the request might grab some token to unlock the bootloader. But anyway if you manage to unlock the bootloader that would a great present to all of us Zenfone 8 Users around here ;)

Supports says that is possible, that the Unlock Tool will be made available in Q3 2023 but the don't give you any insurance about this ;) – We are a little bit doomed since the downtime of the Tool....
[ASUS ZenFone 8] StapledBattery:
I've done a little poking around; here's what I've found:

Modifying the unlock tool app itself is out; it communicates with a system service that checks its signature. If it is not the official Asus signed version, it won't work.

The unlock app doesn't verify HTTPS signatures, meaning that its communications can be modified by a tool such as HTTP Toolkit.

Modifying the APK version in the request is the first step. The error changes from "APK VERSION LOW" to "SW VERSION INCORRECT". I'm not sure what "SW" is referring to.

There are two requests made to the server: "login", which sends: a RSA-encrypted string containing the phone's SSN (serial number) and IMEI, the IMEI in plaintext, model number, and carrier. The other request is "register", which contains the APK version, "keyIndex" (which is always 1), and "ISN".

The register request is expected to return a "secret CPU ID" which is used to unlock the phone. It is a hex-encoded string at least 256 bytes long.

If the IMEI is omitted from the login request, I get an interesting error. "系统内部异常:nested exception is org.apache.ibatis.exceptions.TooManyResultsException: Expected one result (or null) to be returned by selectOne(), but found: 14945". I suspect the keyIndex has something to do with the same database.

I'm not sure what the ISN is. It might have something to do with the "SW VERSION" in the error message. Can someone who's also on the latest patch and ASUS_I006D-WW hardware version DM me so we can see if they match? (No need for HTTP toolkit; the ISN appears in logcat when you run the unlock tool).
[ASUS ZenFone 8] Chaphasilor:
@StapledBattery just wanted to let you know that "SW Version" probably stands for "Software Version" :) Hoping you can figure out a way to spoof the response somehow!
[ASUS ZenFone 8] lilddd:
I asked a question to ASUS TAIWAN by mail, and this is the answer. I'll share it with you guys.

Dear lilddd

Greetings for the day! Thank you for sharing your query with ASUS and providing us the opportunity to assist you.

My name is Abhishek and I will be glad to assist you with your query today.

I understand that you are unable to unlock bootloader in your Premium Phone -> ZenFone -> ZenFone 8.

As per your concern regarding bootloader, we regret to inform you that the phone unlock tool has been temporarily removed as we are undergoing a significant redesign at providing a better user experience and functionality.

We value your needs and understand your expectations for the phone unlock tool. Therefore, we are positively redeveloping and optimizing it to ensure that the new version meets your requirements. We anticipate completing the development in the third quarter of 2023. It will be relaunched and made available for your use.

Thank you very much for your patience and understanding. If you have any further questions or require assistance, please feel free to contact us. We will be more than happy to assist you.

You will be receiving a mail satisfaction survey within 3 working days, and we look forward to receiving your valuable feedback, as your opinion is very important to us.

Thank you for contacting ASUS and have a great day ahead.

Regards,

ASUS Technical Support
[ASUS ZenFone 8] xiaowei666777:
Look like Java code？ibatis
[ASUS ZenFone 8] GDorn:
From the support site, a recent update:

Given that unlocking the bootloader forces a factory reset, I've been watching for the tool to be re-implemented. But really this is a garbage nonsense problem that only a corporate brain could screw up; it's likely a tiny bit of java running on a cloud instance somewhere that a single dev in the company could set back up in an hour, but somebody up in management didn't like how it wasn't logging enough PII or didn't slot into the rest of the infra with the right buzzwords for whatever became fashionable six months ago and now they have to rebuild the whole thing from scratch.

Or they want to protect their kickbacks from the Google infestation for as long as possible...
[ASUS ZenFone 8] nilezon:
They have pulled all update zips, all source code and the unlock tool. There is only one good reason to do this: security breach. My money is on Asus being hacked and they had to shut the servers down to contain the damage, or the attacker removed data from their servers.
[ASUS ZenFone 8] D-IMAN:
I was rummaging through my files and came across an APK file that seems to be unlocked by the bootloader.

I downloaded it a long time ago from the Asus website.

This is not enough to unlock the bootloader, are there any other manipulations needed?
[ASUS ZenFone 8] bnsmb:
I guess you're talking about this APK (or another version):

AsusUnlock_1.0.0.7_210127_fulldpi.apk

This is the official unlock tool from ASUS, but it will not work without access to a server that is run by ASUS. And this server is currenty not running so you can't use the tool to unlock an ASUS phone

regards

Bernd
[ASUS ZenFone 8] D-IMAN:
It's a pity...
[ASUS ZenFone 8] Blumi511:
This is worst **** Asus has pulled. With the security updates stopped and the bootloader not unlockable this device has become a brick to me, since I must not use it for work anymore.

So here I am, waiting 14 days out for a Google Pixel 8.

Yay.
[ASUS ZenFone 8] bnsmb:
Hi

for what it's worth:

I created image files from my 2 Zenfone 8 (both with unlocked boot loader):

The partitions asuskey, asuskey2, asuskey3, and asuskey5 are all equal in size and content on each phone.

The partitions asuskey, asuskey2, asuskey3, asuskey5, asuskey6 are equal in size and content on both phones

Only the partition asuskey4 contains some data:

The first string in the partition asuskey4 is the serial number of the phone

The second string in the partition asuskey4 is the IMEI for slot 1

The third string in the partition asuskey4 is the IMEI for slot 2

The fourth string in the partition asuskey4 are different on the phones

The fifth string in the partition asuskey4 are equal on the phones

The sixth string in the partition asuskey4 are different on the phones

Update 22.09.2023/bs

The fourth string in the partition asuskey4 is the value returned by the command "fastboot oem isn-info"

The sixth string is in the partition asuskey4 the value returned by the the command "fastboot oem get-toolid"

see the partition details below

The installation of a raw OS image from ASUS will not overwrite the partitions asus* and the installation of a raw image will not re-lock an unlocked phone. So it can be assumed that the lock/unlock status is stored in one of these asus* partitions.

Do you have some details about this "secret CPU ID"?

What about the bootloader ?

Is the source code of the bootloader available?

There must be some code in the bootloader to check if the phone is unlocked or not.

I guess the code to check if the phone is locked or not is more or less the same on all Android phones (but I may be wrong here)

I read sometime ago that the initial boot loader on the phone is the uboot bootloader

regards

Bernd

Spoiler content hidden.
[ASUS ZenFone 8] bnsmb:
fyi:

The asuskey* parittions are not referenced in the source code for Android (tested with the source code for OmniROM):

Spoiler content hidden.

regards

Bernd
[ASUS ZenFone 8] bnsmb:
I found out how to get the values for the 4th and 6th line in the partition asuskey4:

[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/scripts_on_linux ] $ sudo fastboot oem isn-info
(bootloader) ISN_NUM = HB15HABF0700JTT00IRA
OKAY [ 0.000s]
Finished. Total time: 0.001s
[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/scripts_on_linux ]

[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/scripts_on_linux ] $ sudo fastboot oem get-toolid
(bootloader) TOOLID = 15715839e737449088fe70f7faf618f0
OKAY [ 0.000s]
Finished. Total time: 0.000s
[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/scripts_on_linux ]

There is also a property for the toolid:

ASUS_I006D:/ $ getprop ro.boot.toolid
15715839e737449088fe70f7faf618f0
ASUS_I006D:/ $

[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/asuskey/dev ] $ strings asuskey4.img
M6AIB760D0939LX
355375324140646
355375324140653
HB15HABF0700JTT00IRA
ASUS
15715839e737449088fe70f7faf618f0
[ OmniRom 13 Dev - xtrnaw7@t15g /data/develop/android/asuskey/dev ] $

The first string in the partition asuskey4 is the serial number of the phone

The second string in the partition asuskey4 is the IMEI for slot 1

The third string in the partition asuskey4 is the IMEI for slot 2

The fourth string in the partition asuskey4 is the value returned by the command "fastboot oem isn-info"

The fifth string in the partition asuskey4 are equal on the phones

The sixth string is in the partition asuskey4 the value returned by the command fastboot oem get-toolid"

regards

Bernd
[ASUS ZenFone 8] vgmoose:
Also! This article appears to go over something very similar, in terms of trying to reverse engineer an unlock token: https://o0xmuhe.github.io/2022/11/01/Qual-Android方案Unlock学习-以Oneplus7Pro为例/ (although I don't think they were successful).

Interestingly, the XML file that they've posted (ctrl+F for "token=") stores the token in the exact same size and format as the asus unlock apk implies its token should look when received fromthe server (as a giant ascii hex string of the bytes).

Running the string through a Java interpreter with the decompiled code gives us back a 256 (well 257, but close enough) size string, which should be how the 0x100 bytes of the token is parsed by the APK:

str ==> "C5DB7CFB89D7A9DBB005388A52F8622FC20BDDD89F5CAD8E ... 3030A6B4F7FC7AC576D07FFF2"
jshell> str.length()
==> 512
jshell> (new BigInteger(str, 16).toByteArray()).length
==> 257

The bottom line is copy-pasted from the "fromHexString" method in "src/main/java/com/asus/unlock/utils/Utils.java" in the unlock tool decompilation. Worth noting, but I couldn't really understand how the author was deriving the token, or how relevant it is. Notably, this blog article has the same GUID(?) string as the ASUS abl.img UEFI image: "volume-ee4e5898-3914-4259-9d6e-dc7bd79403cf/file-f536d559-459f-48fa-8bbc-43b554ecae8d"
[ASUS ZenFone 8] bnsmb:
HI

if anybody else wants to analyze the bootloader itself :

I created a HowTo for that

https://xdaforums.com/t/how-to-analyze-the-boot-loader-of-an-asus-zenfone-8.4631111/

regards

Bernd
[ASUS ZenFone 8] vgmoose:
Mind if I ask about the contents of your sysconf or devinfo partitions? I've found using "fastboot flash asuskey asuskey.img" and "fastboot flash asuskey2 asuskey.img" appears to successfully flash the partitions on device, even with a locked bootloader. I'm wondering if there's something I could write to one of these partitions that might help. It doesn't recognize asuskey4 however.

The list of partitions that fastboot will recognize appears to only be those that have a size and type defined from the list returned when running "fastboot getvar all". There's another oem-specific command "fastboot oem gpt-info" that lists a lot more info and more partitions, but when trying to flash those ones, fastboot reports the partition doesn't exist (so not asuskey3 through asuskey6).

Also, during the init of the ABL (near string "##### ASUS ABL INIT START #####" when disassembling) it loads values in this order: SSN, IME1, IMEI2, ISN, CID, Country, and ToolID, and references both asuskey4 and "Device Info" (not sure if same as "devinfo", or which partition is the source of truth here).

On this site (and as posted elsewhere on the forum) the ROG phone is claimed to be able to be unlocked without using the unlock server. I think a potential way this could be done without breaking the RSA verification stuff is:

Have captured a previous signed unlock token for a given ISN, from while the server was still running (the 256 byte asuskey payload)

Spoof the target device to have the same ISN as the one that matched that token, through fastboot flash or EDL commands

Write this previously signed token for "your ISN" to the asuskey partition and pass the verification checks in the fastboot unlock commands

Unknown/mostly baseless speculation if #2 is possible though, without having an unlocked bootloader already. I was just surprised to see that asuskey and asuskey2 both were able to be flashed via flashboot, and it makes me wonder about the other partitions.

My personal goal is starting to become to learn more about how this works– hearing that someone else was able to actually get the unlock to work is encouraging, but the deeper I try to dive into it the less hope I'm having. 🥲