Database Develop

[boot.img] Patched boot.img files & patching tool

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

[Q][BONITO] Descendant X - android ver. 10r32

{
"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

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"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 don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix

Official TWRP for A12 ONEPLUS 7 PRO is now released.

Hello,
as I mentioned in the title, you can now download the official TWRP for the official website, and the most recent version supports encryption/decryption.
https://twrp.me/oneplus/oneplus7pro.html

Does it support 13? I'm running pixel experience.

fli2008 said:
Does it support 13? I'm running pixel experience.
Click to expand...
Click to collapse
they said A12 try it on A13 and see

I can't any more unlock the bl since A12. :/

khalisz said:
I can't any more unlock the bl since A12. :/
Click to expand...
Click to collapse
Yeah thats true, always unlocked it on A11 before flashing A12

yassine2217 said:
Hello,
as I mentioned in the title, you can now download the official TWRP for the official website, and the most recent version supports encryption/decryption.
https://twrp.me/oneplus/oneplus7pro.html
Click to expand...
Click to collapse
Did you manage to run this recovery on OOS A12? As experience shows, this version only works with OOS A11, on A12 I and many people get the "fastboot mod" logo in the center of the screen, without running TWRP.
By the way, here is the official theme of the TWRP developer on guacamole, on xda:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
He has a chat in Telegram, his unofficial recovery is published there.

Rein0ud said:
Did you manage to run this recovery on OOS A12? As experience shows, this version only works with OOS A11, on A12 I and many people get the "fastboot mod" logo in the center of the screen, without running TWRP.
By the way, here is the official theme of the TWRP developer on guacamole, on xda:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
He has a chat in Telegram, his unofficial recovery is published there.
Click to expand...
Click to collapse
I test it on my phone with elixir A12 work perfetcly and i made a nandroid also with no issue

yassine2217 said:
I test it on my phone with elixir A12 work perfetcly and i made a nandroid also with no issue
Click to expand...
Click to collapse
Yes, I know about support for custom ROMs, but they use FBEv2, OOS uses FEv1, as far as I can understand. Therefore, I am collecting information about the operation of TWRP 3.7 with OOS on A12 (because this version is declared to support OOS A12, but only works on OOS A11)
Thank you for your answer!

Rein0ud said:
Yes, I know about support for custom ROMs, but they use FBEv2, OOS uses FEv1, as far as I can understand. Therefore, I am collecting information about the operation of TWRP 3.7 with OOS on A12 (because this version is declared to support OOS A12, but only works on OOS A11)
Thank you for your answer!
Click to expand...
Click to collapse
I confirm that too, it works under OOS11 but not with OOS12, all on OnePlus 7Pro.

I'm on OOS12 stable. Installing it somehow managed to get my magisk looping in some "downloading the full magisk package"-mode. Didn't mind as I thought I might just flash it via TWRP later on. Unfortunately I don't even get that far.
Just to clarify - I tried "fastboot boot" the following items:
- a magisk patched boot.img extracted from the OOS12 stock image
- TWRP 3.6.2 (V1) unofficial by Nebrassy
- TWRP 3.7.0 V1 Official
All ways lead me to a "fastboot mode" logo.
Am I missing something here?

RfBob said:
I'm on OOS12 stable. Installing it somehow managed to get my magisk looping in some "downloading the full magisk package"-mode. Didn't mind as I thought I might just flash it via TWRP later on. Unfortunately I don't even get that far.
Just to clarify - I tried "fastboot boot" the following items:
- a magisk patched boot.img extracted from the OOS12 stock image
- TWRP 3.6.2 (V1) unofficial by Nebrassy
- TWRP 3.7.0 V1 Official
All ways lead me to a "fastboot mode" logo.
Am I missing something here?
Click to expand...
Click to collapse
As I wrote earlier, TWRP 3.7 and less cannot run on A12.
After flashed a modified boot, what happens to your phone? Bootloop ?

ADB tells me it sent and wrote boot partition via command "fastboot flash boot [...]". After that nothing happens.
Forced it to reboot afterwards and I am back to my UNpatched boot partition.
I patched the image with magisk manager on the device itself then transfered it back to my PC. I just transferred it to the phone again to verify, if it is actually patched. Magisk tells me it is.

RfBob said:
ADB tells me it sent and wrote boot partition via command "fastboot flash boot [...]". After that nothing happens.
Forced it to reboot afterwards and I am back to my UNpatched boot partition.
I patched the image with magisk manager on the device itself then transfered it back to my PC. I just transferred it to the phone again to verify, if it is actually patched. Magisk tells me it is.
Click to expand...
Click to collapse
If fastboot take a message "Finished. Total time: ..." and sending/writing have status OKAY, then new mod_boot.img flashing sucsessful. I don't quite understand what you get when you try to start the system after flashing ...

{
"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"
}
When restarting after flashing the patched boot image I am back to my unrooted state. Everything else is working. No bootloop or else. Just no root either.

RfBob said:
View attachment 5750285
When restarting after flashing the patched boot image I am back to my unrooted state. Everything else is working. No bootloop or else. Just no root either.
Click to expand...
Click to collapse
I can try to share patched_boot, which firmware version is on your device?

Rein0ud said:
I can try to share patched_boot, which firmware version is on your device?
Click to expand...
Click to collapse
Sure, please. Firmware - GM1913_11_H.30

RfBob said:
Sure, please. Firmware - GM1913_11_H.30
Click to expand...
Click to collapse
Pathed boot from H30

Phone booted up just fine with your patched image (just as with mine). Thanks mate, but still no root.

RfBob said:
Phone booted up just fine with your patched image (just as with mine). Thanks mate, but still no root.
Click to expand...
Click to collapse
Hmm, then you should try the method with getting root on OOS 11, local update via zip to 12 and then Magisk firmware in both slots, then reboot

This is exactly where I came from. Updating local caused magisk to redownload some additional files in a loop. So I had to reinstall magisk. Since then - although no reboot in between - I'm unable to get it rooted. Even booting the patched images tells me "no root".

[ROM][13.0][OnePlus8T] PixelExperience [AOSP/UNOFFICIAL] - JUNE 24, 2023

YOU MUST HAVE STOCK OOS13 INSTALLED ON BOTH SLOTS TO AVOID TOUCH SCREEN ISSUES. IF YOU ARE ON A11 or A12, THEN UPDATE TO A13. IF YOU ARE ON A13 then you are good to flash this already. Use copy partions if you want to make sure firmware is on both slots.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
YOU MUST BE ON STOCK ANDROID 13 ON BOTH SLOTS FOR IT TO WORK PROPERLY. IF NOT, THEN UPDATE TO A13.
THANKS TO THE ENTIRE PE TEAM FOR HAVING THEIR SOURCE AVAILABLE FOR USE!!!
What's working?
You tell me
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
DOWNLOAD ROM & RECOVERY FILES HERE
Put recovery files in same folder as your fastboot or platform tools folder.
Install instructions also located here.​
Android OS version: 13.0​
Security patch level: June 2023​
Device Source code: https://github.com/PixelExperience-Devices​
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250​
Source code: https://github.com/PixelExperience​
ROM Developers: jhenrique09, Broly
Maintainer: TheSayaMan
XDADevDB Information
PixelExperience A13 ROM for OnePlus 8t Kebeb
REBOOT TO BOOTLOADER
fastboot -w​fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
fastboot flash recovery recovery.img
Reboot your phone to recovery mode, click "Install update" -> "ADB Sideload"
adb sideload PixelExperience-Plus-kebab-WEEKLY-13.0-20230624-UNOFFICIAL.zip
REBOOT TO SYSTEM TO SETUP. IF YOU WANT ROOT, THEN BOOT BACK TO RECOVERY AND ADB SIDELOAD MAGISK
adb sideload magisk.apk or rename magisk.apk to magisk.zip and adb sideload magisk.zip
IF YOU ARE ALREADY ON PREVIOUS UPDATE, YOU CAN DIRTY FLASH NEW UPDATE. REBOOT TO BOOTLOADER.
IN RECOVERY, SIMPLY ADB SIDELOAD NEW UPDATE.
UPDATES ARE INSTALLED TO INACTIVE SLOT IN CASE OF INSTALL ISSUE, YOU CAN REVERT BACK TO PREVIOUS BOOTABLE SLOT.

Oos12 or oos13 based ?

i try flash on oos13.

diegots said:
Oos12 or oos13 based ?
Click to expand...
Click to collapse
I have tested on 13. No idea if it will work on 12. It definitely will not work on 11.

vallobrescia said:
i try flash on oos13.
Click to expand...
Click to collapse
It will work fine

TheSayaMan said:
It will work fine
Click to expand...
Click to collapse
which recovery did you use? is the twrp from the official site ok?

Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)

SaigoW said:
Flashed,screen touch not work,and stuck at google logo for a long time(I'm on oos13 fw)
Click to expand...
Click to collapse
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.

vallobrescia said:
which recovery did you use? is the twrp from the official site ok?
Click to expand...
Click to collapse
Yes twrp is fine or if your on another custom rom, you can use that one as well. I will post a recovery for this when I can.

TheSayaMan said:
You must have firmware on both slots. That's the usual cause. Flashing copy partitions will solve this problem.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
reboot to recovery, factory reset and adb sideload copy partitions. Reboot to recovery again and factory reset again then sideload rom and see if problem goes away.
Click to expand...
Click to collapse
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ

logan_007 said:
I followed what you said and tried many times. It boots up smoothly, but the screen touch doesn't take effect. QAQ
Click to expand...
Click to collapse
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.

does this one work better or the one on the official site?

TheSayaMan said:
Sì twrp va bene o se sei su un'altra rom personalizzata, puoi usare anche quella. Pubblicherò un recupero per questo quando posso.
Click to expand...
Click to collapse
Good job, I'll run this thread right.

TheSayaMan said:
Somehow you don't have current fw on both slots. I would try to install this rom on both slots but it may not work. Worth a try. When you apply a system update, it only updates to opposite slot and leaves the other at previous version which causes problems. By coping partitions, it insures both slots have current fw.
Click to expand...
Click to collapse
I use Pixel Experience recovery to flash the rom.
I flashed in the official Oxygen OS 13 version，It booted fine and everything works fine.
and then unlocked the OEM, extracted the Pixel Experience 13 recovery and then flash into this Pixel Experience recovery.
Also follow the tutorials to flash the rom
(https://wiki.pixelexperience.org/devices/kebab/install/)
After the first boot devices,the screen touch is not working.
{
"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"
}
Then I followed your instructions and the screen touch did not work either.
-----
I use the same way flash, PE ROM 12 is everything works, and I have used it for half a year.
Also I can't use twrp,I can't use twrp since android 11, even though I flashed in the latest version, it can't decrypt my data correctly and can't identify my data correctly. Maybe it's just a problem with my phone.
So I can't flash the PE rom via twrp either
just now I went to test the latest version of LineageOS android 13, also following the official tutorial to use LineageOS recovery to swipe in, and found the same problem, normal boot up, the result is the same as PE rom is on the new user guide page, the screen touch does not work.
---
I haven't seen too many people report this kind of problem, I think there may be some strange problems with my phone. TAT

vallobrescia said:
does this one work better or the one on the official site?
Click to expand...
Click to collapse
The official hasn't updated the security patch yet.

Thread updated with recovery install instructions.

Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?

M_Power01 said:
Hi !
After few days, i noticed a battery drain by Pixel Launcher.
anyone else have the same problem ?
Click to expand...
Click to collapse
It's a known problem. I switched to Nova Launcher and then disabled that.

No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.

Dior DNA said:
No touch screen here either ... (not in system not in recovery)
I flashed following instructions on PE 8T page.
(I read here but not on that page : -disable-verity --disable-verification for dtbo and vbmeta, but I guess that won't matter, or does it?)
I had fresh OnePlus8T-KB2003_11_F.13 OOS13 on both slots. Which should provide OOS13 firmware on both slots.
... Interested in anyone who worked around this and how.
Click to expand...
Click to collapse
Although this is Android 13. It's based on Android 12 so you must have a12 on both slots for it to work properly. Sorry for the confusion. I have updated the instructions, sorry.