Disclaimer
Builds are provided AS-IS without warranty or repair. I am not responsible if you brick your device.
About
I was using the existing TWRP build that's been floating around and noticed it had a few issues, so I made a device repo and rebuilt an improved version.
Noteworthy features:
English language defaults
Added support for microSD
Added support for USB storage mounts
Added support for userdata encryption
Support for MTP and ADB
Added backup options for DTBO, verity meta, OEM partitions
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
Downloads are available at https://github.com/shinyquagsire23/twrp_sony_pdx203/releases/
Flashing
Flashing is only supported on phones which have an unlocked recovery and verified booting disabled!
Code:
#!/bin/bash
# Reboot to fastboot
sudo adb reboot bootloader
# Flash recovery img
sudo fastboot flash recovery recovery.img
# Reboot to recovery
sudo fastboot reboot recovery
Source Code
Source code is uploaded at https://github.com/shinyquagsire23/twrp_sony_pdx203/. I also provided some brief compilation instructions in the README.md for anyone interested.
Special Thanks
Thanks to Sjll for twrp_sony_pdx201, which I based my repository on.
Thank you, I will be testing this weekend.
Very cool, thanks for sharing.
You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!
Junior-J said:
You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!
Click to expand...
Click to collapse
thats why older Samsung phone running android 7 and lower are considered the safest. they have a inbuilt download mode to recover their software incase of a bootloop. but xperia phones aren't the hardest to root either since they are one of the most used. only problem is that some xperia phones will have their recovery menu and commands etc in chinese/japanese depending where you bought them.
Thanks for sharing,Great Works ~!
Does this not support decryption? I wasn't able to get in with my password using this version of TWRP, but I was with OrangeFox.
Can you give me build.prop from Sony xperia 1 ii Please? give me in my mail or telegram : t.me/Info_Shakib [email protected]
Seems there is a fix for fastbootd @ https://gerrit.twrp.me/c/android_bootable_recovery/+/2910
If I have time next week I'll try patch and make PR shinyquagsire23 unless someone does it first..
Can someone tell me how can to compile twrp recovery for xperia 1(j9110). I need some guidance. Thanks.
TWRP flashed on xq-at51 android 11 without any issue, thank you for the guide
Is it work for experia 1 iii ???
recovery not booting up after flashing stock android 12 january patch, the screen keeps getting splashed with the logo of twrp
Ask, Pixel Experience Plus 12.1 v413 is only img after decompression, can only use TWRP to flash the machine, 1ii 12 has no TWRP available, whether to downgrade 11, use TWRP to flash .img, which partition to flash into TWRP, still trying to learn, Please enlighten me.
Thanks so much. Exceptional.
Works on XQ-AT51 (Europe, dual SIM) . Flashed twice to _a and _b. on Android 11.
I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help
marcvie said:
I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help
Click to expand...
Click to collapse
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/
Gunseng said:
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/
Click to expand...
Click to collapse
Thanks for the reply, that will be handy for flashing, but i eventually got my 1ii rooted using this guide: https://www.getdroidtips.com/unlock-bootloader-root-sony-xperia-1-ii/
If u r on Android 12, just use recovery of this thread:
[ROM][Officiall][pdx203][12.1] LineageOS 19.1
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Not twrp but almost the same (lineage).
Flash recovery, then "fastboot reboot recovery"
And this is really working on a rooted stock rom ?
Related
So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-
Thank you! TWRP worked as intended, installed root manually. Donated as well.
TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..
Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864
Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse
unlock with developer rom
XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..
yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock
Magisk not detect root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks
Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?
How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main Highlights
✪ MTP support
✪ Can flash stock os Images
✪ Backup/restore works with any os
✪ Restore your old twrp backup
✪ Optimized and faster
✪ Build On A29 Pre Built Kernel By Realme
✪ Full compatible with color os
ScreenShots
Download Link:
https://mega.nz/#!5gYnjQSB!YhC_ZTHuopwwP50LxTvJ1VOq4zYSfG0LAudWr6gatUA
Code:
Bugs
:GSI Flashing Has Some Issues
:If You Finds Any Other Bug Then Report Me
Credits;
AnuragRai(Developer)
Hamza(Tester)
RK(Tester)
Jatin(Tester)
MKS(RM2p Dev,Always Supported Me)
And Whole Realme Tester Team
XDA:DevDB Information
TWRP[UNOFFICAL]-BETA-BUILD-[12-03-2019], Tool/Utility for the Oppo Realme 1
Contributors
anurag rai, hamza
Version Information
Status: Beta
Current Beta Version: 01
Beta Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
Flashing Guide
Code:
[CENTER]
:adb reboot bootloader
:fastboot flash recovery recoveryname.img
:reboot phone manually ,not from fastboot
:After phone boots up,power off it
:Press Power Button+Volume UP &Down For Approx 20 seconds
:After You Are Inside Of Twrp,do this
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Reserved
Thankyou bro..
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
anabhi said:
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
Click to expand...
Click to collapse
Bro can you help me with fixing reboot to recovery issue
anurag rai said:
Flashing Guide
Code:
[CENTER]
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Click to expand...
Click to collapse
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
It's Working ! Thanks Alot Mate.:victory:
awesome work bro.. thnks a lot u r too fast..
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Awesome man!??
svsexodia said:
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Click to expand...
Click to collapse
Yes you can
manavkush said:
Flashing Guide
Caution
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
Click to expand...
Click to collapse
Charge it bro
Realme 1 - Treble Rom
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
johndoe5 said:
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
Click to expand...
Click to collapse
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
It's_Shawn said:
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
Click to expand...
Click to collapse
Which TWRP did you use?
And where can I find the stock firmware?
johndoe5 said:
Which TWRP did you use?
And where can I find the stock firmware?
Click to expand...
Click to collapse
That Time I Didn't Use Any Recovery,I Used Fastboot Commands
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
5s4rnv33r said:
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
vikas2316 said:
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
Click to expand...
Click to collapse
Updating OS will remove root but will it also remove TWRP ???
One more question I followed all the steps correctly (including wiping data) but from TWRP I can't mount DATA.
---------- Post added at 10:01 PM ---------- Previous post was at 09:13 PM ----------
After wiping data if I just reboot to TWRP recovery then I can mount the DATA but once I have started the phone and set it up then again I boot into TWRP recovery and when I try to mount DATA I am not able to do so. Can't mount /data invalid argument. Please suggest something.
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
https://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Note: The one for xiaomi.eu is custom rom, not stock EU.
If you can't find a patched boot.img for your version, you can also patch it yourself with this tool:
http://www.mediafire.com/file/c5e0idf6cy5ap25/patcher.7z/file
(follow instructions in readme file; credits to Russian 4pda forum)
Where i can find xiaomi.eu ROM for this device?
NV-Dev said:
Where i can find xiaomi.eu ROM for this device?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261652844
Can you please upload patched boot for 11.0.2 indian rom???
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
anonymousfun122 said:
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
Click to expand...
Click to collapse
Here for you
Mokee_boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not working for me
Auto Reboot to recovery
It worked
sjcbank said:
Here for you
Mokee_boot.img
Click to expand...
Click to collapse
Thank you so much !!! It worked instantly . I was trying weeks to make magisk working on the mokee rom.
Thank you !!
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Tenome7 said:
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Click to expand...
Click to collapse
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
sjcbank said:
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
Click to expand...
Click to collapse
I've been toying around with Android since it's Lollipop versions, rooting them, intalling custom ROMs etc. Probably 6 years. More than 7 devices.
As far as installing a custom ROM on this phone (Redmi 7A) is concerned, the different versions, like Indian, Global have different drivers or HAL's.
So, after successfully booting up into MOKEE OS on my variant 3-4 times, Torch, Audio, Video, Calls...... Nothing worked.
And to be very honest, there was nothing mentioned about this in MOKEE OS thread, as to which version of this device is not compatible with the ROM. The only reason I messed up was because the introduction of GSI ROMs has made the custom ROM creation process easier, but introduced a ****load of work in some devices, and ending up causing trouble.
This was the reason I requested all the steps in the thread so I could verify if I was missing some important step as far as the Indian variant is considered.
But thanks to everyone, I successfully booted Mokee ROM with everything working on my variant, including superuser privileges.
Also I messed up partitions in TWRP, and ended up with only 22gigs of Internal storage available, lol.
Thanks.
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Ok I figured it out, AFTER you flash the patched boot.img you need to format the data partition, you'll loose all your data, however the ROM will boot.
I'm running Android 10 mokee os, more stable and no bugs compared to lineage os 17 rom
cg730620 said:
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
Click to expand...
Click to collapse
Hi
Do you have a patched boot.img for my 7A 11.0.18.0 (PCMEUXM) ?
Thanks
axy_david said:
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Click to expand...
Click to collapse
Sorry for being so late to reply here. I would suggest using MIUI v10.2.10.0 as the base over which the Mokee OS needs to be installed.
As far as root is concerned, I tried Magisk but it gave me bootloops every time. As an alternative to getting root, I flashed the AddonSU installer which I downloaded from the Mokee Official site. You would just need to find it on the website.
I hope this helps. If you have further doubts, I'll stay a bit more active here. :fingers-crossed:
I want to unroot, but when i choose restore images in magisk manager it says stock backup doesnt exist. I downloaded the patched boot and stock boot.img prior to rooting, i didnt use magisk to patch the stock boot. What do i do now, i want to unroot and install ota on my xiaomi mi a3.
Can anybody help me?
I need the new version of patcher and the creator's website doesn't load me correctly.
Anyone have got pine 11.0.7 global patched boot image??? Cz yaalex patcher is down showing internal error
redmi7a
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
I asked the developer about a similar issue with the downloadable patcher, and he suggested me to try with the online one, which is more up to date.
https://patcher.yaalex.xyz/
romam suchanek said:
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct
Android OS version: 10.0.0_r32
Security patch level: March
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11
Cool cool some more love coming in
Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/
What version do I have to download for a 3a xl device ?
Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?
Hasn't been updated in like 2 months if I am reading it right
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
First time installation:
Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
Code:
fastboot -w
Gapps:
1. Fastboot boot TWRP
2. Flash Gapps arch64 version 11
3. Reboot
Magisk:
1. Boot into TWRP
2. Flash Magisk vs. 21.1
3. Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel https://github.com/Odin1101/Project-Sofia/tree/Upstream-test
Download: https://sourceforge.net/projects/crdroid-v7-x-sofiar/files/CrDroid-Sofiar/
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Device support Telegram link: https://t.me/joinchat/0IkIqVQMwM45MDZh
Thanks to the following devs and contributors
@bcrichster
@Beetle84
@asineth
@gearsofwar567
@kjjjnob
Special thanks:
@vache
Looks like Android File Host is down...
Downloading now to test. Thanks!
Does it work on sofia (r) (p) variants?
Nauwu said:
Does it work on sofia (r) (p) variants?
Click to expand...
Click to collapse
Yes
Thank you for this ROM. Does it support signature spoofing? I'm planning to flash NanoDroid instead of GApps. @Rondeau79
sanzhang said:
Thank you for this ROM. Does it support signature spoofing? I'm planning to flash NanoDroid instead of GApps. @Rondeau79
Click to expand...
Click to collapse
It should, but getting it set up might take some tinkering.
Can anyone suggest a way to install gapps without TWRP? Since some of us get the inverted TWRP touchscreen making it impossible to flash gapps.
TWRP does not install GAPPS, it says no enough space to install
For TWRP make sure your phone is fully charged and then switch to a USB mouse on an OTG cable then you can control TWRP. For GAPPS, try NANO and then you can load whatever Google apps you need via the Play Store.
viccskor19 said:
TWRP does not install GAPPS, it says no enough space to install
Click to expand...
Click to collapse
What version Gapps are you using?
Okay so I managed to do a very unsupported thing and have it still somehow boot. I upgraded to crdroid RQ1A.210205.004 (using the previous separate IMG files download as they were newer and I was wondering what difference if any they had over the regular 7.3 that was dated a day earlier? are they just newer builds or just essentially duplicates, or they were not really supposed to be public? anyways,) from my existing AICP 10 install.
I just dirty flashed the ROM only, waited for it to boot up and then to my amazement it did! I then installed the 11 opengapps as everything was crashing but the only thing is that essentially all google apps were broken requiring a reinstall of them (regular app data wipe didn't help and the play store works fine so I just did that) to not just close out when launching them.
is this fixable or it's a lost cause? lol. Thanks for this ROM, it's come a long way since I tried your first builds, this is actually usable and not just a black hole for google apps
No version of GAPPS that I can find will flash and boot. Which version do you recommend using? I usually use OpenGAPPs but they don't have android 11 up at this time.
Jaxgun said:
No version of GAPPS that I can find will flash and boot. Which version do you recommend using? I usually use OpenGAPPs but they don't have android 11 up at this time.
Click to expand...
Click to collapse
they have test builds up
Jaxgun said:
No version of GAPPS that I can find will flash and boot. Which version do you recommend using? I usually use OpenGAPPs but they don't have android 11 up at this time.
Click to expand...
Click to collapse
Much appreciated! I was looking on the Open Gapps Sourceforge page but I must've skipped over the TEST builds unintentionally.
dandu3 said:
they have test builds up
Click to expand...
Click to collapse
I was unable to find the test builds on the sourceforge page yesterday. Thanks for pointing me back there, I was able to find it this time.
I Have a Moto G Power XT2041-4 on Verizon. Why is that my mobile network is all wonky on the 11 Roms? Cannot send or receive MMS. Mobile data turns off when trying to send myself an MMS. Then turns right back on after trying to send and tells me it was unsuccessful. Mobile data turns itself on and off every few seconds. If i'm on a phone call mobile data icon stays on but still no data. There is absolutely no APN options for me on 11. I've tried flashing the stock modem. Erase carrier. Resets. I have none of these issues with any of the 10 Roms.
I am using the Superior version of the Android 11 OS on XT2041-4 on Verizon and I have not experienced any of these issues. I went with Superior because I was unable to load GAPPS on CRDroid and have found Superior to be ... superior.
djdio68 said:
I Have a Moto G Power XT2041-4 on Verizon. Why is that my mobile network is all wonky on the 11 Roms? Cannot send or receive MMS. Mobile data turns off when trying to send myself an MMS. Then turns right back on after trying to send and tells me it was unsuccessful. Mobile data turns itself on and off every few seconds. If i'm on a phone call mobile data icon stays on but still no data. There is absolutely no APN options for me on 11. I've tried flashing the stock modem. Erase carrier. Resets. I have none of these issues with any of the 10 Roms.
Click to expand...
Click to collapse
You provide me with no logs, any technical data and what version of the ROM you were using. Therefore I cannot help you with your situation.
does OTA work even without TWRP on this?