Related
Obviously I'm not responsible for your mom exploding or your phone disowning you, but.....
I got tethering and Android Pay working on stock Nougat - that's Android N, folks - on a Nexus.
(confirmed will work on Marshmallow and up on 5, 5x, 6, 6p...etc.)
Thanks to @Chainfire, @ManHands and @interloper, and you!
click thanks if this helps, or buy me a beer or something.
prerequisites:
working adb and fastboot (from platform-tools in the Android SDK if you don't know where to find it)
twrp .img for your device
latest stable systemless supersu
1. be on Marshmallow or Nougat obviously
2. flash twrp
(volume down + power on nexus gets you into bootloader, then after flashing recovery, use volume buttons to scroll and power button to select recovery mode)
3. flash systemless root while booted into twrp (unsure if .supersu SYSTEMLESS=true in /data is still needed, but can't hurt - mine is still there from earlier.)
4. while still in twrp, go to mount and check system. Make sure you allow changes.
5. from your computer, do this
Code:
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop
6. reboot into Android.
7. Install Terminal Emulator from the Play Store.
8. Launch it, and in Terminal Emulator, do this
Code:
su
settings put global tether_dun_required 0
exit
9. go into Supersu, expert, scroll to the bottom and hit full unroot. No, you don't want it to patch you back to the stock boot image or recovery*. If it hangs, just reboot and try doing it again.
10. ????
11. Profit! You should have tethering unlocked, be unrooted, and have full Android Pay goodness working.
To take an OTA, do this, because Flashfire gets confused after you've done build.prop edits -
1. go to About Phone, scroll down. Find your build number.
2. download that Nexus Factory Image.
3. Unzip it all. ALL OF IT.
4. Make sure you have Android SDK & platform-tools (or just a working Fastboot and ADB)
5. just flash boot, system, and recovery - you can now OTA with no problems. Then repeat the above guide on your new OTA. Confirmed working 10 minutes ago, OTA'ing from Marshmallow to Nougat and then getting tethering working again
ALTERNATE IF YOU PREFER FLASHFIRE:
All the above steps, but you only have to flash the System image to fix the build.prop hash fail then flashfire should work for you. Wouldn't necessarily recommend upgrading version numbers (6.0.1 to 7.0.0) with Flashfire, but who knows, it might work great! Chainfire is a wizard.
*you can do this if you want, but when I let it patch my boot image I got the dreaded "device corrupt!!!!1" message at boot. Did not try letting it flash stock recovery image.
You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?
codycook said:
You're mentioning to do a systemless root but enable read/write on the system partition. Isnt't that counter-intuitive?
Click to expand...
Click to collapse
Nope! rw system is only for the build.prop echo, other than that you don't touch /system
Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
Hmm. Bummer. For a split second, I felt like I finally had a fully functioning Android
Almost regret upgrading to NBD90Z, but figured it would be less buggy. If anyone has figured out how to get AP and NBD90Z to work with a slightly modified build.prop file (to allow tethering), please update this thread!
cal028 said:
Yes i'm seeing this also and other not root methods for tethering don't not seem to work either with NBD90Z .
Click to expand...
Click to collapse
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z
w8291 said:
same for me too. Pulled build.prop and verified net.tethering.noprovisioning=true and settings put global tether_dun_required 0
still no luck on NBD90Z
Click to expand...
Click to collapse
Flashed back down to NRD90S and the method works again.
Where did you download that version?
The stock Nexus 6 images on the official Google site do not list that version as valid for the Nexus 6.
Are you using the Nexus 6P image?
May be a dumb question but I have a Moto X Pure running Ressurection Remix nougat ROM and I don't have WiFi tethering in my settings. Would this method work on it?
worked, thanks
n8onXDA said:
Have you been able to get this to work with the latest factory Nougat images from Google's website?
I successfully did your process above when I was on an older version of Nougat for Nexus 6 (beta release), but when I try now with NBD90Z Google Pay won't work after rooting after a full unroot.
Click to expand...
Click to collapse
With the current build, no methods work. SafetyNet check fails with the last 2 builds
Safety net now requires OEM lock, even fully stock with open bootloader never rooted fails
Sent from my Nexus 6 using Tapatalk
Ok great! Well at least I know I'm not missing some clever workaround. Isn't there a way to bypass SafetyNet and/or OEM lock? I thought someone was trying or working on something like this...
wrecklesswun said:
With the current build, no methods work. SafetyNet check fails with the last 2 builds
Click to expand...
Click to collapse
So I read that the March 2017 7.1.1 Update for Nexus 6 broke Android Pay even on non-rooted devices so Google released images with SafetyNet disabled. Would that version allow us to root AND use Android Pay since SafetyNet is disabled to make it work for regular users?
Had to do this but gaining root was going to be tricky (encrypted partition), and I didn't need root for any other reason. I unlocked the bootloaded, flashed twrp, and used adb to pull build.prop, added the line in (net.tethering.noprovisioning=true), pushed it back using adb (with twrp still running), and rebooted. Tethering is working fine now.
By the way -- this is so infuriating. When tethering does not work it asks your provider's permission even in airplane mode (which fails, it's airplane mode), so you can't use the phone to provide wifi to other devices. Such an amateurish disrespect for my rights as an owner of an unlocked device.
I flashed Vanilla rom 7.1.2, then flash stock recovery and locked bootloader and Android pay, Netflix and Snapchat etc all work. After I flashed Vanilla rom Android pay wasn't working stating I had a root, so I locked bootloader but was bootlooping into twrp. After flashing stock recovery it worked just fine
I discovered that you can you can have TWRP recovery and still use android pay so long as you have your bootloader locked. I am pretty sure you can still flash roms w/ locked bootloader in recovery but I am not positive
First off I am not criticizing the amazing XDA developers here, and all the people that help make root and ROM's happen.
This is aimed at Essential the company themselves
I was under the impression the Essential Phone was sort of like a Pixel, or Nexus, or OnePlus type of phone. Meaning running a near stock Android OS, an unlocked device, easily rooted. For example when a new OnePlus phone is released, root is out super fast. But the reason the Essential Phone has not been rooted yet is because of Essential holding back the factory images on us still. I guess I have to ask why would Essential do this ? I thought they touted this phone as a open platform, very similar in idea to the old Nexus line ?
The Essential Phone has been out 2 months now, and the important files for rooting still have not been officially released to the public yet ? What's up with Essential holding back so long ?
https://ibb.co/mgaVcb Mine ist rooted
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Last I read was the boot image that was pulled didn't enable root with magisk and hadn't seen anything more from it. Did you have to do anything specifically?
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Interedasting.
It'd be great if you could provide further proof/instructions.
Thanks a bunch.
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either.
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
*Found the thread here:
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583
kchino said:
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either. Maybe it was a Larp ¯\_(ツ)_/¯
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
Click to expand...
Click to collapse
Pretty sure the staff that did the AMA was just the design staff, not software staff. As soon as the files are released it will take about a day I bet for root. I remember seeing a thread on reddit that you are referring to as well. I think the people who can root it won't until the files are released. One **** up and they have a very expensive brick.
Thanks for the replies. So any idea as to when this source code image files will get released from Essential ? What's their holdup ?
Agreed, dicey proposition with no factory images.
We have devs working on it. Root has been achieved and there's a TWRP build but the touchscreen doesn't work you have to use a mouse to navigate. Also, there's no factory images yet to go back to stock in case of a problem. Once they iron out the issues I'm sure someone will release a guide.
Currently on the Nexus 6P, that's getting bad. I really want the Essential phone, but only if root comes out for sure, also ROM's would be great.
Otherwise I may just wait for the OnePlus 5T announcement, and if it's $500 go that route instead. At least the 5T will have good development
Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Man how did u root?? I really wanna root
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Can you provide the file for TWRP and boot img?
drocny87 said:
Can you provide the file for TWRP and boot img?
Click to expand...
Click to collapse
Just join the Discord Server and load it from there.
Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Thanks
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Z-Fire821 said:
Just join the Discord Server and load it from there.
Click to expand...
Click to collapse
What's the link to it?
ROOT
Guys, if you truly, truly want to root your device, follow these steps. Just remember, I am not responsible if you end up bricking your device (and neither are the main developers currently working on TWRP and Lineage). YOU ARE RESPONSIBLE FOR WHAT YOU DO ON YOUR OWN DEVICE! (also this probably voids warranty btw)
THESE INSTRUCTIONS ARE FOR NMJ20D.
Now, one more thing. Remember, this TWRP build is very much in alpha stages and there are some major bugs with it, including no touch support and no crypto. Also, when I rooted, I had to use my USB OTG Mouse in order to maneuver around TWRP, but with this method, hopefully anyone can do it, without the mouse. The boot.img I will provide is the NMJ20D boot.img with the patches that Magisk puts in when you install it, so it's not exactly stock. Also, you might need to factory reset your device via the stock recovery (and make sure not to boot it back up until after you flash Magisk) just in case, since TWRP is buggy with crypto atm.
You can find a dump of NMJ20D here, in case you need to fix a bootloop (due to a bad Substratum theme, etc...) -- (you'll likely need only boot_a.img and system_a.img (within the system_a.zip).
If you wish to return to stock in order to accept OTAs, feel free to flash the unofficial factory images here and, should OTAs still fail, you may be required to wipe your data, which can be done via "fastboot -w". (Side Note: I believe the script included within the unofficial factory images also flashes the firmware to both partitions, so if your fingerprint sensor is seemingly absent or not working, this might actually fix it, as it has for some custom ROMs on the Essential.
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course, your bootloader must be unlocked.
1. Reboot your Essential into fastboot mode. Once in fastboot mode, flash TWRP via
Code:
fastboot flash boot twrp-mata.img
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type
Code:
adb shell twrp sideload
and then
Code:
adb sideload magisk.zip
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
Code:
fastboot flash boot boot_a.img
4. Now reboot! You should now have root and stuff via Magisk!
Appreciate the root guide, guess I can pick one of these up now to play around with. Awesome!!
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk![/QUOTE]
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
shooterlgk said:
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk!
Click to expand...
Click to collapse
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..[/QUOTE]
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?
bmg1001 said:
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
Click to expand...
Click to collapse
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?[/QUOTE]
I should of took a picture cuz I can't remember but it does give me an error tho ..I'm gonna retry when I get home from work but I literally sat there for almost 3 hours attempting to root to no success
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.
So i've exhausted almost every xda thread I can find, and finally decided to make a post myself. This is maybe the 6th or 7th time I've had to MSM tool my phone because I softbricked and could only access bootloader. I'm a newbie so you may need to go in detail in what I should do. All help is very appreciated.
I'm trying to flash a new ROM to my phone, the one in question is the latest nightly build of LineageOS: lineage-17.1-20200806-nightly-fajita-signed.zip, the ROM itself works fine, however, flashing TWRP after flashing this rom (even if I wipe dalvik/cache) I no longer am able to access wifi). I've flashed stock and started over about 5-6 times (from the very very beginning, including unlocking the bootloader) and I'll always end up with a wifi issue or a bootloop.
I've tried multiple different versions of twrp, including the unofficial 3.3.1-32 Q unofficial builds from this guide and both 3.4.0-0 and 3.4.0-1 from the official website, both leading me to the same results. (the unofficial build wouldn't decrypt, so I failed with that one).
I'll go through the steps I do in detail, and if anyone sees an issue with my process, please correct me.
1- enabled developer options
2- enabled usb debugging and oem unlocking in developer options
3- booted into bootloader with
Code:
adb reboot bootloader
4- checked to see if phone is connected and unlocked the bootloader with
Code:
fastboot oem unlock
5- set up my phone again, enabled dev options, and enabled usb debugging again.
6- booted into bootloader again
7- typed this into the terminal to temporarily boot TWRP
Code:
fastboot boot <recovery_twrp>.img
7.5- flash copy-partitions.zip from the LineageOS install guide
8- went to advanced>adb sideload>swiped then went on adb terminal to sideload TWRP installer
Code:
adb sideload <twrp-installer>.zip
9- went to menu>reboot>recovery
10- after rebooting went to wipe>factory reset slide>swiped slider
11- went back to menu>advanced>adb sideload>swiped then went on adb terminal to sideload (while checking wipe cache/dalvik)
Code:
adb sideload <lineageOS-rom-nightly>.zip
12- tapped reboot system
this is where things begin to go wrong:
- i notice that I can't boot into lineageOS, lineageOS claims android data is corrupted and needs to factory reset
- factory reset phone
- boots up fine, go through set up process (wifi works right now, only problem I notice is that within build settings, it shows a completely different phone number on my SIM card rather than the phone number I actually have, but it doesn't look broken or corrupted), enable usb debugging again, boot into bootloader
- type
Code:
fastboot boot <recovery-twrp>.img
- twrp loads up fine
- go to menu>advanced>adb sideload>swipe to begin sideload then type
Code:
adb sideload <twrp_installer>.zip
- reboot system
- boot process takes forever, (restarts 3-4 times) phone feels sluggish, and wifi will no longer work (data works fine)
- i give up and I MSM tool my phone.
I genuinely think this is because of TWRP, I read through a few xda threads claiming that the official 3.4.x builds had many issues, and therefore would reccomend using 3.3.x builds. I tried both from the official website and the unofficial TWRP by mauronofrio, where i get decryption problems on both of them. only 3.4.0-x TWRP builds would get me as far as flashing the rom. I've tried this process on both android 10.3.0 and 10.3.5
I genuinely would like some help. this phone is my daily driver and not being able to use TWRP (let alone properly flash a ROM) is a big problem that destroys what I loved about my phone in the first place. Thanks in advance.
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Extreme_Ninja2099 said:
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Click to expand...
Click to collapse
Im not rooted, im coming from unrooted 10.3.5
OhioYJ said:
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
Click to expand...
Click to collapse
this worked!! thank you so much for such a great guide!
I did one thing differently though, instead of using the fastboot rom or running it through scripts, I used the copy-partitions.zip file available on LineageOS' fajita install guide to make both partitions appear the same. I realized my mistake when I didn't flash the rom twice, as that's mandatory when it comes to A/B partitioned phones
Everything works smoothly! thanks!