Hello. If i run twrp through fastboot boot command and flash magisk and use systemless root, will i be able to lock the bootloader using fastboot oem lock? Technically i did not change the recovery image. I planned on making a few changes to a few apps (patch ytb to background and remove google ads) then unroot and remove magisk and lock it.
Root is a no go back option. If you unroot, stock rom will reupdate itsrlf
Sent from this galaxy
i recieve OTA uodates since i have another system (MIUI). I tried flashing everything (literally every single thing, 15 fastboot commands) except boot and system images and then locking but it didnt work. Unfortunately had to keep magisk. Nop. Doesnt work. Only way, - fullstock or stock based builds roms.
Related
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.
How i can root lolipop stock ROM of lenovo tab 2 a7-10f ?
I have tried kingroot and much more methods, but doesnt support.
I heard people say that lolipop version cant be rooted, just kitkat version which is first ROM. Lolipop is OTA upgrade from Lenovo.
I dont want to flash ROM, i want to use some tools which are available throught root.
I have tried flashing TWRP throught unlocked bootloader (fastboot), when i run command:
fastboot flash recovery c:\twrp.img
It says, done.
But i cant eneter recovery, and i flashed it multiple times, and it says it flashed fine.
But when i use key combination i enter in stock recovery.
And i tried diffrent command (i didnt know that command is bad idea)
fastboot flash boot c:\twrp.img
And i stucked in twrp recovery, it coudnt boot in normal system, because i changed what android should boot.
I extracted from stock ROM, boot.img and flashed it only in fastboot.
And booted normaly, but when i run on recovery, i saw i deleted it's stock recovery.
I was freaked, and i didnt touched anything anymore, i lost stock recovery but i dont care, i care that tab is still alive.
I'm not able to flash anything in any other way that fastboot which is quite scary to use if tab is working good (i dont want to break if something works)
How i can root it.
I have knowledge of adb commands but with all that knowledge i didnt managed to get root to this device, it looks like it's locked in that way.
Lolipop is best, it is very good and accesibile, and i just want to tweak it more with some xposed modules and apps that support root.
Hi all,
I have read about how to install Twrp, with method described for flashing roms, but i need twrp only for flashing mods eventually and nothing more, and i need to receive ota.
Which is the simpliest and secure way?
Boot.img method or fastboot slot a/b?
Hope i was clear enough and thanks all in advance.
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
_mysiak_ said:
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
Click to expand...
Click to collapse
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
HTCDevil said:
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
Click to expand...
Click to collapse
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
_mysiak_ said:
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
Click to expand...
Click to collapse
Thank you again, you are right, probably magisk is more secure than if you haven't it once bootloader is unlocked
Correct me if I'm wrong, but I've learned that TWRP has not been released for this device yet. I need to use Magisk to modify the boot image, then flash it using fastboot. So I would have rooted, without unlocking bootloader, without installing TWRP.
I have two questions. My first question is, is it safer to unlock the bootloader now for anticipation of a future TWRP release?
Scenario 1: Keep bootloader locked, maybe root. But when TWRP is released, in order to flash a custom recovery, I'll need to unlock bootloader, which will wipe all my data, which I don't want.
Scenario 2: Unlock bootloader now, maybe root. When TWRP is released, I can install it without needing to factory reset.
Question 2: Should I root now or wait until TWRP is released? I am used to using systemless magisk. In TWRP, I used to choose the option for mounting system r/o and flash magisk systemlessly. However without TWRP the option is to patch the boot image. I'm confused as to whether or not this still constitutes a systemless root. Is there any difference between
A) rooting using patched boot image with fastboot
B) flashing magisk systemlessly in TWRP
You cant have root with locked bootloader. And to answer your last questions in both scenarios you do the same but in different way
You'll need to unlock the bootloader in order to root, regardless whether a custom recovery is working or not.
Question 2:
Systemless magisk means it doesn't touch your system.
(And ift literally can't, since in Android 10 it's permanent read only)
There is only one way to root with magisk, and that is by patching the boot image. With TWRP you do it on the fly, but since we don't have TWRP we extract the boot and patch in manually. Same thing, just 2 different ways.
(So of course, it's still systemless)
Sent from my OnePlus7TPro using XDA Labs
EugenStanis said:
You cant have root with locked bootloader. And to answer your last questions in both scenarios you do the same but in different way
Click to expand...
Click to collapse
Lossyx said:
You'll need to unlock the bootloader in order to root, regardless whether a custom recovery is working or not.
Question 2:
Systemless magisk means it doesn't touch your system.
(And ift literally can't, since in Android 10 it's permanent read only)
There is only one way to root with magisk, and that is by patching the boot image. With TWRP you do it on the fly, but since we don't have TWRP we extract the boot and patch in manually. Same thing, just 2 different ways.
(So of course, it's still systemless)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Thanks for the clarification guys.