yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Pain-N-Panic:
So I began the next step. I think I may easiest method here is to modify AOSP mods so the "hide fingerprint background circle" mod when activated adds a custom FP image. I've decompiled the AOSP Mods APK and found the string "remove_fingerprint_background". Now I just need to find which overlay APK is responsible for the mod itself. I'm having difficulty doing this as there's a lot.

I'm curious, is there a logger with root privileges I can run in the background while I activate and deactivate the fingerprint mod which will produce a logcat that will give me some more insight as to which overlay APK is being used to hide the fingerprint background?
[Google Pixel 7 Pro] craigacgomez:
Maybe this will help you dig further. The fingerprint icon is part of the SystemUI (or SystemUIGoogle). The assets are part of the SystemUI (or SystemUIGoogle) apk. Look at the keyguard section of the SystemUI code to figure out what needs to be done.

packages/SystemUI/src/com/android/keyguard - platform/frameworks/base - Git at Google

packages/SystemUI/src/com/android/keyguard/LockIconView.java - platform/frameworks/base - Git at Google

packages/SystemUI/src/com/android/keyguard/LockIconViewController.java - platform/frameworks/base - Git at Google
[Google Pixel 7 Pro] siavash79:
It's an open source software. Instead of decompilation you can directly explore the source
[Google Pixel 7 Pro] Pain-N-Panic:
Guess I should have checked the GitHub page lol thanks
[Google Pixel 7 Pro] K1nsey6:
I thought Google camera was supposed to be top quality. The picture showing in the view finder looks like its got a brownish/grayish filter over it with colors washed out, and the display keeps dimming with Adaptative brightness off. Often the picture looks blurry. Coming from OnePlus it's a very disappointing camera.

Update: Turns out I have a bad unit. After comparing camera quality to other Pixel 7 Pro, the difference is incredible. RMA back to Google
[Google Pixel 7 Pro] EtherealRemnant:
Sounds like your phone is defective because my OnePlus 9 was the most disappointing camera I have had since my HTC Mogul. I have yet to be disappointed with a picture from my 7 Pro.
[Google Pixel 7 Pro] K1nsey6:
Im leaning towards defective too. Im about to factory reset to see if that clears it up. It only seems to be the front camera, rear is good
[Google Pixel 7 Pro] zat0x:
The biggest thing i dont like about this camera is the extreme oversharpening wich destroys the image
[Google Pixel 7 Pro] whatsisnametake2:
yes, processing is up a notch since the 6. also the 7p tele is a downgrade from the 6. it's a shame. I use the tele on the 6 loads and love it. I don't think I can give it up for the 7 tele.
[Google Chromecast] backball:
I'm using Home Assistant (home-assistant.io) as my home automation controller and there's a great integration for the Google Chromecast with Google TV.

The issue is the device needs to run Android 9. Mine is on Android 10 which introduced a security policy SELinux and stops a command I need from running.

So the only way to get this to work is to go back to Android 9.

I have no idea how to do that or whether it's possible in the first place.

I have read of ADB (android developer bridge) which lets you access the console. Do I need to unlock the bootloader? Where would I get the relevant Android 9 image? Pretty much lost on what to do and would appreciate any help. Txs
[OnePlus Nord 2 5G] Petitoto:
Hey,

I've recently updated my Nord 2 from A21 to C10. Phone was unlocked and rooted, so after having reflashed the original boot.img, I forced the installation of the official OTA through TWRP. I had to set ro.commonsoft.ota=OP515BL1 to make it work. After the installation, TWRP failed to mount /system, but that didn't surprised me. I checked that the boot partition has been well flashed.

Now every time I try to power on the phone, it directly tries to run into recovery mode. However it fails and start again and again...

Maybe the system tries to install the OTA using the original recovery, which of course fails, and because of an unknown reason, it doesn't reboot to system.

Because of the last update, fastboot is not accessible anymore using vol -, and BROM mode is not accessible using vol + / vol -.

I tried to crash the preloader using mtkclient but it didn't work.

I tried to use META mode to switch to fastboot, but preloader only answers "READY" (instead of "READYTOOBTSAF"), and nothing changes.

I try to reverse engineer preloader and lk but it's something new for me. META mode code is still present in the preloader, so I don't understand what's wrong with it. Maybe disabled by default on USB...

Does anyone has a solution to boot into BROM mode or make META mode work ?

Or maybe I could find DA authentication files somewhere ?
[OnePlus Nord 2 5G] Beanow:
@Petitoto can you share a bit about how you got the meta command running?

I'm in a similar situation with a Nord 2T. While mtkclient can get some info out of the preloader, meta never seems to connect.

mtk gettargetconfig

Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Device detected :)
Preloader - CPU: MT6893(Dimensity 1200)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x950
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Main - Getting target info...
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False

mtk meta FASTBOOT

META - Status: Waiting for PreLoader VCOM, please connect mobile

META - Hint:

Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.

...........

META - Hint:

Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.

...........

META - Hint:

Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.
[OnePlus Nord 2 5G] Petitoto:
Hey @Beanow,

I have the same gettargetconfig output, which indicates that the phone is not in BROM mode but stuck in preloader. Trying to interact with the preloader always lead to error because of the DAA (DAA_SIG_VERIFY_FAILED for example).

I have the same issue with mtkclient and meta mode. You can use the following modified mtk-bootseq.py:

py mtk-bootseq.py FASTBOOT COMXX (or python3 mtk-bootseq.py FASTBOOT /dev/ttyACMXX on linux).

import sys
import time
from serial import Serial

BOOTSEQ = bytes(sys.argv[1], "ascii")
DEVICE = sys.argv[2]
CONFIRM = b"READY" + BOOTSEQ[::-1]

while True:
try:
s = Serial(DEVICE, 115200, timeout=0.1)
print(".\n[+] Device detected")
break
except OSError as e:
sys.stdout.write("."); sys.stdout.flush()
time.sleep(0.1)

print("<-", s.read(256))

def send(bytes):
s.write(bytes)
print("->", str(bytes))
resp = s.read(256)
print("<-", str(resp))
return resp

resp = b''
while resp != CONFIRM:
resp = send(BOOTSEQ)

print("[+] Boot sequence sent")

On another device, it works and I get:

...............................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READYTOOBTSAF'
[+] Boot sequence sent

However, on my Nord 2, I get:

...........................................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READY'
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''

Then the next s.write() is hanging.

I get the same result for any other boot mode. However, the code is still present in the preloader.

I unfolded my phone to try to find a test point. I tried all golden points but I only found:

- a point which loads preloader (and not BROM...) in the same way vol + / - do (in red in the picture)

- a point which boots the phone but without Android and OnePlus pictures (what's that ??) (in green)

View attachment 5737397

I don't know how test point is handled: if that's the role of preloader, it may have been disabled by the update (as the BROM and fastboot). We may need to find the DAT0 point of the eMMC to short it and prevent the BROM to find the preloader, making it to go in EDL mode. However, I think that this point isn't exposed, and I won't disassemble my phone further without beeing sure of success...
[OnePlus Nord 2 5G] Beanow:
Thank you so much for the work so far!

Unfortunately I get no response at all on the Nord 2T.

.......................................
[+] Device detected
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
Traceback (most recent call last):
File "/media/droid-work/mtkclient/mtk-bootseq.py", line 31, in <module>
resp = send(BOOTSEQ)
File "/media/droid-work/mtkclient/mtk-bootseq.py", line 24, in send
resp = s.read(256)
File "/usr/lib/python3.10/site-packages/pyserial-3.5-py3.10.egg/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

How did you connect to the device that you're getting these responses?

In my case, I need to use vol+, vol- and power, like mtkclient, or the ttyACM0 won't exist.

(I've got udevadm monitor up, watching for the usb/tty to be added)
[OnePlus Nord 2 5G] Petitoto:
Indeed, you need to run into preloader using vol +, vol -

Maybe a driver / python module issue. I've got similar issues on my linux. Try on windows or try to reinstall drivers.

It should work at least for the first answer. Else it means that your preloader doesn't send any data, which is not the case as mtkclient works.
[OnePlus Nord 2 5G] Beanow:
I also tried a different baud, because a pl_lk log from oplusreserve2 partition suggested it may be used. No luck though. Note, this was a very old log I saved early on. Definitely not reflective of latest Nord 2T update.

[PLFM] boot_tag size = 0x0
BOOT_TAG_VERSION: 0
BOOT_REASON: 0
BOOT_MODE: 0
META_COM TYPE: 0
META_COM ID: 0
META_COM PORT: 285220864
META LOG DISABLE: 0
FAST META GPIO: 5906
LOG_COM PORT: 285220864
LOG_COM BAUD: 921600
LOG_COM EN: 1
LOG_COM SWITCH: 0
MEM_NUM: 2
MEM_SIZE: 0xAE7B
MEM_SIZE: 0xAE8D

I guess I'll try windows then :sick:
[OnePlus Nord 2 5G] Beanow:
python mtk-bootseq.py FASTBOOT COM4
...................................................................................................................................
[+] Device detected
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''

Windows looks to behave similar. Though windows wouldn't take the MTK VCOM driver, so this is win10 default serial, in a VM over USB passthrough.
[OnePlus Nord 2 5G] Beanow:
So, same result not in a VM. Though specifically with powershell I got the same output as you did.

...........................................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READY'
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
[OnePlus Nord 2 5G] Rokshana Roji:
This is really a helpfull post for us. I've already a oneplus nord 2 phn,from this post i know the more information about this phn.
[OnePlus Nord 2 5G] Rokshana Roji:
Thank you so much.
[OnePlus Nord 2 5G] Petitoto:
@Beanow So same results...

It's weird that it doesn't work on Linux. Maybe an issue related to pyserial or connection settings.

What's preventing the device to be detected by mtkclient is line 54 in mtkclient/Library/meta.py: and cdc.pid == 0x2000 should be removed. So you can try to switch to fastboot using mtkclient on Linux, but with my Nord2 I get the same results as mtk-bootseq.py on Windows
[OnePlus Nord 2 5G] roldev:
Thanks for this. No need to switch to windows anymore, to use mtk client.
[OnePlus Nord 2 5G] Beanow:
Is it 'not working' though? It's also weird to me that I had the same output as Linux using Windows' cmd, while there was READY spam in powershell. Same drivers, same python, same libraries, but different output?

I suspect that it might be a timing issue. Maybe the serial console doesn't care about or wait for input at all. And just spams READY a few times. It would be a matter of how fast the connection is established.

Perhaps as well there's a different subsystem sending commands to the 'meta' environment and the READY spam means it's processing those commands rather than whatever we're sending.

All theories, but I would find it really hard to believe there's a problem with Linux drivers / libraries for something as basic as a UART/serial console over USB.
[OnePlus Nord 2 5G] Beanow:
I also suspected this PID check and tried to log the else cases, but never reaches those for me.

So removing the check didn't help for mtkclients' meta commands.
[OnePlus Nord 2 5G] Petitoto:
Differents results when using cmd and powershell? 🤨 There is really no reason for that. Unless it's not the same Python environment, with different pyserial for eg. I have issues to run mtk-bootseq on Linux, but always the same output on Windows' cmd.

Maybe. On linux, I can get different results depending on baud rate, timeout (and luck?). If there is an issue related to the connection, it might explain why the preloader doesn't answer as expected. But as other commands (like mtk gettargetconfig, but also manually handshaking connections and gathering informations in pyserial) work well, I tend to think it's just disabled.

I don't really know how it works. The code is still present in the preloader. However this functionnality is not always enabled. Maybe reversing the preloader more or analysing the log you provided on Github might help to determine whether or not it is enabled. Moreover, even if we manage to switch to fastboot, if the bootloader has been fully disabled, we may face the issue of the preloader trying to run into a non existant fastboot. Maybe the FACTFACT mode may help to reset the device, but I don't really know a lot about this mode.

Once you removed this check, if you print the data sent by the preloader, you'll get the multiple "READY" like mtk-bootseq on Windows. Moreover, I can switch to fastboot using this command on another MTK device.
[OnePlus Nord 2 5G] hyperbasspro:
Dear Sir,

Do you have any method to recover my phone as the figure show?

Thank You
[OnePlus 8 Questions & Answers] Xryphon:
Been looking for a solution to convert this device to the global variant successfully with the modem working or to get Verizon to release the update. It's been one year since Android 12 has been released and it doesn't seem like OOS 12 is coming anytime soon, so if anyone knows how to get the modem working on the global variant, I'd be glad.
[OnePlus 8 Questions & Answers] FoxyDrew:
The hardware and kernel source are fundamentally different on the Verizon model. Even if you somehow got global firmware installed with working data, you'd have a lot of other bugs and glitches because the hardware isn't compatible with the Global OS.
[OnePlus 8 Questions & Answers] Thorin_Stone:
It works quite well. on the V model (that's what I have). but you need to back up your modem for data. It's best to reset to 11 factory. Then you can run ROMs that are OS 12.
[OnePlus 8 Questions & Answers] Sнаđошƒаӽ:
It works? That's awesome! Can you please share the link to the guide you followed to do it, pretty please?
[OnePlus 8 Questions & Answers] Xryphon:
I believe he means that you can run Android 12 ROMs, not custom ROMs, unless I misread?
[OnePlus 8 Questions & Answers] Thorin_Stone:
I did not use a specific guide. I have been rooting the phone for some time and found that I could flash os global using a fastboot flash ROM. If you root your phone and save the stock os the 11 modems you can replace it in the global rom.

I will correct myself and say that I don't remember for sure if global will work (for modem replacement) but you can get custom ROMs to work well with that method.

I would have to go back and sort through for the links or try again to be sure. But if you know what you're doing, it is pretty hard to brick the phone. So play around with other guides. (with your own risk and discretion involved).

You can even run android 13 on the V model( not good IMO. buggy).
[OnePlus 8 Questions & Answers] Mr Hassan:
Which rom u used?
[OnePlus 8 Questions & Answers] Thorin_Stone:
Deerpfest works for sure
[OnePlus 8 Questions & Answers] Mr Hassan:
I think stock rom u talk about
[OnePlus 8 Questions & Answers] Xryphon:
I don't think the stock Verizon modem works on the global ROM? Or did it work for you?
[OnePlus 8 Questions & Answers] Thorin_Stone:
Stock modem does not work. That is for sure. I've moved to the pixel 7 Pro so I won't be messing with the one plus anymore.
[Touch Pro, Fuze Accessories] lost_reaver:
DealExtreme has a Crystal Case for the TP for $1.99

Link: http://dealextreme.com/details.dx/sku.16786

They also have silicone cases starting at $2.19

Blue: http://dealextreme.com/details.dx/sku.16830

Pink: http://dealextreme.com/details.dx/sku.16831

Black: http://dealextreme.com/details.dx/sku.16828

White: http://dealextreme.com/details.dx/sku.16829

Smoke: http://dealextreme.com/details.dx/sku.16793
[Touch Pro, Fuze Accessories] elladb:
did someone tried it? how is it? can u post more pic?

10x
[Touch Pro, Fuze Accessories] lost_reaver:
I will be ordering 2, 1 for each of my fuzes once I get home. Will post pics once I get them. Which with DX that is usually about 2 weeks.
[Touch Pro, Fuze Accessories] rock5669:
WTF??? Is it just me or does it look like the silicone case are WAY to big for the touch pro? I can clearly see 1/8-inch of space in between the inside of the case and the side and top of the touch pro.

the plastic one also looks like it does not fit.

I was seconds away from ordering when i decided to double check which color I wanted and saw that.
[Touch Pro, Fuze Accessories] rock5669:
or is that a regular htc diamond in a case designed for htc touch pro??
[Touch Pro, Fuze Accessories] Zaiaku:
It's a seriously oversized case for it. Don't even go near this case.
[Touch Pro, Fuze Accessories] lost_reaver:
I don't know about you guys but it clearly see a cardboard cutout of the phone in the cases just like most manufacturers do to show what device it is for, but anyways I have 2 on the way and will update with pics as soon as I have them.
[Touch Pro, Fuze Accessories] lost_reaver:
Now with pics see post #1
[Touch Pro, Fuze Accessories] Ovrclck:
No problems sliding the keyboard out?
[Touch Pro, Fuze Accessories] lost_reaver:
Nope don't have any problem on any of the functions of the phone.
[Touch Pro, Fuze Accessories] know_fun:
in thanks lol its $2 i'll find change in my sofa to cover this

i'll post and see if i like it

and i just saw this

Step 1 (1-3 days): Products are collected from our suppliers.

Step 2 (<1 day): Order waits to get packaged.

Step 3 (1 day): Order is packaged.

Step 4 (10-13 days): Order is enroute via Hong Kong Post.
[Touch Pro, Fuze Accessories] rcll:
Yea Deal Extreme shipping is super slow..

But it makes sense since it comes from Hong Kong via their low cost post.

I ordered Wii screwdrivers from them and it took 15 days. Ordered an Xbox screwdriver set and it took 17 days.

Just don't be in a hurry when you order things from Hong Kong and you're fine.
[Touch Pro, Fuze Accessories] JstarLuvsTina:
i guess u get what u pay for..that thing looks horrid on a Fuze..

u can get a treo case if u cant find the one ur looking for in the intrim, or dont want to shell out too much for a Fuze case.

OR

cough up the $32 bucks and get the Body Glove looking At&t Fuze Case..i mean if u can spend $200 or $250 plus on a device u can shell out a few extra pesos to protect it.

Late,

Jstar
[Touch Pro, Fuze Accessories] jojorios:
I bought the black Silicone one when i first got my phone on ebay. Best 5 buck case I had ever bought. Yeah it feels cheap but protects it well. And real easy to work with the keyboard.
[Windows 10, 8, 7, XP etc.] MadManMaitland:
i need a key for windows 10 pro my laptop wont update without it can anyone help me out i also need to make it a dul boot wit hunbutu becase it just rock oyut with it nm
[Windows 10, 8, 7, XP etc.] ze7zez:
If Windows 10 works, it is very likely that the key is entered into UEFI. In that case, you don't need to know him. Dual boot will do ubuntu during installation.
[Windows 10, 8, 7, XP etc.] MadManMaitland:
It says I have pro with a home key what am I supposed to do
[Windows 10, 8, 7, XP etc.] ze7zez:
1.

Find your Windows product key - Microsoft Support

Learn how to find a Windows product key for activation, and when you'll use a digital license instead.

support.microsoft.com

2.

Upgrade Windows Home to Windows Pro - Microsoft Support

Learn how to upgrade from Windows 10 Home to Windows 10 Pro or Windows 11 Home to Windows 11 Pro, including how to use a valid product key or the Microsoft Store.

support.microsoft.com
[Windows 10, 8, 7, XP etc.] ianreesdavies:
Have mine....Win 10 pro key

W269N-WFGWX-YVC9B-4J6C9-T83GX
[Windows 10, 8, 7, XP etc.] ketogeno:
Try these https://sharetext.me/m67l9svaid

Windows edition upgrade - Windows Deployment

With Windows, you can quickly upgrade from one edition of Windows to another, provided the upgrade path is supported.

learn.microsoft.com
[Windows 10, 8, 7, XP etc.] Minionguyjpro:
Try to enter the key: 'W269N-WFGWX-YVC9B-4J6C9-T83GX'. This is the official Windows 10 Pro key, but it may install an unactivated version of Windows.
[Samsung Galaxy A7 (2018) Questions & Answers] Moe.n:
I decided to give this rom a try and I needed to flash TWRP but apparently it wasn’t the right version or something. But what happened is, before I flash twrp via Odin I don’t why I wasn’t able to enter download mode by pressing [VOL - and POWER]. I was able to do it through bootloader option in the standard recovery, so I did, but twrp didn’t run correctly, its home page shows glitches then the phone turns off and boot by it self again to the glitched twrp screen and keeps doing this over and over till the battery dies, and whatever I tried to press nothing happens, it’s like trying to wake a phone that doesn’t have any recovery or download mode.

Is there anything I can do?

I live in Damascus, Syria, so it’s impossible to reach samsung customers care because of the sanctions :/

Sorry for my bad English
[Samsung Galaxy A7 (2018) Questions & Answers] ze7zez:
Can you provide a link to the manual with which you flash TWRP?

Without that, it's hard to understand why you can't access download mode.
[Samsung Galaxy A7 (2018) Questions & Answers] Moe.n:
Actually I wasn’t able to enter download mode in the usual way [VOLdown and POWER]. I think this happened after the last firmware I used, I noticed something isnt right because It has so many bugs but I kept using it for a year because I was afraid to break the phone permanently. But now when I took the risk I entered download mode through bootloader option.

Here the twrp I tried to flash

https://xdaforums.com/t/recovery-root-twrp-3-2-3-1-galaxy-a7-2018-a750.3876798/
[Samsung Galaxy A7 (2018) Questions & Answers] ze7zez:
Why are you trying to start DOWNLOAD mode via two buttons VOL DOWN and POWER, when the TWRP flashing manual says to press three buttons?

1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)

Re-flash TWRP exactly as instructed but without RMM.