Database Develop

[GUIDE] Root Samsung Galaxy Music S6012 & S6010

There have been many people looking for an easy way to root the Samsung Galaxy Music S6010 (single sim model) and the S6012 (dual sim variant) since this phone came out six months ago. These people have all been frustrated. If anyone found a reliable way to root these phones, they have not posted them here on XDA.
So, here it is, with pics, so that it is easy for the noobiest of noobs.
standard disclaimer: BEFORE STARTING BE AWARE THAT ROOTING VOIDS YOUR WARRANTY (THOUGH YOU CAN EASILY UNROOT AND GET YOUR WARRANTY BACK) . I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE!!!
First of all, thanks to XDA member stat'o'flow who posted the method for Chinese tablets and phones, which seems to be pretty universal, but I am going adapt his method a little to focus on this particular device:
{
"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"
}
HOWEVER IT SHOULD WORK ON MOST DEVICES, INCLUDING CHINESE PHONES AND TABLETS.
Do check if it works on your device and let us know in this thread.
On your PC:
1. Install USB/ADB drivers from Sumsung's website or simply install the Kies software for the Galaxy Music.
2. Install this software: http://www.moborobo.com Management Tools, loads own device specific ADB-drivers
3. Download & install this software from http://www.shuame.com/
- Install on your pc. During Installation uncheck every checkbox except the one that grays out the next-button upon unchecking. Now, there should be three shortcuts on your desktop. we are only going to use the first two.
4. On your device: turn on USB-debugging. Settings>Developer Options>OK>Tick USB debugging
On your PC:
5. Run Moborobo Software, then plug your device to USB-Port, wait until Moborobo has recognized it
6. Run the Shuame software.
7. Wait until shuame app appears on your device's screen. Then on your pc, in the Shuame window click the 4th icon in the top row (step 1). On the screen that appears, click on the 4th icon in the 2nd icon-row (step 2)
8. On the device click the 'Restore my Data' button
9. On the pc, wait for the green line to finish moving to the end (your device might restart in between)
Click the blue button!
On the Phone:
10. Download and install SuperSU app from Play store.
11. Shuame will ask for permission to grant superuser to SuperSU in Japanese, so remember you have to click on the left-hand side button.
12. Download and install root checker app from play store. Check if you are rooted.
13. Uninstall shuame and maroboro using ES explorer or Titanium (you will have to grant these programs superuser permissions first).
14. That is IT!!!
​

You can also use this Shuame software to unroot the device (always remember to do this before giving it in for service or claiming warranty!!!)
And also may other things, as you can see in this pic, with easy to understand translations of the chinese lettering.
You just have to click on 'REMOVE ROOT'

Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Can u give any method for installing custom recovery guide on this music duos after rooting ??????
I also wanted a good call recording mod
Pls anybody on this forum guide me
thanks
Sent from my GT-N7000 using xda premium
Sent from my GT-N7000 using xda premium

Can u give any method for installing custom recovery guide on this music duos after rooting ??????
Click to expand...
Click to collapse
Some developer has to make a custom recovery for this particular model before you can install it on your device. AFAIK there are no ROMS or recoveries available for the Samsung Galaxy Music phones.

Someone asked me this question on PM so I am quoting it here for other people.
Hey bro, do you know what I'm doing wrong? I don't get the recovery option on my phone but it get root... Maybe I'm I deleting the wrong archives on the last part or I just get a temporary root because 30 minutes later it say the us file don't exist
Click to expand...
Click to collapse
I have not encountered this situation before (not getting the 'restore my data' window) but try doing the entire process again. This time install the superSU app before restarting the phone after it gets root. Then delete the kinguser or kingroot app from your /system/app folder with ES Explorer (you have to grant it superuser permission first, and also change permissions for the app).
Uninstall the shuame and moroboro apps the normal way.
Now restart and see if you still got root.
Also please ask questions in the thread instead of pm, so others can also read (or offer) solutions.

FallenAngelmxw said:
Hello! I was looking into your thread about rooting the Galaxy Music, and I just wanted to say that I had the same problem than the other guy that sent you a PM!
I downloaded all the softwares you said, made everything correctly.
And after the sad result, I formatted the phone with Factory Data Reset.
The problem is: I can't make the root, the Android don't asks me if I'll accept the Full Restore, and when it finishes, I go to the root app checker that says my phone isn't rooted.
And even if I make the factory reset the Japanese crazy apps remains there!
And sorry about sending the message through here, I can't post on your thread because the rulles don't let me.
I'm a little desperate about my phone because it came with a lot of apps that eat the entire ram memory, so it starts to be very slow.
I already had tried another root option that didn't solve the problem.
Thanks for reading.
If you discover something about that problem, I'll be very glad!
Click to expand...
Click to collapse
If the phone does not ask you to restore your data, it might mean that there is some anti-virus or other security software that is interfering with the root process.
Or you do not have the correct ADB drivers for the phone. Check that you have the drivers for your model, disable security software temporarily and try again. Use the original USB cable that came with the Galaxy music phone to connect to the PC.
When are you factory-resetting the phone, right after you check with the root checker app or before? Factory reset can remove root. The fact that the Jap apps are still there after you reset means that they have succeeded in installing themselves into the system. Which superuser app are you using, Superuser or SuperSU? SuperSU is better since it also replaces the binaries.

FallenAngelmxw said:
Hello! Thank you for the support!
After resetting the phone I tried to root it again.
It occurs that when you open the root app checker, pops up a message in Japanese (that is the "root" permission), and on you have 2 options, the left one is to allow the access and the right one have a countdown and is the one that deny the access!
When I rooted for the first time, I denied without knowing what was happening.
Now I press the left one that is the allow one, and it works!
I wanna thank you for the thread, and I'm asking you again to quote this and post in the thread, because I don't have a permission.
I always entered in this forum, but never made an account, now that I saw this root a resolved to make one, so that's why I can't post. I have to post at least 10 messages on the general forum to grant my permission in other forums.
Click to expand...
Click to collapse
Thank you for providing this solution. I had also clicked on the wrong button, but somehow forgot to include this in the tutorial! I have now updated the guide.

:laugh:
NEW: UPDATE YOUR SAMSUNG GALAXY MUSIC DUOS S6012 TO OFFICIAL JELLY BEAN 4.1.2!!!
THE COMPLETE GUIDE IS HERE
:victory::victory::victory:
​

Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?

rahulsinha said:
Tried the above rooting method but didn't get the RESTORE option so clicked the blue button on the monitor which created an application in Japanese language and the phone shows rooted now.
Only problem is if I disable that new Japanese app the phone says not rooted. so i have kept the app and every app which requires rooting permission takes permission from that Japanese application.
The SuperSU app also works but only for 10-15mins, have to give that admin rights in every 15mins, so i use the japanese app itself to grant permissions. Is this ok what I have done ?
Click to expand...
Click to collapse
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?

itsnotmeatall said:
Ya, it's ok. But ideally you should install an English language app such as Superuser or SuperSU. When you install SuperSU, do you also update the binaries? That is required for SuperSU to work. When Shuame asks for supersuser permission for an app, here should be option allow for ever. Once you have SuperSU installed, you can uninstall Shuame with the method described above. The trick is to allow SuperSU superuser permission for ever instead of just 15 mins. The English language apps have this option.
BTW, did you root the ICS build or the new Jelly Bean build?
Click to expand...
Click to collapse
Ya, I did update the binaries, it asks as soon as the app opens but after every 10mins it used to ask me to update binaries. Now what I did is that I made it install as the system app and also checked TRUST SYSTEM USER & now on every app is seeking the permission from Supersu & not Shuame, so i have just disabled not deleted the Shuame permission app.
I had rooted the ICS version not Jelly Bean, quoted the wrong message by mistake.

I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??

rahulsinha said:
I have one question, will this root method work with all the phones if you have all the needed USB / ADB Drivers ??
Click to expand...
Click to collapse
Ya it should work on most devices.
Only way to know for sure is to try it!

Thanx

itsnotmeatall said:
Ya it should work on most devices.
Only way to know for sure is to try it!
Click to expand...
Click to collapse
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641

mattanur said:
There is a great tutorial on "How to root MSI Windpad Enjoy 71" by kibaruk which uses only one English tool Cydia Impactor. I could root my Samsung Music Duos GT-S6012 updated to 4.1.2. JB very easily. No hassle with chinese language. I also faced the problem of not getting "Restore Your data" window while using Shuami software.But with this tool every thing is very smooth.
Vist this page: http://forum.xda-developers.com/showthread.php?p=45409641
Click to expand...
Click to collapse
Just tested it, it works smooth as butter!! Thanks Mattanur!!
It really is a much easier way to root the Samsung Galaxy Music (Note that I haven't tested with the stock ICS build, only the Jelly Bean 4.1.2 official update)
I will update my 'Update S6012 to Jelly Bean' thread with the method.
Thanks again!!

Not Work
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help

-iCode said:
Why not work, i can't see anything on my phone (when i try to install SUPERSU). I've done all you asked. Help
Click to expand...
Click to collapse
Check with root checker to see if you are rooted

itsnotmeatall said:
Check with root checker to see if you are rooted
Click to expand...
Click to collapse
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk

-iCode said:
Oh my god. Home i can reportage the Chinese Root with SuperSU I or Superuser??
Sent from my Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Nothing happens when you try to install either of those apps? There is no popup in Japanese asking for permission? By your rather cryptic (possibly google-translated) reply above I assume you are already rooted?
Try clearing cache of both the japanese apps (in app manager) then try again.

[Q] My HTC One is broken

First of all, my HTC One is unlocked and s-off.
Originally I was using 4.4.2 stock rom, then I started using ARHD 41.0.
It worked very well at first, but when I added a few mods(xposed), I experienced terrible battery drain.
I'm not sure if the mods caused this, or because I just spent a lot more time using my phone.
Anyway, after a while I tried upgrading to the latest ARHD 51.0, but it didn't work, I couldn't boot to android.
So I tried re-installing it(wiped everything), still couldn't boot to android. At this point, I think my phone is actually soft bricked?
I tried to go back and install ARHD 41.0 instead, but it didn't work either. I tried different stock roms and using HTC RUU, all efforts failed.
I remember this recurring error: set_metadata_recursive: some changes failed
My phone is currently running a guru reset rom. I rooted it, but permissions are acting weird.
Most apps or functions which require root access don't work properly.
In other cases, even though I have granted root access to some apps, once I re-open them, request for root access procs again.
Please help!

theplaypig said:
First of all, my HTC One is unlocked and s-off.
Originally I was using 4.4.2 stock rom, then I started using ARHD 41.0.
It worked very well at first, but when I added a few mods(xposed), I experienced terrible battery drain.
I'm not sure if the mods caused this, or because I just spent a lot more time using my phone.
Anyway, after a while I tried upgrading to the latest ARHD 51.0, but it didn't work, I couldn't boot to android.
So I tried re-installing it(wiped everything), still couldn't boot to android. At this point, I think my phone is actually soft bricked?
I tried to go back and install ARHD 41.0 instead, but it didn't work either. I tried different stock roms and using HTC RUU, all efforts failed.
I remember this recurring error: set_metadata_recursive: some changes failed
My phone is currently running a guru reset rom. I rooted it, but permissions are acting weird.
Most apps or functions which require root access don't work properly.
In other cases, even though I have granted root access to some apps, once I re-open them, request for root access procs again.
Please help!
Click to expand...
Click to collapse
post the output of "fastboot getvar all"; remove S/N & IMEI before posting
and please mention which recovery(with version) you are using
you should use TWRP 2.6.3.3 to flash KitKat 4.4 ROMs

theplaypig said:
I remember this recurring error: set_metadata_recursive: some changes failed
Click to expand...
Click to collapse
It's probably a recovery problem, use TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure to check MD5 of the download cause that site does not play nice with download managers

Error: no such tool
Thanks for replying, I didn't realize the issue was so insignificant.
ARHD thread did warn to use TWRP, but I thought it was just OP's preference.
My phone is now successfully running the latest ARHD rom and TWRP recovery.
But as I was setting up my phone, I came across another recurring issue(which started occurring after I messed up my rom in the first place).
When I select reboot in xposed installer, this error message appears: reboot: no such tool
Some threads mention updating busybox and possible errors regarding adb drivers and commands.
Since I have no idea what busybox is, I just downloaded it from play store and installed it. Issue persists.
Any help will be appreciated

theplaypig said:
Thanks for replying, I didn't realize the issue was so insignificant.
ARHD thread did warn to use TWRP, but I thought it was just OP's preference.
My phone is now successfully running the latest ARHD rom and TWRP recovery.
But as I was setting up my phone, I came across another recurring issue(which started occurring after I messed up my rom in the first place).
When I select reboot in xposed installer, this error message appears: reboot: no such tool
Some threads mention updating busybox and possible errors regarding adb drivers and commands.
Since I have no idea what busybox is, I just downloaded it from play store and installed it. Issue persists.
Any help will be appreciated
Click to expand...
Click to collapse
Use "soft reboot"
Sent from my HTC One using Tapatalk

nkk71 said:
Use "soft reboot"
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Soft reboot works, but aren't I supposed to fix it? Kinda OCD can't stand these small bugs, must fix please help!
P.S
This is like the final issue, want to fix it and make a perfect nandroid backup!

theplaypig said:
Soft reboot works, but aren't I supposed to fix it? Kinda OCD can't stand these small bugs, must fix please help!
P.S
This is like the final issue, want to fix it and make a perfect nandroid backup!
Click to expand...
Click to collapse
Perfectly normal, nothing to fix.
{
"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"
}
Sent from my HTC One using Tapatalk

Is it a bug?
nkk71 said:
Perfectly normal, nothing to fix.View attachment 2580435
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
But this function used to work when I was still using ARHD 41.0. If this is normal, is it a bug?

theplaypig said:
But this function used to work when I was still using ARHD 41.0. If this is normal, is it a bug?
Click to expand...
Click to collapse
Don't remember reboot ever working, only soft-reboot. (maybe before it didn't show this error, but it certainly didn't reboot)
Can't really say if it's a bug, maybe it works / is needed on other devices. But for us, soft reboot does exactly what needed.
Sent from my HTC One using Tapatalk

nkk71 said:
Don't remember reboot ever working, only soft-reboot. (maybe before it didn't show this error, but it certainly didn't reboot)
Can't really say if it's a bug, maybe it works / is needed on other devices. But for us, soft reboot does exactly what needed.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I remember at one point the error message used to be reboot: not permitted or something similiar.
From what I recall, it worked at first. Then I messed up my rom, it became not permitted. Now it's no such tool.
I guess I'll have to leave it for now, but maybe I should report this issue to the creator of Xposed Installer?
Isn't it weird that such a fundamental function doesn't work on a popular smart phone like HTC One? (Or that no one tried to fix this?)

theplaypig said:
I remember at one point the error message used to be reboot: not permitted or something similiar.
From what I recall, it worked at first. Then I messed up my rom, it became not permitted. Now it's no such tool.
I guess I'll have to leave it for now, but maybe I should report this issue to the creator of Exposed Installer?
Isn't it weird that such a fundamental function doesn't work on a popular smart phone like HTC One? (Or that no one tried to fix this?)
Click to expand...
Click to collapse
Ah, yes that was it: reboot: not permitted
I never really looked into why the reboot option doesn't, as only a soft-reboot is required to get the mods working (and is faster than a full reboot anyway)
Good hunting

nkk71 said:
Ah, yes that was it: reboot: not permitted
I never really looked into why the reboot option doesn't, as only a soft-reboot is required to get the mods working (and is faster than a full reboot anyway)
Good hunting
Click to expand...
Click to collapse
I just remembered when I tried fixing this with adb commands from another thread, cmd shows error: closed.
adb devices works properly, but adb shell has the same error message.

[Q] Xposed causes WiFi to stop working...

So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TPR like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3

Xposed causes WiFi to stop working... fix
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH

prashantsingh480 said:
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
No luck....
{
"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"
}
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk

Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk[/QUOTE]
first uninstall the xposed installer & then check if it catches the wifi network or not ..... :good::good:

Deleted

The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk

tnp9008 said:
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
Click to expand...
Click to collapse
NOW ,root your moto X by root master .
& check if it catches the networks or not if it catches.
the install xposed installer v7.0 not the latest (v7.1).
then check ...
SHOULD WORK ......
BEST OF LUCK....

Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure

rignfool said:
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
Click to expand...
Click to collapse
I know my system partition is read only. The only way to have read/write is to unlock my bootloader which I could do but I don't want to lose my warranty so that's not an option right now. When the warranty runs out I plan to get an unlock code and obtain full root with system read/write but that's a ways off. I don't have custom recovery installed so I can't flash manually in recovery; the root access I gain is temporary. I have to re-root with Towel Pie Root after every full reboot. From what I read in the TPR thread people have had success using xposed on the Moto X like I'm doing, but for some reason it borks my WiFi.
Update: After digging through the TPR thread it looks like this is a somewhat common issue with TPR + 4.4.3 + Xposed. The TPR dev is looking into the issue.

Bootloop after installing Xposed via Magisk

I've got the Google Fi variant of the Moto X4 (XT1900-1). It's running stock build OPW28.46-18 (Android 8.1). TWRP 3.2.1-1. I was able to install the latest Magisk no problem and I have working root access. My issue arises when I try to install the Magisk variant of Xposed Framework. When I do this and reboot, the phone seemingly gets caught in a bootloop. I've let it sit for 15-20 minutes to see if it would recover and it does not. To exit the loop, I reboot to fastboot then to TWRP and flash a ZIP that allows me to uninstall Magisk modules right from TWRP. Reboot and phone works fine.
I've tried both versions of the Xposed Framework in the Magisk downloads section (the smart version that automatically chooses the proper framework, and the explicit SDK 27 version), as well as downloaded the ZIP and tried to install it from TWRP. Similar result in all cases. I have only tried the "systemless" Xposed that works with Magisk thus far.
Has anyone else run into and dealt with this issue, or have any suggestions? I'd really like to get Xposed working so I can get XPrivacyLua going and switch over to using this phone as my daily driver.

how are you flashing Xposed? from Recovery or magisk?

abhi212b said:
how are you flashing Xposed? from Recovery or magisk?
Click to expand...
Click to collapse
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.

I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.

Neffy27 said:
I didn't think there was a version of xposed compatible with Oreo yet but I could be wrong. This would be a better question in Xposed Section of XDA.
Click to expand...
Click to collapse
There's been a beta version for Oreo 8.0/8.1 since maybe January (t's on beta version 3 now I think). I'd tried it on my OnePlus 3 with success. I thought maybe it was a Moto X4 issue and I might as well check here first to see if anyone else with this phone had already run into this and fixed it. I'll go ahead and ask the question in the Xposed section of the forum. Thanks!

Seems the OP of this thread has Xposed working: https://forum.xda-developers.com/moto-x4/help/oreo-magisk-xposed-modules-reboot-t3745612 - Maybe they could help.

Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for posting that

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).

I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.

dcdruck1117 said:
Thanks for the info! Perhaps it's an incompatibility with the stock ROM then, as that's what I'm using. I haven't flashed a different ROM nor GApps on this phone yet (mostly out of fear of not being able to go back to stock with seemingly no official factory images floating around).
Click to expand...
Click to collapse
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!

solara1973 said:
I got bootloops too with Magisk and systemless Xposed. I had pattern password set, so I couldn't get TWRP full access to the data to remove Xposed, so I had to delete all my data.
From what I read, Magisk and systemless xposed will not pass SafetyNet so Android pay won't work.
Click to expand...
Click to collapse
Thanks for the info. You're correct about SafetyNet and Android Pay; I gave up on Android Pay years ago for that reason, because Xposed is too important to me to give it up. Perhaps I'll try starting from scratch again with this phone. I'm hesitant to flash ROMs on this phone, stock or otherwise, because of the scarcity of factory images available should something go terribly wrong..
abhi212b said:
No.. The stock rom is compatible! I simply flashed magisk and then xposed v90... The latest ones! Yeah safety net is broken! But there is a workaround! It is disable the xposed module from magisk and reboot.. Nd then you can use android pay... Once you are done! Activate the module.. And reboot!
Click to expand...
Click to collapse
Thank you. I think I'll try to start over and see if I can get it to work. Or maybe I will try using the regular version of Xposed (not the Magisk version).
If you know of a repository of factory images for the Android One version, that would be helpful. I'm finding some images for the retail version but not much love for the A1 version.
Edit: I just found this post which seems like it may contain what I'm looking for, "Latest Project Fi Firmware (Android 8.1)": https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

I flashed back to stock using the files from the link in my previous post. The weird thing there is that SafetyNet fails immediately now, clearly some side effect of flashing back the stock images. Anyway, I again installed TWRP, then Magisk, then Xposed, and again ran into the same boot loop. I don't know what else to try other than to wait for maybe a new Xposed beta, or maybe try an even older Oreo build on this phone and see how that works.
I've run Xposed (and more recently, Magisk+Xposed) on every Android device I've owned since Xposed has been in existence, and this is the first phone to ever give me trouble.

abhi212b said:
Even i had working xposed!
But did not face bootloops!
The way i do it is!
I flash it when i am flashing gapps!
So...flash rom... Flash twrp... Reboot recovery.. . Flash gapps! Flash magisk... Flash xposed...boot to system!
Click to expand...
Click to collapse
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.

AvenidaDelGato said:
Which Stock ROM version are you using? Xposed worked for me in Oreo 8.0, but has not worked since upgrading to 8.1. I get the same bootloop issue on OPW28.2.
Click to expand...
Click to collapse
Thank you, that's good to know because I'm also on 8.1, so it sounds plausible that it's not just me, but a larger compatibility issue between Xposed and 8.1. on this phone.

Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!

dcdruck1117 said:
Just an update, I ended up flashing a factory 8.0 ROM via fastboot and, while it still fails SafetyNet (CTS Profile Mismatch) for some reason, I was able to get Xposed running and finally start using the phone as my primary device. So it is likely to be an 8.1 compatibility issue on this device that was giving me trouble before. Now hopefully I can find a version to flash that will pass SafetyNet, but until then, this will suffice. Thanks for everyone's help!
Click to expand...
Click to collapse
I've been putting off unlocking bootloader due to my recent concerns with these ota patches being released.
If safetynet fails, what can you not use besides Pay? It's to my understanding safetynet is now being incorporated to several applications and failing, will result in a sometimes inoperable app altogether?

dcdruck1117 said:
I've tried both: installing via Magisk Manager as well as flashing zip in TWRP (xposed-v90.2-sdk27-beta3-topjohnwu.zip). Similar results in both cases.
Click to expand...
Click to collapse
Use EdXposed, works for me, and pass Safetynet
{
"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"
}

Blind app is detecting root with Magisk Hide

I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

mew1033 said:
I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!
Click to expand...
Click to collapse
Did you ever figure it out?

Just. Tried too. For test lol.
Didn't work for me.
I'm having issue with spay for gear 3.
If you can figure it out and maybe we can also both our issues

It suddenly started working for me today...

I was having this issue too. I eventually got so frustrated, I unrooted my device, relocked the bootloader, and did a factory reset. Still thinks I'm rooted, even though I'm completely factory. I think they get some unique device identifier and block your device server-side
If anyone figures it out, please let me know.
A bit of an annoying workaround: if you can make a comment with a different phone, and you get a notification telling you someone replied, you can open the app by tapping on the notification. However, it won't work if you open it by tapping on the icon

Any update?
Tried a whole bunch of things to hide Magisk. Blind just doesn't work.

Works!
Looks like Blind is detecting if your bootloader is unlocked. I installed this Magisk module called "SafetyPatch", which prevents apps from detecting if your bootloader is unlocked. That fixed it for me!

Darn, tried installing SafetyPatch, but still no luck
I suspect my phone has been blacklisted or something

I had checked logcat and it seems that blind was using com.liapp.lockincomp to detect root and display the alert. after hiding magisk manager and using magisk hide on blind it still didn't work even after clearing data/reinstalling the app. after a few days it magically started working again. guess they blacklist devices for x amount of time after they detect root.

I had Blind 2.5 and Magisk 17 working together. About two weeks ago I updated both and it stopped working. Anyone using Blind 2.6 with Magisk 18? I think my device got banned - downgrading Blind to 2.5 didn't help.

{
"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"
}
Seeing the issue on Blind 2.6.4 with Magisk Hide Enabled. Any other suggestions on a workaround?

Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.

babelus said:
Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.
Click to expand...
Click to collapse
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?

1nv1n said:
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?
Click to expand...
Click to collapse
Correct, uninstall Blind, wait a week, reinstall from backup of APK (TitaniumBackup). I can share the APK, but you shouldn't trust me.

I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.

1nv1n said:
I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.
Click to expand...
Click to collapse
Thanks for sharing, this worked for me
(Rooted stock Moto Z2 Force with Oreo)

Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?

1nv1n said:
Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?
Click to expand...
Click to collapse
I can confirm my workaround using the old version of Blind stopped working. New version works for a day or two after installation, then it detects root and I have to uninstall and wait for the ban to expire.

How many days does the ban last for?