so cancel what I said about it working...Apparently once I have gone back into the system I won't have TWRP anymore. I can't get back into it. I have to start over again to get into TWRP
it is the 2020-06-11_22-14-29_twrp_stock_akari_52.1.A.2.1. I removed it and re-downloaded it. Still, I get no mention of a ramdisk in either the advanced menu or the install menu. I have reload theme/partition sd/fix contexts in advanced. In install menu under image it doesn't give me a choice...
I mentioned this earlier... When I go into the advanced menu on twrp I don't see the "Install recovery ramdisk" anywhere! It's not there. I can't install the ramdisk..
Yes. I am on stock rom. Fastboot flash boot boot.img then re-installed twrp, vbmeta, magisk 18.1.
Originally when I did this on Sunday night, all was fine. But it just started bootlooping out of nowhere this morning and doing the above wouldn't stop it this time.
I did go back to 18.1 but my phone was only good for 24 hours...Now I have re-installed the rom, wiping my user data, and am re-installing backups as I type. Hopefully I am good...
After Magisk 19.1 boot looped my phone, I went and flashed the regular boot.img and then re-rooted my phone. It worked fine for a little over 24 hours but now my phone is back in boot loop and installing the kernel isn't doing anything.
the uninstaller bricked my device. I had to flash the boot.img from fastboot to get the device back. Now I ave to start over to root. Which i will do later.
Hi MartinX3, maybe could you update post #3 to show how to go from Oreo to Pie when rooted/drm fix. Not that I have the DRM fix...I have a driver issue apparently. But it'd be helpful to have ALL instructions in one place.
I have the same thing happening but windows won't let me install these drivers. Says the folder specified doesn't contain the drivers for this device. I have the driver signing off...
I have noticed the root Hecker app says something is wrong with the su binaries....
---------- Post added at 11:59 PM ---------- Previous post was at 11:46 PM ----------
That's the problem I am having
The Sony drivers stopped working since the XZ.. I get a message saying that the files cannot be found or that it's not for my device. I was able to get the xz2 driver to work on the laptop prior to unlocking.
I usually have the firewall off...I was using the google drivers because sony drivers will not install on my machines. I also tried with samsung drivers...
Sony drivers xx15-xx19 with enforcement off and windows in test mode will not install those drivers. I have removed all traces of mobile...
I gave it a few more tries. I started over installing twrp, vbmeta, then when in twrp after each step I used adb push to send a file to the SD card with no problems. Then I tried to install the drmfix and it didn't work
I think I should try again. I couldn't find a file that was labeled twrp-installer.zip for my xz2 only in the universal, but it's one of the steps in your instructions so I used the universal one. Where is the installer for my device?
Yes to A?B and Vendor mode, Xperifix does find my device at the beginning, when I am in fastboot, once I set it up as you mentioned and fix my device, it asks me to put it in TWRP mode, then I click TWRP ready and it tells me there was a problem.
No matter what I do, and I have followed everyone's advice here so far, I cannot get past the second step with disabling vbmeta verification. I always get> fastboot: unrecognised option `--disable-verity
I have tried every driver I can get to install from the google adb drivers in the sdk to...