Can someone please guide me on how to install magisk after installing twrp? Should I flash magisk in twrp or rename apk.
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
- Thread starter EduardoA3677
- Start date
-
- Tags
- twrp
Download magisk from here:
Download Magisk Manager Latest Version 25.2 For Android 2022
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
and as you can see, yes rename apk to zip and flash it with twrp
I downloaded and flashed Magisk V.23 Zip in TWRP and it worked. I did not rename the apk. Also, safety net passesDownload magisk from here:
Download Magisk Manager Latest Version 25.2 For Android 2022
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
and as you can see, yes rename apk to zip and flash it with twrp
What happens if I install the recent October system update when I have TWRP and Magisk installed? Bootloop?
You installed the OTA update whilst using twrp? Did it uninstall twrp after updating?
How do I install OTA update? My phone is rooted with magisk 23.0 and I have twrp installed but everytime I try to update it fails. It says installation failed https://ibb.co/9HzknQD
Also what happens after I install an OTA do I lose magisk (including the modules) and twrp?
Also what happens after I install an OTA do I lose magisk (including the modules) and twrp?
Yes, but no big deal if you are using stock, update with oxygen update and before rebooting, install Magisk to inactive slot and then reboot. Reinstall Magisk again (direct install).
Then reinstall TWRP again.
When I restore my backup, my phone goes into Qualcomm Crashdump Mode and I have to use the unbricking tool to get the phone working again. Is there a specific way you have to restore the backups?
im completely stumped and have spent hours and im fairly knowledgeable about this stuff!
ive tried:
1.msm download tool to get to stock and enable debugging but oem unlocking is greyed out when i go to fastboot and do 'fastboot oem unlock' is says flashing unlock is not allowed. i go back to stock and update via OTA.
2.now i can unlock bootloader but with new version twrp doesnt work. the touch screen doesnt work and when i try OTG mouse it sees the sd cards contents but cant see inside any folders for the zips to sideload in lineage recovery
3.eventually can get into lineage recovery but the installs ALL fail at 47% and i get stuck in a bootloop
what am i missing? i hope someone can help me
ive tried:
1.msm download tool to get to stock and enable debugging but oem unlocking is greyed out when i go to fastboot and do 'fastboot oem unlock' is says flashing unlock is not allowed. i go back to stock and update via OTA.
2.now i can unlock bootloader but with new version twrp doesnt work. the touch screen doesnt work and when i try OTG mouse it sees the sd cards contents but cant see inside any folders for the zips to sideload in lineage recovery
3.eventually can get into lineage recovery but the installs ALL fail at 47% and i get stuck in a bootloop
what am i missing? i hope someone can help me
What is needed to support a variant? be2028 T-Mo billie8t ?
Anything you ask for, I'll grab. or point me in the direction to build my own.
your builds of twrp for just plain ol' billie boots, but nothing can mount properly.
Anything you ask for, I'll grab. or point me in the direction to build my own.
your builds of twrp for just plain ol' billie boots, but nothing can mount properly.
I have the same problem and no, it doesn't hang on the loader. It goes straight to a screen requesting my unlock code (for encryption, not the bootloader) but I cannot use the touchscreen keyboard to enter any information.
I booted into the OS, removed the 4 digit pin, and rebooted using power+vol down. Now the touchscreen is working and it didn't request an encryption key.
How would one port this to another variant? This one boots on billie8t, but partitions seem to be all incorrect.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
18Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:#include <std_disclaimer.h> /* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
BUGS
-sdcard
Install guide
boot into bootloader
in bootloader type in:
Code:fastboot flash recovery TWRP.img
Important notes
-DON'T WIPE OR FORMAT SYSTEM AND VENDOR PARTITIONS
-do not use fastboot boot otherwise you will not have touch
TWRP_3.5.2_10-1
TWRP_3.5.1_2100
TWRP_3.5.1-2050
TWRP_3.5.1_10-2000
TWRP_3.4.0_sdcard_fixed-1950
TWRP_3.4.0_1900
SOURCE
TWRP: https://github.com/EduardoA3677/device_oneplus_billie_twrp33
This error will be solved in the next version that is currently in the testing phase, it was possible to install roms with this new twrp that I will launch this week3
They're all lito. That's the specific design of phone.
BE86AA is just the firmware version.
Be2025 is model version for the metrobytmobile device.2
I've got a BE2028 running the global rom (11.0.8.BE86AA) a working recovery is all thats needed to make things like Lineage work so this device can continue to get the updates(and not just security updates) since OP has abandoned em.
I'd be willing to test any built things you have.
