yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Xudong007:
[Oops this was accidetally posted in thread less fitting. Move it?]

The subject headline of this post might introduce an impossibility.

Xiaomi has lately made sure to sabotage any successful unlocking of the fastloader. (Which is consistent with manufacturing products tailored into spyware). In other words no custom rom in these cases.

Would the following attempts make any difference at all or is it just placebo:

- Use Shizuku/Canta: to delete almost every Xiaomi and Google component. Stripping it down to bare bones.

- Use Rethink: blocking all attempts for the last remaining functions trying to 'call home' + ProtonVPN for general reasons.

Does general cautiousness matter? Like using privacy centered apps like Tor and Mull. And encrypted communication via Signal Messenger/Molly. And small tweaks like non gboard etc.

OK so here are my two questions:

1. Does the tweaks above improve anything at all in terms of privacy? If so, how much or how little? (Please explain. I'm sure many of us would like to know more).

2. Lastly and more importantly: Since rooting/flashing is not happening can you suggest something more/better/different/additional than what was been listed above?

Such a pitty that this fine hardware is so poisoned with surveillance-ware

.

Thank you!
[Nexus 7 (2013) Q&A] dawiddluzniak:
Hello, is it possible for the Asus Nexus LTE tablet that I use as an internet radio in the car to also work as a hands-free kit for the phone? Are there such programs or any USB adapters?
[Xiaomi Poco F6 / Redmi Turbo 3] katianiceto:
Onde posso obter o tema Harry Potter do recém-lançado Redmi Turbo 3.
[Xiaomi Poco F6 / Redmi Turbo 3] Badger50:
Greetings, and welcome to XDA. As a friendly FYI, you stand a much better chance of having your questions answered in a timely manner by simply abiding by XDA Rule #4:

Spoiler content hidden.

Which is why I have translated your thread title and post.

Your cooperation is appreciated and expected. Thank you, and have a great day.

-Regards: Badger50
[Nokia 3 Questions & Answers] OtherVlzxr:
So i tried booting into recovery doesn't work after 10 seconds it reboots and tries to boot up but fails windows doesn't recognize what can i do?

View attachment 6092326
[Nokia 3 Questions & Answers] OtherVlzxr:
So i managed to get it to fastboot for now...
[Nokia 3 Questions & Answers] polygonjuggler:
I have the exact same problem. Trying to solve it I have tried almost anything I know and everything I've found online to no avail.

Device: Nokia 3 TA-1020

OS version: Android 9 Pie

Build Number: 00WW_5_180_SP04

How this happened and what I've done so far:

I found out that it is not exactly "Stuck". I discovered this by accident:

If I'm patient enough to wait on that screen for over 10 minutes it eventually continues to the Nokia Logo, and after another couple of minutes, it starts the UI. But even then it is extremely slow at times, system apps like quicksteps, for example, crash frequently and randomly.

All this happened after I rooted the device with Magisk and a couple of days later decided to unroot it because everything worked great except for YouTube, and any other video player on websites which all showed a green screen. Only VLC worked, after changing some of its default settings.

Before uninstalling Magisk I tried the Revanced Magisk module, intending to solve the Youtube/Videos problem (which I know is related to the security/copyright policies and methods Android uses including DRM protection, Widevine, and such). But after doing so Youtube Revanced kept crashing every time I tried to open it.

I disabled the Revanced module and deleted it from Magisk, then I restarted the device but the Youtube app kept crashing, so I uninstalled it (it goes back to the stock version) from PlayStore and Installed it (Updated it) again. Same results as before, it was for some reason corrupted or simply not working.

I Tried installing the Revanced manager apk and installing the Youtube Revanced app with the same previous results, so I decided to disable/delete all LSposed modules, did the same for all Magisk modules (Including LSposed), then uninstalled Magisk to unroot and tried to start over from scratch. But before trying to root again I decided to do a factory reset to have a clean slate to work with, after checking I had no root, nor root apps installed. And this is when I got that Android Logo "Stuck".

I've tried clearing the cache (from recovery mode), flashing the boot.img and recovery.img in case they got corrupted somehow, but same thing: Android Logo showing Orange state for over 10 minutes, and each time it starts the UI it is extremely slow, and random apps keep on crashing making it unusable. (I also did another Factory Reset from the Recovery mode, after clearing the cache once more).

And if I try using the Factory reset option inside the UI, once again (I know it's dumb, but I'm desperate haha) It does it but very very slowly, and after a lot of time and patience it finally restores itself to "Factory" settings. But nothing changes: 10+ minutes of Android logo and unstable, slow IU.

Is there a Stock ROM that I could use since it looks like something on my stock root is corrupted?

Is there any custom ROM that could "fix" this issue? would installing (flashing) TWRP recovery help in any way?

P.S. I can boot into fastboot or recovery mode without a problem, and sometimes I can even use adb if the UI doesn't crash first.

Any help would be greatly appreciated!
[Nokia 3 Questions & Answers] mvikrant97:
Use SP Flash tool V5.2136 and flash the stock ROM in BROM mode. Don't use Format All option in SP Flash Tool.

SP Flash Tool v5.2136 for Windows - MediaTek Flash Tool

Download SP Flash Tool v5.2136 to flash or install Stock Firmware ROM (Flash File) on the devices powered by Mediatek Chipset.

spflashtools.com

Firmware Link

Nokia_3_TA-1032_MT6737M_00WW_3_380_290618_8.0.zip

drive.google.com
[Nokia 3 Questions & Answers] polygonjuggler:
Will this work as well for the Android 2 TA-1020 on Android 9 Build Number: 00WW_5_180_SP04?
[Nokia 3 Questions & Answers] mvikrant97:
Yes it will work.
[Nokia 3 Questions & Answers] polygonjuggler:
Thank you so much! I will try it right away, and report if it solved the issue so it can help others with the same problem on the Nokia 3 and Android 9.
[Nokia 3 Questions & Answers] mvikrant97:
the firmware that I shared with you is for Android 8
[Nokia 3 Questions & Answers] polygonjuggler:
oh ok, but it can replace android 9 and then I could update, right? One more thing and sorry to bother but I've googled, and searched here on XDA and can't get my device into BROM mode.

I Have Tried the following:

- Phone Off and connected to USB cable (Only on its side), then press Volume Down, then connect USB cable to PC, and wait for BROM

- Phone Off and connected to USB cable (Only on its side), then press Volume Up and Down at the same time, then connect USB cable to PC, and wait for BROM

- Phone Off and connected to USB cable (Only on its side), then press Volume Up, then connect USB cable to PC, and wait for BROM

None of the above got me into BROM mode :( Or at least It doesn't look like it. What I get is the same Android logo in Orange state shown by the OP, but if I disconnect the USB cable instead of continuing the boot 10+ minute boot process it just turns off. May this be a BROM mode for this "Stuck" device?

Am I missing something? Hope you can help!
[Nokia 3 Questions & Answers] mvikrant97:
Check the drivers for Mediatek in your PC.
[Nokia 3 Questions & Answers] polygonjuggler:
OK, I'll try that. I'll reinstall them to check if mine were old ones. Thanks for your help and patience!
[Nokia 3 Questions & Answers] polygonjuggler:
Hello again, well, I uninstalled the drivers, installed the latest drivers and tried to boot into BROM mode which I believe that in my device should be as simple as pressing the Volume down and then connect to PC .

The device manager shows the Mediatek USB device for a couple of seconds, then changes to the Mediatek preloader for another couple of seconds, and then disappears from ports devices. After that, the phone screen shows the infamous powered by Android (Orange state your bootloader was unlocked bla bla bla....

Any ideas? :-(
[Nokia 3 Questions & Answers] mvikrant97:
Add lib usb filter for Mediatek Drivers. I have written instructions for another device here >>

View attachment 6103324
[Nokia 3 Questions & Answers] polygonjuggler:
Thanks again for your kind help, and super fast response.

I'll do just that! I appreciate your patience!
[Nokia 3 Questions & Answers] polygonjuggler:
Did it, had to try several times to be fast enough but I finally was able to select the Mediatek USB port device and click on install, it did say: Successfully installed for Mediatek USB Port...... And one second later it disappeared. I restarted the PC and tried to boot to BROM to no avail, I keep on getting the Mediatek USB port connected in the device manager but seconds later dissapearing only to show the Mediatek Preloader which then also disappears, and the phone's screen shows the Android Logo once more.

Do you have any other ideas?

Have you ever tried the MTK Client crash to preloader option? do you think it would work? is it safe? (I know nothing is really safe when messing around with rooting, flashing ROMS, etc, but at least reasonably safe, haha)
[Nokia 3 Questions & Answers] mvikrant97:
Please add filter for Mediatek Preloader port in lib usb.

To connect in Mediatek Preloader mode just connect the phone without pressing any keys.
[Nokia 3 Questions & Answers] polygonjuggler:
Weird (or not, I really don't know), I did as you asked, after successfully installing the filter to the preloader and restarting Windows, now IF I connect the phone to the PC without pressing any keys I get the Mediatek USB Port (COM4) as a connected port in "Ports" (Device Manager) and it stays stable in there, but to check if the phone is "recognized I opened MTKClient and it says: Phone detected, and Status: waiting for connection.

Mediatek USB Port stays somewhat stable with a few disconnections every minute or so and reappears soon after. As far as I know this USB cable is ok, when I reboot to fastboot it seems to never disconnect. But can't bet my life on it, of course.

I just tried pressing the Volume Down key and connecting to PC and I get the same result: mostly Stable Mediatek USB Port showing on Device Manager, and on MTKClient v2.0 Phone detected and Status waiting for connection.

All this while on the phone the screen is completely black, with no message whatsoever. And some random disconnects and reappearances of the Mediatek USB Port. Could I be right know in BROM? could I trust this somewhat unstable connection, or would you suggest something else or buying tomorrow a new USB cable?

One thing I think is worth noting is that if I remember correctly The device Manager should show Mediatek USB Port (and a number or device code) But it just shows (COM4), and I tried checking for connected devices with the command:

adb devices

And it shows no devices connected. So I think I am still unable to connect in BROM mode :-(

I hope you have more ideas, but either way thanks for letting me get to this point!
[Nokia 3 Questions & Answers] mvikrant97:
mtk client does not supports Nokia 3

@IsHacker003

I correct myself, mtk client does supports Nokia 3 but I was unable to unlock bootloader using mtk client.

Please use the SP Flash tool to flash your device.

Wait I will write a fresh new tutorial on the forum.
[Nokia 3 Questions & Answers] polygonjuggler:
Thank you, bro! As of today the phone has a black screen and can't get turned on, at least not showing any logo, just a black screen. It was charging overnight, to discard a low battery issue, but nothing changed I still get the black screen not responding to any button, even very long presses. I don't know if it is completely dead or not, but it still shows up in the device manager as a Mediatek USB port (COM4) as soon as I connect it to the PC.

Since my budget is quite low at the moment, I'm thinking about buying a Xiaomi Redmi A2 (new), or a refurbished Pixel 2XL or 3XL so I'm not disconnected from the world while I keep on trying to revive the Nokia 3 (which is pretty old, but looks new and I'm quite used to it). Any thoughts on Xiaomi A2 vs Pixel 2 or 3?

​
[Nokia 3 Questions & Answers] IsHacker:
This whole thing happened because you flashed custom image with locked bootloader. And yes, mtkclient supports ALL mediatek devices with BROM mode, including Nokia 3. Btw this thread has links for Android 9 stock rom:

NOKIA 3 TA-1032 HEART STOCK ROM ANDROID 9

I HAVE LITERALLY TRIED EVERY SINGLE GOOGLE URL, DOWNLOADED MANYYYYYYYYYYY FILES AND NOT A SINGLE ONE WORKED FOR MY NOKIA 3 TA-1032 HEART !!!!!!!!!!!! DOES SOMEONE HAVE A LINK THAT DOES WORK

xdaforums.com

You can even unlock your bootloader using mtkclient, I did it myself on my Nokia 3 ta-1032. Don't buy a new phone, the Nokia 3 is actually quite fast for normal usage, I'm currently using it as my primary phone.

I should have noticed this thread before, I think it's too late....
[Android Apps and Games] alinpha:
Hey all, I'd like to introduce a note taking app with home screen widget and sync across Android devices - WeeNote.

WeeNote Notes and Widget - Apps on Google Play

Notes organizer reminders memo app with sync and home screen widget

play.google.com

View attachment 6092327

The app allows to manage notes with various customization options, such as setting any color to the notes, setting own image as a note background, using custom fonts, drawing, adding icons, arranging notes in a folders system, and much more.

The recent update version 6 includes a flexible layout settings that allows users to pick notes scroll direction and showing folders contents simultaneously, which could be used for storyboarding.

Any opinion would be highly appreciated, as the recent update showed that users dislike the new app icon, which I personally like very much, but the goal overall is to give the users one good product.

View attachment 6092328

WeeNote Notes and Widget - Apps on Google Play

Notes organizer reminders memo app with sync and home screen widget

play.google.com
[Samsung Galaxy S7 Edge Questions and Answers] w1zard (S7 EDGE):
Hello, I have an S7 EDGE and I recently installed Miui 12 "GSI ROM" and from time to time the device slows down a bit and reboots. Really beautifying the ROM, providing animations but the content of the Random Reboot Problem Is There a Solution to This?
[LG V40 Questions & Answers] comm-ents:
I am trying to find a version that supports LG V40 Verizon model with Android 10.
[OnePlus 12] Nightmare0:
This is based on Canuck Knarf's method. I have converted the script so it is now compatible with macOS (theoretically also works on Linux). Now I have the script ready to flash. Tested. It's all good on my phone

You are required to install the android-platform-tools by using Homebrew on macOS (apt or yum on Linux).

Download the corresponding firmware and unzip it.

Create an arbitrary folder, and in this fold, move the flash file here (remember to unzip). Also, you need to create an FTH folder here. The images files should be copied to the FTH folder.

Also, this tool added an option to delete "-cow" temporary partitions (Highly recommended), of course, you can choose not to remove them.

View attachment 6092329
[Nothing Phone 2] Slim K:
I want to buy this phone for personal usage, however, I need to know If this device supports Re-locking the Bootloader on a custom AVB key. The goal is/always was to build my own AOSP/ROM and re-lock the Bootloader on it using my own private keys/pkmd.bin. If you don't know what I'm talking about, see Device States and Verified Boot 2.0.

I already have a Pixel 6 pro and a Fairphone 4 locked using the above methods, since these devices support it out of the box. I wanted however a newer device with better specs, I arrived at this device with the logic of OnePlus > Nothing (OnePlus devices used to support it as well up until it was acquired by OPPO/before OnePlus 9)

If you want to help me, use root in a terminal or check the EDL package you have for a parition called: avb_custom_key. If it is there, then let me know please, Thank you!! :)
[Nothing Phone 2] V0latyle:
Just curious, why do you want to lock the bootloader on a custom key? This can be dangerous if you're rooted, and aside from software security on a custom OS such as CalyxOS/GrapheneOS, doesn't have much use as your device will still fail hardware backed attestation.
[Nothing Phone 2] Slim K:
Locking the Bootloader is not just a software security measure, it is a hardware-backed measure, since the keys will be stored in Tamper-hardened storage, preventing anyone with physical access the ability to mess around my device. An Unlocked device is inherently unsecure going by the Boot chain sequence android uses.

CalyxOS/GrapheneOS are just using the natural Boot flow that google has designed along with their OS, in fact, GrapheneOS is only available for Pixel devices for this very reason. (and many other requirements, but I and many security focused people share the same views on this matter).

If I wanted to root my device while locking the bootloader, there are many ways to achieve this, see avbroot. AVBroot is meant to patch the existing built ROM for such functionality, but you can use KernelSU as part of your ROM build as well without using the patch. The danger of using root can be easily migitated by leaving OEM unlocking turned on. Sure you may lose your data, but that's a calculated risk I'm willing to take.

Fail hardware backed attestation for GOOGLE SERVICES, which I do not use anyways. I have been on the Internet for longer than 25 years. Never used a google service in seriousness nor do I intend to do that. They do build cool hardware and make a very decent Mobile OS (which is thankfully open source), but that's about it.
[Nothing Phone 2] dlads:
Give it a go and find out mate.. you seem to know more than most about it.

Personally I wouldn't but that's me, plus I've lived Google free and am security conscious but honestly it's a massive ball ache... The convenience + my age and ever growing lack of patience means it would be too much of a pain for me but I am curious.. especially having root and the additional features that root can provide.. with a locked bootloader.

Definitely interesting although had no idea if it was possible. 👍🏼
[Nothing Phone 2] Slim K:
Yeah, about that..... I do not own a nothing phone 2. I don't want to buy this phone if it doesn't have it. Which is why I'm asking here if anyone can check for the existence of the partition named: avb_custom_key as part of the default partition table for the device, which will mean that the people from nothing added this feature as part of the Bootloader (not all phones have it)

Can you please check for me if it exists on your device? you can do that by checking for it in /dev/block/by-name in custom recovery or in a root explorer (or terminal)
[Nothing Phone 2] V0latyle:
If you leave OEM Unlocking on, you're defeating the purpose of this:

Because someone with physical access could then unlock the bootloader. Your data would be protected because of the mandatory data wipe, but they could then do whatever they wanted to it. As long as OEM Unlocking is enabled, the "safety" is off.
[Nothing Phone 2] dlads:
Nah don't think so mate, unless it's called something else.

There's keymaster a and b and keystore? But no custom key

View attachment 6092399
[Nothing Phone 2] Slim K:
Yeah it means it doesn't support custom keys, so i won't be getting this device then. Thanks for the help though, very much appreciated:)
[Nothing Phone 2] Slim K:
Oh I never said or meant that I root my devices. I just wanted to show the *possiblity* that it could be done, even with turning off OEM unlocking. Besides, If an attacker has your phone, All he really wants out of "your" specific phone is your data, If not, he could simply replace the motherboard or exchange/unsoldier/replace the memory chip and bam!!! they have a new device.

Also, on the topic of rooting. I find it to be a very weak solution to mostly trivial problems. Most of what you can achieve/want with root, you can make it work without breaking android Security Philosophies to do. Take for example: Adaway, you can simple build it along with your ROM, granting it the correct SELinux contexts and appropriate permissions to access /system/etc/hosts, in the process making it work without Root. Similar modifications to your phone can be packaged this way as well. Rooting android phones came to be because you didn't have the source for the existing pre-bundled Factory ROM that came with your device, so you resort to "patching" modifications. This of course won't be necessary if you're building The entire ROM yourself.;)
[Nothing Phone 2] dlads:
How would you add additional app if the apps that would otherwise require root access are already "part" of the newly created factory ROM?

How would you use magisk modules?

I haven't seen very many ROMs that would tick all the boxes plus I think theres so much more to it than what you've stated, tbh I don't think I've ever seen a ROM that has apps that require root working in them.

But tbh it doesn't really matter, I've been rooting my phones since the G1 and will continue to do so until they stop allowing it, I've never had a security breach, never been hacked, lost my data or had the alarm not go off.

So as interesting as your suggestion is, I think I'll stick with magisk and it's modules, the apps I have come to like and the ROMs that I like to try from time to time, rooting has given more to Android and it's community than any other 3rd party modification, it is what it is today because of the enthusiasts that made it and use it, so weak is not a word I'd choose to use, it's actually disrespectful imho.

Either way, good luck on the Pixel.
[Nothing Phone 2] V0latyle:
Eh, to each their own. I was just wondering what your reasoning was. As for your original question, I would honestly be surprised if the Nothing didn't support a custom AVB key. Disabling OEM Unlocking after locking the bootloader would be the safest option, but you'd need to make sure your build has ro.oem_unlock_supported and sys.oem_unlocking_allowed must both be 1 so that you can re-enable the toggle once disabled. I believe you can omit the last one because it's generally used on permissive devices that check IMEI whitelists to determine whether OEM Unlocking should be available.

I honestly don't use root for much aside from Magisk modules, but since I'm on the stock Pixel firmware, I don't have AdAway built in. I haven't the first clue how to build a ROM so I just stick with what I know