ubfx

@none24smu pajeet

The task manager and app window handling also almost perfect 🤏 on the Surface Duo 1 running Android 16 (LineageOS 23.2) again this is not a GSI. #Android #Microsoft #SurfaceDuo

+++ BREAKING +++ Under the leadership of @sanchezcastejon, 🇪🇸 Spain deployed 🇩🇪 German deportation expert Lt. Reiner Winkler to counter the ongoing migration crisis.

@NTDEV_ genuinely hoping ur LLM screws up and ur ufs luns are corrupted

Problem solved! Now we can see all the partitions and write to them! Will add some safeguards so that we don't make catastrophic mistakes with the disk😆

this is so fucking sad

Erstes Video des zweiten Attentäters Raynor Wallout aufgetaucht

Ich bin mir noch nicht sicher, was ich von den neuen Euro-Banknoten halten soll.

@eepyeri @NTDEV_ He will, loves stealing patches and only listening to his shitty llm agent. he isn’t learning shit also he’ll stay on one core forever with stock fw from samsung tbf he can remove nearly everything from his list

@NTDEV_ hopefully you dont destroy your ufs content

Getting close to UFS access!

Oh wow, remember the usbliter8 BootROM exploit that Paradigm Shift published about? Magnet Forensics (the GrayKey guys) allege that (1) Magnet products were exploiting it ITW(!) and (2) a former employee who went to work for Paradigm Shift leaked the details to them! 🤯

@AlfinCodes @devXritesh it's a digitizer

@devXritesh I'm also thinking about this, how is this even possible?

Now I finally know why Apple's screens are so expensive

@CtrlAltCuteness @catto34_ tripping knox is not related at all with entering recovery. recovery/fb handling is done within the bootloader which scans what current button is pressed and boots accordingly.

@catto34_ Not all devices are forced to use the same exact way to enter into recovery mode. Samsung's devices actually go and short a little wire / fuse wirhin the phone when you enter into anything other than the OS.

ok apparently I am just stupid and I’ve been holding volume up. its power button + home + volume DOWN to get into android recovery mode.

@Entroprox while yes this is remote desktop, exploits still exist.

They locked the bootloader bro 😭, this is remote desktop connection

@DrJVoices @ibay770 @NTDEV_ we already have it

@ibay770 @NTDEV_ And here github.com/Project-Silici…

Would you look at that: touchscreen now works!

@CuriousBURR @NTDEV_ because it's fucking ai slop

@NTDEV_ Done in less than 24 hours. Damn you're insane, in a good way

@Virusey12 @telegram Then it looks like education has brought you nothing if you believe that is a vulnerability

@Dan50798734 @telegram Brh am a CSE grad and ik what a vulnerability looks like when I see one

🚨 URGENT: Do you use Telegram on your PC? Read this. 🚨 @telegram this should be looked at immediately!!!!! ​A dangerous new hacking method called "Session Hijacking" is putting desktop accounts at massive risk. ​📂 The Exploit: Hackers are stealing the tdata folder from your PC. 🔓 The Result: They paste it on their computer and get full access to your account. 👻 The Catch: You CANNOT see them in your "Devices" settings. Because the session is duplicated, they are completely invisible to you. ​Everyone needs to take extra care right now with the files you download. We are calling on the @telegram team to patch this immediately and protect users. @Eyuel88 @pozlanX @s0meone_u_know @Showy005 @tonhornofafrica @WebOpenWorld ​Please RT to warn your network! Stay safe out there. 🛡️ ​#Telegram #SecurityAlert #TechNews

@Virusey12 @telegram first learn what an exploit really is

@Dan50798734 @telegram Yes but why is this kind of exploit sitting there for the hackers, Dont you think this should be fixed?

@NTDEV_ Feel free to give up your garbage LLM slop, PE already booted on the Exynos S9.

Oh no my PC/Device needs to be repaired😢

@halal_beef_ @NTDEV_ @NTDEV_ and just so you know, with AI you will likely never find out the issue with samsung devices booting woa :) it takes effort to get somewhere, also expecting donations for your llm garbage is rather stupid

@NTDEV_ woa booted on the Galaxy S20, Exynos990 ;)

@zippgod24 If it mentions "early 2020" then it's using CVE-2021-30327. We're still yet to see a retail kona chipset with this bug. SM8150-AA is affected, hard to exploit. About samsung, they're likely using the houston (CVE-2024-56426) exploit.

@Dan50798734 So then what’s your best guess

Samsung S20/S20+/S20 Ultra, leveraging a bootrom vulnerability in the Qualcomm SM8250 (Snapdragon 865 “Kona”) chipset anyone happen to know which they might be referring to maybe this CVE-2026-25262 ? Anyone have any idea