Related
I own Realme 5.
It supports Treble.
I want to select a GIS ROM for my phone.
How do I know the partition type of my phone (e.g. a/b)?
download treble info app
I have a Samsung Galaxy Tab A 8.0” WiFi only 2019 (SM-T290) (gtowifi)
I’m using 2 apps that I have downloaded from the Google Play Store. They are called, Treble Info, and Treble Check.
Treble Info shows A/B system partition (arm64)
Treble Check shows A only system partition
My question is, what system partition variant should I choose when I go and download the GSI from Phhusson’s GitHub repo?
And another question is, the device doesn’t have a TWRP build released yet. And the device doesn’t have a proper fastboot/bootloader mode. So how would I install the GSI and wipe the system?
Thanks.
Realme 5 Pro global ROM for Realme Q
Code:
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
{Mod edit}
If you know exactly what you're doing then jump go step 5)
1) Introduction:
Oh sheet. Here we go again. Hope you guys will make use of this little guide for at least 20 RMQ users PMed me here on xda, on Messenger and on Telegram to help them install RM5P ROM on their RMQ device and had to dump them for I had no idea. Now that I have tried it myself I'll try to do. I've an RMQ device 4+64GB variant which I ordered from AliExpress for 161$/148€ ( in September of 2019 ) and tried loads of tweakings on stock ROM to make it more fitting to a person like me for daily usage but I don't think I have to say... without much success. In this guide I'll try to show/tell you how to make with COS without weeks of testing and debugging I've been through on stock RMQ ROM since October of 2019.
2) Personal reasoning:
I heard there are people who like Color OS as it is existed but still I wouldn't want to believe you even after I talked with some of you. Since the very first day I held my device in my hands I started seriously despising Color OS for I've been a purist, minimalist and stock Android fan for 10 years now and always tried to stick to "clean" ROMs such as LOS, PE, Aosp Extended, AOSIP because of reasons. This is mainly because (Chinese) Android skins modify system/vendor so heavily that they prohibit or interfere (with) basic Android functions that work well on stock-like ROMs. {Mod edit}
3) Features:
Mostly same as on RMQ ROM but...
More languages are supported by the system.
Most of Oppo's restrictions are removed {Mod edit}
3.5) Known bugs:
None. You tell me!
4) Basic terms:
RMQ: Realme Q
RM5P: Realme 5 Pro
RMX1971CN: Realme Q device codename.
RMX1971EX: Realme 5 Pro device codename. Both are used to distinguish China and Global/India ROMs.
COS: Color OS
ROM: Read Only Memory (means for us the OS we use to flash with TWRP/Fastboot)
OS: Operating System
TWRP: TeamWin Recovery Project (the one recovery we use widespread to flash custom ROMs and fixes on our mobile device)
FASTBOOT: A mode of your device and a script on PC that you can use to flash stuff via USB cable onto your device. This is necessary if you are on stock recovery.
FLASHING: The process of writing onto our mobile device's ROM that wouldn't necessarily be possible without using external tools if TWRP wasn't there for us. Mobile device companies don't really support or encourage users to do this.
BOOTLOADER: Default state is locked on our and on most devices. Without unlocking it, it would be extremely hard if not impossible for us to flash custom ROMs on our mobile phones. You can unlock your bootloader by following this guide if you haven't already done that because without unlocking it, flashing global ROM on your device which comes with Chinese one preinstalled will likely be impossible at least not known to the RM5P/RMQ community so far.
MAGISK: Systemless solution which grants root access (admin-like) to the user without really tampering the ROM system, this way granting higher stability than it's predecessors.
5) Precautions:
If you aren't an advanced user and don't really know what you're doing follow the steps closely and it's highly advised to read the basic expressions to understand better what's happening just in case something goes wrong so you can fix it.
External SD card is highly recommended to use because to make this work formatting data is quite likely needed.
If you want to bring your data with you from your current ROM make sure to do either Titanium or Migrate backup and save it to your external SD card.
TWRP for RMQ (this one I highly recommend to use for it has a wide range of features and options that come in handy, unlike normal TWRP)
Magisk if you want root or/and want to pass Google's Safetynet completely.
Magisk COS beta FIX from here (step 6)
Modified vbmeta.img from here. (step 6)
Magisk modules: Busybox and MagiskHide Safety Props Config. (from inside Magisk Manager after successfully rooting with Magisk flashable zip file)
6) Prerequisites:
{Mod edit}
Probably formatting your data.
This means all your stuff, apps, data will be gone after you do this so be prepared and save your stuff to your external SD card.
7) Installing:
A) If you're coming from custom ROM then:
1) Wipe everything (except internal and external storage) including /data/system/dalvik/cache/ but not vendor and vendor shouldn't even appear in the list when wiping anyway.
2) Flash the ROM.zip
3) Flash TWRP.IMG as recovery and again flash it as boot.
4) Flash vbmeta.img as vbmeta.
5) Reboot even if you get notification "no OS is installed".
6) If you're stuck on boot logo for 15+ minutes or bootloop then turn off your device volume up+power then right after shutdown vibration and black screen enter fastboot mode by holding volume down+power, from there select recovery and you should be back to TWRP recovery
7) Select wipe and format data by typing "yes". This will delete all data on internal storage so take care.
8) Reboot to system
9) The device should boot up to COS. Do the initial setup and after that reboot to TWRP recovery again.
10) Flash Magisk.zip
11) Reboot to system
12) Enter Magisk Manager and disable core only mode
13) Reboot to TWRP recovery... again.
14) Flash Magisk COS Fix beta.zip
15) Reboot to system.
16) Check Magisk Manager. Core only mode should be turned off. Check SafetyNet Status. BasicIntegrity should be true now.
17) Download and install MagiskHide SafetyProps and Busybox from Magisk downloads.
18) Reboot to system (normal reboot)
19) Enter Magisk Manager and see if the two installed modules are active. (If yes you probably done everything well. If not, something is fishy.)
20) Download any terminal emulator app, I recommend Termux. Open it and by typing "su" without quotation marks and pressing enter you should grant root access to the terminal app you use. Now type: "props" and press enter.
Type 1) and press enter as edit device fingerprint.
Type f) and press enter as pick from certified fingerprint.
Type 6) and press enter as Google (you can use others too but I used this one so it should be tested).
Type 21) and press enter as Google Pixel 3a XL.
Type 1) and press enter as Android version 9.
Type y) and press enter as yes.
21) Reboot to system and open Magisk Manager. Check SafetyNet Status. Now both cts profile and basicintegrity should be true.
22) Enjoy your better Color OS.
B) If you're coming from stock rom:
If you haven't unlocked your device's bootloader it's time to do it.
After unlocking install TWRP for Realme Q. Then follow the steps above for they're the same.
Don't report issues. I can't help for I'm no developer and I've dyscalculia which means I should be bad at every Informatics stuff that requires math/logic thus I can't compile/rebuild/update ROMs. As for the developer he lost his phone so it's not his interest anymore to make fixes and updates for the ROM/device. Probably pointless to bug him.
Click to expand...
Click to collapse
ROM modified/made by: Birman34
ROM data/turorial written by: greenys'
ROM brought to you by: Realme 5 Pro/Realme Q global Telegram group
{Mod edit}
ROM information:
Security patch date: 2020.01.05.
Kernel version: 4.9.112
Build number: RMX1971EX_11.A.16
Android version: 9.0
It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!
bahuy2003 said:
It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!
Click to expand...
Click to collapse
Well, yes. I wish I had found a simpler method but I didn't and I wanted to make sure everything is going to work fine without letting issues happen during or after installation. Perhaps it seems complicated because of that and that I didn't want to take chances. Better be safe than sorry, I presume. For me, who has been flashing ROMs since 2010 it didn't take more than 5 minutes to complete all the steps. Evidently there are lots of users who just gotten into bootloader unlocking and don't know much about the details of flashing. That's why I tried to make this guide quite well detailed. Anyway, if I find a simpler way or I get know of an easier method or Realme itself will approve the change between regional ROMs I'll add those steps to my post of course. Don't thank me yet. Thank me if it worked btw!
Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ??
nagar.xda said:
Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ?
Click to expand...
Click to collapse
According to my knowledge official ROM change from global to China or vice versa is not possible. I don't know about OTA updates. I presume you can't update that way if you flash this ROM for as you said different partition sizes. This ROM while it's still made from global, several stuff from system were removed so it'd still fit onto an RMQ device's smaller partition. The ota updates are not modified this way so I think you couldn't update that way because the ota would be too big to fit onto the RMQ device's partition. I believe you shouldn't worry about root and bootloader unlock. Without rooting and using safetyprops Google notices your unlocked bootloader thus both cts and basicintegrity will fail. In my tutorial I go through that bothersome Magisk method to trick Google's security system. After doing that both SafetyNet checks pass, meaning Google shouldn't see your device as rooted. Root is dangerous for some apps because it can trick them. Unlocked bootloader is dangerous for the device and its owner. At least according to Google. Meaning with Magisk SafetyProps applied only DRM Widevine stuff shouldn't work completely like Netflix full HD and above. Every other app that requires certified device fingerprint should work. Banking apps and online purchases work just fine for me. I think you shouldn't worry, only if you're the type of guy who wants ota updates badly and watches DRM protected content all the time. Else this is completely safe ROM.
greenys' said:
...
Click to expand...
Click to collapse
THREAD CLOSED due to the distribution of warez.
XDA Forum Rules (excerpt).
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...
Click to expand...
Click to collapse
I'm stuck with trying to get ArrowOS to work on my Pixel 2 XL Taimen.
Bootloader is unlocked, I have flashed TWRP 3.6.0_9-0-taimen onto the Pixel.
At some point I was able to move Arrow v12 and GAPPS zip files to the pixel by dragging the files to the phone in Windows. I was able to see the zip files in windows on the phone, but could not see them in TWRP, all the folders had lots of mixed up numbers. Eventually I found the files with File Manager in TWRP, but couldn't do anything with them. I think I have since wiped everything and can't find them now.
on my pc in SDK/platform tools, I can CMD adb devices and see the phone, but if I run fastboot devices, nothing. I have the Google USB driver activated and can see it as an Android Device in Device Manager on windows.
All I can do on the phone is boot to bootloader and get into recovery which takes me to TWRP. If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Did I just brick my phone? any suggestions on what i can do?
Restore your unit using the full stock ROM package - NOT OTA - from Google. That will get the unit working. To install any ROM you need to do the following.
1. Remove fingerprints and pin numbers from the device. This should disable encryption.
2. In the command prompt boot into TWRP. Do not install unless you want a bootloop.
3. Install Arrow.
As an alternative to 1 above, a USB flash drive with the USB adapter Google includes in the box will also work.
To expand on what @Strephon Alkhalikoi said:
1) TWRP seems unable to handle the encryption used by Android 12, so you probably can't download the new rom to the phone - however sideload should work
2) You should have the baseband and bootloader from the last stock rom installed
3) fastboot devices should work when the phone is in bootloader mode, whereas adb devices works in recovery
4) you may have to format data in TWRP, to clear any incompatible encryption - note that this will delete all the files on your phone
I did the alternative option with a usb drive...worked perfect...thank you so much for helping me!!!
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
bguzz said:
One question...this is my first time installing a custom ROM. I really wanted to try out Android 12 and it is working really well. But my question is, from a security perspective, how secure am I in this mode? not like physical security if someone stole my phone and tried to get in, but secure from online hacking? Will security updates come to me OTA? or will I have to load them from ArrowOS site? I've been on the unsuported updates of Android 11 for a year, so I'm guessing more secure than that?
Click to expand...
Click to collapse
bguzz said:
also, do the Android 12 widgets not come in this ROM, or the GApps ROM? is there a way to get them installed?
Click to expand...
Click to collapse
I believe the ArrowOS developers are working on adding OTA functionality. In the meantime you can flash an update using the USB stick, or you can use adb sideload commands. If you are worried about people accessing your data, a pin and fingerprint lock does wonders.
Which widgets? If you mean the widgets found on the Pixel 6 series, those are exclusive to the Pixel devices: custom ROMs won't have them unless the developer pulls copies from a Pixel 6 / 6 Pro and adds them.
Makes sense. Thank you again.
One thing to make sure if you care about security, is that SElinux is set to enforce. This is an essential security feature that is pretty tedious for the dev to get working, so sometimes it is left as permissive.
Unfortunately, I don't know which roms have enforcing SElinux. If it doesn't say so in the rom's thread, you'll have to install and check.
bguzz said:
If I try to ADB Sideload the ArrowOS zip file to the phone (using sideload in TWRP at the same time) the system just hangs.
Click to expand...
Click to collapse
Try connecting the Pixel 2 XL through a USB hub. I had the same problem in recovery mode and the USB hub solved it.
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, i will laugh at you.
Click to expand...
Click to collapse
Simple guide to use LineageOS 20 with Android 13 on Samsung Galaxy S21FE Snapdragon version (SM-G990B/DS)Should work also with Exynos version.
Unlock bootloader first:
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
Click to expand...
Click to collapse
Flash recovery for snapdragon version, i'm using: OrangeFox Recovery
Please do everything that is written for flashing recovery (Installation), u need to disable encryption and wipe data
reboot and check if phone is on "hello screen"
How to boot on recovery first time:
Uncheck reboot after flash AP in Odin, unplug cable and then push vol - and power -> immiedietly after turn off download mode hold vol + and power and plug in cable -> now should work
Flash GSI image:First you need to download image from here: Image with Google Apps or find image here: all images here
Remember to use arm64 with b !
Reboot to recovery
Now u should see on PC when u connect via cable internal memory - copy image to folder, probably should be "Fox" or create new
Touch files, find image
Now select to flash System image
Reboot
And thats it you should boot to system.
Post install settingsOn Phh Treble Settings set:
Samsung features:
Use alternate audio policy
Enable stereo audio mode
Enable extended brightness range
Enable double tap to wake (if u want)
Enable reversed wireless charging (if u want to reverse charge other device)
Enable access to all cameras
Enable extra sensors
Misc features:
On Display set rounded corners diameter to 44
Force FPS to [email protected] if you want 120Hz refresh rate display
On camera set expose aux cameras and force enable camera2api
To disable AOD u need to uncheck quick setting on desktop.
That works:
Dispaly with 120Hz
WiFi (5GHz too)
Sound with stereo
Camera back and front
RIL also works (mobile data checked)
MHL
Fingerprint sensor
Bluetooth audio (tested on Galaxy Buds 2)
And probably rest of functions
Not working/problems:
Google Pay app nor NFC
Galaxy wearables
Device have strange model build name, so most of the apps will be problematic.
Root image to flash after boot to GSI:
WARNING! Boot image comes from G990BXXS2DVL1/G990BOXM2DVL1/G990BXXS2DVL1 version! (EUX) You need to create own root patched image if not use my stock samsung rom version that i have before GSI!
Instal magisk
copy image here to download to internal memory
flash via recovery boot image
reboot
go to magisk select yes for popup message
reboot
viola!
Thanks for support. When is it coming to exynos?
you can also flash build on exynos soc, but u need recovery for exynos. Is similar to snapdragon, just to remember to know how to flash.
Master , I hope that nfc will be fixed in this version cuz is really needed. Call recording is working ?
originalul said:
Master , I hope that nfc will be fixed in this version cuz is really needed. Call recording is working ?
Click to expand...
Click to collapse
I'm not your master ....
NFC works with root and safynetfix, don't using call recording so i don't know.
Is it possible to change the device type?
gunar74 said:
Is it possible to change the device type?
Click to expand...
Click to collapse
With magisk hide props
joke19 said:
With magisk hide props
Click to expand...
Click to collapse
Can you help me with it?
Tried with this beta: https://forum.xda-developers.com/t/...re-forked-and-ready-to-go-live-again.4510729/
but not success. It is enough me when it emulates for example S20 FE or similar.
Also tried with latest official, but the app, which is need to it still shows TrebleGSI.
because we need to change something in build.prop not via hide props. someone with root on stock samsung rom need to copy all strings from build prop and upload here. Changing name on settings do nothing, because on google accounts still show something like GSI-romish phone. And safetyfix only hides phone on g appstore and on gpay to simulate vaild phone.
of course no one cares to make full ported rom only some s**ty oneui ports, so we can only use GSI system image. Still - all cameras dont work even if you try to use via opencamera.
I flashed this to my s21 fe and it all went fine till I found out the fingerprint scanner doesn't show up at all in settings?? Is anyone else having this issue?
Can't download anymore as zippy share has gone. As of 26th April
if you want to root phone u need to extract image from stock firmware or put AP image to internal memory and in magisk patch it and flash. (or just extract boot.img, patch and flash via recovery)
So my recovery only gives me these options.
Billabomb75 said:
So my recovery only gives me these options.
Click to expand...
Click to collapse
dude.. just scroll down xD and u see system
hunter3000 said:
dude.. just scroll down xD and u see system
Click to expand...
Click to collapse
It doesnt allow me
on my fox recovery im able to scroll down, so on your side is something wrong, or try twrp or other recovery.
hunter3000 said:
on my fox recovery im able to scroll down, so on your side is something wrong, or try twrp or other recovery.
Click to expand...
Click to collapse
I just reflashed it now. Will see now.
hunter3000 said:
on my fox recovery im able to scroll down, so on your side is something wrong, or try twrp or other recovery.
Click to expand...
Click to collapse
Worked now... Flashed Lineage but having issues with apps with Root although they hidden from Magisk and Magisk is Hidden. so switched back to Slimsang..
May I know if VoWifi / VoLTE works?
Samsung Galaxy 21 Fe 5G I can't find oem unlock t mobile G990U