[GUIDE] Two ways to root oppo a5s (CPH1909)+ Unlock bootloader after security update ( without downgrading )

[jimenezshown]

@Anonymous V @Zezo 089 Hi guys, I managed to flash the lk file and this removed the "your device is unlocked and cannot be trusted , rebooting in 5 seconds" , but not the second message "dm-verity error, Your android system / device is corrupted...", should the lk file remove both message or or just only the first message?

 

[jimenezshown]

Yep
But data will be lost
But maybe there's a way to unbrick (recover) the phone after bricking without losing the data , but

I don't mind losing the data as long as I can make the phone bootable if ever. Thank you, atleast I'm confident doing this all over again.

 

[Anonymous V]

@Anonymous V @Zezo 089 Hi guys, I managed to flash the lk file and this removed the "your device is unlocked and cannot be trusted , rebooting in 5 seconds" , but not the second message "dm-verity error, Your android system / device is corrupted...", should the lk file remove both message or or just only the first message?

can you still boot your phone? or atleast operate it? and also does your phone has a fastboot? try to test it if there is

 

[jimenezshown]

can you still boot your phone? or atleast operate it?

Yes, I can still use my phone, it's just during power on cycle, dm-verity error still showing.

 

[Anonymous V]

Yes, I can still use my phone, it's just during power on cycle, dm-verity error still showing.

so you can use your phone like normal and no bootloop or other shinanegans happens your phone right? but only the message appear when the phone is booting right? well see if there is a solution for that because that never happens to me

 

[jimenezshown]

somehow that LK file after I flashed it, successfully removed this message:

The message will say (" your device is unlocked and cannot be trusted , rebooting in 5 seconds ")

but not this message:

another message appears (" dm-verity error,
Your android system / device is corrupted, please select whether you want to boot in E10 mode or RESTART mode ")

 

[jimenezshown]

so you can use your phone like normal and no bootloop or other shinanegans happens your phone right? but only the message appear when the phone is booting right? well see if there is a solution for that because that never happens to me

that's right, though it's not affecting my phone's performance and I don't mind if this will take time to get fixed, I'm only wondering if it's possible. Thank you bro.

 

[jimenezshown]

(" dm-verity error,
Your android system / device is corrupted, please select whether you want to boot in E10 mode or RESTART mode ")

I read that this could be solved by flashing with vbmeta.img but I'm scared to do it and I don't know where to get the vbmeta

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

 

[Anonymous V]

I read that this could be solved by flashing with vbmeta.img but I'm scared to do it and I don't know where to get the vbmeta

yes it can be fixed in that way ,were thinking the same way and i think you can get a vbmeta image in your stock firmware just extract it and you will able to see vbmeta image in there because every phone has a unique vbmeta

 

[jimenezshown]

yes it can be fixed in that way ,were thinking the same way and i think you can get a vbmeta image in your stock firmware just extract it and you will able to see vbmeta image in there because every phone has a unique vbmeta

The problem is I don't seem to find any vbmeta image in a stock firmware and even in my fully back up firmware though. Anyway, not really a big deal for me, kinda bothersome a bit but as long as phone is working as intended then it's fine.

 

[ZG089]

so you can use your phone like normal and no bootloop or other shinanegans happens your phone right? but only the message appear when the phone is booting right? well see if there is a solution for that because that never happens to me

Maybe i have a solution for this , but i'll get the link after minutes

 

[ZG089]

@Anonymous V dude , yep he is right , the frimware does not have vibmeta file at all

 

[jimenezshown]

@Anonymous V dude , yep he is right , the frimware does not have vibmeta file at all

As per the instruction in magisk, I patched the stock boot.img again this time with "Preserved vbmeta in boot image" then flashed "same issue". Next was checking the 3 options then flashed again but message still appearing during power cycle. I also read that fastboot in our device is factory disabled and inaccessible so doing that fastboot command is not the right method for our device.

 

[ZG089]

Dude What the heck you did

As per the instruction in magisk, I patched the stock boot.img again this time with "Preserved vbmeta in boot image" then flashed "same issue". Next was checking the 3 options then flashed again but message still appearing during power cycle. I also read that fastboot in our device is factory disabled and inaccessible so doing that fastboot command is not the right method for our device.

View attachment 5926499

THIS DOES NOTHING
+ IT IS DANGEROUS TO DO THIS

 

[ZG089]

As per the instruction in magisk, I patched the stock boot.img again this time with "Preserved vbmeta in boot image" then flashed "same issue". Next was checking the 3 options then flashed again but message still appearing during power cycle. I also read that fastboot in our device is factory disabled and inaccessible so doing that fastboot command is not the right method for our device.

View attachment 5926499

Also yep oppo a5s has no fastboot

 

[ZG089]

As per the instruction in magisk, I patched the stock boot.img again this time with "Preserved vbmeta in boot image" then flashed "same issue". Next was checking the 3 options then flashed again but message still appearing during power cycle. I also read that fastboot in our device is factory disabled and inaccessible so doing that fastboot command is not the right method for our device.

View attachment 5926499

+ I know a way using a program but maybe it needs Activation

 

[jimenezshown]

Dude What the heck you did

THIS DOES NOTHING
+ IT IS DANGEROUS TO DO THIS

I don't know bro, but the good thing my phone is still functional though.

 

[jimenezshown]

I also wondering if "DT-verity error" is the reason why my CPU governor app won't save and apply the setting after reboot, is "DT-verity error" likely the culprit for this bro?

 

[jimenezshown]

+ I know a way using a program but maybe it needs Activation

let me know if you manage it bro. Thank you.

 

[ZG089]

I also wondering if "DT-verity error" is the reason why my CPU governor app won't save and apply the setting after reboot, is "DT-verity error" likely the culprit for this bro?

Nope
The FRICKING System changes it