So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
nickdagriff said:
So has anyone tried to keep root when switching to the new OOS12 Open Beta build released on 10/4/21? If so did you just do the same as doing a normal update? i.e. Going into Magisk before reboot and hitting the OTA button in the installer app.
Click to expand...
Click to collapse
cant root dp2
will cause cash dump everytime
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
Do you know why
encoded
FizzyAps said:
encoded
Click to expand...
Click to collapse
Do you think I should just throw myself off a building?
i mean its beta what did you except lol
I was just hoping to be able to test it and root it like every other open beta.
What about twrp
You cant flash anything at this time
It will cash dump
FizzyAps said:
cant root dp2
will cause cash dump everytime
Click to expand...
Click to collapse
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Burt Squirtz said:
What do you mean can't root db2? He's talking about the new open beta. Have you actually tried to root that?
Click to expand...
Click to collapse
Yes I tried rooting both and they both end In cash dump
FizzyAps said:
Yes I tried rooting both and they both end In cash dump
Click to expand...
Click to collapse
How did you try though? Install to inactive slot, AND adb? Or just one of the other?
flashed patched img on both slots
FizzyAps said:
flashed patched img on both slots
Click to expand...
Click to collapse
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
ENCODED, NO METHODS WORK....
I rooted successfully with a Chinese tool
It works on both OOS12 and ColorOS12
Burt Squirtz said:
Can you try this method bro? This is the surefire way to root color OS. A friend reported that it works. I'm traveling not near a PC now otherwise I'd do it.
Somehow I managed to get root on dp2 and I don't know how I did it. Because I didn't do these steps.
<How to Root OOS12 OP9 (aka ColorOS)>
Extract boot.img, vendor_boot.img, vbmeta.img from ota file first
Patch boot.img and vendor_boot.img using magisk manager
reboot phone to bootloader after moving patched imgs to pc
fastboot flash boot patched_boot.img
fastboot flash vendor_boot patched_vendor_boot.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I used this method to root last night and can confirm it works on OB 1 A12. I did the vbmeta part before flashing boot.img and didn't do the vendor_boot part at all.
https://www.droidwin.com/root-android-12-via-magisk-patched-boot-img-without-twrp/ this is the guide I followed.
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
ecera said:
P.S. On a side note I found it interesting that the "unlocked bootloader" message screen when booting is absent on this new OB1 A12 build. It's kinda nice, I know how much of an eye sore it is for some.
Click to expand...
Click to collapse
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
terlynn4 said:
Really?? I'll try it just to get rid of that message. I'm all about faster boot time.
Click to expand...
Click to collapse
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
ecera said:
Well I cant really say the boot time is noticeably faster, but the unlocked bootloader message is deff gone for me.
Click to expand...
Click to collapse
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
terlynn4 said:
Since boot is significantly slower after unlocking bootloader, I figured the message was to blame and the reverse would also be true. I could be wrong. Thanks for the info though. It'd be nice if they get rid of that message entirely with A12 stable and going forward.
Click to expand...
Click to collapse
It probably does boot a bit faster. Like you said that message is an extra few seconds. To me its not really noticeable, maybe to someone else it might be.
Related
Hey guys,
Ever since I updated my Wileyfox a few days ago, it's gone to crap. Half my apps don't work, and they've removed features I really liked.
Is there any way to reverse this dreadful update and restore it to how it was?
Thanks in advance
jjl5590 said:
Hey guys,
Ever since I updated my Wileyfox a few days ago, it's gone to crap. Half my apps don't work, and they've removed features I really liked.
Is there any way to reverse this dreadful update and restore it to how it was?
Thanks in advance
Click to expand...
Click to collapse
Here you go
http://www.mediafire.com/download/24748t4ghkoam9h/cm-12.1-YOG7DAS2FI_%28recovery%29_%2828.12.15%29.zip
This is the recovery zip, I also have the fastboot zip if you want it?
robin0800 said:
Here you go
http://www.mediafire.com/download/24748t4ghkoam9h/cm-12.1-YOG7DAS2FI_%28recovery%29_%2828.12.15%29.zip
This is the recovery zip, I also have the fastboot zip if you want it?
Click to expand...
Click to collapse
Thanks very much Robin. Is that the cyanogen/android version prior to this latest OTA update? I'm looking for the official cyanogen, not cyanogenmod.
Do you know if I need to root my phone to be able to install it? Presumably I'd lose all my data?
Sorry for all the questions
EDIT: I think you sent the firmware for the Storm?
jjl5590 said:
Thanks very much Robin. Is that the cyanogen/android version prior to this latest OTA update? I'm looking for the official cyanogen, not cyanogenmod.
Do you know if I need to root my phone to be able to install it? Presumably I'd lose all my data?
Sorry for all the questions
EDIT: I think you sent the firmware for the Storm?
Click to expand...
Click to collapse
Yes it is cyanogen not cyanogenmod
and yes it is swift and not storm
robin0800 said:
Yes it is cyanogen not cyanogenmod
and yes it is swift and not storm
Click to expand...
Click to collapse
Ah ok, if you are 100% sure. Cos if it's for the storm it will probably hard brick the phone!
jjl5590 said:
Ah ok, if you are 100% sure. Cos if it's for the storm it will probably hard brick the phone!
Click to expand...
Click to collapse
I don't have a storm why would I download a storm file?
robin0800 said:
I don't have a storm why would I download a storm file?
Click to expand...
Click to collapse
I don't know xD
Did you also downgrade from the latest update?
Ok stupid question but do I need to root my phone to install the downgrade?
jjl5590 said:
Ok stupid question but do I need to root my phone to install the downgrade?
Click to expand...
Click to collapse
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
robin0800 said:
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
Click to expand...
Click to collapse
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
jjl5590 said:
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
Click to expand...
Click to collapse
You don't need a custom recovery that is the whole point of it being a signed zip
unzip first?
robin0800 said:
No its a signed Zip so should install on a stock ROM but be careful if you are downgrading the bootloader as that has been known to brick phones.
As far as I know the swift won't be bricked by this. But if you are worried I would use the fastboot zip and use a script to make sure everything is wiped first.
Click to expand...
Click to collapse
Hi,
When I am trying to
fastboot flash recovery filename
do I need to unzip the folder first?
or do I :
fastboot -i 0x2970 flash filename.zip
?
jjl5590 said:
I'm trying to follow this guide to install it but it's saying I need a recovery as well, do you happen to have that too?
http://techchomps.com/how-to-install-a-custom-recovery-on-the-wileyfox-swift/
Many thanks
Click to expand...
Click to collapse
if you can find the 12.1 fastboot zip you can revert back to factory reset stock by fastboot flashing:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
and
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
PM me if you cannot find cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip
Hi, could you please confirm if this worked? I'm on a completely stock Swift with OTA to Cyanogen OS13. I'm finding the battery life disappointing so want to try downgrading to 12.1
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Solved: Always unlock_critical when unlocking your bootloader! Some say it's optional but it can/will lead to problems!
rank78 said:
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Click to expand...
Click to collapse
Did you extract the factory image? And then place all those files in the platform-tools folder?
Badger50 said:
Did you extract the factory image? And then place all those files in the platform-tools folder?
Click to expand...
Click to collapse
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
Shouldn't all those files be in the platform tools folder?
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
I agree as well. Isn't those files suppose to be in the root folder of platforms tools folder
Put those files in that folder and do the commands again. Should work
Badger50 said:
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
Click to expand...
Click to collapse
Dirty. I'll try doing that in the morning.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
Yes but kept them in a folder so you guys can see.
TonikJDK said:
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
Click to expand...
Click to collapse
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Nevermind, wrong thread. Sorry
rank78 said:
Dirty. I'll try doing that in the morning.
It won't matter, if you haven't done the command...fastboot flashing unlock_critical
Your not going to be upgrading everything with the factory image unless you try to flash them individually. Which probably still won't work without the updated bootloader.
Yes but kept them in a folder so you guys can see.
Yep, they'll need to go in the platform-tools folder.
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Click to expand...
Click to collapse
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Badger50 said:
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Click to expand...
Click to collapse
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
Amen to that bro! ????
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
This. When I first unlocked my bootloader I didn't see to unlock critical, and when I saw afterward it was said to be unnecessary. I'll start from scratch and report back. Sigh.
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
rank78 said:
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
Click to expand...
Click to collapse
I still use TiBu to restore the data on all my user apps. Google just doesn't quite do all of that just yet
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
dd66 said:
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
Click to expand...
Click to collapse
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Badger50 said:
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Click to expand...
Click to collapse
Solved. (ran fastboot oem-info)
Thanks anyway
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.
What are the steps to rooting my phone safely?
I'm on MIUI 12.5.7.
I've done a lot of research but I'd like to confirm on here before doing anything just in case, I can provide any other information needed, thanks!
You want confirmation ? Then list what are the steps and we will approve or disapprove.
Fytdyh said:
You want confirmation ? Then list what are the steps and we will approve or disapprove.
Click to expand...
Click to collapse
I'd like a definitive list of what to do lmao, I've seen lots of different ways to do it so there's confusion on what to do.
from what I can tell the basic steps are to unlock bootloader, flash custom recovery then flash magisk?
yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.
Fytdyh said:
yes those are the basic steps. do go on. you said that you ve made a lot of "research" but so far i have not seen any. dont be lazy or you will hard brick your device.
Click to expand...
Click to collapse
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.
Canny1913 said:
Eh hard-bricks are not a big deal anymore.
As for rooting:
1)Unlock your bootloader using MiUnlock (or mtkclient if you are impatient)
This will wipe your data unless you are using mtkclient. (which to my surprise doesnt wipe data)
2)Disable Android Verified Boot (causes soft-brick if u dont)
Extract vbmeta.img from the ROM zip file then flash it using this command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2)Install TWRP
MIUI 12.5 TWRP:https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
3)Download Magisk, rename .apk to .zip then flash it.
That's it. Now you have a rooted phone.
Click to expand...
Click to collapse
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files
Luxetrixx said:
hihi, sorry for the late reply, I would've written out what I knew but this pretty much it, my main questions were which TWRP files to use and about MiUnlock, well now specifically mtkclient. Is it completely safe to use? I'd prefer not to wipe my files
Click to expand...
Click to collapse
I've watched a few videos about it and some of them were formatted, some of them were not.
Try at your own risk.
When unlocked using mtkclient it may throw a dm-verity error or fastboot may refuse to work. Both of these are normal.