yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] 96carboard:
Are you looking at this from a data security standpoint? Or from "make sure its worthless to the thief".

Data security I believe is much more important than causing the phone to self destruct if stolen, and from a data security standpoint, you don't need to worry about root, because the data stored in the userdata partition is ENCRYPTED, and this encryption is tied to lockscreen security. In other words, they need to be able to legitimately get past the lockscreen in order to have unencumbered access to your data, regardless of what they change with respect to boot and system partitions.

If on the other hand, you're more worried about rendering the device worthless if stolen (i.e., thief can't actually use it), then you're actually talking about gooble's factory reset protection, which pretty much locks you to factory images, and locked bootloaders, and the "unlock bootloader" switch set to not-unlockable.

Factory reset protection works by forcing you to validate that you are the owner of the gooble account previously registered as owner of the device. It can be trivially bypassed as long as the "allow oem unlocking" flag is set to true, or the device has a 3rd party OS key installed, such as from grapheneos.

Also, having the device REPORTED as stolen if it is, will make it unable to connect to a cellular network, which pretty effectively makes it worthless.
[Google Pixel 6a] tarun0:
Thanks for detailed answer. It answers my question.

While data is first priority, rendering device non-usable is also a deterrent.

Gotta find some ROMs which allow encryption tho. Thanks again :)
[Google Pixel 6a] 96carboard:
It isn't a useful deterrent to theft, because they have to steal it first before they can find out if its been rendered useless or not. Its not like they'll return it if they find out that its useless.
[Google Pixel 6a] optimumpro:
You should be worried more about having unlocked bootloader as opposed to root.

Root can only be obtained via Magisk, which creates a layer making your System think that Magisk is a part of it. No root could be obtained other than through Magisk manager, and even then, you will get a prompt to allow root to an app or adb. You can provide time limited root or one time only for apps. In other words, root gives the user control. Your OS already has root regardless of Magisk. All Magisk does is give you the power to grant or deny root.

Locked vs unlocked bootloader: this is where you should be concerned. If your bootloader is unlocked, it might be possible to boot or flash a modified recovery or TWRP that will have full write access to your system partitions, which are not encrypted. Android, unlike Linux or Windows never encrypted anything but data partition, and a few years ago, Google dropped even that in favor of file encryption. So, your data partition is no longer encrypted, just the files. So, when TWRP has full access to your system, an adversary may succeed in removing your screen lock/password/pattern and force system to boot straight without any lock. Note, the attacker wouldn't have to deal with encryption at all, but rather use natural Android weakness, which is: the first boot after installing a brand new rom is always without password prompt. So, in this case, the attacker will have the full access to your data.

With locked bootloader, this is not possible, as all fastboot actions are disabled.

99.9% of custom roms require unlocked bootloader. Those few, which are available on locked bootloader, do not provide root. There are only 1 or 2 developments that can provide optional root + locked bootloader.
[Google Pixel 6a] tarun0:
Ahhh... So there are options albeit just 1 or 2 which can root with bootlocker locked!!

I thought it's just impossible to root without unlocking bootloader.

Thanks for the nice explanation :)
[Google Pixel 6a] optimumpro:
Just my view: if I were you, I wouldn't buy any Pixels phone that has Titan chip in it. It is just one more reliance on such a 'bastion' of privacy as Google. Note Titan is closed source, and not only it deals with certificates, but it can also modify firmware. Here is Zdnet's description:

"The Titan chip manufacturing process generates unique keying material for each chip, and securely stores this material -- along with provenance information -- into a registry database. The contents of this database are cryptographically protected using keys maintained in an offline quorum-based Titan Certification Authority (CA).

"Individual Titan chips can generate Certificate Signing Requests (CSRs) directed at the Titan CA, which -- under the direction of a quorum of Titan identity administrators -- can verify the authenticity of the CSRs using the information in the registry database before issuing identity certificates."

So, each machine's individual key is stored with some 'magic' database maintained by Titan Certification Authority. In other words, an entity funded by three-letter agencies now has an additional database holding individual keys for each phone.
[Google Pixel 6a] tarun0:
Thanks for the opinion broski! But what brand are available there?

I don't like Samsung anymore because they destroy screen with update and don't help customers. Rest brand look more on papers but not in real.
[Google Pixel 6a] optimumpro:
Onepluses allow relocking bootloader on custom roms.
[Google Pixel 6a] truepremiumsecureos:
Don't be intimidated by the technical language - it's not as complicated as it seems. All hardware security modules come with a key that is installed at the factory and signed by the manufacturer. This initial key is only used to establish a basic level of trust, and the HSM will then generate a unique key for encrypting your data and performing attestation. This process is the same no matter what brand of device you use, whether it's an OnePlus, a pixel, or any other brand

Newer pixel models have a feature called ATTEST_KEY that allows each device to have its own unique keys. If one of these HSM keys were to be compromised, it wouldn't affect your security. However, rooting your phone can compromise your security and make verified boot ineffective, even if the bootloader is locked. If you value security, it's important not to root your phone
[Google Pixel 6a] truepremiumsecureos:
This statement is incorrect. The Android user interface was not designed to handle permission prompts for root access. When you root your phone, you increase the potential for UI bugs that were previously not able to cause harm to become attack vectors that can be used to gain full access to your phone. Rooting also weakens the security of your phone by adding new permissive domains and making the *_app SELinux domains more permissive

It is heavily recommended to read this article https://madaidans-insecurities.github.io/android.html
[Google Pixel 6a] truepremiumsecureos:
For the past five years, it has been required that all Android phones have encryption enabled by default. If you purchase a Pixel phone, it will come with encryption already enabled, but you can further enhance the security of the encryption by installing GrapheneOS as they increase the file name padding length to the maximum supported by the kernel make certain attacks harder.

Block-based encryption is generally considered to be less secure than file-based encryption because it uses a single key to encrypt all data, rather than multiple keys for individual files (which is what FBE does). Android 10 introduced metadata encryption, which encrypts the sector 0 on the data partition, making it inaccessible to attackers even when attempting to access the data through recovery mode. One of the main reasons file-based encryption is preferred over block-based encryption is that it is more difficult to verify the security of block-based encryption, and the algorithms used in block-based verification can be complex and challenging to implement correctly. Additionally, block-based encryption only encrypts data and does not provide any integrity checking, so if the data becomes corrupt, there is no way to detect it and the decryption process will continue. This can result in broken files at best and potentially allow attackers to tamper with or exploit the Linux kernel at worst, as noted by Linux kernel maintainers
[Google Pixel 6a] 96carboard:
This quote is mostly (the bad part) FALSE. The decryption on the files cannot be performed until AFTER the device has been unlocked. If an attacker installs something that skips the lockscreen, the files will NOT be decrypted, since that lockscreen password/pin/pattern/etc. is needed to gain access to the key.

No matter what, whether the device bootloader is unlocked or not, or the device has root access or not... if the device is physically outside of the owner's control, it is necessary to assume that security on it has been compromised and should not be trusted. As the owner, you should assume that it has been backdoored, so wipe it fully and reinstall OS.
[Google Pixel 6a] alecxs:
there is one exception, though. in AFU state, FBE is already decrypted (same as FDE)

https://bugs.xdavidhu.me/google/2022/11/10/accidental-70k-google-pixel-lock-screen-bypass

(does not concern powered off devices)
[Google Pixel 6a] TechX1991:
Not all of this is really right on the head.

tarun0​

FRP is VERY easy to bypass. Takes me about 2 minutes on Android 13 Jan 2022 update on 7 Pro, 7, 6a, 6 pro, 6, 5a, 5, 4a 5g and the 4a. The data is wiped though, so it at least can't have data stolen, but the FRP is more like a fence with a gate that you can just reach the other side to unlock with a paper clip lol

As far as getting past lock screen, there's USB plug-in's that if a true back actor wanted to get into the phone, it bypasses usb debugging and can force test thousands of pins and patterns per minute without flagging the maximum attempt trigger. But again, what's the chance of a phone getting stolen by someone with that level of knowledge? 90% of phone thieves take it, run and sell it quick flip.

Also, with a custom Android recovery, adb commands are possible, so if the device is rooted with a custom recovery, there's ways to extract the lock screen file where its stored and use it. I don't think the recoveries based on LineageOS can do this, but TWRP definitely can as I've done it personally. So far there's no twrp for any android 13 device to my knowledge. Even the android 12 variants of twrp are shotty and barely function.

Dirty flashing a rom will also remove any passcode generally on a phone. and make data accessible.

Reporting it stolen only goes so far. You can spoof the IMEI if rooted or straight up change it if you have tools like MiracleBox

Long story short, an unlocked bootloader and a rooted android device make the device very insecure. The only roms out there that let you re-lock the bootloader after flashing the rom are Graphene and CalyxOS. And I really don't recommend calyx. Its a pile of ****. Don't root graphene either, as you'll have to leave the bootloader unlocked
[Google Pixel 6a] alecxs:
we are talking about FBE encryption, not old FDE encryption with default_password. do not claim what you haven't tested yourself. FBE is simply secure in BFU state. also against bruteforce as gatekeeper lives in TEE. after 140 attempts the timeout has increased to 1 day.

kindly read about how FBE works

https://android.stackexchange.com/a/241688
[Samsung Galaxy M20 Questions & Answers] aatish2807:
Any android 12 custom rom for sm205f ?
[Samsung Galaxy M20 Questions & Answers] Tahir Jamil:
Yes theres a lineage os which is android 13
[Samsung Galaxy S22 Ultra] hoss_n2:
Dears,

I have S908E 22 Ultra, but my country always get updates very late. So the question is if I flashed other country firmware without changing CSC , will I still get OTA updates ?
[Samsung Galaxy S22 Ultra] the_arxyn:
Yes you will get but those OTA updates will be from that other region only
[Samsung Galaxy S22 Ultra] AlexKz23:
Hi, I have S908E 22 Ultra, I want to flash the USA or SM-G9880 firmware (or any snapdragon firmware) is OK ?

Also I changed the CSC code but the last line (country of production not change) example: COO/COO/COO after change CSC: XID/XID/COO. It's possible to change the country of production CSC without root?
[Samsung Galaxy S22 Ultra] AlexKz23:
Can anyone help with the info if can do it or not, only the last CSC (country of production) other CSC I changed with SamFw FRP Tool but like I said I can change the last 3 letters!

Thank you!
[Touch HD General] kroko.kroko:
I cannot make a success with connecting ubuntu on internet by pluging USB cabel and internet sharing in Blackstone.

Can someone give me a hand?

Thanx
[Touch HD General] Kangburra:
How far have you got? Synce installed? Partnership created?

What version of ubuntu?
[Touch HD General] ptrbee:
Hi Kangburra, if you have this working can you post a how to of how u did it?? I use linux mint ( ubuntu spin off) & ive never managed to get any of my phones to sync in linux..
[Touch HD General] kroko.kroko:
I have ubuntu 8.04.

My last one windows mobile PDA was Eten X500+. For to share internet connection a needed only to have installed two packages:

dkms and usb-rndis-dkms

Its now working now.

I tried to use usb-rndis-lite (http://ohioloco.ubuntuforums.org/showpost.php?p=3588717&postcount=54), but it failed too.
[Android Q&A, Help & Troubleshooting] AstralA:
how booting from a backup on a sd card works with some phones?

Can someone tell me how to take a working rooted model of the same phone and make a recovery sd card?

This might not be so simple though. The ls675 bricked had the wrong rom flashed to it but identical hardware (iirc it was m151)

I wanted the rootability with the working 1 click unlock in dev menu like the m151. I figured since the processor and ram were same size itd work.

It did used to boot into download mode but the lgup tool saw the m151 signature and refused to allow it on ls675. Saying unknown or whatever. I then tried to reinstall drivers but now have it as "unknown device" in device manager.

If someone knew how I would go about tricking the phone to boot from ls675 backup on sd with modified signature to appear like the m151?

Or is this phone irrepairably brickled? Just straight butter brickled? Just time for alley parts harvest? Gold reclaim? Oh say it isnt so. I can only afford this phone?! W why!
[Android Q&A, Help & Troubleshooting] AstralA:
So I have this in qualcomm bulk load mode from trying to boot into download. But no qfil ls675 recovery that I know of? Anybody got the firehose or mprg for msm8909?

Lg flash tool doesnt recognize the port

Is there a board diag file for 8909?

Its com port 40. I thought about trying to download the lg drivers because if lg flash tool could send it down that com port itd work I think. But it appears all lg drivers are done via the cloud and I cant get online on my machine. So if I installed it it wouldnt connect to the lg server.

Well I seem to recall the firehose and mprg or hex are in the phone technically. Could someone explain how to extract such files from a rooted phone? If so id upload it. Thanks
[ASUS ZenFone 6 (2019) Questions & Answers] hotmatua.parulian:
Guys do you know where to find parts for this z6 2019 such as power button and loudspeaker, that can send the parts to Indonesia?
[ASUS ZenFone 6 (2019) Questions & Answers] louislamlam:
https://www.aliexpress.com/item/1005003487852098.html

You could try to find them on Aliexpress.
[Google Pixel 7 Pro] Jch4xer:
So I have root via root checker and root beer is telling me I have root. All my apps that required root are working, but in magisk I can't access the modules.

No new apps are being promoted for root.

When I try to adb flash , it says there's a write error.

Latest everything on a p7p
[Google Pixel 7 Pro] ffuser1:
What do you mean you can't access modules? Are the modules enabled or disabled in magisk? For new apps wanting root, when you look at the permissions in magisk, is root granted/enabled for those apps?

What write error? You need to be more specific with regards to your issues
[Touch Diamond, MDA Compact IV ROM Development] xevier69:
Hi,

I hate to say but I'm not a big fan of Opera browser therefore I was wondered if there is any way to assign the Internet Explorer as a default internet browser for Touchflow 3d instead of Opera? Can this be done by some tweak or does it need to be a new cooked ROM?

Thanks
[Touch Diamond, MDA Compact IV ROM Development] charly_mx:
I thnk there is a way.

Hello my friend. I think its possible to do it. Why dont you search in the themes and software thread?
[Touch Diamond, MDA Compact IV ROM Development] ties:
Yeh, same here..

I can't work with opera..

Read this posting: http://xdaforums.com/showthread.php?t=455239

Just edit the xml file, place it back and soft reset.

Then the default browser is IE.

good luck
[Redmi 9 / Poco M2 Questions & Answers] mashrufhratul:
I updated my phone from MIUI 12.5.6 to MIUI 13.0.2. after the update was installed, phone naturally tried to reboot and got stuck in bootloop. I did not do anything, not even a button press at that moment. It kept booting, showed the Mi logo and turned off and booting again. After the battery was drained fully, it eventually stopped. Now I took it to a repair shop, and he said he can't get to recovery mode, nor fastboot mode. I tried that too, with power+volume up, and power+volume down but it did not work at all. I connected a charger but seems like it's not charging up cause the charger seems cold to touch (usually it gets hot during a charge). Now, I don't know if it's a solvable issue or not. If you have any way out, please let me know. Can't afford to lose my phone.

My Bootloader was locked before update, never really unlocked it.

And, does having less charge mean phone won't boot to recovery of fastboot mode?
[Redmi 9 / Poco M2 Questions & Answers] blackwolfxx:
Me too, you can try this : https://xdaforums.com/t/guide-how-to-fix-a-hard-bricked-redmi-note-9-merlin-hard-brick.4347025/
[Redmi 9 / Poco M2 Questions & Answers] mashrufhratul:
I'll try, but let me know if it worked for you
[Redmi 9 / Poco M2 Questions & Answers] blackwolfxx:
It worked .
[Redmi 9 / Poco M2 Questions & Answers] mashrufhratul:
Same. It worked for me too. But can't log in to Google. Says, there was a problem communicating with Google server. Are you having any issue? Any fix for mine?
[Redmi 9 / Poco M2 Questions & Answers] blackwolfxx:
No, i have no problem.
[Redmi 9 / Poco M2 Questions & Answers] mashrufhratul:
which MIUI version did you install? I still couldn't find any way to log in. I've tried every way possible.
[Redmi 9 / Poco M2 Questions & Answers] blackwolfxx:
V12.0.4.0.QJCMIXM and V12.5.6.0.RJCMIXM
[Redmi 9 / Poco M2 Questions & Answers] mashrufhratul:
Can you please screenshot your google play service version? I'm gonna try downloading the same and try again
[Redmi 9 / Poco M2 Questions & Answers] blackwolfxx:
Newest version .
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Serega da:
[About Us]:

MoKee is based on the Android Open Source Project (AOSP).

It has additional localised and personalised functionality while preserving the stock Android look by adhering to Material Design guidelines.

Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs.

Our ROMs' source code is open source, secure, stable and outstanding. Your experience using MoKee will be butter smooth with added convenience. So do not hesitate anymore, join us now and start enjoying the beauty of stock Android++ or even be one of our developers. Let's bring this project to greater heights!

[Descriptions]:​

Release: When we have achieved our development targets and determined that the current code base is stable, a Release version will be published.

Nightly: Compiled using the latest code base, includes latest enhancements but may also include undiscovered bugs.

History: When we stop maintaining an Android version, we will publish a final archive version before shifting development focus to the latest Android version.

Premium: Endorsed by device maintainers when deemed stable (limited to donors only and not available for all devices).

Experimental: Published when help is needed to test new features or newly supported devices.

Note: If any device-specific bugs are encountered, please kindly report to the respective device maintainers so that they can address them accordingly (device trees are maintained separately from the main MoKee codebase).

[Date]:

2021-10-09 10:45:05

[Android]:

11 (there is 10, 9)

[Google Apps]:

Not embedded

[INSTRUCTIONS]:

1. First Important Step is to Backup (optional for save your data)

2. Download Latest ROM Zip

3. Do clean flash

4. Flash ROM

5. Flash any add-ons if required like GApps, Magisk, etc

6. Reboot & enjoy!

[DOWNLOAD]:

helium , hydrogen

[Acknowledgements]:

The author of the assembly: Wt88047 / GuaiYiHu

It found and installed according to the instructions of AlexXYX
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Serega da:
I put this firmware Mokee-11 on MiMax 3/64. It is quite efficient and fast. Try NOT to install Magisk 25.2. If you don't have the problem of constantly rebooting your phone on 30-40% of the battery charge, then it suits for you.
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] leprince2007:
I tried mokee rom A10 but I found 2 bugs:

1-bluetooth headset

2-phone shutdown at 30% or 40%

Is there any fix?
[Xiaomi Mi Max ROMs, Kernels, Recoveries, & Other D] Serega da:
I admit that that this firmware has a problem with restarting the phone on 30-40% of the battery. In any case, will you get root by means of a Majisk or not.

2. Problems with Bluetooth I've experienced it too. But most likely, it's just a coincidence.

The Bluetooth icon she disappeared yesterday. An unexplained incident occurred. I reinstalled the firmware 3 times ! Different, all from this forum topic. And there have always been problems with a half-working Bluetooth (TV, even a neighbor's, another phone is visible, and the Huawei gt2 watch is not visible).

How can this be???

Bottom line: it is necessary to forcibly break the connection (in setting of watch) between Xiaomi and Huawei, and the Bluetooth icon appears! I don 't understand it !

Here is such a magical story. This firmware has no problems with bluetooth.

But problems with the battery do not allow you to install this firmware, in this state.
[Android Head-Units] KASPERJANI:
Hello!!

Any one know if i can update my car radio for newer android version?Thanks
[Android Head-Units] rigattoni:
Android 10 is for now the newest available firmware. Mostly all units wich are sold with Android 11 are fakes.
[Android Head-Units] KASPERJANI:
Ok,didn't knew that,thanks for your replay👍 the reason i wanted to update because headunit sometime glitching,another question,can i update same software somehow?Thanks
[Android Head-Units] rigattoni:
Ask the seller for updates, may be he has some.

What do you understand with "glitches"?

More information needed to help.

What does occur and when?
[Android Head-Units] KASPERJANI:
Sometimes screen goes black,but music still plays,then i need to disconnect it from power to get screen back on
[Android Head-Units] rigattoni:
Do yourself a favor and install

View attachment 5787037

Monitor the CPU temperature and if this goes up to 90°C you just have an overheating situation.

Check that for some time and report back if this is the reason.

In this case, have a look at the fix provided by @Ati_gangster in https://xdaforums.com/t/fan-mod-px5-px6.4074933/
[Android Head-Units] KASPERJANI:
Thank you very much!!!
[Android Head-Units] rigattoni:
The "Like-button" would be nice. ;)
[Android Head-Units] rigattoni:
By the way... If you open CPU monitor you have some buttons at the bottom.

View attachment 5787041

There you can activate a floating temp overlay on your screen to monitor easier, even if you are in any other app.
[Touch Diamond, MDA Compact IV ROM Development] promomail:
On the Kaiser the Manila Interface featured a convenient ICON names MPAS SEARCH that pulls up a search box linked to GOOGLE MAPS..This is not the same as Google Maps...Any idea on how to get the cab?