Develop Bugs

[GUIDE][ROM] Realme 5 Pro global ROM for Realme Q

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

Red Magic 5G BackUP Request

Hello XDA Forum
I have a little problem with my Red Magic 5G
I accidentally deleted the parameter files and also other important files out of stupidity and wanted to ask whether someone has a red magic 5g and can make a backup via twrp and send it to me? < I really don't know what to do anymore >
I have flashed new software with edl on it and installed all 3 rom versions but I still have the same problem non of them worked i can't even install custom rom anymore.
Best Regards
Akizuma

Has really no one a backup for me left for the red magic 5g ?

Hello, what parameters are missing in your red magic5g, can I help you? I use red magic5s

(I think everthing)
I need a twrp backup from a red magic 5g where everthing still works i destroyed to much,
Not even touch working anymore in twrp.
Edit ( I think not that 5s works on 5g or ? )

you don't need anything from someone else's device.
if you ****ed something up. then you need to use the unbrick tools. and set them up correctly and follow the directions to unbrick.
they will erase all your data. but form what I've read, you lost all that already.
there are unbrick tools for both devices. 5S or 5G on either forum for those devices make sure you're using the correct unbrick tool. 5g does not work correctly with 5S devices, and vice versa.
the unbrick tools will format and restore every single parition on the phone. restoring it to factory settings.
its very possible though if you were messing with partitions that you erased your IMEI.
if thats gone, its beyond the scope of the unbrick tools. you'll have to contact warranty services.
the unnofficial unbrick tools by Johnny in my opinion better.
just make sure your drivers are correctly installed, and up to date. .. this includes windows updates.
(recently there has been a google ADB driver that needs updating thats available through winodws update)
so make sure thats installed too.
set your phone to EDL mode and follow the direction on Johnny's thread.
it will restore your phone as long as you can get to Fastboot mode. (vol down and power)
PM me if you need more help. but that should be enough to get your back to stock.

Problem Fixed ! #closed

@Akizuma it would be kind to post what you did to fix the issue, so others in the future who are faced with the same issue can use your solution.
We are a community here to help others.
If we mention that our problems are sorted, without posting how, it only helps the direct user and other searching for solutions to fix their issues will continue.
Please post what it was you did to fix your issue. It would be very appreciated.

If you're having any of these issues, this option may be able to fix it.
Problem: black screen after boot up, touch not working (TWRP) or automatic booting in EDL mode
First download the Unbrick EDL Tool
(I chose EU)
Download here:
[Tool] Nubia Red Magic 5G Unbirck Tool
So.......It's finally here, the unbrick tool for RedMagic 5G. This tool can help you to unbrick the phone. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm...
forum.xda-developers.com
Then follow the instructions in the folder and install an operating system on it through edl mode
Then you start the installation again but this time you don't run it because I noticed that the tool doesn't flash important image files but skips them (you can even find it in the log)
First go to \ AppData \ Local \ Temp \ is-K4OSH.tmp \ NubiaEmergencyDownload \ software
(name can be different)
And copy
persist.img
boot.img
odm.img
recovery.img
system.img
vendor.img
And put it in a new folder
After that go to the bootloader again and unlock the oem via
(fastboot oem nubia_unlock NUBIA_NX659J)
Then execute following commands for the files like
(Command (Fastboot flash persist [file.img])
(Command (Fastboot flash boot [file.img])
(Command (Fastboot flash odm [file.img])
(Command (Fastboot flash recovery [file.img])
(Command (Fastboot flash system [file.img])
(Command (Fastboot flash vendor [file.img])
It can be that most of them give out an error, execute them anyway in case the folder still exists
Then the cell phone should start again normally.
P.s ( Sorry for my poor english ^^ )

System, Vendor, and odm, are all partitions flashed during the "super" partition.
this is why you didn't see them exactly written in the log they all go under "super" and get assigned a dynamic partition when flashed.
you cna see here how they changed the partitions and how they're written now.
Implementing Dynamic Partitions | Android Open Source Project
either way. thank you for your effort to your solution.

How To Guide guide unlock bootloader & enable root (magisk)

Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* 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 kernel
* 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.
*
*/
GUIDE UNLOCKING BOOTLOADER & ROOTING Xperia 10 III (PDX213)​STEP 1 - UNLOCK YOUR BOOTLOADER
1- GUIDE UNLOCK BOOTLOADER XPERIA
2- WEB UNLOCK TOOLS BOOTLOADER XPERIA
STEP 2 - DOWNLOAD FIRMWARE STOCK USING XPERIFIRM
STEP 3 - extract boot_X-FLASH-ALL-8A63.sin using zip file manager ( 7zip, for ex here I used Ark zip manager from Fedora OS)
rename boot.000 to boot.img
STEP4 - install magisk manager in your phone from official github release
- open magisk patch your boot.img
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
ENJOY

Nice! Now maybe someone can look into fixing that green tint.

zpk787 said:
Nice! Now maybe someone can look into fixing that green tint.
Click to expand...
Click to collapse
idk what issue your referering ( maybe thread green tint in oled
? ) here I have totally normal screen color

So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?

pepijndevos said:
So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?
Click to expand...
Click to collapse
For some reason bootloader no allow fastboot boot
Need : fastboot flash boot patchedboot.img

Yea it's just really scary to flash a patched firmware, what if you did it wrong and it bricks your phone. But well in the end I did it and everything worked out.
One really weird error I get from Magisk is that it says it's in an abnormal state because there is a "su" command that doesn't belong to Magisk. I have no idea where that came from. Should I be concerned? Everything seems to work as far as rooting is concerned, but mysterious su commands could be a security concern maybe. I hope it's not a sketchy GSI or something hehe.
Anyway thanks for your guide. I have MicroG and F-droid working now, as well as ACC. One thing I'd clarify about your guide is that "going into fastboot" is... actual fastboot and not bootloader or recovery which you also use with the fastboot tool. Just a thing that's obvious when you know, but uncertain when you're doing it for the first time.

Oh and another thing that was sliiiightly puzzling is that you actually have to copy the boot.img to your phone, patch it and then copy it back to your PC. Same thing, obvious when you know, kinda puzzling when it's your first time. For me it didn't show up in the file manager after patching so I had to copy it with adb, not sure what that was about.

Did anyone notice negative effects after rooting?
Is the camera working fine?
Is Bluetooth working, the microphone and calling?
Is safetynet check passing?
My main goal is to have Adaway working in root mode and have stable Wireguard VPN connection (without battery saving methods killing the process every few minutes), I will try custom ROMs after I get the rest to run.

Camera, bluetooth, microphone, calling, all working fine. No idea about safetynet haven't checked. As mentioned above, it does say I have an extra `su` that I don't know where it came from.

Did you do any backup of the TA partition (if that is even neccessary)?

I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.

pepijndevos said:
I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.
Click to expand...
Click to collapse
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!

Raubsau said:
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!
Click to expand...
Click to collapse
This is exactly the reason why I haven't rooted my device yet, too. If I understand it correctly, data in the TA partition is modified at the time the bootloader is unlocked, so if we were to create a backup, that would have to happen before unlocking.
The partition is only readable with root privileges, and rooting in general requires an unlocked bootloader. The only way forward is to wait until an exploit becomes available, allowing us to obtain a root shell with the bootloader still locked.
Hopefully it's possible to flash older firmware onto this phone, which would mean we can downgrade to an older Android security patch level if needed (i.e. the potential exploit gets patched by Google or a vendor) - does anyone here know if that's the case? When installing an OTA update, the UI says we won't be able to return to a previous version, but I suppose it's still possible to flash any of the official firmware packages at any point.

Thanks.

Is there any way to get OTA updates while rooted? That's what I loved about LOS. Maybe we'll get it on this device someday.

Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted

Unfortunately many users report a WLAN issue with 62.0.A.3.163.
62.0.A.3.131 cannot be downloaded anymore, except the french (FR?) localized versions. Also, I managed to install 62.0.A.3.131 on a 10 III, but denied the update to the latest version to avoid the WiFi troubles.
The boot.img from 62.0.A.3.131 (FR) and 62.0.A.3.163 (EE) differ. I wonder if anything could go wrong with the newer boot.img.
To my understanding, the boot.img contains the kernel... So, I'd like to test it with "fastboot boot boot.img" before I risk flashing, but: "remote: 'unknown command'".
Any suggestions on how to proceed from here?

You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/

ZenRebel said:
Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted
Click to expand...
Click to collapse
If you've managed to unlock your bootloader, that means you have already entered fastboot mode.

combinedfleet said:
You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/
Click to expand...
Click to collapse
Man! Thank's a lot!
Any idea why the boot_X-FLASH-ALL-8A63.sin files differ slightly even if compared between markets (with the same version numbers)?

[GUIDE] [ROOT] Fix the Qualcomm CrashDump: Keep your data, apps and retain root.

This will not work if your phone bricked after updating to Android 12. You should use the MSM in this case. This guide details downgrading to an earlier version of Android 11 FROM a newer Android 11. You have been warned.
This evening after updating my phone (installing to inactive slot + flashing with Magisk as I have done many times before), I restarted only to receive a Qualcomm CrashDump.
Unlike what I've read online, my one seemed to be a bit more severe. I could not boot into recovery mode (black screen; had to power phone off) and entering Fastboot did not fix the issue. After spending several hours reading through XDA, Stack Overflow, various other sites etc I finally managed to get it fixed. Not only that, but I kept ALL my data AND my root. It's like nothing ever happened.
The issues I faced:
- Mistakenly had USB debugging off (which cannot be enabled when your phone is soft bricked). This made using ADB for initial diagnostics virtually impossible
- Recovery mode showed a black screen; not accessible.
- Installing TWRP, only to find my device passcode (PIN) wasn't allowing me to decrypt my phone data so I could make a backup
- My phone was buggered
How I solved it: Given recovery mode was blank, I flashed TWRP to my recovery drive via Fastboot to bring it back. Because USB debugging was OFF and TWRP wasn't decrypting my data (meaning I couldn't back up any data or download the ROM to my internal storage without wiping it), I activated ADB Sideload within TWRP and then used this to downgrade my version of OxygenOS! After a reboot I received the Qualcomm error one more time, before it continued to boot into OxygenOS with all my data intact.
Your bootloader should already be unlocked. If it isn't, chances are you will be saying goodbye to your data
These steps may not work for everybody, but I wanted to give back what I learned from this, and it was rather unconventional and against the grain of what others have suggested. With that said, do so at your own risk.
This is a simple guide. I will explain the tools you will need and how to fix the issue. Anything beyond that (i.e. installing SDK platform tools) can be researched.
This is written assuming you are on Windows, although the steps are generally quite similar.
Tools Needed:
A computer to download and install:
- SDK Platform Tools/ADB (https://developer.android.com/studio/releases/platform-tools)
- TWRP for OnePlus 8 Pro (https://forum.xda-developers.com/t/...wrp-for-oneplus-8-8pro-official-beta.4341707/)
- OnePlus 8 Pro Drivers (You will need this installed if it isn't already for your phone to appear in SDK Platform Tools. You may need to disable driver signature enforcement on Windows 10)
- The version of OxygenOS you were running before the CrashDump occurred (https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
Steps to take - Initial Setup and Installation of TWRP:
1. Download everything above and then install SDK Platform Tools + OnePlus 8 Pro Drivers if you don't already have them.
2. Enter Fastboot mode on your phone and then connect it to the computer.
3. Ensure the TWRP .img file is in the same directory as your SDK Platform Tools install
4. Open up command prompt with SDK Platform Tools installed and type in
Code:
fastboot devices
Confirm your device ID appears along with "fastboot" beside it.
4. If the device is being recognised, we're ready to install TWRP. Note: Remember your Bootloader must be unlocked for the next steps. While in Fastboot mode, your phone will tell you if your bootloader is locked or unlocked. Now that we've confirmed it is unlocked, Type in:
Code:
fastboot flash recovery_a twrpname.img
followed by:
Code:
fastboot flash recovery_b twrpname.img
5. You can now boot into recovery mode! On your phone, use the volume keys to navigate and choose Recovery so you can enter TWRP
Downgrading to an older version:
When I installed TWRP, I was horrified to see that I couldn't decrypt my phone with my pin code. Apparently this is an ongoing problem with TWRP and the ability to decrypt your phone data varies between devices and builds of TWRP.
1. Now that you have entered TWRP, enter the "Advanced" settings and enable "ADB Sideload".
2. On the computer, type in
Code:
adb devices
. You should see your device appear.
3. Ensure the OxygenOS file is in the same directory as your SDK Platform Tools install
4. Type in
Code:
adb sideload updatename.zip
and let it flash to your phone.
And that's it! Reboot your phone. You may receive the Qualcomm error one last time, so kiss that sucker goodbye with a final reboot (I pressed power + volume up but then it continued to boot as normal; much to my surprise) and you should be good to go.
Hope this helps. This is my first ever guide, but my phone bricked itself this afternoon and it took me 3-4 hours of research to figure out what to do. This community played its role in helping me, and I'm sure someone out there will appreciate this information - definitely wanted to give back. I didn't see any information like this outside of wiping the phone entirely... I'm pretty stubborn and didn't want to do that.
This is definitely a "dirty flash", although given I couldn't even boot into the updated version, I would say a downgrade is definitely just fine in this instance.

I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.

xtcislove said:
I assume that you where using Android 11?
Because in the current situation with android 12 and hard bricking your phone with fastboot flashing this guide is potentially dangerous. As far as i know you should not flash twrp to android 12 right now.
Please correct me if i mixed things up here or if i am wrong. Its better to loose data and use MSM if you are concerned.
You might wanna include this guide in case someone needs to read it before doing anything.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anyway thanks for your effort here.
Click to expand...
Click to collapse
Thank you and you're right. I've added this warning to the top of the post!

Lineage not working - Moto should be compatible

Hi everyone
Below is a cross post from another part of xda developers and reddit.
I got a reply to the post below telling me that Moto Cedric was not an "official" build. I was basing the installation of Lineage on this link: https://wiki.lineageos.org/devices/cedric/ so I'm confused. My phone satisfied all of the requirements. Any help greatly appreciated. Phones are not my strength so I'd be very interested to get opinions as to whether this phone is retrievable, or not.
I have just had Lineage 18.1 put on a Moto G5 (the correct build and model according to the Lineage compatibility guide). There are two problems that stop it working:
The phone will not allow me to connect to the mobile network telling me that 'airplane mode' is enabled and that I need to disable it. Thing is that 'airplane mode' is not enabled. I have tried toggling it on and off with no luck. The phone recognizes the carrier correctly but it won't connect.
The phone is dual sim but it will only pick up one of them telling me that the other sim is disabled.
I didn't flash the phone, I paid someone to do it. When they did it they were a bit surprised that they were able to put 18.1 on it due the age of the phone or something. Would flashing it with 17.1 be a better option? Pardon my total ignorance with this subject.
I can't find any information that helps with these issues so I'd appreciate any help. Phones aren't my strong point I'm afraid so I'm stuck.
Thanks

Do you have stock kernel,vendor?
Give me the model number

Thanks for the replies. Its a Moto G5, Cedric, model XT1676 16gb P5
I didn't do the work on this but I know that it ran into an initial problem here:
https://forum.xda-developers.com/t/...1-lineageos-18-1.4260293/page-9#post-86445333
The solution that is mentioned there was followed and Lineage installed ok but it has the problems above.
I don't know how to get the kernel? And if by vendor, its a Lenovo.
Thanks

I appreciate you taking the time out to have a look at this. I'm signing off now but will check back tomorrow. Thanks.

ok i will update you soon

TUTORIAL:
-------------------------------------------------------------
Donwload file's:
>Rom: mirror EU
>Recovery: mirror EU
-------------------------------------------------------------
-Make sure your computer has adb and fastboot. Setup instructions can be found here.
-on adb open cmd and type "adb reboot bootloader".
-Once the device is in fastboot mode, verify your PC finds it by typing "fastboot devices".
-copy the recovery file onto adb folder.
-Flash recovery onto your device: "fastboot flash recovery <recovery_filename>.img"
-Now reboot into recovery to verify the installation:
-With the device powered off, hold Volume Down + Power, then select “Recovery mode” using Volume keys.
-------------------------------------------------------------
!Optionally, download an application package add-on such as Google Apps (use the arm64 architecture)!
-------------------------------------------------------------
-Go onto recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: "adb sideload filename.zip".
(Optionally): If you want to install any add-ons, repeat the sideload steps above for those packages in sequence.
then Reboot System.

>The dualsim problem can be a rom problem is a generic error.

Topo's said:
>The dualsim problem can be a rom problem is a generic error.
Click to expand...
Click to collapse
Thanks for the reply and the tutorial instructions. I have not done phones but I did manage to flash a Google Nexus 10 tablet with what appears to be an almost identical procedure.
I'll give this a go on the weekend with a clear head.
I forgot to mention that over on the Reddit sub dread (which led me here) one of the posters suggested that the sim slots sounded like they were fried because the phone wasn't reading them.
But, I really thank you for your help. I'll give it a shot.

No problem, thanks you for the question

Just another quick question. Using the method you recommend, that I think is something that I can do, am I likely to end up in the situation (link below) that I mentioned above? If so that looks like a whole other level of stuff for my meagre phone talents. Not having done the install myself I am not sure if your method is a re-install of what was done initially?
[ROM][OFFICIAL][cedric][11] LineageOS 18.1
#include /* * Your warranty is now void. * * 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...
forum.xda-developers.com

My method is basically reinstalling Lineage Os but in a correct way.

Maybe it can solve some bugs about the Motorola.

Got it. I'll give it a go. Thanks.
One last question. Does the "Google Apps" package link the phone to Google? This is what I am trying to get away from. Sorry of this is a basic question, but I see "Google" and I wonder

theredpoppet said:
Got it. I'll give it a go. Thanks.
Click to expand...
Click to collapse
Thanks to you!