Related
This how you unlock bootloader.
Read all before doing anything!
Yes.
Backup all your ect unlocking bootloader will erase all your data.
1 first you will need to USB drivers including adb usb driver.
After that download minimal adb and fastboot.
Make sure you enable debuging and oem unlock in developer's settings.
Download inteladroiddrv.setup.
After you set this up test run "adb devices"
2. Download the twrp that I link in thread.
3.extract recovery .img to minimal directory.
4.open minimal app and run adb reboot bootloader.
5. Run fastboot oem unlock.
6.follow instructions and unlock bootloader.
7.next wait until process is over then it will reboot.
8. After reboot go settings about device go to build tap a bunch of times to reable
Developer's setting enable debugging.
9. Next go to minimal app run adb reboot bootloader your know in fastboot run fastboot boot recovery.img.
10 this will boot recovery then flash root.zip.
11. After that I recommend you do backup and yes it is big after done you can move it to your PC.
Do flash recovery permit touch doesn't work.
https://www.mediafire.com/file/d3h8cnouw8fih6s/android_cdc_driver.zip
Sent from my Studio XL 2 using xda premium
https://www.mediafire.com/file/s4aidnkyacpidjq/latest_usb_driver_windows.zip
https://www.mediafire.com/file/q7nt7xko0f653o4/IntelAndroidDrvSetup1.10.0.zip
skritch said:
I am very interested in rooting the Blu Studio XL2. Can you let me know how you accomplished it?
Click to expand...
Click to collapse
You need to get adb drivers.
Go to settings about device then tap many times on build then go to development settings enable debugging.
You need to unlock bootloader.
Make sure you backup your apps etc.
Unlocking bootloader will wipe user data.
After all USB stuff is in installed.
Adb reboot bootloader this will take you to fastboot next put fastboot oem unlock.
On your phone it will give a choice to unlock bootloader volume up unlocks volume down will keep it locked.
Just pressure you this is not hard to do.
I have two work able recoveries at the time they can bootloop you if you install I was told so here is my solution to this.
Adb reboot bootloader then do this fastboot boot recovery img.
Works like a charm after recovery boots up do a backup.
I will try to drop some links to recoveries for you.
You will likely need to install USB drivers manually local disc c/ programs go into like Intel Android Device USB driver.
This should take care of adb and fastboot problems.
https://www.mediafire.com/file/zy47tm55qr76fc4/SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://www.mediafire.com/file/0ckf...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/jgpx...XL+2+-+S0270UU_V08+-+MT6737+-+by+lopestom.zip
https://www.mediafire.com/file/do0v472pgcxu3s0/minimal_adb_fastboot_v1.4_setup.exe
I f you need help pm me
I will being posting proof of root also.
Update twrp can be flashed on but no touch.
The garlic touch recovery can be flashed and it works.
Twrp can used only temporary by fastboot boot recovery.img.
Update the other recovery can't find SD card don't use it.
Sent from my Studio XL 2 using xda premium
Sent from my Studio XL 2 using xda premium
This works and is easy as hell. You can also install Magisk 14 install zip if so inclined. Instead of the SR3 SuperSU zip. I did because I wanted a properly working for all modules (mainly luckypatcher) Xposed. Normal Xposed v87 SDK 23 doesn't work. All modules report they are not activated when they are. I, after a couple hours dining and trying many things found out that the SR3 SuperSU zip I flashed coupled with BusyBox install on this phone, which has toybox caused and will cause many apps needing root and BusyBox to not work, re, adaway, Xposed official, Rom Toolbox, Luckypatcher and more. So I used my untouched, Ie, non rooted nandroid backup to restore too, rebooted and installed the Xposed Installer that the Magisk module recommend (been through the Magisk/Xposed rodeo many times) and back to fastboot for the cmd "fastboot boot recovery.img"
Flashed the downloaded Magisk v14 zip, reboot again and fastboot twrp boot to lastly install Xposed.v87.3_Sdk23_sytemless.zip.......
Every time I tried installing within Magisk Manager. I could not get it to work even though Magisk Manager reported all was ok and no errors. But zip Flash Xposed via TWRP does. Safteynet will fail but the Xposed Installer has a toggle for on off as well as a recovery disabler zip so one can toggle reboot and it passes or flash the disabler zip instead of uninstalling the framework.
im reading all this info but im still confused. is it possible for someone to make a video tutorial on how this is all done please??
Things are not going real great with this install. First of all I used a package called MTK USB Driver2014 which had an exe file named DPInst64.exe which I assumed was a good idea for my Win 7 64 bit. I got a message screen saying Google and two different groups of Media Tek usbser drivers with various ports defined are ready to use. I went through the routine then as was outlined in the first post. First I got USB debugging enabled on the phone after going through the initial user setup (this is a new phone). Then I set on the unlock option to on as well as usbdebuggin. Then I ran "adb devices" and got nothing. A couple of unplugs and replugs of the USB to the phone showed a USB driver installing. One stated it installed OK and the Media Tek failed. I ran another "adb devices" and saw the device listed, so I decided to continue.
The "fastboot oem unlock" went well and finished in a few seconds. Then the XL 2 screen showed text in tiny, tiny white on black with 3 options to choose. the default was on the reboot option and said to push volume up to select another or volume down to select the one defaulted. I pushed volume down and nothing happened. The device appeared locked. Would not respond to volume + power button or any other controls. I waited a half hour. So I looked online and it said this happens but to reboot it. I couldn't figure out how. So after more research I found that entering "fastboot reboot-bootloader" followed by "fastboot continue" would cause the phone to go back into normal mode where I once again reconfigured the phone from scratch and enabled Developer tool USB debugging.
Now I finished configuring again and the USB drivers started auto installing again and I got the MTK error on the driver install. I had to unplug the USB and replug and enter "adb devices" and at this point the phone asked for approval and I selected always from this computer. All is well so with the TWRP renamed to recovery.img in the adb program directory I entered "fastboot boot recovery.img" and the TWRP menu came up. I didn't back up because I don't have a SD card large enough and since I can't see any files from when I connect the USB cable, I wasn't sure how to download the backup image once it is stored on the phone. So at this point I selected the TWRP menu option to acomplete the install where future use of TWRP would not be read-only (forgot the exact wording, there was a slide to the right on the bottom of the screen to accept write mode).
Now I rebooted the phone by pressing the up button of the volume and the power button at once and I am still taken to the same green on black text that I saw before on the BLU "recovery menu" (without an obvious method to select TWRP). Is this something to be expected, that the TWRP menu is only available to boot via the PC using adb and fastboot or should the TWRP image somehow remained on my phone?
Thanks!
---------- Post added at 08:21 PM ---------- Previous post was at 08:07 PM ----------
Flex_or_fleece said:
This works and is easy as hell. .
Click to expand...
Click to collapse
Not so much for me LOL.
Can you tell me just how to install root, xposed and xprivacyLua on my phone? Would really be appreciative.
See above for how far I have gotten into the process. Not looking for a different image. This is only the second time I have working on this depth of changes. Again, thank you.
I have been working on this now for 2 full days. I managed to install Magisk 16.0 using TWRP, then without understanding or thinking this was old information, I selected Xposed from Magisk (installed from Magisk before I ready about needing to install it from TWRP) and all appeared to be well. I enabled Xposed and added XprivacyLua and enabled it via the Xposed module page. Everything appeared to be setup properly but Xprivacy said it wasn't installed and a log sent to the developer proved that it was not installed (even though the check box in Xposed said so.)
So after reading the posts above, I elected to remove Xposed via Magisk and install the Magisk version of Xposed (xposed-v89.2-sdk23-topjohnwu.zip) via TWRP. Got everything installed again and same results, everything showed the check boxes marked and therefore active but XprivacyLua would not work).
Now reading above about problems with Busybox, I decided to install Busybox and then the busybox binaries via TWRP, downloaded from this location. https://forum.xda-developers.com/an...zip-busybox-v1-26-2-flashable-binary-t3581875
Now after doing that, I am hung up when trying to open Magisk. It is a solid green screen now. Tired re-installing both the zip via TWRP and the apk and have the same results. I assume I am going to have to restore. This is all new to me and I did not make a backup image because I don't have a SD card where I am working on this. All I can find is a factrory image on Needrom website: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar
Can anyone point me to a guide that explains in elementary (as possible) terms how to get this ROM onto my phone and with it restored with the factory image? THANK YOU!!!!!
Flex_or_fleece;73955523 my untouched said:
Hi, is there anyway you would be willing to share this backup? Thank you!. I live in a small town with no computer shops and I did not have a SD card to back up to. Thank you.
Click to expand...
Click to collapse
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Donphillipe said:
I am struggling with everything including lack of mini SD card while residing at the moment far away from a computer store, a USB cord that is flaky as the snow, and a bricked phone because I wrongly read in a prior post that installing Busybox was a way to resolve the issue of Xposed showing it was installed and working when it was not.
Now can anyone suggest a link that shows how to flash the ROM I found online at NeedROM: BLU_S0270UU_V6.0.04.02_GENERIC_20180203.rar to this phone? I am not an expert at this, having rooted only a few phones over the years where I wanted Xprivacy and mostly just entered a few commands to make it happen. Today its getting too complicated.
I don't know if this phone even works with the SP flash tool, and if it does the drivers I have found to attempt it are not working.
Any help would be appreciated. THANKS!
Click to expand...
Click to collapse
Hello! Been through the same thing.
It is compatible with SP flash tool. Think about it: in the factory all phones come empty so there must be something to flash them. In case of Mediatek-based devices, it's SP Flash Tool.
And yeah, your drivers are broken. First of all, uninstall them. Can't tell exactly how because I don't know what you installed but you can try the programs list and the device manager.
After removing them, download mediatek-drivers.zip and extract it.
Now follow this carefully:
1) Go to device manager and click on Universal Serial Bus controllers.
2) Then go to Action >> Add legacy hardware.
3) Select Install the hardware that I manually select from a list (Advanced).
4) In the hardware types, select Show All Devices.
5) Click on Have Disk... >> Browse, browse to where you extracted the drivers, go to mediatek-drivers/Win7/ and select usb2ser_Win764.inf or usb2ser_Win7.inf if your system is 64 or 32 bits arch respectivelly.
6) Click Open and OK.
7) Select MediaTek DA USB VCOM PORT, then just Next everything.
Now repeat every step above but in step 7 select MediaTek PreLoader USB VCOM Port.
Your drivers should be installed by now.
Now if you haven't done it yet, download it here. Run it, go to Download and in Scatter-loading File, choose the MT6737M_Android_scatter.txt file that (hopefully) came with your ROM. If it didn't download it here and place it in the same folder as the .img files that came with your ROM.
If it shows all checkboxes marked, just mark system, boot and recovery. It's a soft brick, you don't need a full reflash. If it doesn't but has system boot and recovery it's fine too. Hit download. Now, with your phone turned off, hold the VolDown key and plug it in. It will start flashing.
A popup will appear when it's done. That's it! Unplug and restart it. Should be back from the dead now.
The TWRP build you are using can only be booted via fastboot but not installed. If you flash it, the touchscreen will not work nor power buttons so you can't select anything. However I found a working flashable TWRP build: TWRP 3.1.1 built by Vampirefo
This one has the touchscreen working so you can permanently flash it on your device. It's very important to have a working recovery on your device that can reboot to bootloader because Power+VolDown actually boots in some kind of hardware test mode on this phone. Basically, if you softbricked your system, no working recovery=no bootloader=no temp recovery. And it's way easier to just restore your backup if you brick your phone.
Also, you can flash it througt SP Flash Tool. Rename it to recovery.img and go for it.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Mark42XLII said:
Hello! Been through the same thing.
Can you reply or PM me with the rom you found? Mine is really old and I always have to wait for OTA...
Also, if you have any progress with Xposed, please share couldn't get it working properly here. Not a single module works...
Tried installing it the regular way with SuperSU and Magisk and tried the systemless install within and out of Magisk. None worked so far.
Thank you!
Click to expand...
Click to collapse
I got the ROM from needrom.com you have to create an account, then just search on Blu studio xl and scroll down to pull the 2 version. Restored using SP Flash tool with non problem.
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Flex_or_fleece who claimed to get this working in a prior post said he resolved his problem by going to the link for BusyBox XDA pages for a solution, well I tried that, first installing BusyBox free from playstore, made sure that it said it was installed, then I loaded the libraries they talk about that is supposed to fix the BusyBox with toybox and after installing and testing the free version of BusyBox, then booting to TWRP and installing the Busybox library zip, once you boot up, the Magisk Manager will never open up again, just a blank green screen.
Time for a restore and try something else next time but unfortunately (unless the guy I asked about what exactly he did regarding BusyBox will respond, which he hasn't yet, ) then it's anyone's guess and I am all fresh out of guesses
Donphillipe said:
This whole thing is really frustrating. Get Magisk installed via TWRP, then to load Xposed Framework, you have to load Xposed via TWRP and then if you follow comments here from Flex_or_fleeceand his mini guide for downloading from Magisk with download only and not an install, you get the universal Xposed Systemless zip that is supposed to be able to choose which OS version you need during the install but that doesn't work installing via TWRM installing the universal version of Xpozed seamless zip so you have to download from the XDA site the latest Xposed with the SDK of your OS, in my case SDK23 latest version for Android 6.0. Now once you get Xposed installed via TWRP, then everything appears to work but trying to load XprivacyLua says it is not installed when the Xposed Module list says it is installed and the module is checked as being active. Yet the XprivacyLua menu still says you need to fix the issue.
Click to expand...
Click to collapse
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Mark42XLII said:
I already did the BusyBox thing you talked about before and it went the same way. The difference is that my first attempt was by downloading from XDA so I didn't went through the universal zip problem. Actually there is now inside Magisk both the universal zip and the targeted sdk version numbers ones. Also I installed GravityBox and it said that couldn't communicate to the framework or something like that. Basically same problem. But I noticed something: when you install Xposed and reboot for the first time, it says that the Xposed framework is installed but not active and tells you to check the logs. If you go there you can see that the log file apparently doesn't even exist. In the second reboot it tells you it's active and running but if you check the logs it still couldn't open it because it doesn't exist. So maybe the problem is that Xposed isn't even starting up.
Click to expand...
Click to collapse
On one of my iterations I installed a playstore app Marshmellow SD fix which fixed my problem with Xposed saying it couldn't read the log file. https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263 But then once I installed this, slide the slider for Xposed to "authorize to sdcard" and then Xposed no longer had the error saying it couldn't read the log file but then simply always said "log file empty".
I'm just trying for Xposed and XprivacyLua only. When if I don't install BusyBox or the follow up install of the BusyBox binary zip file (that locks up the Magisk screen) and when I only start with a full ROM restore, install Magisk with TWRP, bring up Magisk and install Magisk Manager, install Xposed Systemless via TWRP, bring it up then it says Xposed is active. In Xposed I download and install the latest XprivacyLua and click the box in the Xposed module listo enable XprivacyLua, the check box remain checked and show active but the XprivacyLua menu says it is not installed. I sent a trace to the developer of XPrivacyLua and he said that Xposed was never loading it, and this is to repeat with all the respective check box checked and everything but the actual app saying all are active.
Adding "BLU STUDIO XL 2" so maybe Google can find this thread when people don't append the 2 to the XL"
Xposed still not working
I won't use a phone without these tools so at the moment I am still using my old Blu Studio with Android 5 that has the cracked screen and it is getting more and more cracked and harder to read. From time to time I pull my new unused BLU STUDIO XL 2 out of the closet and go a few more rounds with it. I've searched high and dry for the FlexorFliece fellow who claims to have it working and can't find him on any other blog or forum and he doesn't respond to messages but I just don't see how he got the Xposed suite working on this phone. I just spent three 14 hour days working on it as of today and got so frustrated that I reflashed the stock ROM on it and set it back in the closet again to try again another day, perhaps waiting like last time for a few more releases of the respective apps and modules to try again.
Now with several iterations of installing Xposed I've gotten the "green light" from Xposed Installer menu saying that it's installed and working and with the latest release which I think I recall is Magisk 17.1 and Xposed seamless SKD23 at release 89.3. This is actually quite funny that the light is green with Xposed Framework indicated as active from the Xposed Installer menu. You can then start searching for and downloading modules from the Xposed Manager and eventually the "green light" will go red while none of the Xposed modules will ever work, green or red light. At least the red light finally gives you a real indication.
I've loaded versions of Magisk all the way back to V14 and Xposed seamless (SDK23) back to 87.3 and the results are always the same. I'm either in a boot loop on a bad try or on a good try I'm showing the green light on Xposed but with no module working and reaching a threshold of about 6 Xposed modules loaded, then the light finally turns to a red one saying it's not installed or working.
I tried Flex or Fleece's technique of adding the Magisk version (from its repository of Magisk modules), the busybox and the ADB/Flashboot modules as a prerequisite but that didn't do a thing.
Now here's some odd things about this phone and even getting it to a good point to experiment with it.
I've found if I start with a fresh flash of the stock ROM or the phone in any condition without USB Debugging on, for example if I start with a powered down phone and hold the VOL-UP and POWER button at the same time, I can go to the stock recovery to select boot to bootloader option. (Release the POWER button slightly before the VOL UP or you'll boot the phone instead.)
Next I move to the PC and begin fastboot commands:
- get the ADB command window up by bringing up Windows file explorer with the name of the ADB folder visible and while holding SHIFT I then right click on the ADB folder and select "Open command window here" which opens a "DOS prompt" with the adb files in the directory. It's assumed I have pre-copied the new recovery image recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img to the same directory (folder) as hosts the adb.exe and fastboot.exe. Here I go back up to Windows File Explorer open the folder containing ADB/fastboot and rename this image to a shorter name. (Could use the DOS rename command but the syntax is too long and too easy to make a mistake.) Here I have renamed it to simply recoveryTWRP.img
Now then on the PC command window I enter ....
fastboot devices (to check that my USB is working OK)
fastboot oem unlock (to unlock the bootloader)
fastboot flash recovery recoveryTWRP.img (recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img that's been renamed)
fastboot reboot (to reboot the phone)
The phone may not boot after a flash or after and adb/fastboot interaction if the USB cable is not unplugged when done, so be aware of that.
Now if you are fast, you can go ahead and hold VOL UP at the moment the phone begins to boot and at the moment you have completed the fastboot series of commands. As soon as you see the TWRP recover manager you can release the VOL UP and be patient while the TWRP Menu appears.
Note now that you won't be able to use the SD card you may have randomly installedwith TWRP unless you have initialized it via Settings on the phone where you have under Storage option, set the SD card type to be "portable storage". If it's not formated and initialized by this phone, TWRP won't let you select it.
Quirks seen here include a failed install with unable to mount errors on the TWRP console trying to root, that is unless you have actually initialized the phone and set on Developer Tools and turned on USB debugging. (Sounds crazy but that's what I am seeing.) So basically that's what you'll find. ALso this verion of TWRP on this phone will not mount USB storage as with TWRP on other BLU devices I've tested, so copy all l your potential zip files to install as well as your apks you plan to side load (e.g. Xposed Installer and Magisk Installer apk files to the SD card prior to loading TWRP and finding that the files are not on the card or in the phone storage yet.
Other caveats are, with USB debugging off, each time you plug in the USB cable and want to upload files to the phone, when you go looking for the files in Windows device manager you will see a blank white screen appearing like there are no files on the deivce. What you have to do is slide the phone messages up and down a few times (perhaps dragging down from the top if it's not on the main screen) and finally the small window will appear on the phone where it asks for USB Charging only which you can tap and change it to USB Media and at that point you can see the SD card and Internal Storage for the phone in the respective Pc window where you can drag files into the phone's folders from the Windows PC. Otherwise with the phone having USB Debugging on you are supposed to be able to set it permanently to USB Media but you actually can't set it permanently. If you do research you will see online articles claiming that with Developer Options enabled and USB Debugging on, that setting the option just above the green "input" word on the Developer options screen allows you to set USB Charging to USB Media and it should stay permanently. Well stay it does on the menu but the function itself does not stay. Here each time you plug the phone in with the USB cable you will be curious why you cannot access the phone's storage because you believe the menu in Developer options that says it has been set to USB Media. Yes, it shows that way but you still can't see the storage on the PC. What you have to do each time you attache the phone with a USB cable then is go to Developer Options (shortcut would be to click on the info bar stating USB Debugging is enabled and when you arrive at Developer options, page down to just above the green "input" word and then temporarily set the option from USB Media to one of the other options, then set it back again to USB Media and you once again can see the phone's storage on your Windows computer.
And all this work and dealing with quirks is required before you even try to root by using SU or Magisk zip files and attempting to install then via the new TWRP recovery image you installed and gain access to by rebooting and holding in the VOL UP button to access the TWRP menu.
Otherwise the best performing ROM I have found is BLU_S0270UU_V6.0.04.02_GENERIC but when I went looking for it just now, the only place I can find it is now with the new toll-booth controlled need.rom repository. Yes I now see that needrom.com has now started charging to download the zip recovery modules we all uploaded there for free. What a sneaky bunch of #$#R)!!! Also, the spamming of Google has made searching for ROMs and any information about rooting a phone all but worthless. For example when I searched for BLU_S0270UU_V6.0.04.02_GENERIC which I believe is the latest ROM. I know there is a V8 floating around out there that I loaded but just in setting it up, the layout of the screen first went crazy and then the wireless log-in gave problems and then and finally the turning point was that the camera or video wouldn't work, so I gave up that version of the ROM. Anyway, searching for the ROM resulted in 5 full pages of search results with every website on every page saying they had the rom to download but in fact none of them did. I got directed from everything from purchasing female teen clothes, to sports gambling sites to unending surveys to you name it. What a vast wasteland it is out there these days. Unless Google does something to stop this technique where every website says they have a hit on your phone model when all they do is to stuff your search argument into a page of generic randomly generic diatribe, one day we will no longer be able to use the Internet to find things, or certainly it will take more time while weeding through all the disinformation.
Now
Yes, but that is not the challenging part. The challenging part is to get Xposed installed and the Xposed apps working with your root that you can obtain by several methods.
TWRP and this phone is easy, as you said and as I agreed. You will not be able to get Xposed apps running if that is the goal - even with root.
What is the main interest in this phone rooted? No one has gotten Xposed working so far or if they do get the green banner saying it is installed, it doesn't work with any of the apps. (Reported as due to toybox.) The phone has been rootable for nearly a year now, it's just that you can't do much with the root once you get it.
I have had my phone rooted for over a year now. Every few months I try again installing the latest version of Xposed via SuperSU or Magisk. Xposed apps will not work with either.
Get Edxposed, Magisk, and GPay to work together.
1. Install or make sure you are on latest Magisk Manger (7.5.1 or newer)
2. Install or make sure you are on latest Magisk (20.3 or newer)
3. Hide the following in Magisk Hide
-Google Pay
-Google Play services, only select the following
-com.google.android.gms
-com.google.android.gms.unstable-Google Play Services for AR
-Google Play Store, select everything but com.android.vending
-Google Services Framework
-Nfc Service
4. Install the following modules
-GPay SQLite Fix (Full Edition)
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176-SQLite for Arm aarch64 devices via Magisk Manager
-hardwareoff by @Displax (Thanks to @Kris Chen for making me aware of it) or use MagiskHide Props to set check to basic and fingerprint to Pixel 3a
5. Reboot
At this point make sure you have GPay working before installing edxposed. If for some reason you are unable to use GPay try deleting data for Google Play Services/Google Play Store/Google Pay
After you confirm that GPay is working then move on to installing edxposed
1. Download and install Riru - Core via Magisk Manager
2. Download Edxposed Manager (4.5.4 or newer) (Don't Install Yet!)
https://github.com/ElderDrivers/EdXposedManager/releases/3. Download Edxposed (4563) (Don't Install Yet!)
I'm personally using the YAHFA version.
https://ci.appveyor.com/project/ElderDrivers/edxposed/history
4. Once you have all these files downloaded turn on Airplane Mode and install the Edxposed Magisk Module (Magisk -> Modules and press the + sign, find the downloaded zip and select it, Magisk will install it) and Edxposed Manager APK and reboot
5. Once booted up remain in Airplane Mode
6. Open Edxposed Manger and go to Settings and turn on "App List mode"
7. Exit and reopen Edxposed Manager
8. Go to Applications on the side menu (should say "Black List" on top) and select the following apps
-Google Pay (may not be needed)
-com.android.nfc.auto_generated_rro_product_
-com.android.nfc.auto_generated_rro_vendor_
-Nfc Service
-pixelnfc (new in Android 11)9. Go to Settings on the side menu, at the bottom of settings find and enabled "Pass SafetyNet"
10. Reboot and turn off Airplane Mode
11. Optional* Hide Magisk Manager
Note. Steps 4-9 should be done in Airplane Mode, this will keep anything tripping safety net during the setup process.
eg1122 said:
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Click to expand...
Click to collapse
Here are some screen shots of it working
Thanks for this @eg1122.
After soft-bricking on my first try, I've been wondering what the working version combination is.
The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Sent from my Pixel 4 XL using Tapatalk
View attachment 4858559
Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Sent from my Pixel 4 XL using Tapatalk
xdeslitx said:
Finally got exposed/gravitybox installed.
Anyone know any tweaks for the home screen grid size?
Click to expand...
Click to collapse
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687
xdeslitx said:
The one that is available to me is an older version maybe that's what caused my bootloop? Why does my screenshot look like crap?
Click to expand...
Click to collapse
Use the link I posted to get 0.4.5.5
eg1122 said:
Check my thread in Themes and Apps section
https://forum.xda-developers.com/pixel-4-xl/themes/substratum-pixel-launcher-editor-t3990687
Click to expand...
Click to collapse
That looks pretty nice...thanks
Sent from my Pixel 4 XL using Tapatalk
eg1122 said:
I've been reading a lot of our forums and many are asking about Xposed. Decided to make this thread to try to keep all discussion in one place and make it easy to find information.
I am currently running Xposed and I'll lay out the steps I took to get it working.
1. In Magisk Manager find and install Riru - Core v19.5
2. Reboot
3. Download and install Riru - EdXposed v0.4.5.5_beta (YAHFA) via Magisk
https://github.com/ElderDrivers/EdXposed/pull/354
4. Install EdXposed Installer
https://github.com/solohsu/XposedIn...d_v2.2.5/EdXposedInstaller_v2.2.5-release.apk
5. Reboot
6. Enjoy
Click to expand...
Click to collapse
This won't trip Safety net right i assume?
varun.gid said:
This won't trip Safety net right i assume?
Click to expand...
Click to collapse
Nope
Disregard...
How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.
Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?
gettinwicked said:
How does using Xposed affect monthly security updates? Do you have to disable or whatever? I'm not sure I want to do this, I'd rather not cause problems.
Click to expand...
Click to collapse
I disable big modules like Xposed when I update. Then re-enable them once update is completed. I'll put a step by step here.
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
tardis_42 said:
Got xposed installed and running thanks to this thread, but the module download screen is empty - just shows the refreshing icon and "module list will be loaded in a few seconds" forever. Anyone else seeing this?
Click to expand...
Click to collapse
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up
eg1122 said:
Try the following
Try clearing app data and cache for edxposed.
Uninstall Edxposed installer and reinstall
Reinstall any Xposed modules not showing up
Click to expand...
Click to collapse
Clearing data did it, thanks!
How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.
madgooner2810 said:
How do you install edexposed via magisk? I haven't rooted since the P1 so I'm out of the loop here sorry.
Click to expand...
Click to collapse
In Magisk, go to Modules and press the + button, then find the zip and select it.
Thanks...
FYI, Riru - EdXposed v0.4.6.0_beta (YAHFA) via Magisk also works.
@eg1122 great instructions worked perfectly. Thanks!
This is my first venture in the absence of "comfortable" apps that come from Google, so please reply with any suggestions for things like messaging, calendar, etc.
I did a similar guide for the Pixel 3a but the 3a came with a broken speaker so we ordered a 4XL and I'm adding this guide specific to that phone, and switching from Google Apps to microG. Also in the previous guide it was using Google Apps, whereas this guide shows how to do it with microG, F-Droid, and Aurora Store to replace the Google Play store and its related bloatware.
This guide will should work on the Google Pixel 4, and possibly other Pixel devices as well assuming you adjust your release version appropriate to your model (eg, "coral" is for the 4XL).
Enable developer mode
OEM Unlock: method 1, method 2
Unlock the bootloader:
adb reboot bootloader
fastboot flashing unlock
Install the latest android platform tools for fastboot and adb:
https://developer.android.com/studio/releases/platform-tools
Install the official Android 11 for updated firmware:
https://developers.google.com/android/images?authuser=3#coral
Agree to terms and conditions
Download the latest v11 zip (RQ3A.211001.001, Oct 2021)
Unzip and run:
Windows: flash-all.bat
Linux: ./flash-all.sh
Repeat #3 above if necessary
Download and transfer LineageOS 18.1 with microG patches:
https://download.lineage.microg.org/coral/
Download the latest recovery .img to your desk
Download the latest .zip to your desk
Install the recovery image:
fastboot flash --slot all boot lineage-18.1-20211103-microG-coral-recovery.img
Reboot to recovery (may need to power off first)
From the Phone: In recovery it should show the LineageOS icon:
Advanced->Enable ADB (may not be necessary)
Apply Update
Apply from ADB
From your desk:
adb sideload lineage-18.1-20211103-microG-coral.zip
If you get errors like error: protocol fault (no status) then your version of adb is too old.
It should say Total xfer: 1.00x but the official LineageOS installation docs say that it might hang at 47% and that is ok because it is done transferring to the phone at that point.
Using microG. just reboot From your phone:
If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
If so, then tap Apply Update->Apply from ADB and follow Google Apps .zip install notes below in #7.3
If not, then tap the left return arrow and then tap "reboot now"
F-Droid
Open the "Browser" app
Go to www.f-droid.org
Download the .apk
Open the Files app, browse to Downloads and open the F-Droid.apk file.
OPTIONAL: If you want apps from the google store, then install Aurora Store:
Open F-Droid, search for "Aurora Store" and install it
Now install whatever other F-Droid and Aurora apps you want.
Alternative Apps
I always install AFWall+ and allow only the apps that I care to have access. If there are alternative apps to AFWall+ that work well for a firewall then please reply below!
Maps & Navigation: Haven't tried these yet, but trying to jump ship from Google Maps. What mapping software do you like?
OmsAnd
Organic Maps
Navit
Please suggest others and I'll update them here
Optional ZIPs:
If you are already in recovery, go to step #7.2. Otherwise, get into recovery. If you already booted into LineageOS, then I find it easiest to reboot into recovery by enabling "Advanced Restart" :
Systems->Advanced->Gestures->Power->Advanced restart
Then hold down the power button and select Power->Reboot->Recovery
To install zips:
First mount /mnt/system: Adbanced->Mount/Unmount System
This is necessary because the Pixel is a A/B boot slot device and not all .zip's will know how to mount.
Use adb sideload <filename.zip> as in #6.4 above (but with the .zip you want!)
You may be prompted on your phone to install even though the signature is untrusted.
Root your device with Magisk:
Download the latest Magisk APK:
Note that the .apk is also a .zip, so rename it if you must (but I didn't need to).
Enable adb
Install the apk:
adb install Magisk-v23.0.apk
Troubleshooting:
LineageOS recovery doesn't like to install multiple zips at once. If you get the error adb: sideload connection failed: closed then click the left back arrow, then again folow steps from 6.4
Try factory reset if you have boot issues the first time
Should i do factory reset in recovery?
I think I formatted every partition on mine during install, so I'm not sure I did a mfg reset. You may need it, however. Backup any data you might want first!
Will whatsapp and banking apps works?
@skothiya, I haven't tried, I'm assuming you are referring to SaftyNet. MicroG does have SaftyNet spoofing which may or may not working back depending on the app.
Read this article on the subject: https://github.com/microg/GmsCore/issues/1397
Here is a thread with more info about the microG setup:
Getting started microG: how I degoogled my Google Pixel
Hello all, Recently I got a new phone and installed it using LineageOS + microG. Many Android apps rely on the Google Apps API, but many people no longer trust Google for various reasons. In response to this, microG was created as an...
forum.xda-developers.com
Hello everyone,
Lately there has been lot talking about Facebook Meta, Virtual reality and stuff like that. I decided I also wanna try some VR experience, so I bought headset for 30 bucks, took my old mata lying around and got Daydream, nowadays unsopported but very good vr platform, working on this phone.
Daydream was interduced alongside first Google Pixel and died with Pixel 3. There wasnt many phones on the market wit official support which caused platform to die. But thanks to our skilled guys, we can enjoy it on pretty much any device.
Im using my PH-1 as a 360 cam so my guide will be showing how to get this working on latest stock firmware.
1. Install adb/fastboot tools
Guide here
2. Unlock bootloader and critical partition ( just to be able flash full firmware in step 5)
You can watch guide here
3. Download necessary files
Download stock factory images from here
And magisk manager app from here
4. Ensure youre on build number QQ1A.200105.032, if you are skip to step 6
5. Updating to latest firmware
Extract downloaded factory images, reboot phone to bootloader mode and doubleclick flashall.sh
Newest firmware should be flashed in a few minutes. then reboot the phone.
6. Rooting the phone
Copy magisk.apk and boot.img from factory images folder into your phone storage.
Install magisk app, open it and click install, select and patch file and choose boot.img you moved to your phone.
Move patched boot image back to your PC
Reboot phone to bootloader mode once again
Flash patched boot.img via command fastboot flash boot_a /location.of.your.file repeat for second slot fastboot flash boot_b /location.of.your.file (some of you may have to use command fastboot flash:raw boot_a). Then reboot the phone.
7. Setting up magisk
Magisk manager should appear in your menu. Open it and it will install its full app. After opening newly installed magisk, phone will restart and magisk will be fully installed.
8. Unlocking Daydream.... finally
Open magisk
Switch to modules (bar at the bottom of screen)
Search for Pix3lify and click install
During installation choose Slim installation otherwise you will end up on bootloop
Restart the phone
9. Fixing Library resolution
Open magisk once again
Open modules
Pick install from storage
Install this module
Restart the phone
10. And thats it, daydream should appear in your google play store after a while. If not just sideload it from apkmirror, but everything should be working nicely.
to moderators: this is my first thread ever, and thought a complete guide like this really has to be done. if it's not right or not in the right place, do what is right
Click to expand...
Click to collapse
Since there are only 3 useful guides about modifying this specific phone, and some really don't answer a few barriers placed in our way by HMD Global and its ridiculous OEM unlocking restrictions (-_-), and also Google probably dropped making OTA updates for it (which was very important to me, because Android 9 and 10 had bugs), I decided to mix them all up (I will give credits, obv) and add some more info I found and create a thread which will work on Android 11, which worked on my phone, not tested on another Nokia 2.2.
Hope it helps y'all!!
Part 0: Preparations
WARNING: Your storage will be wiped completely!! so make sure to back everything you need up before doing anything. Unless you have bricked/soft locked your phone, then in that case you can use MTK Client app to backup userdata.bin (more info on Part 1-2, marked with a )
Requirements:
A good computer
Obviously a network connection on your computer for downloading files, and on your phone if you wanna update thru OTA
USB cable, capable of transferring data, and without any annoying repeated disconnections or "has to be put in the right angle and position". Just use a fresh one
VCOM and adb drivers, which can be a little annoying getting them to work. Best option is to install 15 seconds minimal ADB and make sure you say Yes when it asks if you want to install device drivers.
Android SDK Platform tools, which can be downloaded from here (NOTE: You have to use Platform tools. minimal adb will NOT work with fastboot on this device. So go to C:\adb and delete everything in there, then extract platform tools in that folder instead)
and the most important of them all: MTK Client by Bkerler which can be downloaded from here. Follow the installation instructions in the link, install Git and Python and also usbdk installer featured in the Github instructions for MTK Client
All done? Great! moving to the next part
Part 1: Unlocking the bootloader
The most annoying part. Thanks to hikari_calyx for their awesome guide on how to unlock the bootloader for this phone. We will follow it step by step until we reach step 6, where we are about to flash all those backed up img's back using mtk-su. Here's the problem, you can use mtk-su only on Android 9. it doesn't work on Android 11 sadly. so we just make sure we have unlocked sec1.img and seccfg.img in a safe place, then install a fresh stock Android 9 rom om our phone with any method we are most comfortable with, like SP Flash tool like in the guide, or booting into recovery and sideloading thru adb or from sdcard. just search the net and I'm sure you will find a loooot of sites explaining how you can flash a stock android on your phone. Just make sure you won't mess IMEI and Serial Number up!!!
**There is a "unlock bootloader" option in the flash tools tab of MTK Client. haven't tried it out myself but you can give it a try**
Extra: Booting into stock recovery
There is another detailed guide on how to enter recovery mode, by foobar1123321 which you can see in here. You might need it to apply updates to your phone
After flashing and updating your OS to latest version of Android 11, it's time for Unlocking the bootloader again. but sadly, Unlocked OEM doesn't let OTA updates to be received, and trying to flash sec1.img and seccfg.img on Android 11 is not possible without root, and root is not possible without OEM unlocking :\
So here comes the neat part, MTK Client
Part 1-2: Unlocking the bootloader again
Go to the folder where you installed MTK Client (hopefully you know how git works and got it cloned and working, if no, then read Installation instructions carefully in their Github page), and open a CMD window there by typing in cmd in the address bar. then write python mtk_gui and hit enter. Do not use mtk_gui.bat since it will close the cmd and not work. Do NOT close this cmd tab. After a while, the app will start and asks you to connect your phone.
Shut down the phone, and after 5 seconds, press and hold both volume up and down keys (without the power button) and connect the phone to your computer via cable while still holding the volume buttons. If you have installed the drivers successfully, then you'll see some texts generate in the cmd window, and will (probably) wait for the Preloader VCOM.
you can let go of the volume keys.... but not for so long. Disconnect the USB cable, hold volume keys, and connect the phone again and you'll see that MTK Client successfully gets access to your phon. YAAAY!!
now you can let go of the volume keys
Go to "Read partitions" tab, and select Boot_a, Boot_b, sec1, and seccfg (make sure you wouldn't mistake them with unlocked sec1 and seccfg)
And then click on Read partitions button in the right side, and choose a location to save these partitions
You can also check userdata, if you have bricked/soft locked your phone and wanna backup your Internal storage data. You can flash it again with this app after you have fixed your phone. and if the problem wasn't caused by your data, you can use them again like you never wiped your phone
After everything is backed up, go to "Write partitions" tab, and find sec1 and seccfg, click on "set", browse and select the respective unlocked partitions we got in Part 1 (you may need to change their extension from .img to .bin for them to show up)
Click on "Write partitions", and done! You have unlocked your OEM on Android 11!! and if everything is done correctly, you'll see
Orange state Your device is unlocked and cannot be trusted Your device will boot in 5 seconds...
Click to expand...
Click to collapse
or something like this when powering it on, congrats!!
Part 2: Installing TWRP
from the official TRWP page for Nokia 2.2, download the latest TWRP image file and move it to c:\adb on your computer and rename it to twrp.img
you will also need to download a stock vbmeta image, which can be found here or simply by reading it from your phone via MTK Client (there will be two A/B partitions, any of them works) and rename the downloaded/grabbed file into vbmeta.img and move it to c:\adb
power off your phone, then boot into fastboot by holding Volume down + Power for a few seconds, until it says FASTBOOT MODE => then connect the phone to a PC, and write:
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
and then
fastboot flash boot twrp.img
Click to expand...
Click to collapse
Now we have the latest TWRP on our Nokia 2.2 , but seems like accessing TWRP is only possible by either rebooting to recovery when the phone is powered on, via Magisk, Termux, or any other app with power options (after rooting the phone), or writing this when the phone is in fastboot mode:
fastboot reboot recovery
Click to expand...
Click to collapse
You can use TWRP and all of its awesome features now, except for MTP, backup, reading userdata partition, etc. to fix that, you gotta wipe internal storage, so make a backup of your files before processing.
**IMPORTANT: Do not flash TWRP after rooting the phone or it will unroot it**
Part 3: Rooting via Magisk
I'm gonna use Magisk because... it's better than other SU apps. Get it from here and install it on your phone. Now that you have your OEM unlocked and boot partitions too, you just have to copy the partitions we got via MTK Client on your device, launch Magisk app, select Install Magisk, then choose a file, which is gonna be Boot_a.
Wait until patching is finished, and after it's done, go into downloads folder and rename it to Boot_a or you will get confused later
After that you can choose Boot_b to be patched, and after it's done, rename it to Boot_b too
Copy them both to C:\adb from your phone to your pc, and power off your phone
after you get sure device is not connected to the computer via cable, and is powered off, hold down the volume down key with power button, until your phone boots into fastboot mode
Now open a cmd in C:\adb, and write
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_b.img
Click to expand...
Click to collapse
when done, disconnect your device, and restart. You can check the Magisk app, and realize you now have superuser permissions!!!
**UPDATE** Part 3-2: Hiding Magisk
Hiding Magisk and bypassing SafetyNet is another challenging problem on this phone. Cause when you try to Hide the Magisk app, you'll come to a simple "Failed!" error which is most probably caused by SELinux status. To fix this we gotta install some modules
First of all, install Busybox from Google Play or any other source. It's not necessary, but it's good to have. simply just install it, no need to restart
Then we need to install a module called SELinux permissive (wow, how unique ;w; ) by evdenis, which can be found here. download the zip in your phone, open the Magisk app, and in the modules tab browse for our newly downloaded zip and wait until the operation is done. Reboot your phone, and you are now able to hide Magisk app without any problem.
So do so, open Magisk -> settings -> hide the Magisk app. Choose a name (settings by default) and wait until app launches itself, asking you to add a shortcut to your home screen (optional). This way, your Magisk app now has a random package name and signature and can't be detected by other apps. Now moving to the next part
Bypassing the SafetyNet:
First, in Magisk settings, enable Systemless hosts. it will add its module to the modules tab. check if it's enabled
Then toggle Zygisk in Magisk settings, and restart your phone again (2 restarts? alright no problem)
Once your phone booted up, on the main screen of Magisk, check if it says Yes in front of Zygisk. if yes, than congrats! we are not down yet tho
Go to Magisk settings and toggle Enforce DenyList, don't reboot for now (yes, there is a 3rd one coming ), but go to Configure DenyList and choose the following apps
Google Play Service
Google Play Store
Google Service Framework
Google Play Protect Service (which is probably not present, but wrote it just in case it is on your phone)
Click to expand...
Click to collapse
and also you can choose your banking apps, or any app that prevents you from using them like Netflix or some games. Now you gotta restart (third time is the charm )
Now we gotta install another module which is Universal SafetyNet fix by kdrag0n which can be found here. Download it to your phone, choose it in Magisk module browser, wait for it to finish, and restart (I'm losing my control!!! Hmph!)
Now that we did all this, we have to clear data of apps in our DenyList so they would never remember if we ever had root or no
Go to settings (the actual settings, not our now hidden Magisk app) -> Apps -> all apps -> tap the 3 dots on top -> show system apps, then find all the apps you added to your DenyList and clear their data (not cache, data itself)
Now that this is down, restart your phone ((╯°□°)╯︵ ┻━┻) it's the last time, so you can stop raging now (┬─┬ノ( º _ ºノ))
Now we can install an app like YASNAC and run SafetyNet attestation, if the results showed two pass checks, Congratulations, you bypassed SafetyNet!!!
Totally worth the restarts. (Thanks to Droidwin for their article)
And that's it!! Hope you enjoy your now rooted Nokia 2.2 phone with Android 11
Great guide, and yes mtkclients unlock will work but it may put Ur device into verity eio mode
¿Can I use the Part 3-2 to hide Magisk in Android 9 instead of 11?, I find stock Android 11 very laggy and unstable on my phone (using the camera on any app can take from 1 to 3 or 4 tries to get it working, for example), and Android 9 has served me waaaaay better. However, my banking app refuses to work with root.