Related
I have searched a bit and found nothing so far. Is it even possible to gain root on this phone? I have the 32gb with 3gb ram Android 7.
Anyone?
Any help at all? Anyone?
Man I can't find anything either! I guess our only option is to wait
I'm a 3rd person looking for info on rooting this Blu R2 Plus. I have found someone using Majisk but the steps are not detailed enough.
Braunish said:
I'm a 3rd person looking for info on rooting this Blu R2 Plus. I have found someone using Majisk but the steps are not detailed enough.
Click to expand...
Click to collapse
Hmm sounds liable but I'm not too keen to risking it
Don't risk it until we get further info
totheark408 said:
Hmm sounds liable but I'm not too keen to risking it
Click to expand...
Click to collapse
I've lost one to boot loop because I patched version provided in this thread, and then flashed that to v4.01 rom is where I think problem arose.
Braunish said:
I've lost one to boot loop because I patched version provided in this thread, and then flashed that to v4.01 rom is where I think problem arose.
Click to expand...
Click to collapse
Was the rom specifically meant for the r2 plus?
Updated ROM by Blu for R2 Plus on 2/11/18
totheark408 said:
Hmm sounds liable but I'm not too keen to risking it
Click to expand...
Click to collapse
I'm not sure you found this out, but there have been 2 versions of Blu Rom issued in February 2018 alone. I did update to the 4.01 version (2.11.18) found at https://www.needrom.com/download/blu-r2-plus/#comment-389270 using SP Flash, latest version, and it worked fine.
---------- Post added at 05:59 PM ---------- Previous post was at 05:52 PM ----------
totheark408 said:
Was the rom specifically meant for the r2 plus?
Click to expand...
Click to collapse
The file is no longer available, but yes it was presented as Blu R2 Plus, but I think it was factory version 3.01 they were dealing with according to the dates on messages. Verison 4.0 and then Version 4.01 came out in February. There is another thread where they talk about using majisk manager and yes the instructions were very vague. My next step it to try to test the patched_boot.img file without flashing it or destroying my phone, or just wait. Been using KingoRoot and KingRoot to no avail.
Braunish said:
I'm not sure you found this out, but there have been 2 versions of Blu Rom issued in February 2018 alone. I did update to the 4.01 version (2.11.18) found at https://www.needrom.com/download/blu-r2-plus/#comment-389270 using SP Flash, latest version, and it worked fine.
Click to expand...
Click to collapse
I was not aware! Ill definitely look into this. Have you made any progress on rooting?
BLU R2+ root using Magisk v16.0 & ADB/Fastboot
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.
Porting efforts and magisk/xposed/mod testing
Recovery porting experiences:
I ported a few stable builds of TWRP from two different MT6753 based devices. I used the R2+ v4.01 ROM as the stock rom and overall had limited success.
Two out of three were bootable, and those two worked correctly when booted via "fastboot boot recovery.img"; however, when flashing to the recovery partition the touchscreen does not work on either of the ones I made. Research on the issue indicates this a kernel restriction. Did not test backup/restore functions. Instead I ported a LineageOS 14.1 rom to test flashing with the ported recovery I made. Wiped and installed ROM + GApps. TWRP reported successful, however the ROM got stuck on the BLU logo white screen. With the custom roms flashed recovery/fastboot both still loaded like normal. Battery charging was bugged though which I've seen in other CM variants on many devices. It seems the flashing worked correctly from my observations. After all this I flashed back to stock using SP Flashtool.
Testing Xposed Framework/Modules and other observations:
I had continued issues with Xposed when installed via a Magisk module on both Magisk v16 and v16.3. Basically both the official magisk module and the xposed systemless module only work after a soft reboot. I did not like this and finally tried a standard Xposed Framework (v89) install using the official Xposed Installer APK (v3.1.5). This so far works without any problem and has never shown the "installed but not active" warning. As for Magisk, root access works great and the xposed not active issue aside, it's a perfect root solution. I should add I have not done any magisk/root hiding and Xposed Framework installed in any of these variations via Magisk will not be hidden from apps/services that checks for it.
I've tested Amplify, Greenify, GravityBox[N], and XLED Xposed modules and have not encounted any issues in those.
GravityBox's fingerprint launcher option works and can be set to sleep giving a combined wake/sleep using the Fingerprint scanner.
XLED control works. LED in the R2+ only seems be very basic and only have two colors (green and red). Setting to any blue shade either results in red/green or nothing. Testing in Lightflow gave similar results. At least having an override option for the apps that would default to solid blue and thus have no LED flash at all is nice though. Overall Xposed when installed via the standard/official method works great.
I've been using Substratum in Legacy mode and it also works as expected given it's limited functionality without OMS. Themes do work but there isn't a whole lot of selection for legacy themes.
Overall this phone seems very root friendly and has great potential. I do hope someone out there finds this info useful and would love to see some actual development beyond my meandering experiments and attempts.
Great work nucleusprime! Could you share a custom recovery you used to install xposed? Thanks
_renzomc said:
Great work nucleusprime! Could you share a custom recovery you used to install xposed? Thanks
Click to expand...
Click to collapse
I will gladly share anything that's helpful or interesting. If your goal is to install Xposed I was able to do that using the xposed installer app.
You can get the app from the Official Xposed thread here
Download and install the apk. Initially it will say Xposed is not installed.
Tap the INSTALL/UPDATE Version 89 button.
{
"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"
}
Select first option "Install" and when prompted grant Xposed Installer root permission.
Wait for the install to finish and and then reboot the device.
After reboot it should show Xposed is active.
Edit: I made a few screenshots but I'm unable to post them here yet.
I can see your screenshots from gmail app
Worked great! Thank you. I'm gonna try GravityBox now
_renzomc said:
I can see your screenshots from gmail app
Worked great! Thank you. I'm gonna try GravityBox now
Click to expand...
Click to collapse
Thanks for the update! Glad to hear it's working for you.
I am completely new to rooting and am completely unfamiliar with adb, etc. I understand the meaning of obtaining root, unlocking the bootloader and installing a custom room though. I really just want to gain root access and I don't have a newer computer I can use to assist me in this. I do have a very old Windows XP laptop. Isn't there a way I can gain root without using adb or installing another rom? The one on my.phone is newer than the one listed here as well, 7.0.04.03_GENERIC 08-06-2018. Is it not possible to gain root without the use of a PC? This phone is my daily driver so I don't want to take too big of a risk and just giving me access to light customization and being able to ditch preinstalled apps taking up space and using ram is good enough for me.
I require rom blu r2 plus
nucleusprime said:
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.
Click to expand...
Click to collapse
Friend can have the link of the rom of the blu r2 plus, and why I need a room I can not download them. :good:
nucleusprime said:
I successfully rooted my new BLU R2 Plus using Magisk v16.0 and ADB/Fastboot. Sharing the steps I used to help any R2+ owners out there.
I did these steps on two of the stock ROMs I found at NeedROM that were linked by the BLU Development Team G+ Community.
The ROMs I used are named:
BLU_R0190WW_V7.0.03.01_GENERIC-18-10-2017
BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018
The 1st ROM matched the build ver/date preloaded on my new BLU R2+ (v3.01).
The 2nd ROM is the latest ROM available on NeedROM (v4.01) and I believed it to be the latest update.
Tools I used:
Minimal ADB/Fastboot v1.4.3
Magisk Manager v5.6.4
Magisk v16.0(1600)
Device details for preloaded ROM for the curious (Settings >> About Phone):
Model number
R2 Plus
Android version
7.0
Android security patch level
October 5, 2017
Baseband version
MOLY.LR9.W1444.MD.LWTG.MP.V110.5.P38, 2017/10/17 20:51
Kernel version
3.18.35
[email protected] #2
Wed Oct 18 15:22:31 CST 2017
Build number
NRD90M
Custom build version
BLU_R0190WW_V7.0.03.01_GENERIC 18-10-2017 14:31
Disclaimer: This is posted for educational purposes only. If you perform these steps you do so at your own risk.
Step-by-step Guide (aka what I did):
1. Unlocked bootloader using ADB/Fastboot using standard adb/fastboot method on Win10 laptop.
Enable Developer Opts >> Enable OEM Unlocking >> "fastboot oem unlock" >> "fastboot reboot" >> wait for FDR.
2. On laptop downloaded ROM from NeedROM and unzipped it to a new folder.
3. Copied boot-sign.img from unzipped ROM folder on laptop and transferred to R2+ using USB File Transfer.
4. Side-loaded Magisk Manager v5.6.4 and opened it.
5. When opened Magisk Manager prompts to Install Magisk. Prompt says "Do you want to install Magisk-v16.0(1600).zip now?".
If you cancel the first prompt tap the Install button at the bottom of Magisk Manager screen.
6. Select INSTALL at the prompt and then Magisk prompts to Select Method. Select "Patch Boot Image File".
7. Select boot-sign.img that was transferred to device. Give permissions to Magisk as needed.
8. Magisk will create a patched_boot.img and save it to the device. I copied this back to the laptop.
I had to rename patched_boot.img on the R2+ in File Manager for it to show in Windows Explorer on the laptop and be copied.
9. Rebooted into fastboot and tested patched boot image in ADB using "fastboot boot patched_boot.img".
After booting the patched_boot.img MagiskManager app showed v16.0 was installed.
Installing and running Root Checker verified the device was rooted.
This part could be skipped but I wanted to play it safe.
10. Rebooting the device shows Magisk is not installed and Root Checker says the device is not rooted.
11. Knowing the process worked. I then wanted to repeat it on the latest update I saw on NeedROM.
I installed the OTA Update on the device before realizing it showed v4.01 instead of v4.02.
It's worth noting the OTA installed with the bootloader unlocked.
The download was apparently done in the backgound and thus the install started immediately.
I have never found a way to dump the stock ROM on an MT6753 device I decided to test SP Flash Tool.
I flashed BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018 using SP Flash Tool v5.1804 on a Win10 laptop.
12. Flash to stock ROM v4.01 was successful. I had to perform bootloader unlock again and then I repeated steps 1-10 on v4.01.
13. I flashed the patched boot image using "fastboot flash boot patched_boot.img" then rebooted with "fastboot reboot".
14. Confirmed again using MagiskManager/Root Checker. Success.
WARNING: I do not recommend doing these steps using the ROMs I used unless you are running the same version as the downloaded file or are doing the steps on a boot.img you know is for your hardware and currently installed firmware.. Doing otherwise may not work and could damage the device. It's also possible any boot.img for your device would work, but I am not sure and only did this using the exact same boot image as the firmware installed on my device at the time. I would prefer people be cautious and only do this with a file they KNOW is for their device.
Final thought: I have a theory that the BLU R2+ has a doppleganger named the "Symphony P9+".
Update: I had trouble installing Xposed module in Magisk Manager. I installed the Busybox for Android NDK module. Busybox installed, but after reboot Xposed still failed.
I then (re)installed Magisk via Magisk Manager using the "Direct Install (Recommended)" Option. The install was successful and after reboot Xposed 89.2 (Systemless) installed successfully but was reported in Xposed Installer for Magisk as installed, but not active. A second reboot fixed that and Xposed was active. Installing GravityBox [N] module in Xposed had no issues and works nicely so far. Root works so I think I'll try my hand at porting TWRP next.
Click to expand...
Click to collapse
good morning, friend, test and method as you explain with the version BLU_R0190WW_V7.0.04.01_GENERIC-11-02-2018, to the flah the boot the team goes into boot loop and does not start. Because this happens, could you send me the patched boot of the flash version on my phone?
I was on 9.5.5 with TWRP and Magisk
I deleted the guest account and remove the island in "Island" to be able to create a full backup in TWRP recovery (Had error 255 before I removed the two other users)
Downloaded the 9.5.7 using oxygen updater
Uninstalled magisk ("Restore images")
Installed 9.5.7 using settings/local update
Went back into Magisk Manager and installed Magisk to inactive slot and rebooted - everything went great and I'm now on 9.5.7 with Magisk ??
Now I'd like to install TWRP recovery using the TWRP app but I'm unsure if I should select the zip file or img file?
evalu8t0r said:
I was on 9.5.5 with TWRP and Magisk
I deleted the guest account and remove the island in "Island" to be able to create a full backup in TWRP recovery (Had error 255 before I removed the two other users)
Downloaded the 9.5.7 using oxygen updater
Uninstalled magisk ("Restore images")
Installed 9.5.7 using settings/local update
Went back into Magisk Manager and installed Magisk to inactive slot and rebooted - everything went great and I'm now on 9.5.7 with Magisk
Now I'd like to install TWRP recovery using the TWRP app but I'm unsure if I should select the zip file or img file?
Click to expand...
Click to collapse
Id download the zip and flash it in magisk.
2nd vote for zip.
Know for sure that the zip will install on both slots. Don't know for sure whether img does.
Therefore, zip.
Not sure how to flash it from Magisk but I'll try the zip from the TWRP app later ?
Thanks for the response ?
...so... the "Flash" button in TWRP does absolutely nothing but download the file (?)
Going to Magisk/Modules and selecting the zip file does the magic ?
EDIT: No, I did not RTFM as I could not find the f**ing manual...
There was a note saying "you are now unrooted" so I went back to Magisk and pressed "Install (Direct)" before rebooting and everything worked as expected ? now on 9.5.7 with Magisk and TWRP ?
Zip. Img doesn't quite install right and disappears on boot.
JhinCuatro said:
Zip. Img doesn't quite install right and disappears on boot.
Click to expand...
Click to collapse
Flash Magisk right after flashing the zip (don't reboot), and see if TWRP "sticks".
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
joemossjr said:
First method was the right method. But don't flash the ab retention script. Flash the file in system update then go to magisk and flash to inactive slot. Reboot after that and when you boot back up flash the twrp installer in magisk and reflash root and reboot to recovery to verify its there.
Click to expand...
Click to collapse
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
i.Design said:
I'm assuming you mean flash TWRP installer via Magisk once rebooted? I just want to make certain before trying again.
Click to expand...
Click to collapse
Yes
joemossjr said:
Yes
Click to expand...
Click to collapse
This didn't work. I was able to at least see my storage now and installed OTA via TWRP > TWRP installer > Magisk to update Slot B now I'm having the same issue in both slots.
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
I have downloaded the 11 update via OxygenUpdater using VPN (Location is set to France)
Since i diden't get the update on my real location.
Rebooted to TWRP->Flashed 11 update->Flashed TWRP->Rebooted to TWRP>Flashed Magisk>Flashed Kernel>Rebooted to System.
Everything seems to be working.
Try this simple and straight forward method,
Download the full zip 9.5.11, not the update zip but full zip,
Transfer to phone storage,
wipe only dalvik cache and data, DO NOT WIPE SYSTEM OR VENDOR, OR INTERNAL STORAGE,
Flash the oos zip,
Flash twrp, Reboot recovery,
Flash oos zip file again followed by twrp,
Reboot recovery,
Flash magisk 19.3,
Now Reboot system,
Do not click on any slots in twrp let the system select the appropriate slot, system will take some time to boot also will Reboot itself, but will boot eventually,
hope this helps, cheers.
How this helps, worked for me, I don't have T-Mobile version
i.Design said:
Alright, I have tried just about everything and keep running into the same roadblock so I am going to post here and see if someone has an idea of what is going on and how to work around it. I will outline each method used below as detailed as I can. I'm currently on 9.5.9 and looking to upgrade to .11. I'm currently on Slot B.
First Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Installed locally via System Updates
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Second Method:
1.) Disabled all Magisk modules / themes etc
2.) Downloaded .11 OTA from OnePlus Updater
3.) Reboot to TWRP
4.) Flash ROM
5.) Flash TWRP installer
6.) Reboot recovery
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. I reboot to slot b and try again.
Third Method:
1.) Disabled all Magisk modules / themes etc
2.) Download / Install via system updates message to upgrade to .10
4.) Installed TWRP A/B Retention Script in Magisk
5.) Magisk OTA install to inactive slot
6.) Reboot
Result: Reboots to TWRP in the new slot but no pin number is requested and no files showing under Install, cannot reboot to system. Upon rebooting to slot b I at least got a notification that the update had failed and to enter repair mode to attempt again, however, I decided to not do this yet to avoid issues with breaking root / TWRP.
-----
As you can see... I am getting to the point of rebooting to recovery in the new slot but am unable to do anything in terms of flashing ROM > TWRP > Magisk to update both slots or do anything in the new slot. I'm almost assuming a clean ROM flash, flash TWRP / Magisk might fix any issues but I want to prod you all first for a solution before I go with the nuclear option.
Click to expand...
Click to collapse
OP7PRO, stock ROM, stock kernel
This has been ABSOLUTELY working for me and how i was used doing it back in the days..
*After switching off all modules in Magisk and do a system reboot to apply this..
(Do I have to mention it's probably best, when updating to disable any password/fingerprint protection when rebooting AFTER FLASHING OTA, TWRP and Magisk in recovery?)
*I didn't use local update setting.
*What's on in developer options?
-OEM Unlock allowed
-Advanced reboot
-USB Debugging
*Don't know if having these developer settings otherwise would interfere, I just try to write it down as specific as of how i did this.
*Also: I didn't even bother looking at A/B partitioning and where to install what, please correct me if i could be wrong, but using this method worked for me and also when installing TWRP zip in recovery, the log showed A/B sloth solution success when installing.
*Not using substratum themes etc., but I want to say it's probably best to go as clean as you can anyway, since you can always go back being beautiful afterwards I guess?
So try remember where you left off being a makeup loving customiser and momentary revert being as clean as possible.. at least for maybe 20 minutes okay?
How I did it:
-Download the OTA update zip on your phone (full update file zip just shy of 2 Gb) using oxygen updater app in Google playstore.
(Don't install the systemsoftware zip from the oxygen updater once downloaded), you're going to install the systemsoftware.zip in TWRP recovery as opposed to update via Magisk to install the new systemsoftware).
-Download TWRP (INSTALLER!!) have this ZIP on phone (Find it by reading some posts about TWRP Installer zip or use link below)
*I used: twrp-installer-3.3.1-4-guacamole.zip
https://dl.twrp.me/guacamole/ (for TWRP zip)
-Download Magisk zip
*I used: Magisk-v19.3.zip
(So far 3 zip files, have them somewhere pretty obvious on your phone)
-Boot into recovery (I did this by using this option in Magisk manager)
Then:
-Flash the update OTA ROM.zip (just shy of 2Gb)
*DON'T REBOOT*!!!!
-Go back in TWRP recovery menu, Flash TWRP Installer zip
-Still in TWRP recovery menu go back, Reboot to recovery
-Back in TWRP, flash Magisk zip
-Clear Dalvik cache (not sure if this is actually still needed)
-Reboot system normally, enable Magisk modules you want, reboot system...
Updated to 9.5.10 works
Updated to 9.5.11 works
Updated to 10.0.0 works
I can't find the full zip for 9511 anywhere
joemossjr said:
there has to be something else up with your device. I would try a clean flash with magisk or try the latest magisk canary build.
Click to expand...
Click to collapse
I ended up having to reformat to deal with the encryption issue. After reformatting I was able to boot to slot b and am at .11 now!
I'm really hoping this ordeal fixed whatever the problem was so that future OTA's aren't this much of a headache. I'll keep the tips in mind. I'm just glad to have a working device at .11 with root even if I have to re-install all of my apps etc.
virtyx said:
I can't find the full zip for 9511 anywhere
Click to expand...
Click to collapse
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
smariob said:
It's live on XDA frontpage.
---
I think best update method is get full zip, do local upgrade, flash Magisk after OTA on inactive slot, reboot, flash TWRP installer via magisk and reflash magisk (direct method). Reboot and zero issues.
Click to expand...
Click to collapse
just came up now
what i normally do is flash full zip
reboot
then reboot fastboot and boot twrp, then flash twrp then magisk.
i like the OS boot first time without twrp or magisk, just habit i guess
everything working fine, nightscape also
EDIT:
i think SWAP has been turned off in 9.5.11
it no longer displays in ElementalX app (with stock kernel)
What did I do wrong?
Someone help me shed some light. I'm not sure what I did wrong while updating using magisk.
So this is the steps I did.
1. Installed the OTA update
2. In magisk went to install to inactive slot (after OTA)
3. Then it went through the motions and restarted.
At the screen where you put the password in it shut down and then went to the stock recovery. Tried again, same thing. So after some panicking I did this.
Reflashed twrp via computer
Flashed the uninstall of magisk
Flashed twrp zip
Restarted it and everything is fine now. I just had to re-flash the modules which was quite annoying.
So what did I do wrong? Have I buggered up anything to do with the inactive slots or partitions?
I don't know why people have such difficulty?
1. Get the full zip via Oxygen Updater or some other method.
2. Do a local install vis the settings. DO NOT REBOOT.
3. Install Magisk via the "Install after OTA" from Magisk Manager.
4. Reboot
5. You will now have the slot rooted that you updated.
6. Run the local install again. This will install to the other slot. It will fail the first attempt. Do it again.
7. Install Magisk via the OTA option and reboot.
You have now updated both slots and rooted them.
If you would like TWRP or custom kernels, follow those instructions.
If you install TWRP, you MUST install Magisk in the same slot or you will get a boot loop for that slot.
That is the reason why I keep both slots at the same OS level and rooted with TWRP installed.
What country guys you are from that you are getting update? Im in USA and still got nothing.
netgar said:
What country guys you are from that you are getting update? Im in USA and still got nothing.
Click to expand...
Click to collapse
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Krsmqn said:
Using oxygen updater, try disabling all.mods before checking for update. Or in oxygen updater settings, select advanced mode, and see if update is available.
Click to expand...
Click to collapse
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
netgar said:
By mods you mean magisk modules?
Update
Advanced option did the job. Updated with magisk and few magisk modules + few substratum themes.
Thx
Click to expand...
Click to collapse
Yeah, meant magisk modules, sorry. But looks like you got it anyway. ?
All update methods to 11 failed.
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Bump
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
You are on stable channel surely the notified upgrade is to version 10.0.11, so you can update and keep root and twrp working.
To do this follow the steps described by @strongst in the op7 forum and you will have no problems.
Here the steps to follow:
Optional but highly recommended, backup everything in case of issues.
Download the full rom zip file and the twrp zip installer file and place it into the phone storage memory.
Go to Magisk Manager and uninstall all modules.
Reboot phone.
Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, select the .zip file of the new firmware and wait for the installation to finish. Attention don't reboot yet!
Install TWRP within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+" select .zip file of the twrp recovery installer. Attention don't reboot yet!
Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot".
Finally reboot.
Reinstall your Magisk Modules.
Done! Your device is now updated and you keep TWRP and root.
Very important: At the moment this procedure is to be considered reliable only if used with firmware based on Android 10.
scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
As of right now there is no TWRP working some have had luck but unfortunately most havent. i have uploaded a patched boot.img that will let you root
how to install android 11 on gm 1925, if my phone does not see files via local update?????
As in the subject, I have a problem with the magisk on the Mi 10 Lite 5G.
I downloaded room miui_MONETGlobal_V13.0.2.0.SJIMIXM_f2b661bdf6_12.0
Due to the fact that on android 12 there is no TWRP working yet, I uploaded magisk 24.3, patched the boot.img file and uploaded via FASTBOOT, everything is loaded, I have root access but the application does not work as it should. When he wants to hide an application under the name of settings installed he gets the message: "Restore application magisk, this application cannot run as root has been lost. Please restore it to its original state." and here I have install at the bottom. after installing the application from scratch, I get another message "Your device requires additional configuration for the magisk to work properly" I click ok and I have the message "configuration failed."
I tried multiple times to patch boot.img and upload it via Fastboot but I have the same problem every time.
Anyone know the solution to this problem ???
I'm still on MIUI 12/A10, I haven't tried this out.
But - since the flash-script is just a fastboot script, you can do it a bit backwards.
Install any pre-A12-rom, after that, boot in to TWRP. Flash boot.img from the A12-rom. Then flash magisk.
Now you edit the fastboot.bat or fastboot.sh-script. Remove the line with fastboot flash boot images\boot.img. Boot in to the bootloader. Then run the script.
You should now have a fully working A12-rom with magisk.