u/HTC_Beaups

Neither Chinese nor Taiwanese.

Doesn't matter, considering neither Chinese nor Taiwanese are considered "race"s. Keep digging.

And you would still be incorrect.

He is Taiwanese, not Chinese.

He's not Chinese.

If you'd like to experience Dublin, Tucci's for a nice meal in a classic place (and its the best food in Dublin) or Vaso for some tapas in a new and modern (too new and modern?) more urban feel. If you venture into the short north, Hubbard Grill and Marcela's are both excellent for somewhat casual (the shrimp/shortrib appetizer and brussel sprouts are seriously phenomenal @ Hubbard). Want to step it up a notch? Go to M.

​

--beaups

I don't know how I can make this any clearer. There are a TON of commands in the eMMC firmware that specifically, and individually, allow you to bypass several specification-defined security features. Backdoors, plain and simple, no matter how bad you want them to not be. There are several reasons your "safe mode" analogy (its not even a metaphor) is ridiculous.

The subject "device" is the eMMC. Samsung placed secret codes/commands in the firmware to allow "them" to be able to do things that are supposed to be locked out, both for security and per the eMMC specification. Just because you don't know what a backdoor is, doesn't mean its not a backdoor.

To be more clear, it is most definitely intentional, as are the read/write/execute commands they had to publicly release, and the ~25 additional vendor codes I was able to reverse. I breezed over the comparisons required to complete the necessary branch, because it's boring to explain a bunch of compiler optimizations. But it is certainly not an unintended feature.

edit: clarification

um, this vuln is the very definition of a backdoor.

I probably have the fewest, at somewhere around 40 (would need to count). I was loving my 14x until I shattered the screen a few months ago. Then switched back to my m8, which I shattered two days later. My damn m9 that I'm using now won't shatter :/

It's certainly a lot easier to permanently ruin an s-off device vs. a device that's only bootloader unlocked. That said, it seems a majority of those bricks come from people flashing things, making edits, etc using tools/roms made for other devices. Some sanity checks in rom flashing checks and using /dev/block/....../by-name/.... instead of hardcoding partition #'s would probably prevent 90% of the bricks we see.

^bingo. My nick is loosely based on my (french) last name.

I run stock, and typically unrooted on the phones I use on a daily basis. On occasion, I'll unlock the bootloader if I want to tweak/patch anything kernel side.

We spend most of our time on HTC. Sometimes we get bored and research/add support for other devices.

we support 4.4.4 and 5.x on the '14x. It's a very different device vs the '13x.

like ropes, but with a b

However many fit in the drawer of a fairly large end table. My favorite was a month or so ago, was working on "something", made a couple tweaks, and it bricked the device (htc e9+ if you care). So I sent the binary I was working on to jcase - "hey, this bricked my e9+ but I don't see how/why. Can you try it on your e9+?". You can only imagine how this story ended.

In current form, probably not. Maybe we'll take another look at the 13. There's just too many devices and not enough time :/

When it works.

Yes, of course. Apps in the store could contain exploits to obtain root. Depending on the nature of the exploit, it may not need any "odd" permissions. Once it's escalated to root, the permission model is irrelevant.

It sounds like a major inconvenience to users, and thus I see people working to bypass it. But I'll reserve final judgement until official release.

moar s-off's

Yay, more HTC devices. I could use a few more research devices. Shall we give out SunShine codes to the winners?

hah, FYF!

oh yeah, that :P