As the title states...
I downloaded the appropriate boot.img version for my current version of Oxygen OS, I patched it with Magisk and then flashed it. Now my phone will not boot beyond the fastboot bootloader.
I've tried flashing firmware again but continue to be stuck in the bootloader.
Any suggestions would be very appreciated.
What guide for rooting are you following? I don't recall ever having to do this, you can just install Magisk from custom recovery (e.g. TWRP) (and then, again, as an app, once loaded). Just need to rename to have .apk and .zip for app and system loads, respectively.
As far as [recovering from] your case... while you could likely play until it is figured out, the MSM tool is probably the easiest and safest bet. Yep, phone gets wiped, but a 99.999999% chance of unbricking as long as it isn't physically broken.
Related
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.
Hey I just picked up this phone and decided I would like to maximize it to its fullest potential, and root it as I have done with previous phones. This ones giving me a hard time, and I just can't seem to find the proper info for it.
I have unlocked the bootloader, flashed TWRP 3.1.1 and want to gain root access. I have followed several guides, used every possible one-click unsuccessfully, and tried installing SuperSU with TWRP. After I reboot, SuperSU is installed. I'll open it up and it tells me the binaries are occupied. I've tried downgrading and updating the binaries but I get errors. (I believe this is because it must be rooted first - of course.)
So I'm stuck unable to get any further. If anyone has any suggestions, I would appreciate it. Is this phone with this configuration unrootable? There must be a way if I have recovery right?
Asus Zenfone 4 Z01KD/ZE554KL
Android Nougat 7.1.1 - 14.1060.1708.63 (NOT 1708.70)
TWRP 3.1.1 installed
One thing I have not tried is using Magisk. When I try it, it stops because I already patched with SuperSU (even though it failed). I never backed up before I did it with SuperSU I really thought it would work.
I read of people doing it with Magisk after updating to Oreo. I want to give that a try but I can't OTA or flash from TWRP. All attempts result in error 7.
I can't find a stock recovery to flash to do the update either. Is there a way to undo this, OTA and repatch with Magisk? Even if I don't bother updating, I would like to find a stock image to flash so I can try patching with Magisk.
Stock rom recovery.img anywhere? Am I alone?
i dont own this device but i read this and it might apply to you. also did you flash the supersu uninstaller and them try magisk?
https://forum.xda-developers.com/zenfone-4-2017/development/twrp-3-1-zenfone-4-2017-ze554kl-t3690349
hey i have the zenfone 4 ze554kl i updated it to android 9 unlocked the bootloader and got Twrp running but not correctly and i can't root the phone .....
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.
Hi all,. for a friend I am trying to root a G398FN (PHN) with Magisk and a patched boot file. I went thru the unlocking process at the bootloader, I took the latest android Q firmware and with 7Zip Zs I unzipped the AP file, and then I got the boot.img.
Magisk says it is patched, then I use ADB to GET the file back on my PC, and then I flash it with Odin.
I have tried all sorts of combinations, flashing the patched boot alone, flashing the enitre AP file, flashing the patched AP file alone, and the complete firmware, but in any case I end up with a phone that should have a patched boot, but doesn't. Magisk is not a stub, and Magisk asks for the original rooting method.
Does anybody know what I am doing wrong here ? The patched boot is downloaded via ADB, then flashed with the latest Odin but the phone is not accepting the changes.
So i Have a Xcover 4s G398FN with android Q latest firmware, latest Odin, unlocked bootloader and I have tried almost every combination there is to make the phone work with the patched boot. What is happening here? Any help would be greatly apreciated.
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.