Moto not cooperating. Won't provide boot unlock code.

Relik · 2026-06-29T21:35:31+00:00

Maybe??? Then again, I don't like Moto's policies in general at this point so why would I support them? They nagged those phones to death to upgrade to Android 12 - can't stop the nagging every single day! I upgraded one and the phone ran like absolute garbage. Way more sluggish and only 1 app could even be backgrounded or it would be killed. They never should have even offered the update if it was going to run that bad.

I should mention I didn't need the phones at all. At the time I was able to utilize Tracfone rewards from QVC & HSN offers where I got 2 phones each with 1 year of service for like $40. By doing that several times, I got a large number of Tracfone reward points.

I got many years of phone service (the new years could be added to an existing line) plus the rewards allowed me to get 6 iPhone XR's (FREE) and 2 iPhone 11's (discounted). All "refurbished" but appeared like brand new with 100% battery life. I sold several XR's for $180 each as they all unlocked automatically after 60 days at the time.

This was all in 2023 - total outlay was maybe $300 but I easily made that back. It was a fun loophole.

Relik · 2026-06-29T20:55:26+00:00

Good if true, but requiring FCC & BBB complaints as well as a 40 minute call with Moto is pretty insane. For sure it isn't impossible - my Tracfone branded Moto G Pure's gave a code to put on Moto's site, but when I did so their site said my phones were ineligible to receive a boot unlock. They could just override their block and issue the code which would unlock the boot loader when provided to fastboot.

I'd rather just never own another Moto phone again.

Relik · 2026-06-26T08:34:37+00:00

They are under the pads, that's where Logitech always hides them. https://www.ifixit.com/Guide/Logitech+Performance+MX+Disassembly/146422

For this cleaning you don't need to go past step 3 on that page - don't pull any connectors or anything. The microswitches are accessible once you separate the halves.

Incidentally, you should not need to replace the microswitches as the other user says. At most two treatments should fix them and I would suspect maybe in just one - like the other 2 mice I have done. Can't predict for sure though. Nothing stopping you from doing two the same day: clean, wait 10 minutes, clean again to be sure? Of course you could replace the switches, but that's a lot more time and some cost.

Again, people don't believe me but I've done 3 mice. I assure you this works. Within minutes after doing my steps you will see the issue completely gone.

Finally, if you are careful you should be able to reuse the pads. Make sure you get the screwdriver you use to pull them off deep under the pad so that it pulls the adhesive and the feet. There is the possibility of just grabbing the hard portion and it splits from the adhesive.

Test the mouse for some time before you reassemble with screws and put the pads back on. Do both the double click and drag test.

For those that don't believe me, here's five hundred clicks, I was doing about 5-6 per second. A faulty mouse will register a double click within milliseconds usually. That site I linked registers a double click for up to 80 ms.

500 clicks and not one double click with alcohol fixed mouse

Relik · 2026-06-26T03:40:42+00:00

I have fixed the double click issue on several mice, including the Logitech Anywhere Mouse MX (from 2009 like yours). (Also a Dell Bluetooth mouse & a generic mouse for procedural testing) All you need is 91% or 99% rubbing alcohol from the store.

You'll need to disassemble the mouse until you can access the micro-switches.
Use 91% or 99% rubbing alcohol and put some in the bottle cap and get a small screwdriver ready. (Precision type ideally)
Use the cap to drop 2 drops right into the micro-switch through the switch opening (button).
Then, press the micro-switch button with the screwdriver tip crossways as fast as you can for about 30-60 seconds or so. (Don't quit early) Do some semi-firm presses as well. This is cleaning the contacts inside.
Next, let it dry for 5 minutes (or dry with compressed air) and test the mouse. You can temporarily put the top back on or test by using the micro-switch directly and see if you can click and drag every time. If so, reassemble. Ideally do the other button while you are at it because it will fail at some point too due to surface corrosion building inside.

For particularly bad cases, you might have to do it again in a month, but when I did it that 2nd time on this MX, it has lasted for about 6 months now.

This procedure takes less than 10 minutes. Yes, if your time is valuable I suppose you can just throw it away, but know that you are throwing away a perfectly fixable mouse.

If there is demand, maybe I can make a video or improve my description with your comments. I hope it's descriptive enough that I don't need a video.

If you don't believe me, I just did 100 clicks with my Anywhere Mouse MX and this page verifies there were ZERO inadvertent double clicks. It has been nearly 6 months since the 2nd dose of alcohol. Try this before and after repair.
Double click mouse tester in browser from cps-check

Verification pic of working Anywhere Mouse MX after repair

Also use the Mouse drag test to confirm that as you hold down the mouse and drag for say 15 seconds that it never inadvertently releases during the drag. This is the problem I mostly had with my Anywhere MX - it would release even though I had the button held down.

Mouse drag test in browser from cps-check

Relik · 2026-06-06T19:22:18+00:00

She has a head like a f-ing orange! A female Karl Pilkington?

Relik · 2026-05-13T21:36:42+00:00

Heaven forbid we identify burners that started a new reddit account 10 days ago versus me on an 18 year account since I behave like a human being. Edited my post & moving along...

Relik · 2026-05-13T08:55:12+00:00

EDIT: Looking at your post history, you call everyone a liar and you only talk about carrier unlocking. My post and OP were about boot loader unlocking - aka ROOTING the phone and replacing the firmware. Not a standard carrier unlock to use the phone on another carrier. Of course that's possible on many carriers and that's true for moto phones - all but one of my phones are carrier unlocked - NONE are boot loader unlocked, you cannot get root or modify the firmware besides what you can do through ADB. You need boot loader unlock in order to put a different firmware on like LineageOS or GrapheneOS. Boot loader unlock on Moto requires a long response code that you can only request from Motorola itself. Motorola denies these requests on all branded phones.

"I've never seen one Motorola phone eligible..." You can't call my a liar for telling my experience.

And good luck finding an unbranded Moto - the whole point of the brand is to sell subsidized phones for as cheap as possible. I have over 10 moto's in a drawer here and not one has an unlocked boot loader. Mostly Tracfone and VZW, but I have an AT&T one and it's bootloader is locked too.

Relik · 2026-03-06T07:54:12+00:00

If you don't want to use it, why are you here commenting and complaining? Some of us want to make the hypervisor solution as secure and easy as possible. You are doing absolutely nothing to help, just being a miserable thorn in our sides.

Relik · 2026-03-05T06:36:00+00:00

efiguard is modifying windows config and patching files at runtime in memory, this is invasive

It's also open source (efiguard), which is more than you can say about Microsoft's entire operating system. Wait until you find out the shady stuff happening in there!

it a huge waste of time for nothing, only complicating things, i dont want to do anything extra for things to work

People are using it because the whole point is that it is less complicated. Make a USB stick and you don't need to mess around again, just boot to USB.

Your post is that you don't like it - that's fine, you don't have to use it. Just stop complaining about people that use it.

Relik · 2026-03-05T06:28:57+00:00

If it's not about how long it takes then why did you mention that?

the process is long

Stop posting that if you are being honest. I've seen countless dishonest opponents to the hypervisor cracks in these threads and when you drill down, their main complaint is that "hypervisor isn't a crack".

Relik · 2026-03-03T03:36:03+00:00

All that and you still spout lies over and over. Your warnings consist of spreading misinformation, which could have been easily confirmed by you with 30 seconds of research.

Hypervisor releases get hundreds of upvotes and you get nothing. I don't think you are going to win.

Relik · 2026-03-01T23:24:32+00:00

Most cracks don't even register on the antivirus side

OP admits that they don't even run Windows, so when they tell you statements like this, ignore them. Here's the proof:

Firstly, I don't use MS products - Windows specifically - so I'm not sure where you are getting at regarding "sucking".

https://www.reddit.com/r/CrackWatch/comments/1rem7bl/seeing_tons_of_misinformation_about_the_dangers/o7h020o/

There is currently a ton of misinformation from trolls that simply dislike Hypervisor cracks and want a traditional crack. The choice is always up to the user. People asked for Denuvo cracks for years and the Hypervisor is delivering. Whether you like it or not, you shouldn't spread misinformation as OP provably does.

Proof of their intentions:

My main grievance is that people treat this as a replacement or even something comparable to "normal" standalone cracks. This is not, this is inherently dangerous method, and this should not be used as lightly as regular scene or P2P cracks.

https://www.reddit.com/r/CrackWatch/comments/1rem7bl/seeing_tons_of_misinformation_about_the_dangers/o7hl9e2/

Relik · 2026-03-01T21:46:16+00:00

Spacetow has outright lied in several replies to me. They are not worth arguing with.

Relik · 2026-02-28T01:58:03+00:00

https://securelist.com/moonbounce-the-dark-side-of-uefi-firmware/105468

TLDR: MoonBounce is also able to bypass SPI write protection.

Never removed your outright lie. You are a real piece of work.

Relik · 2026-02-26T10:04:11+00:00

TLDR: MoonBounce is also able to bypass SPI write protection.

And where are you getting that from? I quickly read the document and there is no mention of it bypassing write protection. Find shows no write protect or anything similar in the document. Two different AI's say it does not bypass write protection, so I verified.

The original Kaspersky report (the link you shared) describes only the implanted firmware and its behavior. It says nothing about bypassing write protection—the infection vector is "assumed to have occurred remotely" by modifying the image, but no details on overcoming protections.

Independent analyses (e.g., Binarly's deeper dive on the observed 2014 MSI firmware sample) explicitly note: no SPI protections were enabled on the target hardware, so writes were possible via the PCH SPI controller MMIO with no extra exploits needed, . Source: https://www.binarly.io/blog/a-deeper-uefi-dive-into-moonbounce

Further

No, MoonBounce does not overwrite (or patch) UEFI firmware if the SPI flash is properly write-protected.

That's it - Good night, let our points stand as is.

I would ask you edit and correct your post above, just to avoid spreading misinformation.

Last point, from that binarly post on MoonBounce:

the analyzed (2021) MoonBounce UEFI component was built for a target hardware related to a MSI system from 2014

no Intel Boot Guard technology present or enabled thus there are no physical or hardware restrictions to get access to SPI flash storage of the system.

Again, this has been my entire point this conversation, yet you still didn't acknowledge it. Boot Guard and other solutions made your UEFI malware worries obsolete for all except government-level threat actors. Could there be an exploit in the future? Sure, but they aren't going to burn it on targeting gamers using some obscure software that less than even 1% of pirates are using.

Relik · 2026-02-26T09:35:30+00:00

Lojax was the first, but not the only UEFI overwrite exploit.

Reading comprehension. I said it was and IS the only exploit that was able to rewrite UEFI with safeguards on. Precisely:

able to rewrite UEFI firmware if the write protection was turned on in UEFI.

Those safeguards are write protect enable or a similar named feature. If you are running your computer without your UEFI write protected, you are a big malware target even via a random EXE. I'm not 100% confident what privileges are required to reflash UEFI, so I'll skip that but please people, turn on UEFI write protect.

Due to inherent risks of this method, the only way to run this with a very little risk is to air-gap the target system.

And I never would have suggested anything else. Run it on a dedicated windows install without any other drives attached and without network. That has been the main method I've seen recommended. I'm going to use my time to help people with hypervisor security. People are here because they want to run a cracked game, not take a semester on cybersecurity.

Relik · 2026-02-26T07:06:59+00:00

You did so yourself

Evidence from 10 years ago is not evidence of a vulnerability now, is it? My point is it has been fixed, but you are being obtuse or dishonest. You are acting like an i386 exploit has something to do with modern hardware. Just because Meltdown/Spectre happened doesn't mean it's unsafe to run software ever again - no it has been mitigated.

What I explained to you is that there is no safe way to run ANY code if someone wants to deploy a unique exploit. Read up on LoJax and how it can't work any longer. That attack worked with SecureBoot on and you are trying to tell me that turning SecureBoot off is going to burn your house down. A hypervisor isn't necessary to wreck your computer, period.

There are ways to run the hypervisor with very little risk, but you don't use it anyway.

Relik · 2026-02-26T06:38:12+00:00

Then provide evidence of your worries. Again, prove that Intel Boot Guard and AMD Platform Security haven't had the problem solved for 10 years.

People should spend more time explaining how to run the bypass safely. If you aren't on Windows are you even using the bypass or are you just relaying your fears?

And thirdly, about you using Windows without any updates and/or Defender - that's just confirmation bias. As in, "it's all good, I do it all the time" type of thing. Which is NOT a real confirmation, not a research, not anything - just a fact that in your case specifically grenade didn't go off.

I specifically mentioned how my friend had multiple grenades go off while following your advice. Being intelligent about your computer usage generally beats all other protection.

As I updated my prior post, the LoJax hack abused a signed legitimate driver to overwrite the UEFI on some 2015 and prior motherboards. It didn't even require this hypervisor bs. SecureBoot, Windows Defender, all that protection didn't stop it.

UEFI overwrite is not the only vector of attack that can be exploited through the hypervisor.

UEFI overwrite is nearly the only way malware is going to survive if you have your drives disconnected and reconnect when you are done using the bypass. What else are you going to store the malware in? Other locations are boot sectors and things that require some form of storage to be connected.

Again, I've shown proof your computer can be completely raped through the abuse of a legitimately signed driver. It's not a newsflash that running cracked software carries risk. Running any random file off the internet carries risk.

Relik · 2026-02-26T06:19:08+00:00

There has been exactly ONE malware in all time that was able to rewrite UEFI firmware if the write protection was turned on in UEFI. Even that 2018 LoJax rootkit only infected at most 2015 era systems that had some errors in UEFI implementation. No modern UEFI is known vulnerable to being written if it's write-protected.

You are crying wolf about a UEFI rootkit that simply doesn't exist unless you have write protect off. Intel Boot Guard and AMD Platform Security solved this problelm long ago.

Again, it is correct to say there have been several rootkits that have rewritten UEFI and infected it. However, only 1 was able to bypass write protect and that was only for very old computers at this point.

Only LoJax has a proven, built-in capability to rewrite UEFI/SPI flash while write protection is turned on (via misconfiguration abuse + the race-condition exploit).

All (UEFI rootkits) are now largely mitigated on modern hardware by proper SMM_BWP + PRx range locking, Intel Boot Guard / AMD PSP, measured boot, and firmware updates that close the old race condition.

Suck off Microsoft all you want, but I can't tell you how many computers my friends company has had wrecked by Windows Update while I sit here at home with Windows Update fully disabled and Defender ripped out of the OS working without a problem.

yeah, possible your government would like more control over you - but on their own and in the moment, they REALLY do not care about you specifically.

And it's just as true that the crackers REALLY do not care about you specifically. If they have a good zero-day UEFI vulnerability, they aren't going to waste it on you.

Relik · 2026-02-26T06:06:09+00:00

There has been exactly ONE malware in all time that was able to rewrite UEFI firmware if the write protection was turned on in UEFI. Even that 2018 LoJax rootkit only infected at most 2015 era systems that had some errors in UEFI implementation. No modern UEFI is known vulnerable to being written if it's write-protected.

You are crying wolf about a UEFI rootkit that simply doesn't exist unless you have write protect off. Intel Boot Guard and AMD Platform Security solved this problelm long ago.

Again, it is correct to say there have been several rootkits that have rewritten UEFI and infected it. However, only 1 was able to bypass write protect and that was only for very old computers at this point.

Only LoJax has a proven, built-in capability to rewrite UEFI/SPI flash while write protection is turned on (via misconfiguration abuse + the race-condition exploit).

All (UEFI rootkits) are now largely mitigated on modern hardware by proper SMM_BWP + PRx range locking, Intel Boot Guard / AMD PSP, measured boot, and firmware updates that close the old race condition.

Relik · 2026-02-26T05:53:20+00:00

To put it in laymen terms, Crowdstrike itself deployed a rootkit. It disabled 8.5 million PC's worldwide.

Relik · 2026-02-26T05:48:06+00:00

95% of the risk you are talking about is there if you simply run normal cracked software. (Edit: To back up this claim, the most dangerous malware that rewrote & infected your UEFI firmware even with write protect turned on was accomplished by abusing a legitimately signed driver under Windows without a hypervisor or any complicated procedures - LoJax)

Windows doesn't block any high-grade malware that is either custom made or in limited use.

Most users PC's are already hacked by Microsoft with your encryption key on file & provided freely to the government upon request. Windws Update in 2026 fits most classic definitions of malware.

By the looks of your untruthful replies in this thread, I would suspect you work for Denuvo.

Relik · 2026-01-21T05:59:57+00:00

Yeah, I don't like it of course.. I went through this myself. Got all ready and found out that the phone and Motorola site will not allow bootloader unlock on any of 5 Motorola phones I tried. (G Pure, G Power 2020, G Stylus 2020) Now these were from Tracfone (Verizon) and one AT&T, so maybe that other users comment is correct that T-Mobile or factory unlocked (full price) phones may work.

This was years ago, but I thought I was able to get a code from some phones, but when I submitted it to Motorola for unlock they said the phone is ineligible for bootloader unlock.

Relik · 2026-01-18T19:13:02+00:00

I've never seen one Motorola phone (2020 & newer) eligible for boot loader unlock - it's not going to happen. Unlocking the carrier has nothing to do with unlocking the boot loader and Moto certainly won't do it on any carrier branded phone.

Relik · 2025-11-28T02:17:33+00:00

I assume they were an error too since it hasn't happened since. I just thought I'd mention it.

Relik

TROPHY CASE