How do i keep root on CM 13? Everytime i flash su2.65 it say boot certification verify and i have to factory hard reset and twrp all over again. DT2W doesnt seem to work. Do i need to be rooted?
Related
Hey guys, i have installed CM 12.1 on my LG G3 D855.
Everything seems to work fine and correct.
Only one problem is left, i made a factory reset (in settings), the phone rebooted. It rebooted in Recovery (TWRP) but there it stuck in a boot loop. I removed the batterie and and restarted the device. Now it boots correct, but i think my TWRP is still broken. Is there a way to fix it?
Can i simply use e.g. Flashify app to install TWRP correct again?
Don't ever perform a factory reset or take an OTA update w/ a third party recovery like TWRP installed. You're lucky you were able to get the phone to boot normally. There's probably nothing wrong w/ TWRP, but yes... you can use Flashify again to re-flash recovery.
Okay, i thought it will only reset the CM - specific settings and not the LG ones.
Can i use "OTA"-CM Updates? As i am using the Nighties and there is an Update everyday - or should i just update once a week?
Could there be a problem with my "broken CR?
As you have said I can use Flashify for flash TWRP again, can i use the normal files which are made for stock, or do i have any special CM ones?
Thanks.
hey,
I wanted to root my nexus 5x too, first I tried to do so with the nexus tool kit....
it was all working until it came to the root process:
it said in the log:
Rooting....
Waiting for your device....
and nothing else happened anymore.
So I tried it manually with a guide.
As the bootloader was already unlocked, I continued with flashing the recovery (twrp 2.8.7.2) in fastboot.
Then it rebooted into the recovery.
Then twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I allowed the system modification then... so then before rebooting, twrp wasn't asking me if I want to flash the SuperSu.
Since this I'm stuck in a bootloop.
I can boot into the bootloader and recovery, I also tried to do a factory wipe or also formating data. But none of them worked for me. I'm still stuck in the bootloop...
I have no idea what to do now....
I'm really thankfull for every kind of help!
sorry wrong subforum...
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Vulkaistos said:
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Click to expand...
Click to collapse
I have to add something which i forgot to mention.....after I flashed the recovery and booted into it for the first time, twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I'm not able boot my phone up anymore.... I can try to flash the recovery with fastboot again...if this is what you mean?
okay i pushed the supersu zip onto the phone, and just flashed it. And my phone is booting normally now
thank you very very much. you saved me and my phone
That's nice to hear.
Have Fun with your Phone!!!!!!!!!!!!!!
Hello.
I was trying to complete https://forum.xda-developers.com/xperia-m5/development/kernel-stock-marshmallow-kernel-root-t3453072 this guide to keep all my drm keys. But I got a bit lost in moment when I need to "flash_dk". Then I installed twrp recovery and after it found out how to pass through Dk thing. But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Jeffrrey said:
But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Click to expand...
Click to collapse
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Everlastingman said:
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Click to expand...
Click to collapse
Flashing magisk through adb sideload worked. Thanks for your time, I don't know how to close threat
Hi,
I dont know what I am doing wrong, really.
I managed to unlock bootloader and install custom ROM, everything works fine then.
I install TWRP without an issue. I can decrypt partition by wiping all. Once I flash SuperSU 2.82 or Magis 18.1. I get a bootloop when trying to reboot. I waited like 15 Minutes. Also tried KingRoot.apk methid, didnt work.
So no way to get root access works for me?
Any idea? Thanks!
Best
UPDATE: It worked now.
How? Download TWRP from here: https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
Install latest Magisk 18.1.
Done
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
mmedei9 said:
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Click to expand...
Click to collapse
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
polfrank said:
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
mmedei9 said:
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
Click to expand...
Click to collapse
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
polfrank said:
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
Click to expand...
Click to collapse
Of the handful of tutorials on the forums, which would you recommend for flashing TWRP and rooting the device?
Would it require me flashing the global rom in the place of my global (EEA) rom?
polfrank said:
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Attention because there will be no more updates for the redmi note 8 pro concerning the rom xiaomi.eu! (announcement on their site ...)
I flashed patched boot image without disabling avb and now I'm stuck in bootloop.
Is it necessary to disable avb before flashing patched image through fastboot?