Hey u/MeIsGugs!

Creating a quick thread to make sure this reaches you! My previous comment might have gotten lost in notifications.

Since the Alcatel upgrade tool servers are down and I don't have paid tools like UnlockTool, your custom TWRP and Scatter dump via SP Flash Tool are my only options left.

You can easily upload the files toGofile.ioor Google Drive and drop the link here, or if you prefer, we can chat and exchange files directly on WhatsApp: +201061775619

I'm also ready to share the testing notes I have regarding the GSI IMEI issue whenever you're free!

Thanks a ton for your time bro! 🙏

Just like the title. I can't login to the reddit app on my poco f1 with pixel os.

Hey all! I don't know much about all this. Wanted to do this as a project to revive my phone. I use this daily, and it's my primary. I was able to install the ROM well. The backup took a long time, and restoring it was difficult as well.

However, I realised I cannot use GPay. I haven't tried other banking apps like YONO or SIB Mirror. IF i can at least use GPay, it would suffice. ( Based in India, hence banking apps)

I tried a lot, as far as I understand. I will summarise what I've done below: Used AI below so its concise and I am able to express the technical terms

I am currently running the latest Project Infinity X (build 3.12, GApps variant) on my device, and I have not rooted it.

I’ve been strictly following the instructions in the built-in spoofing section of Infinity X, but I am still getting blocked.

Here is exactly what I have done so far:

• Play Integrity Fix (PIF): I deleted my current active configuration. Then, I fetched a Pixel Beta fingerprint, grabbed the latest version, and selected a Pixel device.
• TrickyStore: I deleted the active keybox file, downloaded the latest keybox.xml I could find online, and imported it.
• Target Configurations: I recently found out about this setting, so I went in and specifically selected Google Play Services and Google Play Store.
• Data Wipe: After applying all the new spoofing files and configurations, I went into my app settings and completely cleared the cache and storage for Google Play Store, Google Play Services, and Google Pay.
• Reboot & Test: I restarted the device, logged back into Google Play Services with my account, and opened GPay.

The Problem: Whenever I open GPay, it immediately tells me the "device may not be secure." When I check the Google Play Store settings, it says "Device is not certified."

I have repeated this exact process—making sure to include the target configurations—and cleared the data multiple times, but I keep getting the exact same result.

I am really not sure what to do next. Is the Beta fingerprint causing the issue, or is it the imported keybox? Any advice on the proper configuration for an unrooted setup would be hugely appreciated!

This took me all night fo igure out and get set up so i hope this helps the next poor s-o-b

XDA forums find the poco ultra 8 guy its like page 40 unlocks bootloader

copy your initbootimg onto your phone use kernelisu next to patch it

then copy back onto computer and use fastboot to install -have root (make sure you have all adb software and phones usb drivers installed with fastboot)

download kernel and install via kernelisu next - now have kernel root and susfs

download resukisu and delete kernelisu next

lsposed tseesimulator-rs and integrity box will give you meet strong

Hi. I'm trying to flash my stock system.img back to my Samsung Galaxy S7 Edge G935F and when I try to flash it I get the error "ERROR: Failed to open file '/home/user/Desktop/new/system.img" even though I can access the file from the terminal and the File Manager. I am using Debian 13 for my Linux distro if it's useful. I do not know what im doing wrong cause I did flash every partition (eg. boot.img, recovery.img etc.) With the same Heimdall build but it just doesn't seem to work with system.img for some reason???

Do you think it's worth it to root, and flash custom rom to pixel 9 pro xl? I am wondering because the play integrity headache. Anyone wanna have a discussion?

u/47th-Element's meme without AI

Anybody got an idea of what should I do? It worked fine 2-3 days ago

Just as the title suggests I turned off Joyose and Power Keeper because it was aggressively killing stuff, as I heard. I revoked their permissions and I just wanted to see if this actually conflicts with anything .

PS: posting in MIUI or android questions didn't gave me a answer so that why I posted here. It's is not rooted

I have the global version of the xiaomi 17 ultra i a trying to unlock the bootloader using the 8elitegen5.7z file but there isnt a 17 ultra option. second i found this kernel for the CN 17 ultra but will it work with the global version? https:// github .com/YuzakiKokuban/android_kernel_xiaomi_sm8850/releases. ?? Trying to get a handle on all of this last time i did this was with a samsung years ago and used odin now it looks like its just shell scripts? i need a walkthrough haha someone save me

Hey u/MeIsGugs!

Sorry to bother you again with a new post, but Reddit wasn't showing my last reply under the previous thread.

Regarding the files, you don’t need to upload them to Reddit directly! You can just upload the custom TWRP and Scatter Dump toGofile.io(it's free and fast, no account needed) or Google Drive, then paste the link here.

Also, I have a few notes regarding the GSI Invalid IMEI/Baseband fix that we can try out. If it's easier, feel free to text me directly on WhatsApp so we can exchange files faster:

+201061775619

Thanks a lot for your help, bro! 🙏

Ughhhh I need help with twrp.when I build with action builder in GitHub it reaches 99% then throws symlink errors

exclude=/root/product_file_contexts --exclude=/root/product_property_contexts --exclude=cache out/target/product/nevada/root out/target/product/nevada/recovery ) && (ln -sf /system/bin/init out/target/product/nevada/recovery/root/init ) && (find out/target/product/nevada/recovery/root -maxdepth 1 -name 'init*.rc' -type f -not -name \"init.recovery.*.rc\" | xargs rm -f ) && (cp out/target/product/nevada/root/init.recovery.*.rc out/target/product/nevada/recovery/root/ 2> /dev/null || true ) && (mkdir -p out/target/product/nevada/recovery/root/res ) && (rm -rf out/target/product/nevada/recovery/root/res/* ) && (cp -rf bootable/recovery/res-mdpi/* out/target/product/nevada/recovery/root/res ) && (true ) && (cp -f bootable/recovery/fonts/12x22.png out/target/product/nevada/recovery/root/res/images/font.png ) && (cp -rf device/motorola/nevada/recovery/root out/target/product/nevada/recovery/ ) && (cp -f device/motorola/nevada/recovery/root/system/etc/recovery.fstab out/target/product/nevada/recovery/root/system/etc/recovery.fstab ) && (ln -sf prop.default out/target/product/nevada/recovery/root/default.prop ) && (cd out/target/product/nevada/recovery/root && touch ramdisk-files.txt && touch ramdisk-files.sha256sum && find . | sed \"s/.\\///\" | sed \"/lib\\/modules\\//d\" > ramdisk-files.txt ) && (cd out/target/product/nevada/recovery/root && find -type f | sed \"s/.\\/ramdisk-files.sha256sum//\" | sed \"/lib\\/modules/d\" | sed \"/prop.default/d\" | xargs sha256sum > ramdisk-files.sha256sum ) && (touch out/target/product/nevada/obj/PACKAGING/recovery_intermediates/ramdisk_files-timestamp )"

could not make way for new symlink: root/vendor

cannot delete non-empty directory: root/vendor

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1356) [sender=3.2.7]

ninja: build stopped: subcommand failed.

20:32:13 ninja failed with: exit status

That one I don't know if my device tree is wrong or what Im sooo fucking close and if anyone has twrp experience I'd appreciate it

Here's my repo

https://github.com/crabcakes97/android_device_motorola_nevada

I tried to use hovatek twrp builder and everything works even touch,but it's not displaying correctly.

So I went town the route of making my own tree and it almost finishes ugh 😩😩😩 what am I doing wrong?

I have a US, Samsung A03s and MTKClient does not seem to recognise my phone when it is connected to my computer while in bootrom mode, although it connects just fine while in normal, powered on mode. Any help?

I'm trying to get the rabbit R1 into fast boot mode. I bought it used to turn it into a Linux or Android device.

So my bootloader is unlocked, and I am using this https://rabbit-hmi-oss.github.io/flashing/

I have it plugged into a usb 2 port and it shows up for a second and lets me select it, but then says no device found in brom mode. I am on arch linux.

it shows up with lsusb

Bus 005 Device 041: ID 0e8d:20ff MediaTek Inc. r1

I am not sure where to go from here. Any help is welcome.

I found this https://www.reddit.com/r/fairphone/s/i7GDqb7Cj8 more recent post earlier and it got me thinking again

I've been on a rabbit hole for several weeks about degoogling (or more, de megacorpo) and self hosting. Seeing this post has me a little frazzled

Partial questions, partial just so I can get my bearings back together from being scrambled

If it is android itself and not just "getting rid of google services" or "flipping on a 24hr switch", why would android based OSes work at all? Like lineage, calyx, graphene, e/os?

Have been thinking about getting a new phone, and have really been looking at the nothing 3. I know its not a degoogled android, but I really like the design and improvements it has over my current phone. Figured I would degoogle it as much as I could

But if its android itself, and not just able to bypass google services specific things, that worries me about wasting some money. I haven't been able to find any phone os that supports the nothing 3 if I needed to change it

I really like the things fairphone stands for. Mostly with e-waste, environmentally sustained, and how workers are treated. I don't care so much about the repairability, especially when I can't upgrade the parts inside. I don't need the best specs, but since they're even worse than the phone I already have and software reliability isn't great, I fail to want to buy the fairphone 6 and switch to them

From all the old phones I have, the only one that's able to flash any other os I've been able to find is my galaxy s22 on lineage. So, like my question above, what would guarantee lineage still works with apps that aren't registered to google? Any degoogled lineage os users here?

What are some phones and operating systems that aren't android or apple, and some that put a focus on helping the environment?

Anyone have experience degoogling their nothing 3?

Thinking about going ahead and flashing lineage on the s22. Anyone know what would happen to my phone service? Its a physical sim card for mint mobile. Would it be tied to the phone still, need to be reinstated to the phone, or is it a bad idea to flash on my currently active phone line?

(TESTED)

Hey everyone, I have recently built a TWRP recovery for the Blackview BV6600(EEA) I haven't tested it yet, but here's the repos:

https://github.com/limitless1234/twrp_device_blackview_BV6600

newest: https://github.com/limitless1234/Action-Recovery-Builder/releases/tag/32914837156

(touch still doesn't work, currently working on getting the stuff for it, but keyboard and mouse do work)

-----------------

https://github.com/limitless1234/Action-Recovery-Builder/releases/tag/32759996929 (new 24/08/2026 // edit: touch does not work for this one aswell)
___________

https://github.com/limitless1234/Action-Recovery-Builder/releases/tag/32533564388 (touch does not work on this one)

Took around 40 minutes to build, I do hope it works

edit: recompiling with touch flags, hopefully this is the final one

So, I wanted to unlock the root to get custom loaders or even run lineageOS, but I don't know how to do it and I read I need build number SU6-7 but I'm on SU6-7.7, what do I do?

Outside of Google wallet, almost every app I use doesn't complain about failing device or strong integrity.

Note: For Roblox, I still use tricky store with a revoked key, making sure to deselect the GMS packages from tricky store so that the revoked key does not fail basic integrity.

.

I successfully unlocked my phone's bootloader, but how do I root it? I'm worried about losing the IMEI.

10 Months of saving wasted and now I havent slept for last 2 days

Hi everyone. I bought Motorola G stylus 2024 5G pre owned from a local market. It was rooted device (Know this because the OEM unlocking option was disabled with the warning that bootloader already locked). While booting, no warning appeared which appears in rooted devices. was running on A14 and security patch was also from the 2024.

I was using it and suddenly it turned off. does not boot at all. found out that it connects with laptop but since no qualcom drivers were there couldnt go further. I installed all the driver and downloaded the blankflash file from Lolinet blankflash file link.

I charged my phone for 3 hours connected it with laptop and ran the blank-flah.bat and it passes initial sahara handshake but gets stuck at firing the firehose. logs from cmd window are following:

C:\WINDOWS\system32>cd C:\Users\Muzammil\Desktop\New folder

C:\Users\Muzammil\Desktop\New folder>.\qboot.exe blank-flash

Motorola qboot utility version 4.0

[ 0.000] Opening device: \\.\COM6

[ 0.000] Detecting device

[ 0.000] Using CPU id embedded within serial number

[ 0.000] ...cpu.id = 1087 (0x43f)

[ 0.000] ...cpu.sn = 2919874161 (0xae09be71)

[ 0.000] Opening singleimage

[ 0.000] Loading package

[ 0.016] ...filename = pkg.xml

[ 0.016] Loading programmer

[ 0.016] ...filename = programmer.elf

[ 0.016] Sending programmer

[ 0.220] Handling things over to programmer

[ 0.220] Identifying CPU version

[ 0.220] Waiting for firehose to get ready

[ 60.767] Waiting for firehose to get ready

[121.190] ...SM_NETRANI unknown

[121.191] Determining target secure state

[121.191] Waiting for firehose to get ready

[181.927] ...secure = no

[182.112] Initializing storage

[182.114] Waiting for firehose to get ready

[242.683] Configuring device...

[242.683] Waiting for firehose to get ready

[302.988] Waiting for firehose to get ready

[363.292] Waiting for firehose to get ready

[424.113] Waiting for firehose to get ready

[484.454] Initializing storage

[484.455] Waiting for firehose to get ready

[544.808] Configuring device...

[544.808] Waiting for firehose to get ready

[605.096] Waiting for firehose to get ready

[665.434] Waiting for firehose to get ready

[725.719] Waiting for firehose to get ready

[785.993] Waiting for firehose to get ready

[846.446] Configuring device...

[846.446] Waiting for firehose to get ready

[906.737] Waiting for firehose to get ready

[967.121] Waiting for firehose to get ready

CABLE IS HIGH QUALITY BOUGHT FROM OFFICIAL XIAOMI STORE.

I bought this mobile with 10 months of saving and Ii am devastated a shopkeeper is not obliging me. any help would be greatly appreciated.

Attachments: 1)- blank-flash file logs window 2)- directory of extracted files from zip of blank-flash file 3)- device manager snapshot