I'm trying to unpack Android 13/14 ROMs from a set of different vendors but it seems that all images using Android 13+ have some changes in how the filesystem images are built. Using simg2img (simg2img ./system.img ./system.raw) I'm capable of converting the sparse system.img file of a ROM correctly into some unknown image format. Inspecting the converted image shows that it no partition is detected. For Android version below 12 usually it was an ext4 partition.

file ./system.raw
./system.raw: data

However, the file command shows that it is recognized as a data partition. So I guessed that we need to identify some offset to be able to mount or convert this image correctly. I tried to identify if the partition is a F2FS image (following [this tutorial](https://baremetallics.com/blog/how-to-extract-f2fs-android-flash)) but wasn't successful in identifying the magic bytes for F2FS. Does anyone know how to mount or convert Android 13+ ROMs? Are there any good script out there to automate it?

I started with CWM to get **Cyanogenmod** 12 but all I did was remove any OS present. Now no OS is currently installed, and I cannot install any ROM as any installation fails with error 7. I tried to fix it with many possible solutions, none of which worked. 1. deleting assert, 2. updating binary file for patch, 3. replacing set_metadata with set_perm. Now what to do? It will be great to get the stock ROM back.

Last night I installed **SlimKat** on my rooted S3 (SGH-I747M, Canada Bell) and I had no network connection, so I downloaded the Samsung original firmware from SamMobile.com. I flashed it on and everything is working now network wise. However, when I enable the WiFi it doesn't turn on at all. Not sure what to do at this point, do I need a different firware or what? Eventually I would like to have a custom rom, but I know I need to re-root it and then install it using CWM, but I don't want to do anything until I know that I have Wifi working. Another weird thing is that I'm currently in Prague, Czech Republic and I was able to connect to my network here (Vodafone CR) without any problem. I thought it would be locked into Bell again (This is a very good thing obviously, just don't really know why...)

I want to swap Recent Apps and Back button and keep Home in a middle. Is this possible? All other forums says: "buy Samsung" or "deal with it"

This question might seem to be a duplicate of [this question](https://android.stackexchange.com/questions/24525/why-is-custom-recovery-a-prerequisite-for-flashing-a-custom-rom) but it is different. But I'd like to have a brief explanation on why we need a custom recovery to flash a ROM. My main points of confusion are: 1. In stock recovery we have a option to "*Install Update from SD card*". Why can't we directly flash a ROM from there? 2. If signature verification is the problem regarding the first point, then how can we root and flash custom recovery using update from SD card? Why doesn't any signing or verification problem occur while flashing root package or custom recovery package? Like any other custom ROM package they are also unsigned. Why is this?

After flashing a custom ROM, there is a watermark in the top-right of the screen saying > > > 未写入google key和tee key I've googled it and have tried several of the solutions suggested, but none have worked. Interestingly, most people get a slightly different variation of this message, in red. I've removed "FactoryTest" from my phone, but do not have com.mediatek.factorymode as some have suggested. I've messed around with my IMEI keys, this did not help. The message also still appears even with the SIM card removed. Where on the phone could this be stored? My phone is rooted, so if I could locate the file responsible, I could easily delete it.

I know there are tons of questions about this, but I have tried many possible solutions to no avail. I believe the "Out of space" error is misleading... I have a problem: **I cannot install any .apk file** no matter what I try... I can install apps using **Play Store** though. When I tap on an APK file in any file explorer, Android Package Installer launches. I tap the INSTALL button but I always got the following error: > Out of space {AnyAPKApp} couldn't be installed. Free up some space and > try again. I have *plenty* of space, but even a tiny 248 KB APK won't install with the same argument... This is the only problem I have with the ROM and it is very frustrating... First, the details of my case: - *Device:* Samsung Galaxy Grand Prime+ SM-G532M, alias Galaxy J2 Prime (Xtreme detects my device as *Model Number:* SM-G950F) - *Android:* 6.0.1 - *ROM:* Xtreme Ultimate V6.0 (15.07.2018) - *TWRP:* 3.0.2-0 - *Magisk:* v17.1 - *Magisk Manager:* 6.0.1 (151) - *Storage:* Adoptable - *Internal storage:* 7.02 GB used of 8.00 GB - *SD card:* 9.09 GB used of 14.70 GB - *Root Essentials "View storage used":* 9759/15787 MB (62%) - *DiskUsage analysis:* /system = 2.94 GiB; Free space 1.61 GiB I've already done my homework and tried all of the following to no avail: 1. Move all movable apps to SD 2. Enable Adoptable storage 3. Wipe *Dalvik / ART Cache* and *Cache* partitions with TWRP 4. Full clean with *SD Maid PRO* 5. Force move apps to SD using *SD Maid PRO* 6. Uninstall *Google Play Services* and *Google Play Store* updates 7. Overcome *unauthorized device* issue while using ADB 8. Trying to install APK using ADB (e.g. adb install someApp.apk). I got: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE] 9. Delete /data/log contents as suggested here 10. Attempt to install in Safe Mode 11. Using Termux and the df command, I got the following output and there is free space in each partition: df output" class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> 12. Using pm install test.apk in a terminal emulator (*Termux*) I got [INSTALL_FAILED_INVALID_URI]. Using full path pm install /storage/emulated/0/Download/test.apk I got the same error: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE] The problem still remains. I think this is not really related to the full storage device error, I have plenty and the error seems misleading. It has to be something else... I gave as much info as I thought it was useful. If more is needed, just tell me to share it. I hope you can give me some advice to try to overcome this annoying issue. *P.S. I'll add more attempts to my list as I try them.*

I have just bought a second-hand Oppo Find X6 Pro and it has a global ROM on it. I don't know how they did it because there's no global version of the phone. I think they might have tweaked the firmware because everything seems valid, except it hasn't got any updates and its security patch is of June which is pretty behind for this device. This is the version on it: PGEM10_13.1.1.144(EX01). The (EX01) OPPO Reno 10 Pro 5G has it and it stands for a European version, I think. That's why I say they might have tweaked something because even Google recognizes the device as OPPO Reno 10 Pro 5G. > **Check your Oppo Reno10 Pro 5G** > > Google sent a notification to your Oppo Reno10 Pro 5G. Tap **Yes** on the notification, then tap **17** on your phone to verify that it's you. So I wanted to roll back to stock firmware. I downloaded different stock ROMs, but there wasn't any way to flash them on the device. Can someone help me and go back to the stock ROM? - I tried https://oppostockrom.com/oppo-find-x6-pro-pgem10 but didn't figure it out. - I also used the QPST Flash Tool, but the firmware didn't contain anything to open it inside QPST like .hex or .mbn. It just had .elf for the programmer which when I chose it to flash the ROM, it said error FireHose. - The recovery mode also doesn't have a local update and online update. - When I reboot to EDL using adb, it just shows a black screen, but the computer does recognize Qualcomm 9008. I think the recovery is also not stock. I will attach the system information:

From my understanding Project **Treble** was supposed to separate Android's OS data from the OEM's binaries (which are more or less equivalent to the drivers one installs on Windows) into different partitions. From that point on, Android device certification would include ensuring a device could boot Google's Generic System Images and Treble support was supposed to become mandatory for devices released with Android 9.0 or later. By this logic, seven years later, everything one could reasonably get their hands on would be Treble compliant - yet custom ROMs still seem to be made bespoke to individual devices, and I do not find much mention of people installing Google's GSIs. Why? Did Treble fail in its original purpose somehow? Why is there still no equivalent to doing a clean Windows install for Android devices?

I recently flashed a custom ROM and rooted my Redmi 7A, and now each time I try to connect to a network from a TP-Link router, it just says "Check password and try again," even though I insert the correct password. Also, before rooting and flashing a custom ROM, it worked just fine, and I have tried multiple ROMs, and it still doesn't work.

My android device CPU is MT6592 (8xARM Cortex –A7@1664 MHz) with instruction set 32-bit ARMv7. Board and product is ht1_107a_iball_mjk. Apart from this, Codename is REL, Internal Memory is 16GB and RAM is 2GB. I did root and un-root my device multiple times. I see connected device through **adb devices command**. After **adb reboot bootloader** and **fastboot oem unlock**, I confirmed on android device by pressing Volume Up key but there is no change on device screen and computer screen even after 30 min. I changed USB cable and USB port. However, there is no change. Therefore, I am not able to unlock its boot-loader. After **adb reboot bootloader** and **fastboot flash recovery twrp.img**, I found No TWRP or other Custom Recovery images are compatible for my device. Therefore, I am not able to install Custom ROM as well. I tried all above procedures multiple times and with multiple ways. However, at the end I am with Stock ROM (Android 4.4.4). And only two processes I can do successfully; rooting and un-rooting. In such scenario, may my device be hard bricked, if I continue above processes multiple times forcefully?

Are custom ROMs different for different makes of handsets? Or is there only one CyanogenMod for, say, Android 2.2? Can someone please elaborate why a 'ROM' is called as such? I mean, does it have any similarity to Read-Only Memory?

I'm currently using my OEM's AOSP distribution with Google Mobile Services pre-installed. However, it's nigh unusably buggy, [\[1\]] [\[2\]] [\[3\]] [\[4\]] [\[5\]] [\[6\]] [\[7\]] so I want to switch to a 3rd-party distribution, still with GMS pre-installed. For this to be viable, I want to ensure that I'll remain able to access [Google Pay](https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&pcampaignid=web_share#:~:text=Google%20Wallet) and [my bank](https://play.google.com/store/apps/details?id=com.rbs.mobile.android.natwest&pcampaignid=web_share#:~:text=Icon%20image-,NatWest%20Mobile%20Banking,-National%20Westminster%20Bank) , which are both Play Integrity protected (at their point of invocation, rather than installation, like Netlix is). However, LineageOS, /e/OS, and CalyxOS do not guarantee this. WayDroid on postmarketOS doesn't even come close. Irrespective, these can all spoof Play Integrity compliance with a Magisk module, but I don't want the worry that an update to something might ever cause me to lose certification, because I need access to my finances. I'm not directly asking about SafetyNet because I believe that it's been disabled, although if there's useful certification information about it too, I'll be glad to hear it. [\[1\]]: https://issuetracker.google.com/issues/423197817#comment1:~:text=%60com.android.settings/.wallpaper.WallpaperSuggestionActivity%60%20hangs%20the%20OS%20and%20crashes%20when%20resized%20to%20its%20smallest%20size%20with%20%60enable_freeform_support%201%60 . [\[2\]]: https://forum.fairphone.com/t/videos-recorded-via-com-fp5-camera-are-1-s-long/118864?u=rokejulianlockhart [\[3\]]: https://forum.fairphone.com/t/fp5-display-continually-loses-touch-input-when-device-is-charging/115559/18?u=rokejulianlockhart [\[4\]]: https://forum.fairphone.com/t/freeform-mode-windows-previews-are-transparent-in-com-android-quickstep-recentsactivity-view-until-the-activity-is-reinvoked/118055/2?u=rokejulianlockhart [\[5\]]: https://forum.fairphone.com/t/i-am-unable-to-utilise-split-screen-mode-with-3rd-party-launchers/118038?u=rokejulianlockhart [\[6\]]: https://forum.fairphone.com/t/navigation-bar-disappears-on-a14-using-fp5/110086/20?u=rokejulianlockhart [\[7\]]: https://forum.fairphone.com/t/random-screen-dimming-while-brightness-slider-stays-at-100-after-a12-update/93195/454?u=rokejulianlockhart

I was trying to unlock the bootloader of an old Redmi Note 4x, Downloaded fastboot and adb. I first enabled developer option and turned on USB debugging. I tried finding OEM unlock option which was not present on the phone. After few hours of searching about it online, I finally concluded it is not available for the phone. So I went on and fired up my terminal \[in administrator mode\];

$ adb devices
> List of devices attached
> 8H4DZP69S44DQOEM        device

then I rebooted my device in bootloader (fastboot)

$ adb reboot bootloader

My Phone restarted in bootloader, then I went back to my terminal and checked if the fastboot was working or not;

$ fastboot devices
> 8H4DZP69S44DQOEM        fastboot

After confirming that the fastboot is running, I tried unlocking OEM;

$ fastboot oem unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

which.. well... failed and I don't know why. I tried searching this very error code online but failed to find anything close to it. My other attempts like unlocking flashing failed in similar fashion;

$ fastboot flashing unlock
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

$ fastboot flashing unlock_critical
> (bootloader) Start unlock flow

> FAILED (remote: '
> Unlock failed - Err:0xffffffff
> ')
> fastboot: error: Command failed

Nothing seems to be working, Please help!

My device has terrible adb support. Can I install a ROM without using adb?

I want to know is it possible to edit a custom ROM from zip and then zipping it again (flashable) to a device. Will it brick the device? Thanx

I have a generic Chinese tablet (Model: Gener8 7", 2GB RAM, 16GB storage, running Android 10?). I want to install a lightweight custom ROM to improve its performance, but I can't find any ROMs for this specific device. I've searched XDA-Developers and other forums but haven't found anything for this tablet. Does anyone have any idea of some compatible custom ROMs? Here is the link for the tablet.

There are several reasons to be looking for a ROM: - Upgrading or downgrading your stock ROM - Looking for firmware from a different region/language - Flashing a custom ROM for different features, removing bloat, etc. But where can one find ROMs in the first place? What sites are likely to have the ROM I need? *[This question is intended to be canonical](https://android.meta.stackexchange.com/questions/782/where-can-i-find-x-rom-questions-should-be-treated-like-shopping-questions) ; please add to the wiki answer instead of posting separate answers.* See also: https://android.stackexchange.com/q/13510/1465

Can you tell any custom ROM for e-reader? I have tried looking up but there are none and android onyx refuses to publish there code. The e-ink screen requires special customisation I could find inkbox OS but no other reliable way to root an e-reader. Can you tell a guide for rooting EREADER of onyx BOOX devices?

When flashing custom ROMs, I've noticed that it's recommended to perform a clean flash (i.e., wipe the device's data, cache, and system partitions) when upgrading between different Android versions (e.g., from 12 to 13). However, this isn't the case for OEM updates, where I can seamlessly update from one version to another without performing a clean flash. What are the technical reasons behind this difference? Why is a clean flash required for custom ROMs but not for OEM updates?