Because of a defect, my phone is no longer rooted/unlocked. Unfortunately Huawei substituted it with a new one, instead of repairing my old phone.
So my bootloader is locked, there actually is no possibility to unlock and I don't know, if I would pay for it again, because even with root the possibilities with Huawei's restrictive policy are limited...
So I won't patch any files anymore, but if you'll provide your patched/unpatched files, I will update this thread furthermore.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
EMUI 9
You may not have root, if you don't (re)start as if you wanted to start recovery mode: [Vol+]+[Power]
All provided files are for customisation C432 - I don't think, there is any difference to other customisations, but I don't know exactly and don't warrant it.
EMUI 9.1
Important Note for EMUI 9.1: Actually the phone can't boot to recovery by holding [Volume +], so you have to do it in adb-mode:
Code:
adb reboot recovery
If not, you won't have root, even with patched recovery_ramdisk.
Issues:
The feature to charge the powered off phone will be broken - as soon as you connect USB, the phone will boot up.
You won't have any working recovery. If you need your original recovery back, reflash unpatched recovery_ramdisk.img with fastboot in the same way.
Requirements / Downloads
Mate 10 (Pro) with unlocked bootloader
Minimal ADB & Fastboot
If you own ALP device (build 159): (for some newer versions see instructions below to get your own recovery_ramdisk)
Unpatched Recovery_Ramdisk ALP 9.0.0.159
Patched Recovery_Ramdisk ALP 9.0.0.159
If you own BLA device (build 161): (for some newer versions see downloads below)
Unpatched Recovery_Ramdisk BLA 9.0.0.161
Patched Recovery_Ramdisk BLA 9.0.0.161
latest Magisk Manager stable build
I. Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder. [If you don't want/can use my provided files, go now to step II.1. to patch your own file and root with it]
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk [I]name_of_your_patched_file.img[/I]
(You must adapt the file name to the real name of your file, e.g. RECOVERY_RAMDISK_PATCHED_BLA_EMUI_9.0.0.161.img)
6. Reboot with this command "fastboot reboot recovery" or shutdown and press [Vol+]+[Power].
7. Download Magisk Manager (latest stable build) and install.
---If you used my provided file, now you are ready and rooted.---
II. How to get the fitting recovery_ramdisk for your own OS version
1. Download Huawei Firmware Finder, search for your device and download your desired firmware version.
2. Extract update.app from downloaded update.zip.
3. Download Huawei Update Extractor, start this tool, go to "Settings" and uncheck "Verify header checksum".
4. Go to "Extract" and open your update.app.
5. Extract RECOVERY_RAMDIS.img (Yes, there is no "k" at the end), rename it, if you want to, and then transfer it to your phone, if you want to patch it (instructions see above).
III. Install Magisk Manager and patching files by yourself / root with your own file
1. Download Magisk Manager (latest stable build) and install.
2. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk and root with your own file:
3.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
4 Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk [I]name_of_your_patched_file.img[/I]
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
3.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Download options for some unpatched/patched files
ALP 9.0.0.159 (C432) unpatched / patched
ALP 9.0.0.194 (C636) unpatched / patched
ALP 9.0.0.195 (C636) unpatched / patched
ALP 9.0.0.213 (universal cust) unpatched / patched
ALP 9.0.0.217 (C636) unpatched / patched
ALP 9.0.0.228 (C636) unpatched / patched
BLA 9.0.0.161 (C432) unpatched / patched
BLA 9.0.0.179 (C432) unpatched / patched
BLA 9.0.0.197 (C432) unpatched / patched
BLA 9.0.0.206 (C432) unpatched / patched
BLA 9.0.0.211 (universal cust) unpatched / patched
BLA 9.0.0.215 (universal cust) unpatched / patched
BLA 9.0.0.223 (universal cust) unpatched / patched
BLA 9.0.0.224 (universal cust) unpatched / patched
BLA 9.0.0.226 (universal cust) unpatched / patched
BLA 9.0.0.231 (universal cust) unpatched / patched
BLA 9.0.0.233 (universal cust) unpatched / patched
BLA 9.0.0.238 (universal cust) unpatched / patched
BLA 9.0.0.243 (universal cust) unpatched / patched
BLA 9.0.0.246 (C432) unpatched / patched
BLA 9.0.0.259 (C636) unpatched / patched
Thanks to
@topjohnwu - magisk developer
@gmanrainy (Team MT) - Huawei Firmware Finder
@worstenbrood - Huawei Update Extractor
probably stupid question, but the device must be with boot loader unlocked right??
Sent from my BLA-L29 using Tapatalk
optiplex2012 said:
probably stupid question, but the device must be with boot loader unlocked right??
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
Yes, this is mandatory to flash imgs by fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
is that a official twrp recovery for mate 10series?
for me , really want to go back to emui8.0 ..and flash treble Roms
---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------
anyway thx
craigzhong said:
is that a official twrp recovery for mate 10series?
for me , really want to go back to emui8.0 ..and flash treble Roms
---------- Post added at 01:54 PM ---------- Previous post was at 01:54 PM ----------
anyway thx
Click to expand...
Click to collapse
There is no TWRP recovery, that is compatible with EMUI 9. This solution isn't based on TWRP...
To downgrade to EMUI 8, look there or there.
Hello
Here is a clear and precise procedure good work a big thank you.
Even if I restart my phone normally I do not lose root in any case for me his walk.
dany67310 said:
Even if I restart my phone normally I do not lose root in any case for me his walk.
Click to expand...
Click to collapse
Yes, you're right. I tested it too. I think, this was valid for topjohnwu's first canary build, that was able to root EMUI 9.
I will remove my warnings from opener.
What does not work for me is fx explorer I did not pass link2sd to freeze apps because impossible with fx explore otherwise all work like a charm.
dany67310 said:
What does not work for me is fx explorer I did not pass link2sd to freeze apps because impossible with fx explore otherwise all work like a charm.
Click to expand...
Click to collapse
I think, this is rather an EMUI 9 or Android 9 issue with that app than a Magisk issue.
This is the address
This is the address that needs to be added to the magisk
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
Athanatos81 said:
I think, this is rather an EMUI 9 or Android 9 issue with that app than a Magisk issue.
Click to expand...
Click to collapse
That's what I think too.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
Sergiocubano1 said:
This is the address that needs to be added to the magisk
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
Click to expand...
Click to collapse
Yes
dany67310 said:
That's what I think too.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
Yes
Click to expand...
Click to collapse
although it did not work for me in any way, the magisk still does not appear [emoji22]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado desde mi ALP-L09 mediante Tapatalk
Sergiocubano1 said:
This is the address that needs to be added to the magisk
https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
Click to expand...
Click to collapse
The forum software shortened my link ...
Thanks.
Sergiocubano1 said:
although it did not work for me in any way, the magisk still does not appear [emoji22]View attachment 4681545
Enviado desde mi ALP-L09 mediante Tapatalk
Click to expand...
Click to collapse
Did you flash the patched recovery_ramdisk.img with fastboot?
If yes, shutdown your phone and try to restart by pressing [Vol+]+[Power].
Athanatos81 said:
Did you flash the patched recovery_ramdisk.img with fastboot?
If yes, shutdown your phone and try to restart by pressing [Vol+]+[Power].
Click to expand...
Click to collapse
it's worth it now yes I got it many thanks [emoji7][emoji847]
Enviado desde mi ALP-L09 mediante Tapatalk
---------- Post added at 07:07 AM ---------- Previous post was at 07:06 AM ----------
Athanatos81 said:
The forum software shortened my link ...
Thanks.
Click to expand...
Click to collapse
if it was that when I put your link I got an error and I did not skip the magisk actu and looking on the internet if with that and if it worked
Enviado desde mi ALP-L09 mediante Tapatalk
Hi, the installation for the other applications works well, but how to use the modules magisk? they do not install any module ..
pacifox said:
Hi, the installation for the other applications works well, but how to use the modules magisk? they do not install any module ..
Click to expand...
Click to collapse
You have to be more specific.
Is there any error message? Did you notice the max. Android /API number of the magisk module?
I've got several modules installed...
Athanatos81 said:
You have to be more specific.
Is there any error message? Did you notice the max. Android /API number of the magisk module?
I've got several modules installed...
Click to expand...
Click to collapse
Same error for all module... see screenshot
Thank you very much, with your method I root my honor 10 view under emui 9 with my own patch.
Related
Here is TWRP for the Mate 9. This works on Android Pie (EMUI 9.0). I ported it over from the Mate 20 X and themed it with my Black & Blue theme. Thank you to @freeza for the original recovery. Flash this in adb with the fastboot flash recovery_ramdisk twrpxxxxxx.img. Then in TWRP you can flash this TWRP image file to erecovery_ramdisk and then flash the rooted recovery_ramdisk to recovery_ramdisk. Then you'll have root on regular recovery and TWRP on erecovery. To be rooted when you boot you have to hold in volume up at boot. It will boot normally into Android and you'll be rooted. If you don't hold in volume up while booting you'll be booted normally with no root. To enter TWRP boot with the USB cable plugged into your computer and hold in volume up. If you don't want to do this then simply choose either root or TWRP and flash the appropriate img file to recovery_ramdisk. Decryption will not work on EMUI 9.1.
TWRP
https://www.androidfilehost.com/?fid=1395089523397925791
L29C636B159 Rooted Recovery Image
https://www.androidfilehost.com/?fid=1395089523397925213
for install this m9 twrp
fastboot flash recovery_ramdisk twrpm9.img ok
for enter twrp after ?
only turn On and press volume+ ???
with twrp no possible root correct ?
the original recovery is recovery_ramdis.img extract update.app ??
aureliomilitao said:
for install this m9 twrp
fastboot flash recovery_ramdisk twrpm9.img ok
for enter twrp after ?
only turn On and press volume+ ???
with twrp no possible root correct ?
the original recovery is recovery_ramdis.img extract update.app ??
Click to expand...
Click to collapse
Yes you're correct but you can technically have both root and twrp. If you fastboot flash just twrp then volume up + power will boot you into twrp. If you want root and twrp then first fastboot flash twrp then boot into twrp then go to install then choose Image then browse to the twrp image then hit ok then choose erecovery_ramdisk. This will install twrp on the erecovery ramdisk partition. Then hit install then Image then browse to the rooted recovery_ramdisk then hit ok and choose to install it to recovery_ramdisk. This is the only way to have root and twrp right now.
After you do this, volume up will boot with root and volume up with the USB cable plugged in will boot into twrp.
huuuumm
for twrp + root
need install twrp in recovery_ramdisk partition and magisk in erecovery partition?
aureliomilitao said:
huuuumm
for twrp + root
need install twrp in recovery_ramdisk partition and magisk in erecovery partition?
Click to expand...
Click to collapse
You can do it either way. It's easier to install root in the recovery_ramdisk so if you restart your phone you can press volume up before it boots and you'll be rooted. To get a rooted boot.img you have to have your original boot.img on your internal storage and install Magisk Manager and choose "Patch boot image" to have Magisk Manager create a Magisk patched boot image, then you can flash that in twrp to either recovery_ramdisk or erecovery_ramdisk.
ajsmsg78 said:
You can do it either way. It's easier to install root in the recovery_ramdisk so if you restart your phone you can press volume up before it boots and you'll be rooted. To get a rooted boot.img you have to have your original boot.img on your internal storage and install Magisk Manager and choose "Patch boot image" to have Magisk Manager create a Magisk patched boot image, then you can flash that in twrp to either recovery_ramdisk or erecovery_ramdisk.
Click to expand...
Click to collapse
ok but
for enter twrp is boot and volume +
for enter root need boot and volume + ( no enter recovery) boot system root direct
so
how enter twrp and root together ?
aureliomilitao said:
ok but
for enter twrp is boot and volume +
for enter root need boot and volume + ( no enter recovery) boot system root direct
so
how enter twrp and root together ?
Click to expand...
Click to collapse
You don't have to have root loaded when you're in twrp. You can do everything in twrp that you can do with root.
On MHA-l29 with Magisk works like a charm! Nice work!
Does it support decryption?
rufik said:
Does it support decryption?
Click to expand...
Click to collapse
I've always been decrypted so I haven't tested that but I don't think TWRP supports decryption on Pie yet. If you do a data format and modify the vendor/fstab and remove the forceencrypt then you'll be decrypted and stay decrypted until you flash back the stock rom in erecovery.
Do work this boot.img also on L29C432B158 ?
Gesendet von meinem MHA-L29 mit Tapatalk
Midnightkey said:
Do work this boot.img also on L29C432B158 ?
Gesendet von meinem MHA-L29 mit Tapatalk
Click to expand...
Click to collapse
It should work fine. Try for yourself.
I can't decrypt my device,what can I do?
How can i handel the root permissions? in magisk manager i dont have the SU menu
Gesendet von meinem MHA-L29 mit Tapatalk
---------- Post added at 06:48 AM ---------- Previous post was at 06:38 AM ----------
[email protected] said:
I can't decrypt my device,what can I do?
Click to expand...
Click to collapse
I think u must do an factory reset in twrp, so save everything in the internal storage
Gesendet von meinem MHA-L29 mit Tapatalk
put in external still can see in twrp
To remove encryption you need to edit vendor/etc/fstab.hi3660. Copy it to your pc or open it any text editing app and remove the forceencrypt line. Then put it back in vendor/etc. Then boot into twrp and format data by going to wipe, format data and typing in YES. This will remove encryption and because you just modified the fstab file you'll stay decrypted. Twrp will now also see your internal storage correctly as well.
Hi all, here is a with Magisk v19 patched recovery_ramdisk.img
- which is not depended to a specific EMUI 9 firmware or cust - so it should work on all current and future EMUI 9 Firmwares and models of MHA (L29, L09, AL00, TL00): https://www.androidfilehost.com/?fid=1395089523397933251
If you like to use it:
0) Delete Magisk Manager before flashing the patched recovery_ramdisk.img
1) Flash patched recovery_ramdisk and boot with disconected USB and Vol+ and Powerbutton to system
2) Install then newest Magisk Manager from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3) Enable permission for storage in Settings/Apps/Apps/ Magisk Manager
4) Switch automatic battery management in Settings/Battery/App launch/ Magisk Manager to manual - and make sure, all three options are enabled: Auto-Launch, Secondary launch and Run in background
5) Open now Magisk Manager first time and accept the "additional setup" - Magisk will download and flash a additional zip for the "workspace environment"
Many thanks to @ajsmsg78 for this EMUI 9 TWRP for Mate 9
I made a Thread on Android Hilfe de for German speaking users with credits for this new TWRP: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-mate-9.3022/root-fuer-mate-9-mha-l29-und-mha-l09-emui-9_android-pie.908543.html
Thank you very much for your VERY detailed and comprehensive tutorial (using google translate )
With HWOTA9 i upgraded my MHA-L29C432 from oreo to pie 9.0.1.158, and with your guide i succeed to root (without TWRP) :good: :victory:
Does back up and restore in TWRP working now? right now i cant see some easy solution if i bricked/bootlooped my phone.
thanks.
weyrulez said:
Does back up and restore in TWRP working now? right now i cant see some easy solution if i bricked/bootlooped my phone.
thanks.
Click to expand...
Click to collapse
Backup/Restore is working. If you use original Huawei Firmware, you cannot backup/restore data (but everything else) except you would format data (to remove encryption as mentioned - but if you are new to this things, I would not recommend since you can use Huawei Backup or Titanium Backup for Backup/Restore data)
---------- Post added at 04:32 AM ---------- Previous post was at 04:30 AM ----------
chaozu said:
Thank you very much for your VERY detailed and comprehensive tutorial (using google translate )
With HWOTA9 i upgraded my MHA-L29C432 from oreo to pie 9.0.1.158, and with your guide i succeed to root (without TWRP) :good: :victory:
Click to expand...
Click to collapse
You are welcome If you like to have EMUI 9 /Mate 9 Callrecorder, you can install this Magisk Module: https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-huawei-mate-9.3022/pie-huawei-call-recorder-fuer-mate-9-emui-9.909715.html
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
Recommended TWRP from TWRP 3.3.1-xx Unified Unofficial by mauronofrio
**Official TWRP may not allow you to boot twrp.img**
OOSNativeCallRecording Module seems to be one culprit. Make sure to Uninstall before updating.
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
mac796 said:
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
Click to expand...
Click to collapse
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
diaztradeinc said:
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
Click to expand...
Click to collapse
I will update it shortly, thank you for the feedback.
Bradl79 said:
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
TWRP from here
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
Click to expand...
Click to collapse
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
matze19999 said:
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
Click to expand...
Click to collapse
It's actually pretty simple, u just have to provide more instructions for people who haven't used twrp. There is no need to flash anything, ik that the uninmod does not work and I thought I tired mm and could not get it working either.
I use MM for TWRP since years and it always worked perfectly.
matze19999 said:
I use MM for TWRP since years and it always worked perfectly.
Click to expand...
Click to collapse
Have u used it with ur 7Pro yet? I tried it yesterday and would not flash along with uninmod would not mount magisk, I think it's issues with dual partition bc it did the same with my OP6
Bradl79 said:
Have u used it with ur 7Pro yet?
Click to expand...
Click to collapse
yeah. Whats not working for you?
matze19999 said:
yeah. Whats not working for you?
Click to expand...
Click to collapse
Got error when flashing, would u mind sharing the file?
Bradl79 said:
Got error when flashing, would u mind sharing the file?
Click to expand...
Click to collapse
I got the one to install from the download section but I've never used it I'm not sure how it works
He's right uninmod and stuff like that doesn't work at all now. It's unable to mount magisk.img it seems to be an issue with our twrp.
As for the statement about the issue being dual partitions that's wrong it's has nothing to do with that. I know he mentioned that uninmod and others did not work on op6 as well.. But it did cause I used uninmod on my 6 and 6T. This is an issue with this device only and possibly the twrp we have currently.
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
equlizer said:
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
Click to expand...
Click to collapse
Are u using OOSNativeCallRecorder module?
Yes i was using it. Just re-installed it.
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
spart0n said:
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
Click to expand...
Click to collapse
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
mlock420 said:
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
Click to expand...
Click to collapse
Well what I'm getting at is that I deleted all 4 of my magisk mods and fixed the bootloop and then reinstalled all 4 of them and rebooted and everything is fine now. I was asking about should we disable all mods, reboot, update, install magisk, reboot, check root with magisk then reinstall all mods and reboot again?
equlizer said:
Yes i was using it. Just re-installed it.
Click to expand...
Click to collapse
You prob only need to Uninstall that next time b/c that is one that is causing issues. I do not use and I have multiple Modules that survive update not needing to uninstall all modules.
Thanks. I had problem with pernament bootloop after magisk instalation.
Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...
I might be doing something wrong but it's not working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Poslano z mojega MI 9 z uporabo Tapatalk
mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk
Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123
Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Magisk v20.4 ERROR 123 ((( for Recovery
Latest Magisk Canary, working like a charm, thanks
Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.
Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work
Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.
(Problems I had when attempting a "dry" flash and patch:)
Just got the phone today (November 18) then attempted to flash the boot.img after patching it with magisk manager (after magisk patches the boot.img it renames it to "magisk_patched.img"). Got the usb debugging authorized after updating my adb drivers. If you want to make sure your phone is authorized you may need to run commands: adb kill-server and adb devices to check and stop/restart adb.
Anyone able to get it flashed? Getting error:
Code:
FAILED (remote: Failed to write to partition Not Found)
after running
Code:
fastboot flash boot magisk_patched.img
from fastboot, bootloader is unlocked. Running version
Code:
bramble-rd1a.200810.022.a4 (October)
I'd recommend patching up to the November update: Settings, System, System Update to the newest November update (11.0.0 (RD1A.201105.003.C1, Nov 2020).
EDIT: I'd recommend installing 15 second ADB https://forum.xda-developers.com/showthread.php?t=2588979, then overwriting it with the newest adb tools from google. 15 second ADB will add the ADB folder to your system's PATH (ENVIRONMENT VARIABLES) allowing you to run adb commands from any folder (not just the folder adb resides in).
Ok, updating to usb_driver_r13-windows.zip and platform-tools_r30.0.5-windows.zip and updating the build to the Nov RD1A.201105.003.C1 will report back lol
EDIT 2: So yeah, update your drivers and platform tools, successfully patched it:
Code:
fastboot flash boot magisk_patched.img
OUTPUT:
Code:
Sending 'boot_b' (98304 KB) OKAY [ 2.310s]
Writing 'boot_b' OKAY [ 0.480s]
Finished. Total time: 3.122s
How to flash and patch:
https://www.xda-developers.com/google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet/
Prerequisites:
Download the applicable factory image https://developers.google.com/android/images The Pixel 4A 5G is codenamed "Bramble" (Pull down your shade or look in Settings, "About phone" for Build number) and extract the boot.img from factory image, then transfer it to phone and patch it with magisk manager:
Open Magisk manager -> select ‘Install’ -> ‘Select and Patch File’ -> select your boot.img file
The patched boot image should be found inside your Download folder
After magisk patches it, mount your phone's storage, copy to your computer and flash it from fastboot. Hold down the Power and Volume Down buttons to enter fastboot.
Run command
Code:
fastboot flash boot magisk_patched.img
Platform Tools (includes ADB)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Usb Drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip?hl=ru
Magisk
Direct Link https://github.com/topjohnwu/Magisk/releases/download/v21.1/Magisk-v21.1.zip
Direct Link https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.3/MagiskManager-v8.0.3.apk
Magisk Releases page (in case of an update to magisk or magisk manager) https://github.com/topjohnwu/Magisk/releases/
VIPER4Android (great Digital Signal Processor)
I have been struggling with getting Viper4Android installed.
Stop-gap here:
I flashed this one, but it's distorting my external speakers and is buggy, but it does process...so BE CAREFUL. This will get you there until a more stable version is out. And the video was just taken down. All you have to do is flash it with Magisk here's a link:
https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing
AdAway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
AdAway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
AdAway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
Good luck all!
Good to see someone working on this. My phone won't be here until tomorrow.
The last time I had trouble flashing, I wasn't running the canary build of Magisk.
Thanks for info and reply on other thread...long time I use this stuff haha
I'm seeing install fail from magisk when I try to patch image .I'm on latest November build
View attachment 5138555
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
andrew207 said:
After successfully fastboot unlocking, when I try to patch my boot.img I get the following error from Magisk:
Code:
-Device platform: arm64-v8a
- Copying image to cache
- Checking ramdisk status
- Stock boot image detected
- Patching ramdisk
! Installation failed
- Repacking boot image
! Unable to repack boot image!
I first tried using the Australian factory image, labelled "11.0.0 (RD1A.201105.003.A1, Nov 2020, AU carriers)" and got the above error.
Then I tried with the Australian + Japan factory image, labelled "11.0.0 (RD1A.200810.020, Oct 2020, AU & JP carriers)" and got the same error.
What fixed it was switching to the BETA update channel in Magisk manager.
Once I changed to the BETA channel I saw in the changelog that they added support for a new boot.img format used by Pixel 5 and Pixel 4a 5G.
Anyone who ends up here from Google, swap to the beta update channel in Magisk manager .
Click to expand...
Click to collapse
Thanks for info ..I changed to beta but still having issues patching boot IMG..is this correct Magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Android 10 and TWRP
Simma said:
There's no custom recovery. You need to fastboot flash a patched boot.img as described in this guide: https://www.xda-developers.com/googl...ass-safetynet/ using the links from the OP.
Just make sure you're using the latest platform tools, download the matching factory image and change magisk manager to "beta mode" before patching the boot.img.
Click to expand...
Click to collapse
WhiteAsIce said:
Do you have a custom recovery installed? I'm trying to figure out how to install Magisk, but I can't find a custom recovery, neither TWRP nor ClockworkMod.
Click to expand...
Click to collapse
More information on Android 10 and TWRP, though there are some devices slowly getting support for TWRP. Haven't heard clockworkmod in a long time.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
lmt1979 said:
[...]
Adaway (system-wide ad blocking)
tried version 5.10 with no luck, let me know if it works for you.
Adaway 4.34 working for me on Android 11.0.0 (RD1A.201105.003.C1, Nov 2020)
Here: https://f-droid.org/repo/org.adaway_40304.apk
Adaway 4.36 (haven't tested)
https://f-droid.org/repo/org.adaway_40306.apk
Make sure to enable "Systemless Hosts" in Magisk Manager before attempting to enable ad-blocking. It's under Settings (the cog/gear in the top right) in the Magisk section.
[...]
Click to expand...
Click to collapse
Got v5.1.0 (from F-Droid) working properly with Magisk running with systemless hostfile. Try installing BusyBox (i have v1.32.0 installed) to '/system/bin', which will be used by Adaway (instead of running native commands on root level, which apparently cause the issue).
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
The linked version worked for me after trying the magical downloaded version. I had the audio modification library and audio compatibility modules installed. I don't remember the exact sequence bit all I have now is the posted module l.
It does have some odd issues with file storage. I can save a new preset but putting my old one in the viper folder in internal storage doesn't work. I also can't rename or delete presets. I ended up having to go to /root/storage/self/primary which seems to be internal storage by another path. Pasting my presets in that viper folder worked. No idea how systemless works so can't even guess what's going on.
mmarcz said:
I can't seem to flash version of Viper in Magisk, it won't let me. I've also tried every combination of the latest viper versions, and their settings, and nothing will run. Perhaps it will on the next version of Magisk. I had posted in the Magisk forum, and none of the suggestions helped.
If anyone has any luck, let us know!
Click to expand...
Click to collapse
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
lmt1979 said:
Just flash the https://drive.google.com/file/d/17-NTL0miBYzk4o4v26MstAL9lOPXF3GN/view?usp=sharing with Magisk. Choose "Modules" the right option on the bottom https://drive.google.com/file/d/1BWLVPtypCjCiqUSEHiRc8sCuMtjqKdY5/view?usp=sharing
Click to expand...
Click to collapse
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
mmarcz said:
Thank you!!!!! Works as advertised!!!!
This was 75% of the reason I bought a pixel!!!
I'm so happy this morning, you have no idea.
It was even processing Amazon music, which didn't work before, so far so good. I only had a chance to listen in the car for 5mins this morning.
Click to expand...
Click to collapse
If it stops processing, long press on the icon on the desktop, select App info, Force Stop and reopen and it'll usually start up again. I had to do this much more often on my Pixel 3 than I have on the 4A 5G.
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
lmt1979 said:
If you're sure you're rooted, some people have noted they needed to use/install Audio Modification Library and possibly Busybox. I'd attempt to clear the cache on Magisk and Viper4Android, as well.
I am on the November build and did not need Audio Modification Library, audio compatibility module (Magisk) or Busybox. I'm using Magisk 21.1 (21180) and Magisk Manager 8.0.3 (314)(14). There's a "puzzle piece" on the far right of the new Magisk Manager menu that has "Install from Storage", this is where I pointed to the Viper.zip and flashed it.
Click to expand...
Click to collapse
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
VerneVerne said:
Tried all the above. No luck though. I remember it being very finicky on my pixel 3. I'll try again when I'm not actually at work. Thanks for the help though
Click to expand...
Click to collapse
I've been glhaving issues too after it worked for awhile. Couldn't deal with no presets thing so tried different Magisks, etc with no luck and now it won't process. I'll update if I find something.
EDIT: the module at https://zackptg5.com/android.php#viper works if run in legacy mode.
EDIT AGAIN: can't save presets for some reason with above module but the ViperFX XDA Labs release before the most current one works in legacy mode https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
VerneVerne said:
I've followed the steps posted above. Flashed the Drive file in magisk but I'm still getting abnormal status, audio format unsupported. Tips?
Click to expand...
Click to collapse
You need to go into the settings for the app force stop it and then reopen it.
lmt1979 said:
You need to go into the settings for the app force stop it and then reopen it.
Click to expand...
Click to collapse
I've already tried. Started from scratch. Still unsupported status.
Edit: after reading somewhere on here that if you use legacy mode it will process. Followed all steps, set it to legacy and now it works. Thank you everyone
[NE2213] OxygenOS 13 C.20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full OTA Link:
[NE2213] OxygenOS 13 C.20
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
S /\ E E D said:
Full OTA Link:
[NE2213] OxygenOS 13 C.20
Click to expand...
Click to collapse
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks
ugendersingh said:
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks
Click to expand...
Click to collapse
I don't think, BTW have a backup from your data before install
S /\ E E D said:
I don't think, BTW have a backup from your data before install
Click to expand...
Click to collapse
Hi Mate I have tried backup using oneplus clone phone app but it doesn't backup photos and videos. Any other way of backing up data?
S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Did someone try alread this method here from android 12 updates?
Magisk OTA Update reboot directly
Hey Guys, I don't found any similar thread about this topic, so I will create a new. I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image ->...
forum.xda-developers.com
NE2215 here; no C.20 yet for us.
2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?
beterman said:
2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?
Click to expand...
Click to collapse
If you ask from me, I answer it with yes, you should do it
However someone else maybe say you skip that
You can also ask from @Prant about this
Prant said:
NE2215 here; no C.20 yet for us.
Click to expand...
Click to collapse
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL
foamerman said:
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL
Click to expand...
Click to collapse
Hahaha, "Global" version.
I'm having trouble extracting the boot.img from payload.bin with payload_dumper in Python. See the error below. Anyone any tips or care to upload the boot.img?
Traceback (most recent call last):
File "payload_dumper.py", line 92, in <module>
dump_part(part)
File "payload_dumper.py", line 55, in dump_part
data = data_for_op(op)
File "payload_dumper.py", line 41, in data_for_op
data = dec.decompress(data)
_lzma.LZMAError: Input format not supported by decoder
NEVER MIND:
used Fastboot enhance instead and that worked well
Hi i have a question somebody can check Viper4android working on oxygen os 13? And how to install
S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Local update option disabled in update menu?
Hello, anyone can help me please ?
after the update, I patch the boot.img with magisk i have magisk_patched.img file and I flash it with the commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
after that the phone reboots in bootloader loop mode forced to reflash the original boot.img
what mistake am I making?
EDIT : sorry i find a tutorial to root :
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
it's ok with this ...
Hi guys !
Is NFC payment with google wallet working on this build ?
And battery life semme better/worst/similar to android 12 ?
I'm still with android 12 and wonder if it is worth to go for A13 now
Thanks !
Yes / better
Prant said:
Hahaha, "Global" version.
Click to expand...
Click to collapse
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.
biglo said:
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.
View attachment 5725283
Click to expand...
Click to collapse
Exactly