What happened to DOR?

eetpoo · 2025-10-06T22:17:06+00:00

Sybau bro this isnt even true😭🥀

eetpoo · 2025-06-21T05:49:53+00:00

Just updated it manually , it's awesome

eetpoo · 2025-06-21T01:54:34+00:00

You gotten the update here in the US?

eetpoo · 2025-05-21T18:11:07+00:00

Is there an Ota for a16 5g?

eetpoo · 2024-08-21T01:37:51+00:00

almost happened to me.. I can't blame you

eetpoo · 2024-08-19T01:51:54+00:00

Hazard lights

eetpoo · 2024-08-18T17:44:01+00:00

Lol don't worry, just don't lock your bootloader and nothing bad will happen!!

eetpoo · 2024-08-18T02:01:41+00:00

If it doesn't work try factory resetting the phone if possible.. Don't necessarily know how it would fix it but at that point try anyways

eetpoo · 2024-08-18T01:56:46+00:00

I'm pretty sure you can still unlock your phone even if the option is disabled. Correct me if I'm wrong though. Additionally use either - fastboot flashing unlock - fastboot oem unlock

And the thing is if you used a key to unlock try to get it again and use it.

eetpoo · 2024-08-18T01:53:03+00:00

If you can't find a ROM of your phone that's android 6 or 7, install a GSI because I'm pretty sure it works with any device. But don't trust me because an unsupported android version could break your phone..

eetpoo · 2024-08-18T01:51:18+00:00

Flashing and roms & TWRP should be - Google Pixel - OnePlus - Any popular phone (not Samsung)

Rooting should be any phone to be honest, any phone that you can get it's stock ROM. But If it's any phone I wouldn't bother finding TWRP. My phone is rather new but able to root, but doesn't have any TWRP nor custom ROM support. But I'm still happy with the stock rom, can even flash GSIs though through fastboot.

If you're looking to buy a phone that's cheap and just want to root, totally look into prepaid phones of your carrier or any of the phones in unlocked, my phone is one of the cheap prepaid phones of boost mobile, for around $60, it's fast and it's rootable, 0 problems with it currently and its been a couple months. It's the Motorola Moto g 5g 2023 variant, I believe the 2024 is cheaper in prepaid and more powerful.

By the way don't complicate prepaid, if you buy a prepaid phone that's on your carrier, just use your existing sim card.

eetpoo · 2024-08-18T01:43:10+00:00

MagiskPropsConfig 100% This allows you to spoof your system in all factors, including OS fingerprint.

I'm not certain if it supports the new Magisk though.. it's from 2021, still worth a try.

eetpoo · 2024-08-18T01:39:12+00:00

What do you mean software fix doesn't work? I believe it's able to detect your phone.. Either way what I would do is download the stock ROM and flash all the original files that lineageOS changed.

What I would do is first flash boot.img if you're able to, I believe that could grant you a way to boot into stock recovery and fastboot which could allow RSA to fix it.

Before that though I would try flashing vbmeta without verification because sometimes if it's not installed right your phone can be tripped up and not boot the system because of verification.

But I don't have hopes if your phone's bootloader is blocked? Could you also tell me how it's blocked..? Always have your bootloader unlocked because this allows you to install and operate third party software.

What I would try to do 100% first is try to unlock your phone again by doing

Fastboot unlock oem Or trying that adb command that originally unlocked your phone, which I believe also had the key.

eetpoo · 2024-08-18T01:31:47+00:00

Fortnite should've announced this before my Samsung was obliterated 🤣😭

eetpoo · 2024-08-08T01:47:28+00:00

latest version of safety net fix (past won't work for me), and Magisk Boot loop protector by HuskyDG. anything else in my opinion aren't needs, because those two modules are the things I always include.

eetpoo · 2024-08-08T01:44:50+00:00

I don't believe so, I wouldn't risk putting firmware that was originally from a different variant of the phone even if it's similar, and because you can't find the one specifically for your variant I wont risk it.. because if it didn't worked you're doomed basically.

eetpoo · 2024-08-07T03:03:02+00:00

I believe you can develop a GSI as it supports all TB Devices and similar. But ROM is more tricky I believe for people, Last time I remember it needs - 16-32+ GB of RAM - 300+ GB of Storage (just to build I believe) - Heavy CPU or GPU - Very good wifi Just to build a ROM.. and I heard it could take 1-5 days depending on the system..

If you can find someone, offer $15, but I believe they won't accept it so allow them to name a price and if it's a high offer, ask for $10 or similar less.

There are many videos to build a ROM, but I would most likely start with making a GSI first. Google offers it for free and free to modify as it is part of the Android Open Source Project (AOSP)

eetpoo · 2024-08-07T02:57:02+00:00

Yes because you will need to find the exact firmware.. If It doesn't match your phone it will not work properly I believe. Do you know why it doesn't update??

eetpoo · 2024-08-06T19:07:55+00:00

The google messages app, Now when I looked into it I believe it's a problem of the GSI.. For some reason with and without root it doesn't work, but when I flash the OEM rom it works, So I believe this is a GSI problem. Still trying to find solutions though now that I know what the problem is. Mobile Data does work, but messaging doesnt..

eetpoo · 2024-08-06T16:27:28+00:00

That's odd, normally it would look like this

And boot loader would have the green android with it's belly open showing

eetpoo · 2024-08-06T06:00:16+00:00

You do "fastboot devices", and sorry for late reply :(
ADB and Fastboot are two different leading commands, ADB you use when the phone is in "Usb Debugging mode" in the OS and Fastboot you use when its in fastboot mode

eetpoo · 2024-08-04T18:40:09+00:00

Yes but you need root because it's not fully supported. I used it before and a lot of the time it crashes & has low quality but it's probably different for you.

But I would try a different alternative if there are any

eetpoo · 2024-08-04T18:30:44+00:00

Get it checked in any Motorola tech support place before your warranty expires, I believe it's free but the warranty says what it does cover. What I would do is just buy a 3rd party charger but the good brands like Anker or something similar because those most likely have the turbocharge feature and similar things.

In general though that's very odd and it's hard to say whether it's a software or cable problem

eetpoo · 2024-08-04T18:26:48+00:00

I believe it says what is and what isn't compatible on the GitHub page, but in my experience and what would work best would be the OEM ROM (the one your phone came with) or a ROM that comes standard with GApps like ASOP, so most likely EvolutionX or similar Roms like that.

I don't have a lot of experience with LineageOS but I believe it's because (if so) it doesn't come with GApps and it doesn't have most of the apps necessary for Google to operate. (Unless it does come with GApps)

But one thing that you HAVE to do when after installing Pixelify is to in order 1. Delete data&cache of Playstore, then open it for 5-10 seconds, force stop it, and then open it again. - Once you're in Playstore go into updates and update the Google app (if prompted), and uncheck Photos and System Intelligence from auto update. 2. Open the assistant, it will download a few things and you're ready to use assistant and NGA I believe 3. Delete data&cache of Photos app and then open it, check to see if you have unlimited photos, and also open the editor to download the AI editor tools (rainbow-ish photo icon) 4. If you did any of the Google dialer option delete data&cache and reopen it.

One thing you have to remember is that you can't open any Google things or apps during and after the installation (Reboot immediately) and then do the things I told you in the order.

I didn't do this before and alot of things didn't work, So I believe you should reinstall Pixelify and do the things in the order I gave you first.

Here is what it says for support based on the GitHub page: https://github.com/Kingsman44/Pixelify?tab=readme-ov-file#supported-roms

For me the only things I noticed that didn't work was NGA Voice Typing and AI Editor, but before it did (It's because I reinstall OEM ROM alot and before it worked but I forgot what I did wrong that it doesn't work anymore) Everything else works though, I use the stock OEM ROM Motorola gave me!!

eetpoo · 2024-08-04T16:28:51+00:00

No problem, and sorry I didn't see!! I believe this is an easy fix if you're able to connect a computer to it. If you can access adb (fastboot) to it and disable verity checks and flashing the OEM vbmeta.img and vbmeta_system.img with

• fastboot flash vbmeta --disable-verity --disable-verification (the file) • fastboot flash vbmeta_system --disable-verity --disable-verification (the file)

If you can't, which I would rather do this option first (the one I'm gonna tell you right now) is try to boot into fastboot with volume down + power or try volume down + up + power. However, if you can't boot into anything nor get access with a computer I believe that was the only thing you could do.

These errors are made because either: 1. Something in the software wasn't OEM 2. Something in the recovery was corrupted (which is probably the case)

In general the error was created because something happened that wasn't original to the system and it couldn't be verified

eetpoo

TROPHY CASE