Develop Bugs

[AOKP][PROJECT_TREBLE][8.1.0][a/b devices only][4/2/18]

This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that

First!
Sent from my Pixel 2 XL using Tapatalk

slothdabski said:
First!
Click to expand...
Click to collapse
Crap missed it..

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
does google camera work with hdr+? do you get unlimited photo storage?

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
We should all be here not everyone can do what you do..

I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.

cdnsnOw said:
We should all be here not everyone can do what you do..
Click to expand...
Click to collapse
What I meant was if you don't know how to use fastboot, you probably shouldn't be messing with your phone because you used the wrong code and bricked it..no offense

What is the difference flashing with TWRP and fastboot method?

So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.

gforceriders said:
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
Click to expand...
Click to collapse
Maybe after flashing vbmeta reboot bootloader then load up twrp

cdnsnOw said:
What is the difference flashing with TWRP and fastboot method?
Click to expand...
Click to collapse
This is a system.img and needs to be flashed to the system which requires fastboot..in twrp you MUST make sure you're flashing to the system_a partition

sixohtew said:
Maybe after flashing vbmeta reboot bootloader then load up twrp
Click to expand...
Click to collapse
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.

abduleo77 said:
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
Click to expand...
Click to collapse
Try booting twrp right after the vbmeta.img

gforceriders said:
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
Click to expand...
Click to collapse
Which device? Pixel 2 xl?

sixohtew said:
Which device? Pixel 2 xl?
Click to expand...
Click to collapse
Yep, the pixel 2 XL.

gforceriders said:
Yep, the pixel 2 XL.
Click to expand...
Click to collapse
Did you come from another rom or were you stock? This boots just fine for me

sixohtew said:
Did you come from another rom or were you stock? This boots just fine for me
Click to expand...
Click to collapse
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.

gforceriders said:
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
Click to expand...
Click to collapse
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?

sixohtew said:
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
Click to expand...
Click to collapse
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.

gforceriders said:
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
Click to expand...
Click to collapse
Yeah if you tried to flash it over another rom instead of stock, issues could arise..I'll put a script together that will flash stock with the new system.img and add the vbmeta.img to it so it flashes all the necessary files

OnePlus 7T 10.3.0 for Indian HD1901, included with patched boot img

This is the new update 10.3.0, for indian 7Ts HD1901, i got this zip from device update itself
OTA rom - https://drive.google.com/open?id=14eM8AzKKeht6i_zHw8lvSaRoknN90PPk
you need payload dumper to open and extract payload.bin to get .imgs of roms
patched boot image - https://www.androidfilehost.com/?fid=4349826312261679634
use this guide to root your 7T using above img - https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307

this is same as the new 10.0.7 for the global/eu versions

Can you please share original boot image from 10.0.7??? payload dumper gives me error.

sagardakua said:
Can you please share original boot image from 10.0.7??? payload dumper gives me error.
Click to expand...
Click to collapse
here it is https://drive.google.com/open?id=1eagdkkAMeaav2AtBI9b7b3m6_LQ-vLH6
this is for indian hd1901, so dont complain to me if you flash this on some another model and get error

I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?

sathya said:
I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?
Click to expand...
Click to collapse
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)

levai_spencer said:
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)
Click to expand...
Click to collapse
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk. Here is what i did.
Entered Fastboot mode
Through ADB, i used "fastboot boot magisk_patched.img
The phone booted fine
Opened Magisk as i was already rooted before
Clicked on Install
Selected "Direct Install"
Rebooted my phone
Stuck at the bootloader warning screen
Unless i load the image again via fastboot, it wont let me in. Hence i am not able to root

sathya said:
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk
Click to expand...
Click to collapse
are you booting or flashing? its a 2 different things...

levai_spencer said:
are you booting or flashing? its a 2 different things...
Click to expand...
Click to collapse
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.

sathya said:
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.
Click to expand...
Click to collapse
its a well known magisk bug, i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
I'll update the patched boot img just in case

levai_spencer said:
i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
Click to expand...
Click to collapse
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?

sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
yes, booting stock boot img will remove root, once you fix the problem, you can follow same root guide and patched img to root the phone again

sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
also, make sure to use same 10.3.0 files to restore your phone using the restore guide i gave (assuming you updated to 10.3.0)

Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.

sathya said:
Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.
Click to expand...
Click to collapse
did you try restore using the guide i gave? i used this guide to fix bootloader stuck
you'll need to download the ota file linked, extract zip, use payload dumper to get imgs, and flash all imgs according to the guide
you can also create your own magisk patched image, thats how i got mine and my 7T is rooted on 10.3.0

okay you can do this if flashing my patched img is causing issues
if you have an old 10.0.6 patched img, use that to get root
i got this one from xda, i was able to also root using that

Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot

sathya said:
Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot
Click to expand...
Click to collapse
did u try to wipe data/internal in recovery?

Android 11 GSI

Has anyone tried to flash it? I remember there being an issue with the layout of our partitions and what not. Just thought I'd ask because it's pretty nice on my pixel 3.
https://developer.android.com/topic/generic-system-image/releases

can't download, when you put gmail ans password account there is the security code from usb? what is it? if you have other link ill be appreciated thanks

Oh that is weird, I've never seen that before.

Me too, I will try it but I can't find the file to download

I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized

Sparker0i said:
I just tried flashing system and vbmeta and also did fastboot -w, but its showing android logo at boot screen, and animation is a bootloop. Luckily adb devices shows my phone, but unauthorized
Click to expand...
Click to collapse
where you downloaded ? can you provide a functional link? thanks

iaio72 said:
where you downloaded ? can you provide a functional link? thanks
Click to expand...
Click to collapse
Official site where the Android 11 gsi is available

Sparker0i said:
Official site where the Android 11 gsi is available
Click to expand...
Click to collapse
Yes of course but download doesn't work...

iaio72 said:
Yes of course but download doesn't work...
Click to expand...
Click to collapse
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..

Sparker0i said:
Sure you can't download the arm64 + gms zip from here: https://developer.android.com/topic/generic-system-image/releases . I can download..
Click to expand...
Click to collapse
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t

iaio72 said:
ok im flashed but at reboot the phone remain in "qualcomm crash dump test"
i think not is good for our op7t
Click to expand...
Click to collapse
Not really in crashdump mode, but for me it was on bootloop at Android logo screen

i have the same issue i believe we need an updated version of vbmeta and a custom boot.img because i have been able to get it to boot but as previously stated before it just bootloops on the android screen

how did you flash the android 11 gsi and the vbmeta?

i flashed it via fastboot commands

I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .

intana said:
I tried several times and still trying . with system.img and vbmeta.img from google stuck at boot screen (Android logo waiting on screen) . Other custom builds (like erfangsi) is giving qualcomm crash dump without google vbmeta . No lack to boot until now . BUt there are some successful boot videos on internet with especially xiaomi phones . I don't know it is real or not . As far as I know op7t %100 of treble compatible phone and it should work .
Click to expand...
Click to collapse
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try

SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
Yes I did . But it didn't work . I am trying every new build and custom roms about op7t-hotdogb and op7tpro-hotdog also . As you know op7tpro's custom roms are running on op7t with some minor problems like fod . Thanks for the advice

SICKMADE said:
I don't mean to ask a obvious question that I'm sure you did after you flashed but did you try flashing then booting into recovery and wiping caches and reboot? Prob won't work but worth a try
Click to expand...
Click to collapse
lol long time no see dude remember you from way back in note 4 days
btw ive been trying to get this to work for a few days lol still trying hopeful it will work

with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

ChrisFeiveel84 said:
with which fastboot commands did you flash the gsi and the vbmeta
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
fastboot flash system_a GSI.img
fastboot flash system_b GSI.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
after "fastboot reboot fastboot" and fastboot -w I used same commands and used system.img and vbmeta.img from the below link (it includes its own vbmeta.img and it says it is AVB verification disabled) then reboot recovery delete cache and data again .
"https://developer.android.com/preview/gsi-release-notes"

Boot.img stock & patched + recovery with adb 11.0.4.4.IN11AA (global)

While there is no link for incremental nor full ota, here comes the Batman.
Google Drive with all stuff
Google Drive link
Spoiler: How to flash kernel?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
Now you can choose between 2 different installation routes
First routeSecond route
install magisk canary and open it
reboot back to fastboot
install → direct install
fastboot flash boot_a <filename>.img
and then flash to the second slot​
fastboot flash boot_b <filename>.img
after installation is done — reboot
fastboot reboot
Spoiler: How to flash recovery?
enter fastboot mode
fastboot flash recovery_a <filename>.img
fastboot flash recovery_b <filename>.img
fastboot reboot recovery
Well done. You are great.

Cheers!

You sure this is for 11.0.2.2.IN11AA?
Because it looks like 11.0.1.1.IN11AA to me, unless I'm doing something wrong (I am new to this).
Cheers
EDIT: Dw, I'm stupid

I had lost root since updating so was looking for a stock boot image for 11.0.2.2 to patch in order to once again restore root by the fastboot method. (It is generally recommended that you patch your own stock boot image.) So, I downloaded your stock boot image which was 98 MB. In the past, stock boot images for the OnePlus 8 Pro have been 16 to 17 MB, so I am wondering if the 98 MB file labeled as stock is actually a stock boot image. Also, both files are exactly the same size so I'm guessing that they are both patched boot images.

vettean said:
I had lost root since updating so was looking for a stock boot image for 11.0.2.2 to patch in order to once again restore root by the fastboot method. (It is generally recommended that you patch your own stock boot image.) So, I downloaded your stock boot image which was 98 MB. In the past, stock boot images for the OnePlus 8 Pro have been 16 to 17 MB, so I am wondering if the 98 MB file labeled as stock is actually a stock boot image. Also, both files are exactly the same size so I'm guessing that they are both patched boot images.
Click to expand...
Click to collapse
To be precise, its boot partition. Yes, boot may size 16mb but partition - not.
And so that's why you you can't say by size which file have patched boot.

more_than_hater said:
To be precise, its boot partition. Yes, boot may size 16mb but partition - not.
And so that's why you you can't say by size which file have patched boot.
Click to expand...
Click to collapse
Thanks for the clarification. After the past couple of updates, in order to get root back I used the Magisk Manager to patch a stock boot image that I found online which was about 16 MB and then installed via fastboot on my PC. Using your 98 MB stock boot image, would I perform the operation the same way by downloading it to my phone and patching it with Magisk Manager before use fastboot?

vettean said:
Thanks for the clarification. After the past couple of updates, in order to get root back I used the Magisk Manager to patch a stock boot image that I found online which was about 16 MB and then installed via fastboot on my PC. Using your 98 MB stock boot image, would I perform the operation the same way by downloading it to my phone and patching it with Magisk Manager before use fastboot?
Click to expand...
Click to collapse
Yes, magisk manager can patch both boot and "boot-in-partition"

more_than_hater said:
While there is no link for incremental nor full ota, here comes the Batman.
Stable stock&patched boot.img
Google Drive link
How to use?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
install magisk canary apk and open it
use direct install method
reboot
fin. you are great.
P.S.
I don't recommend to directly flash patched boot.img to boot_a and boot_b partitions, because smth could go wrong. It mostly works for 99,9% times, but it's better to use magisk direct install method.
Click to expand...
Click to collapse
Do you have the link for the 11.0.2.2AA full ota?

Where is the full OTA Update for this??

someone in a different OP8P thread posted this:
OnePlus 8/8 Pro OxygenOS OTA Updates: Download & Installation (Latest: OxygenOS 13 F.15)
Download all OxygenOS OTA software updates for OnePlus 8 and OnePlus 8 Pro, and learn how to manually install them. Latest: OxygenOS 13 F.15 (Android 13) update
www.thecustomdroid.com

more_than_hater said:
While there is no link for incremental nor full ota, here comes the Batman.
Stable stock&patched boot.img
Google Drive link
How to use?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
install magisk canary apk and open it
use direct install method
reboot
fin. you are great.
P.S.
I don't recommend to directly flash patched boot.img to boot_a and boot_b partitions, because smth could go wrong. It mostly works for 99,9% times, but it's better to use magisk direct install method.
Click to expand...
Click to collapse
I don't understand how you can have the boot patched for OTA 11.0.2.2AA when the update itself hasn't been released yet !?

spaziomilano said:
I don't understand how you can have the boot patched for OTA 11.0.2.2AA when the update itself hasn't been released yet !?
Click to expand...
Click to collapse
But it has been and pulling a boot img from an install ROM is not that hard.
Link removed - was India version

Agimax said:
But it has been and pulling a boot img from an install ROM is not that hard.
https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus8ProOxygen/OnePlus8ProOxygen_15.I.32_GLO_0320_2011190124/OnePlus8ProOxygen_15.I.32_OTA_0320_all_2011190124_6f85dfcc1adc2bc.zip
Click to expand...
Click to collapse
So can I use what you sent me to update?

spaziomilano said:
So can I use what you sent me to update?
Click to expand...
Click to collapse
That's just the official OnePlus link to 11.0.2.2AA India full ROM. Up to you, can flash through updater if it's the version you wanted.

Agimax said:
That's just the official OnePlus link to 11.0.2.2AA full ROM. Up to you, can flash through updater if it's the version you wanted.
Click to expand...
Click to collapse
Really appreciate thanks

Agimax said:
That's just the official OnePlus link to 11.0.2.2AA full ROM. Up to you, can flash through updater if it's the version you wanted.
Click to expand...
Click to collapse
Just make the last update but it's DA version not AA...

spaziomilano said:
Just make the last update but it's DA version not AA...
Click to expand...
Click to collapse
Is it a big problem?

Deleted

spaziomilano said:
Is it a big problem?
Click to expand...
Click to collapse
My apologies, I stand corrected -this was the India version. You are right as the AA full ROM version is not yet available. I'll correct my original post.

Agimax said:
My apologies, I stand corrected -this was the India version. You are right as the AA full ROM version is not yet available. I'll correct my original post.
Click to expand...
Click to collapse
Lolll have make the update and now I'm on stable DA instead AA... All work good, I think is not a big problem

Question le2125_11_c.61 OOS12 root

My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.

EtherealRemnant said:
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.
Click to expand...
Click to collapse
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Yeah that's correct. Bummer that it didn't work. Give me a few to download and patch it.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Well unfortunately I have downloaded two different python scripts trying to patch the full OTA with the incremental OTA and they are both failing so I guess we will have to wait for someone else to do it because I don't have the expertise to fix this.

As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?

djsubterrain said:
As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?
Click to expand...
Click to collapse
You can't boot into TWRP because it doesn't work on OOS12. It crash dumps.
Someone who is rooted needs to install the OTA and pull the image unless there is a tool I haven't come across that works better for incremental OTA extraction.

The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks

observingi said:
The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks
Click to expand...
Click to collapse
I am also facing the same problem..

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.

rustyshakelford2 said:
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.
Click to expand...
Click to collapse
Enable USB debugging in settings, then type adb reboot edl.

razercortex said:
Enable USB debugging in settings, then type adb reboot edl.
Click to expand...
Click to collapse
I got it! I managed to readback boot_b using the password "oneplus". I can't seem to find where it saved the file though.

It's in C:\ aka your root drive

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
That's a cool trick. I didn't know about that one.

Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.

rustyshakelford2 said:
Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.
Click to expand...
Click to collapse
Can you please share the steps to get the boot.img
I have to get it from LE2121

gulshanstrider said:
Can you please share the steps to get the boot.img
I have to get it from LE2121
Click to expand...
Click to collapse
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.

EtherealRemnant said:
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.
Click to expand...
Click to collapse
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?

TornSack said:
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?
Click to expand...
Click to collapse
Did you go to try to direct install? I haven't actually tried C.61 yet, I've got stuff to do this weekend and can't have my phone in an experimental state when I'm trying to call and Uber to get around, so I can't test it myself.