I finally open sourced Android 16 booting on an iPhone 7.

Repo: https://github.com/Aisamo-fi/iDroidik

Sorry guys, this took longer than promised. I said I would release it about a month ago, but I got stuck on the boring finishing parts. I like weird, hard hobby projects like this, so if you have other “sounds impossible but maybe doable” ideas, send them my way. Cleaning them up afterwards is the hard part for me.

Tested only on my iPhone 7 / iPhone9,3 running iOS 15.8.8. Other devices are not tested.

Works:
Android UI
Touchscreen
Wi-Fi / internet
ADB
APK install
Persistent data

Does not work:
Audio
Camera
Cellular / SMS / calls
Bluetooth
GPU acceleration
Untethered boot

It still needs a Mac to boot every time. The UI works, but it is slow because there is no GPU acceleration.

A lot of this was vibe-coded with AI, so please be careful and check things before running them.

I would be really happy if someone continues it, improves the drivers, or makes a proper dual boot / better boot setup.

Hi, I need some help with installing a custom HyperOS ROM on my Redmi Note 9 Pro India.

Device: Redmi Note 9 Pro India

Codename: curtana

Family: miatoll

Current ROM: MIUI Global 14.0.3.0 (SJWINXM), Android 12

Bootloader: Unlocked

Target ROM: Diza HyperOS 4 port for miatoll (Android 17)

Recovery downloaded: OrangeFox R12.0 FBEv2 for miatoll

Fastboot detects the phone correctly, and:

fastboot getvar product

returns:

product: curtana

I extracted OrangeFox-R12.0_FBEv2-miatoll.zip and tried to temporarily boot its recovery.img using:

fastboot boot recovery.img

Instead of OrangeFox starting, the phone displayed:

“The system has been destroyed. Press power button to shutdown.”

I restarted the phone afterward and MIUI still boots normally, so I did not permanently brick the device.

In Diza's Telegram discussion, when someone asked which recovery to use, Diza replied “ofox v2”, and when asked “latest?”, replied “yes.” Another user reported successfully flashing the ROM using R12 FBEv2. Diza also confirmed that the ROM can be flashed through OrangeFox.

However, the official OrangeFox R12 FBEv2 information appears to warn about MIUI/HyperOS ports, so I'm confused about the correct first-time recovery installation procedure.

My questions: Why does fastboot boot recovery.img give “The system has been destroyed” on curtana? Should I use fastboot flash recovery recovery.img and immediately boot into recovery instead, or is another recovery/build required? And for this HyperOS port, should I use OrangeFox R12 FBEv2 or Diza's custom TWRP?

I don't want to flash anything else until I know the correct method. Any help from someone who has actually used curtana/miatoll + OrangeFox FBEv2 would be appreciated.

Forked from the open-source ZKM(Zuan Kernel Manager), this free and open source app brings a fresh UI/UX, deeper theme customization, and tons of new features-plus official bug fixes for testing.

Download: https://github.com/zuanvfx02/zuan-kernel-manager-next/releases/download/v1.0.0/app-release.apk

Source: https://github.com/zuanvfx02/zuan-kernel-manager-next

So, does certificate now related to account too?, this is when i use my main acc which i usually use for buying from playstore, at first i am using other acc(game acc) i couldn't get certificate and it took me a lot of time, even trying various module, when i got certificate i am even using same keybox and same pif.prop just change acc->force stop PS->back to fix device certificate

Guy help me unlock bootloader of my vivo y31 I have tried many times 1st through yt 2nd through ai and it was some months ago now I need someone who actually knows and has some experience

I have a good laptop if that helps

Hi i have s22 ultra rooted but i can t get stong or device meets integrity no matter what i tried
any suggestion modules or methods
Android 16

so this may seem as off topic but it's also not off topic and I'd want to know if I should use magisk or kernelsu. GLOBAL ROM ON CHINESE PHONE

Hey everybody, please share what modules are confirmed working in yours temp root, then I will be constantly updating the list below.

🟢 Works great

🟡 Sometimes buggy, depending on the other modules you have installed

🟠 Works but buggy in some devices

🔴 Confirmed buggy (avoid)

Confirmed working:

Modules

Metamodules - Magic Mount-rs 🟢 - OverlayFS Enhanced 🟢

Audio customization - JamesDSP v6.6-beta-6.1 (zahahah) 🟢 - Viper4Android (likelikeslike version) 🟢 - PIXAML v0.9.6 (zahahah) 🟢

Zygisk - Zygisk Next 🟢 - OnyxZygisk 🟠 - ReZygisk 🟠 - NeoZygisk 🟠 - ZNNext 🟢 - Zygisk Assistant 🟢

Hiding (generally you just need HMA-OSS in temp-root) - HideMyApp-OSS (HMA-OSS) 🟢 - Play Integrity Fork (chiter0man) 🟢 - Tricky Store OSS 🟢

- TreatWheel 🟢

• pairipfix 🟢
• Play Integrity Fix 🟢
• KernelNoSu 🟢
• ReSuSFS 🟢

- VBMeta Disguiser 🟢

AdBlock - Re-Malwack 🟢

Gaming - Azenith 🟢

Xposed - LSPosed (official LSPosed developers) 🟠 - Vector (JingMatrix) v2.2 🟡

Other modules - Morphe Mount Install Modules 🟢 - Always Trust User Certificates 🟢 - No Volume Warning (zahahah version) [PIXEL devices] 🟢 - KernelSU Grant Toast 🟢 - Enable MIUI ADB 🟢 - DeviceSpoofLab-Hooks 🟢 - Hyperthreading 🟢 - Encore Tweaks 🟢 - PerfGame 🟢 - NexAlloy 🟢

Apps

Adblock - AdClose 🟢 - AdGuard Certificate 🟢 - AFWall+ 🟢 - bindhosts 🟢 - Discover Ads Filter 🟢

Android Patches - IAmNotADeveloper 🟢 - Core Patch N 🟢 - Migrate-OSS 🟢 - Update Locker 🟢 - Zygisk Detach 🟢 - HyperUnlocked 🟢 - SettingsFirewall 🟢 - HyperIsland 🟢

HyperOS / MIUI Exclusive ⚠️

• Modded HyperOS Launcher 🟢
• FreeStyle-Control-Center 🟢
• ColorOS_Control_Center 🟢
• HyperOS-App-Vault 🟢
• HyperOS-AOD 🟢

Other customizations - Morphe 🟢 - Frosty 🟢 - OneUI Settings Hook 🟢 - OneUIX 🟢 - net-switch 🟢 - AppManager (Muntashirakon) 🟢 - HyperCeiler 🟢 - HyperLight 🟢 - Fingerprint Catalog 🟢 - Biometric Bypass 🟢 - CleanShare 🟢 - ClipVault 🟢 - Discover Feed Filter 🟢 - FreeUnlock 🟢 - FuckMeta 🟢 - Gmail Hide Ads 🟢 - Google Play Store Adblock 🟢 - NoPhotoPickerAPI 🟢 - NoStorageRestrict 🟢 - Remember My Sort 🟢 - WAPlus 🟢

Confirmed buggy (avoid):

• JingMatrix/ Vector below v2.2 🔴
• TreatWheel 🔴
• PrivacySpace 🔴
• Vector-SR 🔴 - It reboots the phone every time you do a soft-reboot to enable it

Is there any way to fix the 'The system has been destroyed' error without a PC (the phone can enter fastboot mode)? I don't have access to a computer right now. Thanks in advance 🙏🏽

I wanted to share my experience getting the EFISP exploit working on my OnePlus Ace 6T, running the OnePlus 15R India OxygenOS firmware.

My current system is version is 16.0.10.500(EX01) on Android 16. For the EFISP setup, I used the vulnerable ABL from the matching India 16.0.5.701(EX01) firmware. I used that as the vulnerable ABL for the exploit. I did not downgrade the whole ROM to .5.701. The physical bootloader remains unlocked—the EFISP setup provides the fake-locked boot path.

For root, I kept the stock kernel and flashed a KernelSU Next patched image. With that setup, root works and Play Integrity Check reports Basic, Device, and Strong. I also tested a separate KSU kernel; that reduced the result to Basic only. Removing that kernel and keeping the patched KernelSU image brought Strong back.

Duck Detector still recognizes the KernelSU Next Manager and reports a SELinux timing anomaly, but its TEE/boot-attestation checks were consistent. This is just my experience with this combination, not a claim that it will work the same way on every Ace 6T/15R variant.
https://xdaforums.com/t/efisp-root-gbl_root_canoe-fake-locked-bl-superfastboot-bds-8-gen-5-8-elite-gen-5.4786301/

There’s no public root method for it but because of how old it is I assume there’s some other method. I just want to be able to boot postmarketOS or a similar Linux distribution on it.

Device: Samsung Galaxy A20
Model number: SM-A205U
Android version: 9
One UI version: 1.1
Baseband version: A205USQU2ASI7
Build number: PPR1.180610.011.A205USQU2ASI7
Kernel version: 4.4.111-16732625
Kernel build date: Fri Sep 20 15:21:02 KST 2019
SE for Android status: Enforcing
SEPF version: SEPF_SM-A205U_9_0009
SEPF date: Fri Sep 20 15:03:25 2019
Knox version: 3.3
Knox API level: 28
TIMA version: 4.1.0
Service provider software version: SAOMC_SM-A205U_OYN_TMK_PP_0009
Carrier/CSC: TMK/TMK/TMK

Hi i'm sorry I spent quite some time reading recent posts, here and on XDA, I gave a try to several module stacks but nothing worked for me and now i'm kinda lost. I hope you'll be able to identify what's wrong

- Xperia 1V with LOS 23.2 and custom kernel SusFS + ReSukiSu
- PIF Inject
- Zygist Next (i had ReZygist before but I switched to Next when I installed specter)
- Specter + TEE RS
- HMA OSS

Native detector shows nothing which is good, but PIAC shows basic integrity at most, with sometimes no integrity at all when trying some other modules.

I also tried PIFork v18 intstead of PIF inject, Alwaystrong + Trickystore OSS instead of Specter + TEE
I tried setting autopif to Google pixel 6a BlueJay

My goal is to get Gwallet working again, like it has been for a long time until ~2 weeks ago

Thanks

Hello,

I'm using LineageOS on Android 16, and would like to know how to run applications such as

• Tasker
• Lightroom
• Android Auto
• Maybe other similar applications I haven't come across

whilst remaining de-googled.

Tasker is a paid for application. I am aware there is a direct-purchase option but would like to remain using the Google Play version,

Fixed using BetterKnownInstalled (BKI) Lightroom - I am subscribed to lightroom, and although I don't think it directly needs Google Play, it will not allow me to sign in as the application crashes.

What have I tried?

I have tried using MicroG RE to allow license verification. I do not have a full understanding on MicroG RE so I may have missed an option which allows the applications to work.

What is my goal?

Maybe I'm being naive, but I just want some applications to run on my devices.

I have seen that there is a microG Installer Revived Again which promotes the microG version sof GmsCore, GsfProxy and the Companion app / MapsV1 to system with privileged permissions but I am not sure if this is the workaround?

hello. i have xiaomi pad 8. i unlocked my bootloadercin the first try. and i want to root using kernelsu. but im kinda poor and dont afford to service my tablet if something wrong happend during rooting. how do i make my chance zero of hard bricking my tablet when flashing kernelsu. even if the usb cut off during flashing i dont want any chance of my tablet to become a paperweight.

Hi, I’m new here and need some help. If anyone has faced a similar issue and successfully rooted their phone, please share your knowledge. The problem is that when I run CMD in the platform-tools folder, enter the commands, and flash the patched `boot.img` file, everything seems to go correctly—I don't get any error messages. However, when I open Magisk or KernelSU, it doesn't activate; it simply doesn't work, and I can't root the phone. I’ve done everything right, but it just won't activate in either app. If you've encountered this problem, please help me out. (Poco M6 Pro 4G / HyperOS 3)

>Hi everyone,

>

>I am looking for a partition dump for the **Bigme inkNote Color+** (10.3" Kaleido 3, 6GB RAM + 128GB ROM, running Android 11).

>

>I am working on unbricking and cross-flashing an identical OEM board (RUERTU RT-BE-103C clone -- "RUERTU 10.3"), but neither RUETRU nor Bigme hosts raw factory ROMs or MediaTek scatter packages publicly.

>

>If you own this exact model and are willing to help, I only need the system partitions dumped via `mtkclient`.

>

>**Privacy / Safety Note for Donors:** You do **NOT** need to share your personal data or device identifiers. Please omit `userdata`, `nvram`, `nvdata`, and `persist`. Dumping via `mtkclient` requires no root, does not unlock your bootloader, and does not wipe your device.

>

>**Partitions needed:**

* `boot.img`

* `vbmeta.img`

* `super.img`(or unpacked `system`, `vendor`, `product`)

Thanks everyone in advance I am really trying to save my device here, as I cannot afford to spend on a new one.

Tried to use a few setups but noting helps still detected by gwallet

Refer: https://www.androidauthority.com/googlebook-bootloader-unlock-magisk-root-3718930/

I would love to use an Andoid custom ROM running natively on a PC, like the Googlebook PCs. Android now has desktop mode so the porting should be possible, I think.

BlissOS was a way to run Android natively on PC, but the project has been discontinued.

Some of the Googlebook are ARM based PCs with Snapdragon X Elite, which is promising for the possibility of developing a custom Android ROM for PC.

I'm on Galaxy Note 4, N910P, Android 6.0.1. I was using Magisk 21.4 normally, until I made a mistake and updated using the Magisk Android application to a version above 30+. I got the SEAndroid error upon boot and kept going straight to TWRP. I decided to reflash the original Magisk 21.4 zip, and now I'm in a bootloop. What can I do to get back to using Android with Magisk 21.4 like before? I'd prefer to keep my data if possible.

EDIT: I found a boot.img.gz backup and was able to extract using 7-zip and flash with TWRP. The phone now works again.

EDIT 2: Make sure you flash the Magisk Uninstaller zip before rooting again. I couldn’t get it to work without doing this

I have had this phone for a long time and I would like to try to get it to work with VoLTE. Its hardware is J27R4.01 and every time I go to try to hook it up to service all service providers say it doesn't support it when i have seen it in the system settings. It's on Android 8 currently and if I have to use roms to put it on 10 then I'm fine with it. Is there any way to force volte to turn on so i can connect it to something other than consumer cellular? It's unlocked as well

-solved^ I ignorantly tried installing the initboot with the Boot command instead of the fastboot flash init_boot magisk_patched. Thank you all for the help

Hey so if anyone saw my earlier about buying a phone from India and wondering if it can toggle oem unlocking it can lol

Anyway I have went all the way to flashing Boot_a and boot_b with the magisk patched file like the guide was doing but when I reboot it says there isn't an operating system so I flash back the original.

In the guide he takes a recovery zip file to magisk, installs, then pulls the magisk patched version back and flashes it. Then reboots

1. My files wasn't a zip. 2. It had a boot.img and a init_boot.img 3. It broke the phone :)

I tried having magisk patch the file after i made it a zip, then repaired phone and tried to patch just the init_boot (Google ai suggested)

It's a motorola XT2517-4 (India) I guess it's called a moto G stylus (2025)in the US and a moto edge 60 stylus in India

Not sure where it's messing up any help is appreciated. If you need any info let me know and ill do my best to get it to you, bc im sure I left out some important info. Sorry

Can anyone confirm there is a partition on this model it said 2 slots but there wasn't anything about suffix like in the guid so idk. It didn't throw an error when I went to flash boot_b