yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 General] glacious:
Pocket Snes

Wow i found my solution!! > http://xdaforums.com/showthread.php?t=437927&page=2!

Thanks guys, now i only just have to get the sound to work :) !
[Samsung Galaxy Watch 4] Giovanni9921:
Hi everyone, I recently owned a 40mm GW4 without LTE. I have already followed all the guides to improve the smartwatch battery and I am quite satisfied, but I would like it to be even more smart. Is there any way to program AOD based on your phone or smartwatch's GPS location? For example, I would like AOD to be activated when I leave the house to go to work, while when I stay at home it is deactivated.
[Samsung Galaxy Watch 4] shaharofir:
Search here
[Samsung Galaxy Watch 4] Giovanni9921:
Two more questions: it seems that the rest/bed mode does not start automatically but must always be activated from the toogles, is that right? my mi band 5 had it automatically... Is there a way to set the screen timeout to 10 sec without activating energy saving? Thank you
[Nothing Phone 1] poolmaker:
Hi, how to rollback to stable 2.0.5 from Spacewar-u2.5-231206-0153-EEA?

Bootloader unlock and flash fastboot rom, or there are other solutions?
[Nothing Phone 1] poolmaker:
Solution

https://www.reddit.com/r/NothingTech/comments/195262h
[Nothing Phone 1] Kutaygb:
It hasn't worked for me. I'm on Spacewar-U2.5-231206-0153, and I'm encountering an 'installed failed' error on OTA also i can't sideload too.
[Nothing Phone 1] dav1234444:
i get package error when trying to update
[Nothing Phone 1] AnotherM1m:
How did you two installed the closed beta? is your recovery modified? Are you installing the beta offline updater before attempting to install update 1?
[Nothing Phone 1] Kutaygb:
I was on version 2.0.5, and I upgraded to INCREMENTAL OPEN BETA 1 FROM 2.0.5 via OTA. I didn't downgrade my phone, and my recovery is official. Before the update, I changed the boot image to stock, and I also used Magisk.
[Nothing Phone 1] AnotherM1m:
View attachment 6069565

The metadata of the file you shared shows that it install 2256 (open beta), not 0153 (closed beta) like you are writing.

try with the incremental from ob1 to ob2 first then if it doesnt work please post a screenshot of your build number from settings.

UPDATE:

also if you dont wanna to update to 2.5.2 but wants to downgrade to 2.0.5 from OB1, here's the link:

https://d2j3l8bo7dc01w.cloudfront.net/rollback-ota-package/ota_diff_20231215_225600_20231110_173157.zip?Expires=1962191330&Signature=2UCPkbWVjHCy807Eg4cR4abQM0vaibZZ-USVNy~o-vCMtmniCQfHUSce~UEFE8EUqIvGkCsBVsH-qWrvD3490ww1QW703h2MDs11QCHHCycyPZ6OZaGljZZd2H0oelmIkAGskgQqV9BgzNENjN1sdzztSuj4Qbe0xhVMEN2bvrRgEBh5vN62bFXg1SwCK0l9~fMo3sZtjx0erPwLoa4RZYnbWPQNyWZdejvzgaqI6-yzmB~1eZ-ybJ6ho3fuWgWS6Vzkr-cf4xMneV6qQDmGfZblNvxu5D0Bpc6WAy2a9CHq9c9L7fE9Sy-e9tFq43KCgxxQiM8Sb8QNmsc6bxRAnQ__&Key-Pair-Id=K1EOR8HYJKSWP1
[Nothing Phone 1] dtsvtpt1989:
error -2
[Nothing Phone 1] AnotherM1m:
send a screenshot of your build number please, the files that i sent are for a particular context, not for everyone.
[Nothing Phone 1] Kutaygb:
View attachment 6069571View attachment 6069572View attachment 6069574View attachment 6069573

Non of them worked for me
[Nothing Phone 1] AnotherM1m:
Ok confirmed you are not on open beta. I don't know which file you installed.

Follow the reddit link, you didn't installed the beta updater FIRST.

Install it first then use it to update your phone to the various versions. First 1, then 2 and then 3.
[Nothing Phone 1] AnotherM1m:
You are offtopic man, you are on 2.5.2.hotfix

For official firmwares please refer to this topic

Nothing Phone (1) - Repo [ NOS ][ OTA ][ IMG ][ GUIDE ][ ROOT ]

Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with PHONE(1), you...

xdaforums.com

Take a look at the third message, i've received reports that downgrading to 1.5.5 isn't feasible, you'll have to flash 1.1.7 vendor_boot and boot and the adb sideload 1.5.5
[Nothing Phone 1] Kutaygb:
View attachment 6069593View attachment 6069594View attachment 6069595

i'm also getting error with beta updater maybe i need to downgrade to 1.1.7 . how can i update phone faster or any ideas
[Nothing Phone 1] AnotherM1m:
Are you rooted or do you have a custom recovery installed?

If you are rooted remember to restore stock boot before updating
[Nothing Phone 1] Kutaygb:
i have stock recovery and ofc i flash the stock boot image before ota test
[Nothing Phone 1] AnotherM1m:
How did you restore to stock boot? Have you flashed what's in the main xda thread or you went to magisk, selected uninstall and then restore images?
[Nothing Phone 1] Kutaygb:
I used the stock boot from reindex-ot.github.io (v2.5.1 Beta 1), and I also attempted using the v2.5.1 stock boot.img that you shared. However, I'm uncertain about the uninstall process on magisk

edit:i try to flash again and i can't boot now :D

edit2: i change the active slot to b but now i'm getting after boot

View attachment 6069617

edit3: I can open and use my phone with stock 2.0.5 boot.img but because of that i can't ota
[Nothing Phone 1] AnotherM1m:
Ok the problem is that you flashed a stock open beta boot not the closed beta one so it cannot update.

Im not finding the stock closed beta boot anywhere.

When you rooted the closed beta, did you do

fastboot flash

or fastboot boot magisk_patched.img

If you flashed it directly (which is not adivsed) then downgrading with the lost of data is the only way to go, please start a backup of you data. when you are done we can continue.
[Nothing Phone 1] Kutaygb:
i didn't root my phone on 2.5.1 (closed beta) i rooted before the closed beta. I generally use neobackup after the backup i will downgrade to 1.1.7 after how can i upgrade my phone easly should i need update one by one
[OnePlus Nord CE 5G] miyonfaga:
I have this oneplus NORD CE 5G for almost 3 months and i've had since the beginning some issues with lagging, black screen, frozen on fingerprint unlock, etc.

Most of times it takes like only a minute or so for the problem to go away, now i've had a really long black screen, couldn't do anything, i tried forced restart, plugging it in the charger to see something pop up but all i got was a black screen.

Could this be memory related? i was trying to load some story's with bad internet connection.

As I'm typing this the light just lit up and everything seems normal but it lasted well over 10mins..

I really hope this does not happen again mobdro .
[OnePlus Nord CE 5G] kxruu:
Fingerprint won't even work for me
[General Questions and Answers] Lubo99:
Hello folks

so I managed to install this version of linux on my Samsung S9 Ultra Tablet running on android 14

Linux localhost 5.4.0-NOMone-fake #1 SMP PREEMPT Wed Nov 15 00:50:34 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

when I try to install signal-desktop app

using these instructions

# NOTE: These instructions only work for 64-bit Debian-based

# Linux distributions such as Ubuntu, Mint etc.

# 1. Install our official public software signing key:

wget -O- https://updates.signal.org/desktop/apt/keys.asc | gpg --dearmor > signal-desktop-keyring.gpg

cat signal-desktop-keyring.gpg | sudo tee /usr/share/keyrings/signal-desktop-keyring.gpg > /dev/null

# 2. Add our repository to your list of repositories:

echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main' |\

sudo tee /etc/apt/sources.list.d/signal-xenial.list

# 3. Update your package database and install Signal:

sudo apt update && sudo apt install signal-desktop

I end up with

building dependency tree... Done

Reading state information... Done

E: Unable to locate package signal-desktop

any idea what may be wrong? message says it but all installation went without error (packages were installed) but the last one ended like this...
[General Questions and Answers] itzParsaYC:
use this:

sudo apt-get update
sudo apt-get install signal-desktop

In Document's they have writen this is for *x64* Debian Based linux's. this version you have is arm64
[General Questions and Answers] Lubo99:
where do you see it. only i see is 64 bit version and thats what I have.
[General Questions and Answers] itzParsaYC:
you have the arm64 (arm x64 bit) versiom because android phone's cpu are arm64 and you cannot run x86-64 linux on it only arm64 linux's
[General Questions and Answers] Lubo99:
meanwhile I tried this solution - no success

Signal aarch64 Flatpak

. [✓] org.signal.Signal master i signal-arm 165.5 MB / 170.8 ID Branch Op Remote Download

1. [✗] org.freedesktop.Platform.openh264 2.2.0 i flathub 598.7 kB / 884.8 kB

2. [✓] org.signal.Signal master i signal-arm 165.5 MB / 170.8 MB

Warning: While trying to apply extra data: apply_extra script failed, exit status 256

Installation complete.

I am unable to run signal despite updating all dependancies based on tutorial..

so is here someone who was able to install signal on arm64 device?(not mac but android)
[General Questions and Answers] itzParsaYC:
You have PC?

If you have PC update it to windows 10/11 and use wsl2 to install signal
[General Questions and Answers] Lubo99:
no i dont have windows pc and i dont want windows pc. i have android tablet and want to have signal desktop app installed on it without logging of my android phone
[General Questions and Answers] itzParsaYC:
if .deb file are released. install it with apt or busybox
[General Questions and Answers] Lubo99:
i have installed proot-debian 12 in termux and was able to get signal running. however there is an issue with sending receiving images . anyone who can provide cli base solution for this? when sending picture loading never ends. picture is really small 24kb. video same issue but i dont need videos. pictures are required ...
[General Questions and Answers] Iconium_:
Well I have been flashing custom ROMs on my phone and I've got to thinking that is it possible to flash a custom ROM in Recovery partition instead of recovery? Or can you flash it onto SD card and boot it from there?
[General Questions and Answers] V0latyle:
Short answer: No.

Not short answer: Maybe but you'd have to modify partitions, which is a dangerous operation on any device, and you'd have to have a custom boot path. Besides there's not really any point to this - recovery is intended specifically to assist firmware recovery and update, and should be left as such. You should install a system image in /system and leave recovery in /recovery so that you have a way to fix things if something goes wrong.
[General Questions and Answers] Iconium_:
Do there recoveries exist that are not actually recoveries but a very small android? Just bare bones to run chrome and stuff?
[Other SmartWatches] gh0stza:
Hi Everyone,

I'm thinking of starting a new Android project for the Unisoc/Spreadstrum SoC's for cheap chinese smartwatches.

Much like what SlimBoxTV does for cheap chinese STB's running the Amlogic SoC's.

But before I commit I wanted to get the community's input and ideas regarding this project as well as get as much information about these devices I can.

Most of the chinese smartwatches available on banggood and aliexpress run the SL/SC 8541e SoC with Android 8.1.

Which is fine even though I would prefer Android 9 as A9 hit a sweet spot for me with being lightweight, fast, smooth, compatible, secure and stable.

These watches are a good balance between value-for-money and performance with the option of running an almost complete android OS.

But in my mind it means nothing if I can't say for sure: "I trust the firmware" and if the cheap STB's are ANY indication then these smartwatch firmwares would most likely be FILLED with keyloggers and, spyware and adware.

To make matters worse these chinese firmwares are VERY scarce to obtain, the information out there is almost non-existant and there is no root to speak of (in comparison to cheap STB's that usually comes with root OOB).

I found a thread on Hovatek about unlocking the bootloader of these SoC's:

Unlock BL (1)

Unlock BL (2)

More Info

But other then this information I came up with almost nothing regarding these devices.

So my goal with this post is to get feedback from the community

As well as any (AND ALL) information regarding these devices.

Any debug tools, testpoint information or any other flash software or information would also be highly appreciated

I would also appreciate if anyone could upload any firmware they might have for these devices including: A8.1, A9.0, A10 and A11.

So what do you guy's think? Is it worth it for me to start an Android project that targets these SoC's? And what Android version would you guys like to see on it? A8.1, A9, A10 or A11?
[Other SmartWatches] AlaskaLinuxUser:
I guess that depends on what you mean by "Android project"?

Smart watches are tough to build for. Do you have any ROM building experience?

If you are looking for guides on how to do that, I have several tutorials available:

[Guide] Zero to Hero, what to do when your phone has nothing, no TWRP, no custom roms....

Because I created the video series on how to build custom roms and kernels, I get a lot of questions. Most of those questions are exactly the same. One of the most common questions that I get alot in regards to building custom roms for Android...

xdaforums.com

[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]

Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...

xdaforums.com

And here is one I made just for smart watches:

I've built TWRP for smart watches before, and it can be tough to do when you don't have root. However, you can often steal OTA updates or use tools like SPFlash and the like to steal the boot.img as well, and use things like twrpdtgen and aospdtgen to make device trees for them.

One thing to keep in mind is WearOS, Google's smartwatch platform, is not fully open source like AOSP. That can lead to problems.

For instance, you can try to repo sync the WearOS platform, from here:

default.xml - platform/manifest - Git at Google

With:

repo init -u https://android.googlesource.com/platform/manifest -b android-wear-8.1.0_r1

But to the best of my knowledge, which may be out of date, WearOS included proprietary items that are not available to sync. But, YMMV.

However, AsteroidOS is an open source alternative to WearOS, and has an active community, so that is a route you might consider. I've used it on several smartwatches before.

So, all that to say, yeah, sounds like a good project, it will probably be difficult to do, and will require some experience, but there is a big need for smart watch developers here on XDA.
[Other SmartWatches] gh0stza:
Awesome man.

I'm gonna go through everything on your post.

Then over to your questions:

I've never built a complete ROM from scratch - NO. But I am a developer and have built numerous Android apps and been in the Android modding scene for quite some time - so I know my way around android.

And yeah, I'm talking complete ROM with a TWRP, root, the whole 9-yards else I can't trust the firmware and one of the main reasons why I want to be able to trust my smartwatchs' firmware is cuz I want to keep sensitive information of the smartwatch like crypto keys and crypto wallets etc.

"So, all that to say, yeah, sounds like a good project, it will probably be difficult to do, and will require some experience, but there is a big need for smart watch developers here on XDA."

That's just the kind of pep-talk I was looking for :cool:

I'm gonna work through your study material and decide if I will commit to it.

Thnx

PS: This is the test platform watch I'm considering ATM:

Aliexpress
[Other SmartWatches] gh0stza:
And this might sound stupid but, I want to add an always on display option for these watches - assuming it's actually AMOLED as the post says and not just a LCD screen with LED backlights (something that these chinese manufacturers often try to get away with).
[Other SmartWatches] gh0stza:
Could someone with a Servo KOM9 smartwatch upload a A8.1 firmware please - or even better if there is a A9 ROM out there somewhere.

...Maybe an intercepted OTA update
[Other SmartWatches] tancreded:
have a look at the zeblaze thor ultra, they seem to be the first 'name' manufacturer to be using this chipset, and it looks quite a polished device, though no camera

or the rogbid model a if you want to develop for a camera as well
[Other SmartWatches] gh0stza:
I saw both those models. Watched a youtube review of the Thor Ultra as well. Yeah they look polished.... but, if I compare those models to the Servo (or XueSEVEN) KOM 9. The KOM9 wins hands down.

My other choice model is the A7.

I did some research and it seems these devices are developed and manufactured by a chinese factory and the reason why you get more then one 'BRAND' of these devices is because you can buy wholesale from these manufacturers and then upon ordering it you can brand it according to your choice and they provide a 'software SDK'. Now exactly what 'software' that would include is anyone's guess. If I look at the XUESEVEN I assume they give android source too but who knows....

Still comparing everything I'm still leaning towards the KOM9 or the A7.

The A7 has 2 cameras (compared to the KOM9 that only has 1 side mounted camera), same chipset, but slightly more expensive.

I found a few firmware's from users here on XDA and I'm helping to try to unlock the bootloader on these devices as an early test run.

Will be making a HOW-TO-ROOT guide when all the bugs are worked out...
[Other SmartWatches] gh0stza:
In reference to the included software of those wholesale watches:

I assume (or atleast hope) they provide a device tree too. Now what would really help me is if someone that has this device tree could share it.

I'm also looking for kernel sources but I'm not gonna hold my breath...
[Other SmartWatches] tancreded:
you might want to go on the 'fullandroidwatch.org' forum, some of their member's have bought these sc8541e watch's, though i doubt it includes the com9

post on the unsupported watch's thread's
[Other SmartWatches] AlaskaLinuxUser:
Watch sellers never provide a device tree. Rarely do they even follow the rules for Linux based kernels which require they share the kernel code by law. You would have to make the device trees yourself.
[Other SmartWatches] gh0stza:
Yeah the KOM9 is brand new it seems. But, I will def register on that forum and see if I can get some more info...THNX (y)
[Other SmartWatches] gh0stza:
I figured as much. Still, doesn't hurt to ask.

I also contacted the Aliexpress sellers about source code, and the like but they either don't understand me at all - even though I even went through the trouble of translating it to chinese or they are just pretending to not understand me so they won't have to give up the firmware etc.
[Other SmartWatches] gh0stza:
***RESERVED***
[Other SmartWatches] gh0stza:
In reference to the guide on Hovatek ( and the more recently acquired - Guide on Gizdev) they use a file called: rsa4096_vmbeta.pem, which is a 4096bit rsa private key.

Now the files downloaded from ( Hovatek in particular - haven't studied the Gizdev one yet ) these guide use a shell script to use openssl to sign your device_identifier obtained with a modified version of fastboot... so the regular platform tools' fastboot gives an unknown command error on the first step of the unlock process ( which is ./fastboot oem get_identifier_token ).

I've been working with another user here on XDA to try and unlock his bootloader with these tutorials.

Now what's been bothering me is: how did these people get a private rsa key to sign the device identifier. Where did this rsa key come from? And how exactly did they modify the fastboot binary. For them to have modified the fastboot binary there would need to have been some modification on the device side itself before a modification of the fastboot file would make any difference, right?

Am I missing something or can I assume who ever these people are that made the guides had an inside source for the private key or source for the device itself. Is it possible that these people might have had access to the chinese manufacturers source - maybe they bought directly from the manufacturer and this is what comes as the 'software SDK'.

PS: not sure if I'm allowed to post binaries from other forum users here. So I'm making a 7zip archive with only the private key and a signature file. If someone would like to study the shell scripts or the modified fastboot head over to the Tutorial on Hovatek (Linked in post # 1) and obtain a copy yourself.
[Other SmartWatches] gh0stza:
And just to make a comparison: this method of unlocking the bootloader is nearly identical to the method LG uses. And I've given up on trying to crack the LG bootloader unlocking due to it being impossible to get that RSA key. There is a post here on XDA regarding the unlocking of LG BL's that I requested be closed because without that private key it's impossible to unlock the bootloader. So somehow UniSoc's private key got leaked where LG's is still 'PRIVATE'.

PS: if anyone is interested -

See also: lm80-p0436-1_little_kernel_boot_loader_overview.pdf 2.3 Kernel authentication

I wonder if UniSoc uses little kernel too?
[Other SmartWatches] benjibetanzorossel:
Hello, great idea considering how many of these devices are arriving and the great potential they have

Would it be possible to?:

- Get a firmware of any of these devices (p.e. the aforedmention Zeblaze Thor)

- Extract it and patch it (as using Magisk)

- Flash it through the Unisoc tool for it (I can't remember it's name)

Or

- Get the firmware

- Create a "general" firmware compatible with the devices using the same processor
[Other SmartWatches] benjibetanzorossel:
Thanks for the replay, I'd love yo help bit my knowledge it's almost none.

I thought that using an app like SPD Flash Tool you can reflash a modified firmware.
[Other SmartWatches] benjibetanzorossel:
BTW, can anyone share the launcher that comes with these smartwatches? I've seen some that include 4 watchfaces, but mine only have 3.
[Other SmartWatches] gh0stza:
Try this one... Just keep in mind I haven't checked the safety of it yet. Don't blame me if it steals your facebook login or something.

This was pulled directly off a stock X8 Ultra firmware - Android 10 (made with infinitybox)

It's from the priv-app folder - so I dunno if you'll be able to use it without root

You can reflash a modified firmware but the bootloader is responsible for checking the integrity of the 'protected partitions'. Long story short - it compares some stuff to other stuff and determines if the partition (such as the system and boot partition) has been signed by an authorized party.
[Other SmartWatches] gh0stza:
Now that is an exploit! :ROFLMAO:
[Other SmartWatches] gh0stza:
Oh and I also suspect even infinitybox wouldn't have been able to make a firmware dump for me because the data partition is faked to look like 64GB. Cuz I'm thinking InfinityBox just has a ton of FDL files for various models and then just selects one based on the reported hardware. Faking the watch did much more harm then I could have expected.

I'm open to ideas as I have a brick now and I can't obtain that firmware to save my life.
[Other SmartWatches] mhd 12:
Hahahahah i should’ve pasted that for google xD
[Other SmartWatches] mhd 12:
Did u try unlock tool ?!!
[Other SmartWatches] gh0stza:
Yeah like I mentioned the one we're using only has limited options. I need that other version.
[Other SmartWatches] mhd 12:
aah :/ well for me am having a problem unlocking bootloader because it asks me to press volume up while there is no volume up x"D
[Other SmartWatches] mhd 12:
aah btw i have the rom for zeblaze thor 5 pro if u need it
[Other SmartWatches] gh0stza:
Damn yeah that is a problem. Maybe if you open it up there is pins on the mobo.

Bring it on, lets see maybe that one works. It's almost the same hardware