Database Users

ADB Not finding device or displaying an error

Just RUU'ed to the one flipz made (I guess) and neither the kitchen nor adb devices even see my phone or throw an error. Am I screwed?

sad part about this is it recognizes my moment right away

jerry43812 said:
sad part about this is it recognizes my moment right away
Click to expand...
Click to collapse
try RUU back to 1.5 not 2.1

thats what I RUU'ed to... 1.56.651.2 CL85027 release-keys

did you have anything other than the stock radio?

Here's my radio:
that should be baseband, right? 1.04.01.09.21

yea thats stock....hmm debuggings on right?

Yep, I've disabled it, then turned it on after I connect USB, I've had it enabled before i connect usb, i've had it disabled before connecting, and nothing at all.

you try fastboot while usb plugged in?...just had to do this to my boys phone then from there went to recovery and wiped everything and reflashed

how exactly do I do that?

jerry43812 said:
how exactly do I do that?
Click to expand...
Click to collapse
hold volume down and power at same time
then its somewhat like a recovery screen

aauussttiinn88 said:
hold volume down and power at same time
then its somewhat like a recovery screen
Click to expand...
Click to collapse
if thats all iw as supposed to do, is press and hold vol down + power at the same time, then check adb devices, then that didnt work either. this POS is about to go through my window.

jerry43812 said:
if thats all iw as supposed to do, is press and hold vol down + power at the same time, then check adb devices, then that didnt work either. this POS is about to go through my window.
Click to expand...
Click to collapse
did you wipe the device through it?

I RUU'ed over whatever was there, i got sick of playing with this phone and now every F-bomb you can imagine is dropping on this thing as we speak.

Can someone please help? Sitting here wasting time, clueless as to what to do here... I see other thread s with damn near 100 replies.

jerry43812 said:
I RUU'ed over whatever was there, i got sick of playing with this phone and now every F-bomb you can imagine is dropping on this thing as we speak.
Click to expand...
Click to collapse
Try this:
Type adb kill-server
Then type adb devices
See if your device shows up. If it does, everything should work at that point.

tkirton said:
Try this:
Type adb kill-server
Then type adb devices
See if your device shows up. If it does, everything should work at that point.
Click to expand...
Click to collapse
That doesn't worked. Probably did it 35 times while waiting for some help here.

Beginning to hate the Hero.

So, I dont get any help here? Thought this was supposed to be a community where we help each other. I know I've dealt out my fair share.

jerry43812 said:
So, I dont get any help here? Thought this was supposed to be a community where we help each other. I know I've dealt out my fair share.
Click to expand...
Click to collapse
The wireless carrier creates the RUU for the phone, not Flipzmode, myself, or anyone else.
Also, not sure it is resolved since this issue is posted in four threads with a bunch of people responding.
If it isn't resolved, try running this RUU from Sprint:
http://www.darktremor.com/files/RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

$50 if you can tell me how to unbrick i9000 without USB jig

Okay, so I bricked my phone trying to update it, and by all accounts I now need a USB jig to ressurect it.
The problem is I live in the middle of nowhere with no mail delivery, and have to drive almost an hour just to get to my Post Office box. I'm also not the most patient of people, and I need my phone.
I've ordered a USB jig, but it'll probably take at least a few days to reach me.
In the meantime, if you can figure out a way for me to revive my phone without the jig, and without ripping it open and soldering stuff, I will pay you $50 (via PayPal).
I fell like there must be a way. After all my Windows machine responds by trying to install some driver when I plug it in (SEC S5PC110 Test B/D).
I think that something is going on there, but it's just not showing anything on the screen to give me any clues. I've tried all manner of combinations of attempting to power it up, but with no result.
So what do you think? Are you up for a challenge? If you can crack it, before the jig arrives, I'll give you $50.

xtempore said:
I fell like there must be a way. After all my Windows machine responds by trying to install some driver when I plug it in (SEC S5PC110 Test B/D).
Click to expand...
Click to collapse
SEC S5PC110 TEST B/D
You have to use resurection software
http://forum.xda-developers.com/showthread.php?t=1330491

Man are you dump. We're a community and help each other, no reason to bribe someone. As the guy above me said, use unbrickable resurrector.

dark_knight35 said:
Man are you dump. We're a community and help each other, no reason to bribe someone. As the guy above me said, use unbrickable resurrector.
Click to expand...
Click to collapse
Resurrector requires soldering - I don't have the tools or skill to do that.
Offering money is not a "bribe" - it's an incentive.
"Dumb" is spelt with a silent "B", not a "P" - and actually refers to someone who cannot speak. Using it to refer to someone who is stupid is actually very stupid in itself - and spelling it incorrectly... enough said.

Try using odin...
Sent from my GT-S5830 using xda premium

Ok, can you get into download mode?

xtempore said:
Resurrector requires soldering - I don't have the tools or skill to do that.
Click to expand...
Click to collapse
soldering will depend on the mode your phone is currently in , find out first be following this link to download detector http://forum.xda-developers.com/showthread.php?t=1257434

Sorry. I should have been clearer in my original post.
By "bricked" I mean NOTHING shows on the screen. It is completely black. It's not stuck in download mode.
I don't have a Linux box so can't do any Linux things. I have a PC (Vista) and a Mac.
I don't have the equipment or skill to solder things.
And because of where I live, I don't have access to people who might have these things.

What happens if you connect your phone to your PC and run the batch file in this archive:
http://www.2shared.com/file/b_2EYcvS/adbDownload.html

xtempore said:
By "bricked" I mean NOTHING shows on the screen. It is completely black. It's not stuck in download mode.
Click to expand...
Click to collapse
Its currently in a test mode, and the only way to get it into download mode seems to be by what Adam Sandler had done....
anyway you can try the following ( which I doubtful about its success) , meant to get into download mode.
1) First remove Ext SD card and Sim card , also remove battery and reinsert Before any attempt.
IF you have ADB already installed on your PC
click on run and type cmd
now type:- adb reboot recovery or adb reboot download
phone will go into recovery mode or download mode as typed
2)
1. Take Battery out
2. Whilst putting battery in press Vol-Down+Power+Home button
Press the three buttons, and keep them pressed while inserting the battery, and and the phone should get into download mode instantly.

ADB gives "error: device not found"
I've tried every imaginable combination of buttons, taking out battery, removing SIM, trying all sorts of things plugged into USB, plugged into charger, unplugged, ...
I'm currently installing Ubuntu to try Adam Outler's ModeDetect USBID Detector

Tried various things, including installing a VBox Ubuntu, so I could try out some Linux-only solutions. But still nothing has worked.
In fact from what I've been reading, I think even the USB jig won't kick it back into life.
How would I go about finding someone that can repair this sort of thing? I'm in the Crowsnest Pass, AB. My nearest major city is Calgary. I don't even know where to start trying to find a place that can fix this.

xtempore said:
Sorry. I should have been clearer in my original post.
By "bricked" I mean NOTHING shows on the screen. It is completely black. It's not stuck in download mode.
I don't have a Linux box so can't do any Linux things. I have a PC (Vista) and a Mac.
I don't have the equipment or skill to solder things.
And because of where I live, I don't have access to people who might have these things.
Click to expand...
Click to collapse
Save 50$ for a new motherboard. Don't lose time.
Sent from my GT-I9000 using xda app-developers app

Unbrickable Resurector worked for me without opening my phone. It was also totally off and didn't show a reaction. Resurrecting is a thing of half an hour.

xsenman said:
SEC S5PC110 TEST B/D
You have to use resurection software
http://forum.xda-developers.com/showthread.php?t=1330491
Click to expand...
Click to collapse
I was one of the developers behind the unbreakable mod.
There is one failure mode that reaches the TEST B/D.
If you have TEST B/D, you can skip the hardware mod, and just use the unbrickable mod software.

Is it possible to enable USB debugging with adb through a custom recovery?

Hello people,
so a few days ago I dropped my Galaxy S5 and the screen is now black, I can't use it. I want to try to save the data, but it's not as easy as plug in and transfer, since I have a password that I can't unlock. Using a screen mirroring program is also out of question, because I had USB Debugging disabled before I dropped it.
My next thought was to enable USB debugging with the help of adb, but that didn't work, since adb sees my device as "unauthorized". It still shows up as "Samsung Android ADB Interface" up in the Windows Device Manager.
So my next thought was to flash a custom recovery such as CWM via Odin (my phone doesn't have to be rooted for that, right?). That way I could use the volume keys to navigate through recovery mode once I enter it. All I would have to do is look at screenshots online and count how many times I press the volume buttons to know when to hit enter since the sceen doesn't work.
Would that even be helpful? I really hope that someone can help me or at least tell me there is no possible way to recover the files so I can sleep in peace. I've been trying so much, but all I find is more problems. I even had to use the Samsung 300K tool to enter Download mode, since that didn't work at one point. And I did that to use Dr. Fone's Android Lock Screen Remover which didn't remove my password. So that was 50 dollars well spent.
Looking forward to any kind of help, really desperate right now!

i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.

youdoofus said:
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
Click to expand...
Click to collapse
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...

zakuani said:
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
Click to expand...
Click to collapse
nothing else really to take into consideration, just hope it works for ya
https://images-na.ssl-images-amazon.com/images/I/413PWcLXQHL._SY300_.jpg

USB won't recognize.

Do I need some proprietary USB dongle accessory for my G5 Plus for it to connect to my PC? Because I've tried ten different cables over the weekend and the damn phone won't do anything but charge when I connect it to my PC. No dropdown MTP menu selection, no camera mode, nothing. My PC just whines about it not recognizing a USB device and my phone simply charges albeit slowly. I haven't updated my phone at all since I got it on Friday because I don't want to risk screwing root up. Should I try that? I just want to root my damn phone already.

Attempt at helping you, appeasing the karma gods
bizarroted said:
Do I need some proprietary USB dongle accessory for my G5 Plus for it to connect to my PC? Because I've tried ten different cables over the weekend and the damn phone won't do anything but charge when I connect it to my PC. No dropdown MTP menu selection, no camera mode, nothing. My PC just whines about it not recognizing a USB device and my phone simply charges albeit slowly. I haven't updated my phone at all since I got it on Friday because I don't want to risk screwing root up. Should I try that? I just want to root my damn phone already.
Click to expand...
Click to collapse
Hi there: I'm currently soft-bricked, and trying to find my way back to life. I mention that because I can't step through what I'm about to say, it's coming from my human memory. I'm sure some subsequent poster will explain something, give attitude and tell us both how stupid we are, but that's just how it goes.
Assumptions I'm making: You're running windows on your PC, because you said "my pc whines...." sounds like windows to me!
So, as I recall, you need two things to get your pc to "see" your device in windows explorer.
1. Proper Drivers
2. A selection change in the MTP menu
For drivers, windows sometimes does this for you, it works sometimes depending on your windows flavor and your device brand. You can work this angle by looking at usb entries in device manager for yellow warnings or red exclamation marks to see if you're over the driver hurdle. Or you can search for installers of just the drivers for the Moto G5 plus, or you can install Motorola device manager, which installs the drivers.
So if you fix that, your pc won't whine when you plug the device in on usb, but you still can't see it in explorer without going from USB charging to "transfer files". I believe you have to pull the notifications shade down once or maybe even twice where you'll see a list. Because I've been rooted and had usb debugging enabled in the past mine had two entries, and it was the second one at the bottom where I could use it to go from "charging only" to "transfer files".
At that point, your pc should make the thump thump sound and your phone should appear under "this PC" in windows explorer.
To the gods of Android karma. Gimme a break, forgive me for my sins of the past and breathe life back into my primary communication device. Open my blind eyes and give me the understanding to ignore the noise and focus on the message. Lead me to the promised land as I remain your humble servant.

crea95ms said:
Hi there: I'm currently soft-bricked, and trying to find my way back to life. I mention that because I can't step through what I'm about to say, it's coming from my human memory. I'm sure some subsequent poster will explain something, give attitude and tell us both how stupid we are, but that's just how it goes.
Assumptions I'm making: You're running windows on your PC, because you said "my pc whines...." sounds like windows to me!
So, as I recall, you need two things to get your pc to "see" your device in windows explorer.
1. Proper Drivers
2. A selection change in the MTP menu
For drivers, windows sometimes does this for you, it works sometimes depending on your windows flavor and your device brand. You can work this angle by looking at usb entries in device manager for yellow warnings or red exclamation marks to see if you're over the driver hurdle. Or you can search for installers of just the drivers for the Moto G5 plus, or you can install Motorola device manager, which installs the drivers.
So if you fix that, your pc won't whine when you plug the device in on usb, but you still can't see it in explorer without going from USB charging to "transfer files". I believe you have to pull the notifications shade down once or maybe even twice where you'll see a list. Because I've been rooted and had usb debugging enabled in the past mine had two entries, and it was the second one at the bottom where I could use it to go from "charging only" to "transfer files".
At that point, your pc should make the thump thump sound and your phone should appear under "this PC" in windows explorer.
To the gods of Android karma. Gimme a break, forgive me for my sins of the past and breathe life back into my primary communication device. Open my blind eyes and give me the understanding to ignore the noise and focus on the message. Lead me to the promised land as I remain your humble servant.
Click to expand...
Click to collapse
You assume correctly, win7 64bit. Oh I neglected to mention, I've already installed the drivers and the moto manager but my phone won't show me the MTP menu in the dropdown shade when I connect it to my PC via usb and my PC continues to give me the USB device not recognized prompt on my taskbar. I got it to work for half a minute with one cable on saturday but then my internet cut out before I could do anything. The cable stopped working right afterwards too. I already have USB debugging enabled and I haven't bothered to update the phone yet, I'm gonna go to best buy and try finding a new usb cable since all of the ones I have now are old or not meant for phones. I'd use the one my phone came with but I friggin left it at my friends house way up in gloucester and I really don't feel like driving for an hour when I could just get a new one right down the street, you feel me?

Cannot use Google PAY

I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.

chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
Did you convert your tmobile to international ? I guess you did. So either root it and install magisk or livr without Google pay.
Sent from my [device_name] using XDA-Developers Legacy app

chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.

Krzysiek_CK said:
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Click to expand...
Click to collapse
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?

chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
Well you can't do really anything but if you have not had it too long you could return it.

chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
You have 3 options:
1. DO nothing and hope OnePlus will fix it down the road. I actually lost hope with this one.
2. Load T-Mobile version, and loose dual sim capability. Google Play will pass certification and Google Pay will work.
3. Use Magisk, at your own risk, to trick SafetyNet check.

I have one of those scammy "no warranty" T-mo -> Intl. OnePlus 6T and, with enough work, it is possible to convert to the most recent Intl. android 10, and get root and Google pay working. I don't think at this time it's possible to watch Netflix in HD while having your cake and eating it too, sadly. The A/B situation on this phone is painfully confusing and leads to brick after brick as you learn the ropes of this phone. Not sure that's TMo's fault. Thankfully the bricks are fixable. You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
So that gets you to an equivalent to a locked Global 9.0.11 rom with no OTA updates. From there you can do developer mode -> unlock bootloader instantly from fastboot -> (loose all your data) -> TWRP; now the a/b stuff gets really confusing AF but if you do TWRP from fastboot->flash 10.3.2 -> TWRP from fastboot again (it's like ms windows!) -> flash TWRP .zip installer -> TWRP from fastboot yet again -> Magisk, you can finally boot system.
To pass CTS profile you'll need to use the command-line signature changer Magisk module and Magisk Hide. Once the play store says it's "Certified" (certifiable more like...) and Magisk is giving you two green checkboxes, you are ready for more suffering. Now you need to freeze the Google Pay/Play apps and Google Play services and blow away all their data. At least that's what I did. Then make sure Magisk hide has all the Google play/GMS/AR/pay stuff hidden in Magisk, one more reboot for good measure, and you're off to the races. This gets Google Pay working and even lets you watch DRM at Widevine L3 level... it's still not all your cake and all your eating I suppose... hopefully you're not a big Netflix guy. Otherwise you kinda bought the wrong phone.
GL! Oh btw I have not found any way to restore an encrypted TWRP backup on this device. Starting to suspect it's literally impossible at this time -- but, if I'm honest, probably I just haven't gone through enough suffering, yet, to figure it out.

anonywimp said:
There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
Click to expand...
Click to collapse
Nope. Just completely dis-confirmed the above recipe. I am clearly still well in the cargo-cult phase of my OP qdl client tools education
All I can say for sure is randomly frobbing with the buttons and the phone-side usb-c cable for long periods of time will usually eventually start the process. And one sure-that-I'm-not-sure---but-still-fairly-confident correction: It probably helps to /un-/plug the phone from the PC, once it starts giving the meaningless red "Sahara quintessence frobnitz poop" error message (or whatever equally meaningful thing it actually says). If you find yourself in TWRP, you can use the "Reboot edl" button. Likewise, I believe the stock recovery has an interface to jump to qdl mode... could be making that up though Anyhow I think from there you want to turn the phone entirely off, which I believe can only at this point be achieved through continuous, uninterrupted mashing of the power button. So just after your get the error and disconnect, is your opportunity to impress the phone by bleeding all over it.

anonywimp said:
You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..."
Click to expand...
Click to collapse
OK, I think I figured out an actual recipe now, or the beginnings of one. It is still a bit fuzzy in places. It goes like this:
If you're not in qdl mode, or you are there but it won't talk to the proprietary flasher software, get the phone completely turned off. Often this is the hardest part. I have sometimes managed to brick my phone where it will Boot and insta-freeze at the infuriating-yellow-triangle screen¹. Then it will just sit there, indefinitely, and never bring up any sort of USB or wifi connectivity (nor does it show any sign of boot-looping, judging by dmesg output on my computer. It's just cold, and dead. Probably a bootloader bug/secure boot fail). In every semi-brick-like circumstance like this, I've found the following enables me to get the phone to turn itself off reasonably quickly, in fact, in just a couple of seconds, usually: unplug any USB-C cable (so I'm running on batteries), hold down all the buttons* until fingers bleeding or something happens -- if nothing happens, release all the buttons briefly and try again; once off, release all the buttons immediately.
Now get the phone back on, and in qdl mode. Somehow. Usually, if the phone is unplugged and off, I can get it there by holding all the buttons and plugging it into usb. If I'm soft-bricked, I'm already there, so nothing to do. From TWRP I can easily "reboot edl" to get there. Maybe there's ways to do it from fastboot, stock recovery, and system as well, via adb/fastboot commands.... My preferred way is holding "all the buttons" for about 1 second, and plugging in the usb cable, which will cause it to enter qdl mode "just one time" without actually bricking anything.
Now, finally, we run the proprietary flasher tool. Press start and it will go until it gets to the "sahara bingo yip-a-dee-ha" error (or whatever it really says... definitely not exactly what I wrote ).
Now turn the phone off again. Same recipe, but this time it seems to almost-always suffice to keep the phone connected to USB, while holding all-the-buttons. If that isn't working, then I go ahead and unplug, power cycle, and get into qdl mode like above. During this, the computer software is maybe completely disconnected from your phone, *****ing and moaning the whole time about Sahara or whatever. Ignore that, it's fine.
If the phone was fully powered off (rather than power-cycled in place), be sure to next release all the buttons, so that the phone has no usb or button-press input of any kind for at least a fraction of a second. Then press "all the buttons" again (nb: I suspect just vol+ and vol- suffice here, and the power button is superfluous? Maybe even detrimental depending on ordering? If I screw this up (sometimes it winds up booting into recovery or bootloader), then I find a way to ask it to reboot from there into qdl mode, if I can, or else power off from there and try again to use the three buttons.
pro tip said:
It is possible to hold all the buttons for too long. In which case, you may find yourself booting system. From there you may need to start this guide over from the beginning, sorry. The correct period of time to hold all the buttons down is about a second. Two seconds is probably too long.
Click to expand...
Click to collapse
Using your fourth hand, Plug in a USB-C cable, what leads from your computer, to the phone, while continuing to hold down all the buttons with your other three hands (or, if you entered qdl via software, just plug it in, now).
That's it, done. Kick back and enjoy as the tool's progress bars go wild and unbrick your phone tut suite. The qdl process should be able to go all the way to the end where it says "100%" (although when you close the program it will still treat this like you are interrupting it in the middle; I think that's because it does multiple phones at once, and you only ever fed it the one phone, so it is alerting you that, hey, phone #2 never got processed).
I am doing the above in a non-FOSS emulator under desktop linux, using the patched client referenced from xda threads.
I imagine qemu would work, as well. Obviously native Windows is going to be your best bet. I def. wouldn't trust Oracle (VirtualBox) USB emulation with my qdl flashing needs, if I were me -- which I am. Phones tend to look like huge USB hubs, full of an ever-changing kaleidoscope of peripherals. Which I don't think the VirtualBox USB stack is really ready to cope with right now. (Not even with the proprietary USB add-on pack or whatever that is -- I simply don't trust Oracle not to hard-brick my phone; VirtualBox has seemingly perma-bricked one device for me, already. That was some time ago but I'm not going to feed it any more devices and I doubt the USB was fixed in vbox. It think it's paravirtualized, or something, so as to be super-fast, but unreliable when the bus topology changes in meatspace.
-- rants / footnotes ---
¹ You know, that warning screen for "security." Which, currently, happens to be punishing me for trying to put the newest stock security updates onto my phone that I just purchased a month ago¹*².
* Not an "All the things" meme -- by "all the buttons" I literally mean all the hardware buttons: [vol+], [vol-], and [power].
¹*² I imagine the person who made the decision to require this in Android would explain it something like this:
straw man said:
(California accent) "Um, like, why? Are you a criminal or something? You know, you could just buy a new phone for like $899 US. Oh, you're, like, poor, or something? Well, OK, I guess there's no way for us to stop you from doing that. But we, like, won't be able to support you in any way. Also, sorry, but we're just going to need to put a brief warning screen on your phone, as a safety measure? No, it's not really a warning for you. More, like, in case other people might be around you for some reason? It just says, 'Hey, no judgement, but it seems like maybe a poor person owns this phone? And they're definitely doing some really weird stuff with it. So just be careful. Like maybe tell a friend where you're going, if you're going to spend time with them.' What? No, I'm sorry, there's no way to remove it. We paid millions to have it fused into the microchips or something? If you could just remove the warning, that would defeat the purpose. So, I'm sure you'd want the people around you to be safe, right? And, like, so do we! So we, like, locked that down pretty tight, yehh-...!'
Click to expand...
Click to collapse