yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 5 IV] ulasalu:
Yes, there is no BT connection issue since September. The steps that I mentioned earlier solved the problem temporarily because after a restart the connection issue occured again.

I guess the issue is solved by a software or app (Android Auto, Google, Google Play Services etc.) update, because at that time there were same complaints in the samsung forums too.

I recommend you to check software updates and App updates if you have not tried.
[Sony Xperia 5 IV] rumle001:
There are reset options in the about phone settings. Try reseting Bluetooth and Wi-Fi. Also, check the default device in the Bluetooth app. Hopefully unselecting the car as default would help.
[Sony Xperia 5 IV] ulasalu:
The same issue started again after a system update in May.
[Nokia 6.1 (2018) Questions & Answers] bertq#:
Nokia 6.1 ta1043

download lineage os plus associated file boot.img. First i install boot.img fastboot flash boot boot.img unfortunately the device only works in dowlood mode ! android 10 won't boot anymore and also fastboot reboot recovery ends in the android one image.

it is about lineageos 20 android 13
[Nokia 6.1 (2018) Questions & Answers] bertq#:
don't do this if you don't have the money to buy a new phone !
[Samsung Galaxy S9  Questions & Answers] Sp4ll:
heyo I tried to root my samsung s9+ with twrp and it got stuck on bootloop I tried to flash stock rom with odin but it fails

Can someone help me out?

edit: i fixed
[Non-Touchscreen Windows Mobile Other] malkag:
please if there is someone that has a s2u2 for samsung omnia that works please tell me where i can get it. thanks
[Non-Touchscreen Windows Mobile Other] Peopleselbowpad:
I got mine from here

http://s2u2.eqvipage.dk/S2U2-download-1.37-QVGA.html
[Realme GT 2] smashda:
Hey Guys,

what's the recommended way to Update after Unlocking & Root?

There's RMX3311_11_C.12 for Global Devices available, but it shows that "Extraction failed" when trying to Update, cause it probably detects the Unlock.

The File seems to be in the system drive under "data/ota_package/OTA/.otaPackage"

I don't want to brick my device, how can install the Update?

Local installation is greyed out.

Thanks
[Realme GT 2] Luigi2201:
try sideload update
[Realme GT 2] Stano36:
https://xdaforums.com/t/magisk-root-your-realme-gt-2.4582439/post-88559065
[General Questions and Answers] HanderMohander:
Hi!

I was about to end this tutorial to root my MI 9 se (https://xdaforums.com/t/...er-flashing-recovery-rooting-process.4286597/) and when I restart after install Magisk, I get a boot loop. Since then I tried this so far:

-Run uninstall.zip (from magisk apk). Resulting on "Updater process ended with error: 1"

-Install a previous versions (23 and 25). After install each version, I rebooted without success. Trying the uninstall.zip of each version result in the same previous error.

-Flash a boot.img. Doesn't seems to work

-Try the Magisk Manager tool. Running mm says that No magisk is installed, althought installing any verision of Magisk doesnt seems to fail (just the uninstall.zip part)

Since the begginning i had to figure some things by myself because adb not recognizes the device. Fastboot in other hand works perfectly (My computer only detects the device when on fastboot, no the other way. Seems to be something related to encryption by Xiaomi)

Some thoughts?

Thanks!

UPDATE: I had to go back to Stock MIUI through MiFlash Utility. After that, y tried another method with Lineage OS UNOFFICIAL, from this same forum, but I reached the same point, with a TWRP recovery bootLoop. I tried version 3.6 and 3.7 of TWRP and the result was the same.

UPDATE 2: Tried SHRP Recovery, but once flashed, pressing volume up + power button wont boot into recovery, just fastboot again (same behaviour as volume down + power). Its so strange but, well, another one more to the bag of problems.. In this try, I was able to boot again normally if just power on the device normally.
[One (M8s) General] ata-kaner:
NOTE:

This build is unofficial, don't report bugs to the official LineageOS bug tracker.

What's working

WiFi

Bluetooth

NFC

Audio

Screenshots

Camera/Video

RIL (Calls,SMS,Mobile Data)

GPS

Other things i can't remember right now

What's not working

Tethering

Selinux is permissive

Bugs

Audio recording bug is still here

You tell me

Screenshots

View attachment 5925545View attachment 5925547View attachment 5925551View attachment 5925553View attachment 5925555

Use NikGapps instead of MindTheGapps!

NikGapps

Downloads

AndroidFileHost

ROM OS Version: Android 11

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Latest baseband and bootloader

Version Information

Status: Beta

Created 2023-06-04

XDADevDB Information

[ROM][UNOFFICIAL][m8qlul] LineageOS 18.1 for HTC One M8s, ROM for the HTC One (M8s)

TELEGRAM GROUP: https://t.me/m8qluldev

Source

Device tree

Kernel

Vendor files
[One (M8s) General] ata-kaner:
I'm stopping development for Lineage temporarily. I'm trying something different and i'm sure it will be worth.

Spoiler content hidden.
[One (M8s) General] ismaelgt:
Hello @OLRIccc , I have installed it and works good, but I have tried later install with twrp "MindTheGapps-11.0.0-arm64-20220217_100228" and doesn't works.

I have tried first with "arm" but it tell me my dispositive is arm64, is strange.

Thank you for create it
[One (M8s) General] ata-kaner:
MindtheGapps has some problems with our rom. I recommend using NikGapps. It worked with me without a problem.
[One (M8s) General] ismaelgt:
Thank you so much, I have formatted the phone and selected and installed at the same time lineage-18.1-20230605-UNOFFICIAL-m8qlul.zip and NikGapps-core-arm64-11-20230609-signed.zip

Now it works!, really looking forward to seeing new android versions for this phone on the future
[One (M8s) General] ismaelgt:
Hello, I like sometimes enable mobile hotspot to share internet(mobile data) to another dispositives via wifi or usb, but not works, can you try if it works in your mobile?

Thank you
[One (M8s) General] ata-kaner:
Yes it's not working, even with old oreo build. I applied some fixes but there is still some problems i need to fix. I'm trying to reach the latest android version instead of bug fixes right now. But i managed to boot android 12 today so i'm going to stay with 12 and try to fix all bugs, including tethering and sound recording.
[One (M8s) General] ismaelgt:
wow, I love Android 12, this version is enough, not necessary android 13, I'll be here pending to help you and test new things when you release new updates on the future
[One (M8s) General] ata-kaner:
Yeah. Android 13 has some issues with legacy devices. Staying with 12 is a better idea right now. I'll release it when i manage to fix the camera.

Thanks for your support btw. Knowing that someone is using my roms makes me more motivated.
[One (M8s) General] rakeshbro:
@OLRIccc Thanks for reviving this set once again. Stock rom is supper laggy to use now adays. Looking forward to this. Keep up the good work.
[One (M8s) General] ata-kaner:
New build is coming tomorrow.

Changelog

* TWRP Decryption fixed

* First boot doesn't need a hard reset anymore

* DTS Eagle enabled (Check this thread for using it. Only supports DTS Headphone:X)

* New kernel. It should be more stable than old one.

* GPS fixed
[One (M8s) General] ata-kaner:
New build has been uploaded.

And about Android 12 and AICP, 12 has some weird issues with usb connection which disables connection with any other device and blocks adb and AICP has a issue with mobile data (it's fine other than that). I'll release it when i manage to fix it but don't expect new android versions anymore. Android 11 will be the last version for M8s.

Edit: I uploaded the correct build. I was a bit sleepy while uploading. Sorry.
[One (M8s) General] ata-kaner:
Hi guys it's me again. I came back after a tiny adventure with S20 FE development and i started to maintain M8s again. I added a telegram link to thread as well. If you have any questions, you can contact with me from there.
[One (M8s) General] mathew2214:
you got VoLTE working yet?
[One (M8s) General] ata-kaner:
M8s doesn't have VoLTE. It switches to 3G when you start a call in stock.
[One (M8s) General] handynoobinator:
Very good rom so far, thank you very much.

Bugs:

Known Wlan stays disconnected, have to restart, sucks.

TWRP:
https://xdaforums.com/t/recovery-m8qlul-stable-twrp-3-7-0_9-0-for-htc-one-m8s.4518227/post-89496258

LO Tipps:
https://xdaforums.com/t/rom-a5-7-2017-12-13-14-lineageos-19-1-20-21-unofficial.4517749/page-12#post-89480564
[One (M8s) General] handynoobinator:
partly solved:

Cant boot into bootloader or recovery, neither with the power and volume keys, nor with the adb reboot recovery command, or with the advanced boot option in system settings > reboot > recovery v bootloader. What is this, and what can i do?

Had some problems, listed here:

https://xdaforums.com/t/recovery-m8qlul-stable-twrp-3-7-0_9-0-for-htc-one-m8s.4518227/#post-89496258

* I managed to do it, press power volume up, until it reboots and then immediately press power+ volume down, then the menu appears which can reboot into recovery. (maybe needs usb debugging on) Try as many times as it needs to do that, repeat.

No GPS Program gets any GPS fix: OSMAnd, Organic maps, Navit, ZANavi

how to fix this problem? Does it worky on your device?

Flashed stock rom via twrp backup restore, gps works on all four apps. Maybe its because i flashed an older lineage os?
[Touch Diamond, MDA Compact IV General] superkev:
I can't get the LED to flash for new email messages. The option is greyed out in the Notifications tab of Sounds & Notifications. I've also tried Flexmail, which has its own event called "Flexmail New per Message." The checkbox for flashing the LED is selectable for that event, but the LED still does not flash.

Anyone else have this problem?

Bell Mobility Touch Diamond

TouchFLO 3D disabled (using regular Today screen)

ROM version: 1.13.666.7

Radio: 1.04.02V
[Touch Diamond, MDA Compact IV General] malsehn:
try the led-sound-fix.cab . after install, you'll be able to set led signal for e-mail and even unlimited time settings for led-signal for new events like new text message etc. ..
[Touch Diamond, MDA Compact IV General] superkev:
I installed the .CAB file, which did unlock the checkbox for flashing the LED for email messages. But, still no LED flash for new messages in Flexmail :(

Do you know what the .CAB file does? Is it a registry hack, perhaps something that I could adjust for Flexmail?
[General Questions and Answers] Nightwing2099:
I created some gifs on my old Samsung phone and want to copy them into oppo a53.
[Android Software/Hacking General [Developers Only]] mitomanu:
Hello, I have a Huawei Nova 9 se phone, received from a friend. I made the mistake of giving it a factory reset. This is where the problems started. The phone was trying to activate, then I got the message that the security chip is broken. I managed to solve that problem with UAP pro, but the phone no longer boots. Just enter recovery mode. In recovery mode I tried to reinstall the software, which is JLN-LX1, via OTG, but it does not install. Sure, I created the dload file and loaded the update.app file into it. It seems there is a way to bring the phone back to life with .xml and raw files. But all I found are only paid sites and they are a bit expensive. Is there anyone who can help me restart my phone?

Thank you all.
[OnePlus 9 Pro] allemandinstable:
Hi

I am very new to root

I followed the guide for rooting the phone from the pinned guide on the xda forum.

It worked prefectly, however I was getting a weird message in that the device was unsafe but everything was working fine and I thought the oem locking the phone might getting rid of it (I know it's stupid and caused problems) using fastboot oem lock

I now have the following error

Qualcomm Crasdump Mode
-----------------------------

dm-verity device corrupted
verity-ctr

Here's what I have attempted to fix this :

- getting back to fastboot and then using

1. - just booting the original

fastboot --disable-verity --disable-verification boot "/Users/allemandinstable/Downloads/9Pro_F75_Europe/9Pro_EU_F.75_boot.img"

2. - flashing it back

fastboot --disable-verity --disable-verification flash boot "/Users/allemandinstable/Downloads/9Pro_F75_Europe/9Pro_EU_F.75_boot.img"

but none of them work and still gets me the same error when booting

from the 9Pro_F75_Europe.zip which I downloaded [LE2123]

which was my version of OOS13 (F75)

- i looked for other threads and the unbrock guide bellow

the OTA zip files and stuff do not seem clear to me (don't understand) as I am again very new to all of this.

If anyone could help me unbrick my phone (and if you can explain me along the way what to do, how it works, etc...) it would be very nice of you, as I am pretty disappointed right now not having any phone.

Thank you
[OnePlus 9 Pro] TheGhost1951:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)

By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...

xdaforums.com

Use one for your region...........
[OnePlus 9 Pro] allemandinstable:
I think I expressed myself badly, I am from EU and this is the correct phone model (written at the back of my phone and also was visible in the parameters on the stock firmware )

I specified it to provide everything that could help at some point for people with better knowledge

the mistep was to fastboot oem lock after the root was completed ( which wa ssuccessful )
[OnePlus 9 Pro] Nimueh:
He linked you to the MSM tools to unbrick your device. If you're still stuck then follow this GUIDE precisely ;)
[OnePlus 9 Pro] allemandinstable:
OOpsie, my bad ! (stress + non native english speaker might lead to some misunderstandings 😀 )

Thank you for your quick answers

Unfortunately, there is no download link mirror left for my device version [LE2123 - EU] ( following the link from @TheGhost1951 )

which prevents me from moving forward

View attachment 5925619

maybe someone knows where I could find it ?

Thank you for taking some time answering me
[OnePlus 9 Pro] Nimueh:
There is no MSM for OOS 13, you have to use MSM for 11 and then update again to 12 + 13. Please read the guide I linked, it tells you all of that ;)
[OnePlus 9 Pro] allemandinstable:
alright, thank you for your patience !

If I have not found my way out of it by the end of the day I will post again on this thread

thanks 😀
[OnePlus 9 Pro] immortalwon:
Lol you saw the orange message that your device is not safe because of the unlocked bootloader and decided to re-lock it? You have to use MSM tool now.
[OnePlus 9 Pro] Appreciative:
After you get msm'd back to a working phone, get back to oos13 and root again, install magisk fully and then try this: https://xdaforums.com/goto/post?id=88584503

That's a magisk module for removing the orange warning text. You have made a mistake that many of us have made before, welcome to android rooting 🤗
[OnePlus 9 Pro] allemandinstable:
Thank you for your kind message, that's a weird sensation of feeling that stupid when trying out things.

Now I know that before doing anything, I will have a look on XDA Forums 🥹

Learned the hard way.
[General Questions and Answers] blackhawk_LA:
Hello! Yesterday my S22 Ultra was stolen. Everyone knows how does it feels when you lose something that is not only worth nearly 1000$, but also has tons of private information and personal data.

I had a custom ROM installed, and thanks to Samsung firmware, that means having to leave your data unencrypted. I know that most thieves only want the phone for selling it, but of course I'm a bit worried about my data.

My question is: how much more unsecure really is to stay unencrypted? I've read about samsung Knox security being hacked in minutes, so I wonder if in the end there's really a difference (if the thieves want to acces your data, they will do?)

I've just bought an S23U and for the first time, I have doubts about rooting.

I appreciate your answers and opinions.
[General Questions and Answers] jons99:
the difference between encrypted and unencrypted data is when you're data is encrypted if someone tries to look at it he'll only see weird letters and numbers and the only way to decrypt it is with your lockscreen password but if your data isn't encrypted then anyone has access to it no need for password or anything that means credit cards photos contacts everything is right there for the taking you can use the find my phone app to delete your data but I think you need to set it up as an admin app before it can do it I guess what I'm trying to say is stay encrypted if you can
[General Questions and Answers] WoKoschekk:
encrypted data => no chance to get any data stored on the user partition. nothing left to say about it.

not encrypted => all data is accessible!! you are able to restore all apps and you are able to open and to use them. to be honest, that's the worst scenario that could happen to you! you could get into serious trouble.
[General Questions and Answers] xXx yYy:
Always use encryption as that's default in Android ( FBE, FDE ).
[General Questions and Answers] blackhawk_LA:
Thanks people for your answers. I know that there IS a difference, of course. But (correct me if I'm wrong) there's always the chance for hackers to access encrypted data on the phone.

Even taking this in consideration, I also assume that it's better to have "three padlocks" than one if you want to protect something.

My question is maybe more about % of risk.

I think that if a thieve is stealing phones just to send them, they won't care if it's encrypted or not; they will do a factory reset or send the phone by pieces or whatever. Even if the phone isn't encrypted, it's not that easy for a normal person to erase the lockscreen security, isn't it?

But if they are interested in accesing data (like credit cards, electronic IDs and so) they will find a way no matter if the phone is encrypted or not. Or maybe it will bo so much harder if the phone is encrypted (and maybe depending on model and security issues on firmware) that they will most likely won't ever be able to.

That's what I'm asking, in other words: how easy or hard is to access encrypted data for a thieve?
[General Questions and Answers] WoKoschekk:
2-3 min. and I have access. with an unlocked bootloader I open TWRP website, get the build, download odin, flash TWRP, start it, hit the "backup" button and get an archive of your data. I wouldn't boot your phone to get around the "find my device" tools.
[General Questions and Answers] WoKoschekk:
2,158*10^12 years by brute force attack and the use of the most powerful hardware you can get.

How long would it take to brute force an AES-128 key?

How long would it take to crack a AES-128 key using the most advanced technology currently available? The hardware can be anything, be it a high-performance CPU, GPU or even FPGA?

crypto.stackexchange.com
[General Questions and Answers] WoKoschekk:
Upon the initial boot of a modern Android phone your data gets encrypted and keeps encrypted. Even in recovery. What do you think why TWRP has all the trouble with encryption?? In stock recovery you can only use minimal ADB. See source code: https://android.googlesource.com/platform/bootable/recovery/

That means you can only access adb sideload. No data is accessible in recovery since /data gets not mounted!
[General Questions and Answers] WoKoschekk:
stock recovery and any custom build like TWRP have ADB enabled by default. no matter what is enabled in your developer options. no recovery loads your settings.xml stored on /data.
[General Questions and Answers] blackhawk_LA:
Ok. that mostly answered everything. Thank you very much
[General Questions and Answers] WoKoschekk:
I have also a device that isn't encrypted to be able to use TWRP. But that device isn't my daily driver and stays at home. I know what is possible for third persons.
[General Questions and Answers] blackhawk_LA:
It's a pity that is not possible to have all security features on custom ROMs, especially on Samsung phones... Too bad.
[General Questions and Answers] WoKoschekk:
Samsung's encryption is too powerful. Their mobile devices are the most secure ones you can get. ;-)
[General Questions and Answers] V0latyle:
Eh...Not really.

Android Full Disk Encryption is integral to AOSP and while OEMs can modify what they use, such as the minimum key length (256 or 512 bit instead of 128) it's still "built in"

The strength of encryption depends on the algorithm as well as the encryption key. 128 bit AES means that 128 bit key has 2^128 possible values: 3.4028237e+38 possibilities.
[General Questions and Answers] WoKoschekk:
Why doesn't TWRP support encryption on my device?

Why doesn't TWRP support encryption on my device?TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, wh...

twrp.me
[General Questions and Answers] WoKoschekk:
FDE is deprecated and not allowed anymore for newer builds. Even regular FBE is now optimized by the additional use of Inline Encryption.

View attachment 5925721
[General Questions and Answers] V0latyle:
Ah. I missed that

Frankly...I don't worry about encrypting anything. I'm very selective about what apps I use and what access they have to files. I don't store anything sensitive on my phone anyway.
[General Questions and Answers] WoKoschekk:
my chats in Whatsapp (or any other messenger people have installed) is sth I wouldn't like to share with others. especially with someone who has stolen my device.
[General Questions and Answers] OldNoobOne:
Greetings Friends,

So whats the solution? All I can think of is to not use expensive phones at all so that the thieves aren't interested in the phones OR to keep a dummy phone of the same make in the other pocket OR to custom-fit our pockets with Titanium streachable thread/cord leashed to the phone OR hypothetically, somehow linkup the screen-unlock process with a 3rd-party company that verifies the users fingerprint + Face etc. biometrics then if failed remote wipe & share geolocation data with the local police :p

I think TWRP.me should be requested to build recoveries with password protection & usb debugging / dev options should be kept off by the user if not using those features.
[General Questions and Answers] WoKoschekk:
see here https://twrp.me/faq/securetwrp.html

not needed in recovery, enabled by default. only for adb while in system.
[General Questions and Answers] OldNoobOne:
Hi Friend,

Thats nice piece of info there , that article was published on june 4th 23 so its latest info too from twrp.me.

So jtag seems like some universal oem internal tool to access the hardware of a device. But I slept over it and as a solution to Thief-Encryption-Custom Recovery dilema thing I think The OEMs should ship their devices (high-end ones atleast) with unique NFC tags which could have option to set password-pin protection on them and if the device is geofenced with its unique NFC tag then if the device is away from its tag outside a certain pre-determined radial distance of say 15 meters then a OEM app hiding inside /system/priv-app or any other partition like recovery etc. would initiate a (hypothetical) command like Destroy Data Partition or maybe simply auto wipe the phone & send SOS SMS to local police. The Thief would not only need to steal the phone but also have to steal the Unique OEM-NFC Tag which the device owner can safely hide within for example their undergarments or socks or a pendant etc. I think this would be a better idea to keep a 1000$ phone secure from thieves, It surely looks next-gen idea to me :D
[General Questions and Answers] WoKoschekk:
ROFL, lol, haha, uh uh, yeah, yeah, bla, bla, bla... debuggable builds!!
[General Questions and Answers] WoKoschekk:
Did you also install some Magisk modules for your stock recovery or where does the su binary comes from? the default user of your recovery that switches to root is called...? idk... can't follow you.