Make sure your carrier supports and allows the features.
This mod is useful if you have a dual SIM or unbranded device that does not have VoLTE, Video Calling and WiFi Calling features in your call settings. Results may vary and I was successful in activating all my favorite T-Mobile features on a HTC__626 Dual SIM device.
I recommend using FX File Manager and FX text edit apps. You going to need the following.
Latest release of the ViperU12+ Magisk Rom Module
File manager app
Text editor app
RAR app
default.xml from your device's dir /system/customize/MNS
HTC__***_default.xml from your device's dir /system/customize/MNS
Note: HTC__***_default.xml is based on your CID
Using a file manager app copy over your default.xml and htc__***_default.xml files to your downloads folder. Then modify the values from false to true using a text file editor app.
Code:
<item name="carrier_volte_available_bool" type="boolean">true</item>
<item name="carrier_vt_available_bool" type="boolean">true</item>
<item name="carrier_wfc_ims_available_bool" type="boolean">true</item>
<item name="customer_ss_over_ut" type="integer">0</item>
<item name="carrier_htc_volte_ui_checked_bool" type="boolean">true</item>
<item name="carrier_htc_show_volte_ui_bool" type="boolean">true</item>
Make a folder called "MNS" and place your modded xml files inside the MNS folder. Then copy over the MNS folder with it's contents using RAR to the ViperU12+ magisk rom module zip dir /system/customize/MNS. Just flash your modded ViperU12+ magisk rom module like you normally would in TWRP or Magisk manager.
Congrats should now have access to the VoLTE, Video Calling and WiFi Calling settings. Most importantly this mod does not modify the system partition thanks to magisk.
I have included my modded XML files in case anyone with HTC__626 wants them. Just unzip it and copy the contents to the ViperU12+ Magisk Rom Module using RAR. Additionally I have provided optional files that will revert the 4G signal icon to the standard LTE signal icon. Simply delete the ACC folder if you want the 4G signal icon instead.
{
"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"
}
HTC__626 users I will also include my magisk module HTC_U12+_HTC__626_Enable_VoLTE_Video_Calling_&_WiFi Calling.zip (30.9 KB) to provide a simple solution. This will enable all the settings plus change your 4G signal icon to the standard LTE signal icon. This may prove to be useful when Android Pie is finally available and you won't have to compromise these features while Team Venom takes its time to properly develop it's Android Pie Version.
Installation:
Flash in TWRP Recovery or
Flash in Magisk Manager
General Info:
To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
Discussion
This magisk module is untested and highly experiemental. I don't have this device [HTC U11 Dual Sim] so results may vary. Let me know if it works otherwise. If successful it will enable VoLTE and Wifi Calling.
Installation:
Flash in TWRP Recovery or
Flash in Magisk Manager
General Info:
To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
Hi @8bitbang
U11 dual sim Can I use this way on device.
I tried all the ways under the subject of u11 but I could not succeed.
I would be grateful if you show me a way
Thanks.
Derepinar said:
Hi @8bitbang
U11 dual sim Can I use this way on device.
I tried all the ways under the subject of u11 but I could not succeed.
I would be grateful if you show me a way
Thanks.
Click to expand...
Click to collapse
Follow the steps and post the original xml files. It might be possible, I could make you a magisk module and let me know if it works
8bitbang said:
Follow the steps and post the original xml files. It might be possible, I could make you a magisk module and let me know if it works
Click to expand...
Click to collapse
Hi @8bitbang
Viper 2.3 I'm using
its current cid HTC__621 Asia Taiwan Dual sim.
carrier Vodafone tr
Mcc 286
Mnc 02
Thank you very much for your help and support.
Derepinar said:
Hi @8bitbang
Viper 2.3 I'm using
its current cid HTC__621 Asia Taiwan Dual sim.
carrier Vodafone tr
Mcc 286
Mnc 02
Thank you very much for your help and support.
Click to expand...
Click to collapse
Try out the Magisk Module I posted
8bitbang said:
Try out the Magisk Module I posted
Click to expand...
Click to collapse
unfortunately failed.
thank you anyway.
Derepinar said:
unfortunately failed.
thank you anyway.
Click to expand...
Click to collapse
Wouldn't install or the module didn't enable features?
8bitbang said:
Wouldn't install or the module didn't enable features?
Click to expand...
Click to collapse
module properties not enabled.
8bitbang said:
This magisk module is untested and highly experiemental. I don't have this device [HTC U11 Dual Sim] so results may vary. Let me know if it works otherwise. If successful it will enable VoLTE and Wifi Calling.
Installation:
Flash in TWRP Recovery or
Flash in Magisk Manager
General Info:
To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
Click to expand...
Click to collapse
hi
https://forum.xda-developers.com/u11/themes/how-to-enable-volte-wifi-calling-htc-t3838417
I'm following the path under the subject
then I'm installing your module
i am failing again
Merry Christmas
Hello, maybe someone can help me, I'm trying to enable VoLTE and VoWiFi on my HTC U11+, non-carrier version,
European Dual-SIM version, CID HTC__034, with unlocked bootloader, and rooted by Magisk patched boot image,
for my carrier Orange Romania, 226 10. The SIM card is already provisioned, tested in another phone and worked flawlessly.
I've already tried everything that I saw on this thread, modified in /system/customize/acc the default.xml file, but also HTC__034.xml,
with both files but also with each one by itself. Also tried to add my carrier config file in in /system/customize/mns, 22610.xml, based on 226.xml
which was already present there, and added it to mns_map.xml. So far nothing worked, I get the toggles in Settings->Call, but neither
functionality works. Also debugged with Network Signal Guru, and I don't see the ims APN registering.
I see here in the opening post the LlabTooFeR method is mentioned, but the only the changes to /system/customize/acc are suggested further,
then are the changes in /system/customize/mns necessary or not ? And the xml parameters to change are actually different between LlabTooFeR and OP,
then which one are correct ?
But where are the actual apn settings for the carrier network ?, in which file.
For the people that succeeded, was the ims APN added automatically by the phone or did you add it yourself ?
Did anyone succeeded for an Orange carrier in any country ?
Thank you for any suggestions or tips.
Hi @8bitbang i have HTC u11 Dual Sim with Viper Rom on it, shall i just flash that magisk module which you posted or do i have to edit the files from file explorer ?
EDIT : Tried flashing mod on dual sim it doesnt work.
naughty6t9 said:
Hi @8bitbang i have HTC u11 Dual Sim with Viper Rom on it, shall i just flash that magisk module which you posted or do i have to edit the files from file explorer ?
EDIT : Tried flashing mod on dual sim it doesnt work.
Click to expand...
Click to collapse
If you follow the tutorial and post the files, I could make a magisk module out of them. Then you can test it if you want, theres not really a way to make this universal since your phone generates these files when you first setup your device and they contain your carrier settings. Otherwise adding your modified files to the viper rom before flashing it should achieve the same results.
8bitbang said:
If you follow the tutorial and post the files, I could make a magisk module out of them. Then you can test it if you want, theres not really a way to make this universal since your phone generates these files when you first setup your device and they contain your carrier settings. Otherwise adding your modified files to the viper rom before flashing it should achieve the same results.
Click to expand...
Click to collapse
Hi @8bitbang i tried to edit the lines but no luck, also tried
https://forum.xda-developers.com/u11/themes/how-to-enable-volte-wifi-calling-htc-t3838417 this link and
https://forum.xda-developers.com/showpost.php?p=75427506&postcount=6986 this link,
i think i am doing something wrong, i even tried dirty flashing the ROM of US unlocked, Default and Dual Sim still no luck. once i got that VOLTE icon but calling didnt work and it vanished.
i am in Australia on Telstra network, using unlocked dual sim European HTC u11 with FW 2.33.401.19 and Viper Rom 2.3.
i have attached my System/Customize/ ACC & MNS folders which i have edit, and a screen shot of *#*#4363#*#* screen.
should i dirty flash the rom before trying your magisk module.
thanks in advance.
Hi all , I am relative to new Rooting and Custom Roms. I am not sure what i am going to ask does even make a sense or feasible .
I have HTC U11 UAE variant which is basically the same as Indian Variant (6GB , 128 GB) and Indian variant is enabled for VOLTE and WIFI Calling. If i copy MNS folder from Indian HTC U11 and paste in UAE variant. Can this work ?
Finally Volte working on HTC U11
8bitbang said:
This magisk module is untested and highly experiemental. I don't have this device [HTC U11 Dual Sim] so results may vary. Let me know if it works otherwise. If successful it will enable VoLTE and Wifi Calling.
Installation:
Flash in TWRP Recovery or
Flash in Magisk Manager
General Info:
To Disable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
To Enable The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
To Uninstall The Module, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
Click to expand...
Click to collapse
Thanks Bro to your efforts Finally I was able to get VOLTE working on HTC U11 J15 unlocked Version by following these steps.
1.) Downloaded attachment provided for HTC U11 in 2nd post.
2.) Extracted the Zip and copied default.xml files from MNS & ACC folder and pasted copied files into device MNS & ACC folder situated in system/customize.
3.) Delete all other files except default.xml from MNS & ACC folder.
4.) Reboot the device and it's done
I tested on JIO network in India and it worked flawlessly.
Will this work with US unlocked BS_001 model? In the system/MNS/default.xml folder of my phone I don't see where it lists the actual model or CID of my phone.
Some countries like South Korea needs more task. If your country is one of them and U12 is not officially released, you need to do some tasks with QPSD. Just open EFS ports with terminal command, connect to PC and run only QPST EFS explorer, and patch files inside of EFS with files from officially released SD845 devices. This is found by NOT ME, but people who found is active in members-only site('엘리자' in Naver htc users cafe in South Korea; not closed to being a member, but supports only Korean language).
Hey all, but especially hey @gnabtib8.
I've been looking for solutions for this for a little while... I've got a HTC__034 Europe Dual Sim.
Is it relatively safe for me to grab the magisk module zip from the OP and modify it with my own XML files to achieve the desired result?
has anyone else tried this and resulted in failure?
EDIT:
Forgot to ask, will the existing zip work with the latest Magisk version?
Kyuubi10 said:
Hey all, but especially hey @gnabtib8.
I've been looking for solutions for this for a little while... I've got a HTC__034 Europe Dual Sim.
Is it relatively safe for me to grab the magisk module zip from the OP and modify it with my own XML files to achieve the desired result?
has anyone else tried this and resulted in failure?
EDIT:
Forgot to ask, will the existing zip work with the latest Magisk version?
Click to expand...
Click to collapse
Hey @gnabtib8 and @Kyuubi10:
I am on a Dual SIM variant (htc_imedugl: 2Q5510000 with SuperCID). This is a Taiwan variant, but I flashed the European firmware version on it to 2.55.401.1 as I was having zero luck with getting any ROMs to install on the Taiwan Firmware 2.50.709.3
The .401 Euro firmware will not allow LTE or Wifi Calling to work here in the USA. I flashed the zip here in TWRP and rebooted and still did not have any luck....
@gnabtib8 and @Kyuubi10:
***UPDATE***!!! I got VoLTE/IMS/WiFi calling to work!!!!!! If anyone is struggling still, I'm happy to help!
THANKS @gnabtib8 !!!!!!!!!! ?????????
Related
Hi everyone
DISCLAIMER :
I'm not responsible for any damage, brick, silent alarm or nuclear attack on your phone !
Be careful and make a backup before if you're afraid !
Click to expand...
Click to collapse
TL;DR
If your hotspot doesn't work and you don't know why, try this, it's not magical, but it may work
Click to expand...
Click to collapse
Here's the problem : my provider allow me to use hotspot, but my phone don't.
I managed to resolve this thanks to this thread.
But I thought a little flashable zip could help some others people
So i made one, originally for my Oukitel K6000 Pro, but i thinks it may apply for most of android 6+ phones (maybe 5+ ... anyone can confirm ?)
What this script does :
- Edit or add net.tethering.noprovisioning=true in build.prop
- Enable init.d script (without busybox)
- Do `settings put global tether_dun_required 0` on each start with init.d script
- Add ',dun' to your enabled APNs
Required :
- Your phone
- Your head
- A backup of your phone (just in case)
- An USB cable
- A recovery (tested only on TWRP but CWM should work no problem)
Installation :
- Push zip to phone
- Reboot phone to recovery
- Flash tetherByPass.zip
- Reboot
- Try & enjoy
You shouldn't need to clean cache/dalvik, or mount system (or data) before flashing.
Everything is done in script, but feel free to do it if you want =)
Known bug :
- Doesn't work on phones which doesn't show tethering menu (like Sprint galaxy note 4) yet ...
Corrected in v0.92 :
- settings put cmd in init.d script doesn't work on some devices
Corrected in v0.91 :
- telephony.db causing FC of com.android.phone at restart.
If you have this problem, via adb shell do "rm /data/data/com.android.providers.telephony/databases/telephony.db"
You don't even need to restart your phone, it should rebuild the database itself.
I know why it does this, i'm actually trying to correct this
Changelog :
v0.92:
- Fixed init.d script : some devices didn't keep settings information
- Added uninstaller
- Deleted GDrive download link
- Added files to thread
v0.91:
- fixed com.android.phone FC after reboot
v0.9:
- choose good sqlite3-static by arch
- add ',dun' to APNs via sqlite3 to telephony.db
v0.8:
- updated universal mount method using fstab
- build.prop is now correctly edited
- /tmp is now correctly cleaned (in case of multi zip flashing)
v0.5:
- Initial release
Download :
From git : https://github.com/storm1er/oukitelK6000Pro-tetherLimitByPass/raw/master/zippedInstaller/
Fork me on Github : https://github.com/storm1er/oukitelK6000Pro-tetherLimitByPass
Feel free to copy / edit my mod, pull requesting, issues etc ... as long as it has my name on it ...
Credits :
Build.prop editor script from tommytomatoe
Init.d enabler by ALEXNDR (_alexndr @ XDA)
this thread for most things my script does
So does it work? Lol has anyone tried?
Sent from my SM-G900T using Tapatalk
Please give me another link to this script to try it?
github sucks.
bstylz911 said:
So does it work? Lol has anyone tried?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Well, it pretty must apply everything that has been done in this thread.
Originally for Nexus 6, those things has been applied for a lot of different phone. Some worked, some don't.
I put every manipulation I found in this little script.
There is no big modification (only init.d enabler, which is already enable on almost every phone which has a custom recovery). So I didn't make an uninstaller, Should I ?
anees02 said:
Please give me another link to this script to try it?
github sucks.
Click to expand...
Click to collapse
This is a direct link
If it does not work, here's another just for you click here
stormPremier said:
Well, it pretty must apply everything that has been done in this thread.
Originally for Nexus 6, those things has been applied for a lot of different phone. Some worked, some don't.
I put every manipulation I found in this little script.
There is no big modification (only init.d enabler, which is already enable on almost every phone which has a custom recovery). So I didn't make an uninstaller, Should I ?
This is a direct link
If it does not work, here's another just for you [emoji14] click here
Click to expand...
Click to collapse
Thank you for the link.
I tried it on my SM-N910P (Sprint galaxy note 4) with MM 6.0.1 and systemless root supersu 2.78 but it didn't work.
I flashed it from twrp recovery.
anees02 said:
Thank you for the link.
I tried it on my SM-N910P (Sprint galaxy note 4) with MM 6.0.1 and systemless root supersu 2.78 but it didn't work.
I flashed it from twrp recovery.
Click to expand...
Click to collapse
Hmm, ok let's check some stuff before look deeper :
- In your build.prop you should find "net.tethering.noprovisioning", probably at the end - confirm ?
- It should be followed by "1" or "true" - confirm ?
- Then via ADB, do "settings get global tether_dun_required", it should give you a "0" (zero) - confirm ?
If those three things are ok, we didn't find a solution for you phone yet.
Maybe try to add ",dun" in your APN (do you know how to ?) but my script should allow your phone to bypass this.
EDIT : If you don't know, you can follow this : http://techbeasts.com/how-to-enable-wifi-tethering-on-sprint-galaxy-note-4-note-edge/
Tell me if it works. I'm looking for inject ",dun" rule in APN through my script
stormPremier said:
Hmm, ok let's check some stuff before look deeper :
- In your build.prop you should find "net.tethering.noprovisioning", probably at the end - confirm ?
- It should be followed by "1" or "true" - confirm ?
- Then via ADB, do "settings get global tether_dun_required", it should give you a "0" (zero) - confirm ?
If those three things are ok, we didn't find a solution for you phone yet.
Maybe try to add ",dun" in your APN (do you know how to ?) but my script should allow your phone to bypass this.
EDIT : If you don't know, you can follow this : http://techbeasts.com/how-to-enable-wifi-tethering-on-sprint-galaxy-note-4-note-edge/
Tell me if it works. I'm looking for inject ",dun" rule in APN through my script
Click to expand...
Click to collapse
1) net.tethering.noprovisioning in build.prop (not available)
2) Using adb shell settings get global tether_dun_required gives me "0"
3)Adding ,dun in APN doesn't work for me because I am outside USA and I use XAS csc instead of SPR and there is no data in my APN settings.
update: I added (net.tethering.noprovisioning=1 or true) manually to buid.prop
but didn't work.
Update to v0.8:
- updated universal mount method using fstab
- build.prop is now correctly edited
- /tmp is now correctly cleaned (in case of multi zip flashing)
anees02 said:
1) net.tethering.noprovisioning in build.prop (not available)
2) Using adb shell settings get global tether_dun_required gives me "0"
3)Adding ,dun in APN doesn't work for me because I am outside USA and I use XAS csc instead of SPR and there is no data in my APN settings.
update: I added (net.tethering.noprovisioning=1 or true) manually to buid.prop
but didn't work.
Click to expand...
Click to collapse
You could try again but I don't think it will change anything, I'm looking for a solution about your APN.
I didn't even knew there were different kind of APN :/
Are you sure this is just "Secure APN" where you can't edit them ?
EDIT : updates
v0.9:
- choose good sqlite3-static by arch
- add ',dun' to APNs via sqlite3 to telephony.db
v0.91:
- fixed com.android.phone FC after reboot
EDIT : @anees02 : You should re-try the last version. Even for single CSC roms there is APN settings. But you just can't see nor edit them.
stormPremier said:
Update to v0.8:
- updated universal mount method using fstab
- build.prop is now correctly edited
- /tmp is now correctly cleaned (in case of multi zip flashing)
You could try again but I don't think it will change anything, I'm looking for a solution about your APN.
I didn't even knew there were different kind of APN :/
Are you sure this is just "Secure APN" where you can't edit them ?
EDIT : updates
v0.9:
- choose good sqlite3-static by arch
- add ',dun' to APNs via sqlite3 to telephony.db
v0.91:
- fixed com.android.phone FC after reboot
EDIT : @anees02 : You should re-try the last version. Even for single CSC roms there is APN settings. But you just can't see nor edit them.
Click to expand...
Click to collapse
I tried it with the same result.
Does it require any cutom kernel or with stock enforcing kernel it works?
I attached the screenshot and there is no tethering option
{
"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"
}
anees02 said:
I tried it with the same result.
Does it require any cutom kernel or with stock enforcing kernel it works?
I attached the screenshot and there is no tethering option
[picture]
Click to expand...
Click to collapse
huh, weird. Try those methods and tell me if it works : http://www.droidviews.com/enable-wifi-tethering-on-sprint-galaxy-s6-s6-edge-and-note-4-on-lollipop/
EDIT : And no, you don't need custom kernel nor custom rom
stormPremier said:
huh, weird. Try those methods and tell me if it works : http://www.droidviews.com/enable-wifi-tethering-on-sprint-galaxy-s6-s6-edge-and-note-4-on-lollipop/
EDIT : And no, you don't need custom kernel nor custom rom
Click to expand...
Click to collapse
I tried this before and tried it again.
The only thing that works for me is the mods which some developers do in services.jar and makes wifi Hotspot works.
When I used Galaxy Tools GT3.1.5 by idone the WiFi Hotspot seems to work but I couldn't see tethering and Hotspot in settings.
I have to tap on hotspot settings in GT snd the hotspot launches.
But under settings there's no thing tells hotspot.
anees02 said:
I tried this before and tried it again.
The only thing that works for me is the mods which some developers do in services.jar and makes wifi Hotspot works.
When I used Galaxy Tools GT3.1.5 by idone the WiFi Hotspot seems to work but I couldn't see tethering and Hotspot in settings.
I have to tap on hotspot settings in GT snd the hotspot launches.
But under settings there's no thing tells hotspot.
Click to expand...
Click to collapse
So the menu doesn't exist in your phone ... I did some research and ... it's kinda weird :|
My mod aim to delete provider provisioning, but I don't know how to re-enable your menu and I thinks that only an app (or service) can use your wifi :/
Sooooo my mod is useless for you ... I will to enhance my mod so phone like yours can share their connection. But not for now.
Updated OP
stormPremier said:
So the menu doesn't exist in your phone ... I did some research and ... it's kinda weird :|
My mod aim to delete provider provisioning, but I don't know how to re-enable your menu and I thinks that only an app (or service) can use your wifi :/
Sooooo my mod is useless for you ... I will to enhance my mod so phone like yours can share their connection. But not for now.
Updated OP
Click to expand...
Click to collapse
If you want any help or any files from my device I am ready just pm me.
@stormPremier
I already make workaround solution to get WifiHotspot, instead of the option in the settings I used nova launcher activities to make a shortcut in my home page and the WiFi Hotspot started successfully but when I connect from any device it stucks on (obtaining IP address).
Is there any fix for this?
anees02 said:
If you want any help or any files from my device I am ready just pm me.
Click to expand...
Click to collapse
Could be great =) PM with links you thinks may help. Or open issue request on GitHub
(You can send some logs, could be useful)
anees02 said:
@stormPremier
I already make workaround solution to get WifiHotspot, instead of the option in the settings I used nova launcher activities to make a shortcut in my home page and the WiFi Hotspot started successfully but when I connect from any device it stucks on (obtaining IP address).
Is there any fix for this?
Click to expand...
Click to collapse
Don't know yet, But we can find out why
I'm working on this mod too, so update will not be fast as I want.
EDIT:
Updated to v0.92, init.d update & uninstaller added
does this work with nexus 5x? I saw mention of it in a 5x topic, but not sure if you actually tested/used it on a nexus 5x or were just kind of advertising about your work
x000x said:
does this work with nexus 5x? I saw mention of it in a 5x topic, but not sure if you actually tested/used it on a nexus 5x or were just kind of advertising about your work
Click to expand...
Click to collapse
Well It should work. But for some people the problem still remains. It seems that android 7.* ignore net.tethering.noprovisioning=true in build prop.
As there is an uninstaller, you cans till try and tell me if it works.
And, as allways, do a backup in case somethings goes wrong
Will this mod work on the note 4 910t2 4.4.4 kk fw?
roasq12 said:
Will this mod work on the note 4 910t2 4.4.4 kk fw?
Click to expand...
Click to collapse
It should work, try it anyway
If it doesn't work, just use uninstaller.zip to clean all the modifications the mod made.
And, as always, do a backup before install in case something goes wrong
Thank you very much.!!!!!
Working good on ulephone power 3 7.1.1 V35
see you
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
{
"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"
}
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Complete package with everything needed in the guide for the lazy:
https://mega.nz/#!R18XRZQB!pgGx2LgNV8aqfwhsutmUnC4jay-FTGVR3-a9r3TJaEA
Martan404 said:
Finally I can play again since they added the SafetyNet check! It's been way too long.
Worked perfectly on my Galaxy S5! I'm using the Resurrection Remix KLTE 6.0 for my Galaxy S5 so it came with it's own root. I just searched Root in settings, disabled it, flashed the unroot zip and then I was unrooted. Except for that everything worked the way you described! I forgot to reboot after Magisk Hide so I unrooted and reflashed Magisk but I'm not sure that was needed to be honest. Is SafetyNet Checker really needed? Magisk Manager also has a SafteyNet checker.
When I get more time I will do a backup and flash the 7.1.1 rom too and test if it works.
Click to expand...
Click to collapse
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
xJovs said:
There 'is' a Safetynet checker in Magisk Manager, however it will always say 'CTS Profile error', while SafetyNet Checker will say if its either a CTS error, Response Validation error, Play Store error etc. Maybe it's just a bug in Magisk Manager but if it gets fixed; I'll remove SafetyNet Checker from the tutorial.
Click to expand...
Click to collapse
Can confirm that this works on 7.1.1 roms too! As I mentioned in my other post I use the Resurrection Remix rom.
By the way, you could mention that instead of using root browser to change permissions you could skip that step all together and just add the modification to Kernel Auditor. And instead of rebooting to test it you can just click the "Permissions" addition to execute the script right away just to make sure it works and then do a reboot to confirm.
Thank you so much. it worked
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
naveenfre said:
help plse plse give steps by step for 7.1.1(RR)
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
i tried but cts profile mismatch becomes false
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
1. Open the Settings app, and go About phone tab and spam click on Version to enable Developer Tools.
2. Do a search in the settings for "Root" and disable Root access.
3. Reboot to Recovery mode and flash this unroot https://forum.xda-developers.com/showpost.php?p=63615067
4. Reboot phone and follow xJovs' guide from step 3
Note: I also used the flashable zip file from the guide to get root and did not install the APK. https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It might be because of the Kernel but I'm just speculating. Try flashing a new one to see if it helps!
g_BonE said:
Running a Mi Max here and have to say: Not working!
If i fully unroot the phone (magisk uninstaller / unSU script) then safety net helper gives me a red screen (CTS profile mismatch) but after installing Magisk 10.2 i only get a blueish screen in safetynethelper saying "response validation: fail"
Click to expand...
Click to collapse
It will always return blue right after installing Magisk. You need to follow through with the whole tutorial to work. If you have, then it's probably your rom. It happened with me on GraceUX roms.
Latest version of PoGo doesn't appear in magisk hide menu
It works
Thanks! Editing the permission of SElinux files works for me
Nexus 5X
GooglePixelROM v7.0.1
Android 7.1.2
NPG05D
Using Magisk 11.1
Now I can pass SafetyNet and use AndroidPay on a custom ROM
Galaxy Note 3 (N9005) MagmaNX with Magisk v11.1 + MagiskSU
CTS profile match: false
Basic Integrity: false
xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
yo_honey said:
i have HTC Desire 820 d820u running 6.0.1 mm stock.
is this will be ok to try?????
Click to expand...
Click to collapse
Could but I have no idea.
I have tried latest magisk
xJovs said:
Could but I have no idea.
Click to expand...
Click to collapse
Here is full guide https://forum.xda-developers.com/desire-820/general/guide-bypass-safetynet-magisk-t3592508
Doesn't this work for Lollipop or is it just that you haven't tested?
xJovs said:
I would first like to say that I cannot guarantee if this works on ALL devices. I was able to get this to work on the Galaxy S6 and posted it on the Galaxy S6 forums, however I am looking for people with other devices to see if it works for them as well (because why not share the bypass love to everyone ) If it works, please post a screenshot to confirm so I can post it on the thread here. Thanks.
(Please note that I am not responsible if your phone bricks etc. Please use at your own risk! Myself and others who have also tested this bypass have had no reported issues of this bypass causing some sort of brick etc., but I cannot guarantee anything.)
*This is a copy and paste of a thread I made on another forums and I felt like sharing it here. If there is any mistakes in the post, please tell me so I can fix it. Thanks.*__________________________________
Since October 2016, Google has (yet again) changed their way on how SafetyNet works and how they can now easily figure out if your phone is rooted or not. This caused many issues for rooted Android users who wanted to play games such as PKMNGO and use apps such as Snapchat. However, there is still ways to bypass SafetyNet.
Tested Devices:
- Samsung Galaxy S6
- Samsung Galaxy S5
*Looking for people with other devices to try and see if it works for themselves so I can add the device to the list.*
__________________________________
Requirements:
- Basic Understanding on how to use Custom Recovery, flashing zip files etc.
- Running on Android 6.0 (Looking for anyone with Android 7 to see if this works for them as well.)
- Phone has a custom recovery (I suggest TWRP) and on a Custom ROM. (Stock roms "should" work too.)
- Rom should have November 1st Security update or older updates. (Have not tested with roms with November 5th Security update and higher.)
- Magisk V10.2 & Magisk Manager 3.0
- SafetyNet Checker
- Phh Super User APK. PlayStore or 2.0 Beta
- Root File Explorer. I suggest Root Browser
- Kernel Adiutor
- Root Checker
(I have had issues trying Xposed on Magisk V9, however it may work on V10.2)
Tutorial
**WARNING: BIG IMAGES** (Had no time to resize them, but will soon.)
Before we begin, I suggest that you make a Nandroid backup through your preferred Custom Recovery. I suggest you use TWRP however CWM "should" work, but I have not tried myself.
Step 1:
Clean Install
The first step 'is' optional, however it is recommended that you do a clean install. I will be using Alexis Rom 8.0 Beta 2 for my Galaxy S6, but any rom should work. (Other than certain GraceUX ports, but am able to get it to work with other ported rom like CoreUi (a MIUI port) for the Galaxy S6). You should also flash a kernel now as well. I use to personally use Arter97 as SuperSU is not installed in this kernel, however Arter97 is slowly starting to become unstable as it hasn't been updated and there is better kernels out there. For this tutorial, I will be using Twisted Kernel.
Step 2:
Removing SuperSU
This step is 'also' optional, but ONLY if your rom/kernel does not automatically install SuperSU for you. In my case, it is automatically installed.
What you will need to do is to go to the SuperSU app, go to settings.
Scroll down until you see "Full unroot" and click it.
A popup will come up and click "Continue", then followed by another popup and click "NO".
Once you click no, your phone will freeze and then reboot. You should then install Root Checker to verify if your phone is unrooted.
(If for some reason, you are unable to use the SuperSU app but you know SuperSU is installed, I'd suggest you download UPDATE-unSU-signed.zip and flash it as it will manually remove SuperSU.)
Step 3:
Installing required APKs.
You will now need to install MagiskManager 3.0, SafetyNet Helper Sample, PHH Super User APK, Root Browser and Kernel Adiutor.
Step 4:
Flashing MagiskV10.2
You will need to reboot into your custom recovery and flash "Magisk-v10.2.zip", followed by rebooting. If you receive ERROR: 1 in TWRP when it is trying to mount SU, I suggest reflashing a kernel (and re-remove SuperSU), uninstalling Magisk with MagiskUninstaller (in Magisk thread) and reinstall Magisk V10.2, or reinstalling your rom.
Once you have flashed the file, reboot into System and open Magisk Manager to verify you have installed Magisk. A little pop up will open to allow Magisk to have root. Make sure to click allow and set it so it has root for "Forever".
If it states that root isn't properly installed, manually flash PHH Super User V266-2.
Step 5:
Enabling Magisk Hide
In Magisk Manager, go to the side menu and go to "Settings." You will see an unchecked box that says "Enable Magisk Hide." Select it and reboot. Re-open Magisk Manager and verify that it is now check marked. If the App crashes when you select "Enable Magisk Hide", reboot your phone and retry.
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow."
Once you are done, open up SafetyNet Helper Sample and it 'should' pass. If you are getting "Response Validation Failed" and the background is blue, uninstall Magisk by flashing Magisk Uninstaller, flash UPDATE-unSU-signed.zip, then reflash Magisk V10.2. Then, go back to Step 5 and enable Magisk Hide.
Step 7:
Use Kernel Adiutor to automatically set permissions in init.d
This last step is 'optional', however it automates the permission setting as every time you reboot your system, the file permissions will reset. Open up Kernel Adiutor, go to the sidebar and scroll down until you see 'Init.d'. Click it and make sure "Emulate Init.d" is enabled.
Then click the plus button, set the name to "Permissions" and then add the following script:
"chmod 640 /sys/fs/selinux/enforce" and "chmod 440 /sys/fs/selinux/policy" and save the files.
Also allow root access to Kernel Adiutor!
Step 8:
Reboot
Reboot your device, let Kernel Adiutor do its countdown (you will see in the notifications drop down) and once it says "Applying settings completed!", open up Safetynet and you should be passing!
Credits:
topjohnwu - Main developer of Magisk and Magisk Supported Phh Super User
This XDA thread - Helped me figure out how to do this bypass in the first place.
CoreUi Telegram Chat - Helped me test this bypass to see if it worked on different S6 models. Join here!
If I forgot to credit anyone, please tell me.
__________________________________
If there is any mistakes I made, spelling, phrasing etc., please tell me so I can fix it. Thanks.
Click to expand...
Click to collapse
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
savvy1968 said:
Step 6:
Set Permissions
In Root Browser, go to the directory "/sys/fs/selinux" and find the file "enforce" and the file "policy". On the file "enforce", change the permissions of the file from "644" to "640", and for the file "enforce", change the permissions of the file from "444" to "440". If Phh Super User pops up and asks for root access, click "Allow." Which file gets which perms bud you mention the same file twice.
Click to expand...
Click to collapse
Yeah I had to change it on my other thread in the GS6 forums. However I'm stopping maintenance of these threads as MagiskHide deals with all that permission stuff automatically now.
Seems to not working on leeco le max 2
{
"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"
}
HUAWEI P9 Custom Rom EMUI 4.1.1* RENOVATIO *
Based on the European Firmware b182 - Teamwork by Tecalote and KangVTested on EVA-L09 - but should also run on all other models (except P9 Plus and P9 Lite)I am happy to present you my new ROM. Created in collaboration between me and KangV
The ROM is similar to NewWorld: https://forum.xda-developers.com/p9/development/rom-huawei-p9-newworld-7-tecalote-t3543296 - but goes its own way and has therefore the new name: *RENOVATIO*
I think Marshmallow is still a very good and contemporary system with great potential for the P9 - and this I tried to expand in my new Rom and get the best out ...
In the foreseeable future I will release a nougat ROM for P9 - the work is already in progress. But Xposed Framework is not ready for Nougat and some other things may not easy modifiable yet.
German Thread: : http://www.android-hilfe.de/thema/huawei-p9-rom-android-6-0-renovatio-by-tecalote.827314/
Installation Guide:
You must either come from NewWorld 5 or 6 or 7 - then you can start immediately, or:
You are on the last Marshmallow Firmware for your model / device (in case of EVA-L09 on official b182) - then you can start also right away. If you are not on latest Marshmallow Firmware you must update it for your device/model. For EVA-L09 you can use this Link: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v63880/f1/full/update.zip
If you come from NewWorld 4.x you must also first upgrade to latest official Marshmallow Firmware for your device - if you would flash Renovatio ROM from NewWorld 4.x Fingerprint would not work!
If you are come from Nougat , you must first make a downgrade - in case of EVA-L09 b300: http://download-c.huawei.com/download/downloadCenter?downloadId=91727&version=358124&siteCode=nl
After the downgrade with the transition Firmware you have then for EVA-L09 still flash the b182 and Bootloader getting closed.
Bootloader must be open (clear ) "
The data partition must be formatted for this ROM same as in the original Firmware with f2fs - Do not format it with ext4!
For the installation, I definitely recommend a full wipe if you want this ROM to do the best!
You need this TWRP: https://www.androidfilehost.com/?fid=457095661767122229
If you do a Nandroid-backup - please reboot TWRP after via reboot "reboot recovery" (in Main Menu) before flashing the ROM! If you want to wipe your internal storage (optional) reboot also TWRP before doing the next steps - cause with wipe of internal storage TWRP loose the settings and you have to setup it again. If you have rebooted TWRP make a advanced wipe of Dalvik/Art, Cache, data and system - and finally flash RENOVATIO-ROM.
Reboot needs about 9 minutes. After the first setup, enable "USB debugging" and "Allow unknown sources". "OEM" Unlock is already activated.
Tip for extending battery life:
Energieschema starts with standard: Performance - you can change this in the Akkumanager to: Intelligent.
Wifi + allow, disable NFC and VoLTE, if not required, switch off network message in extended WLAN settings. In advanced settings, security you can at the bottom test "disable apps with usage access" for playstore and play services - I have the feeling these services work without this option.
* Renovatio * is available in three editions:
1. Classic Edition
Rooted with @Chainfire SuperSU (2.79 stable) in system and BusyBox 1.26.2
DOWNLOAD: https://www.androidfilehost.com/?fid=529152257862720103
MD5 (please check): 4e74fc5b24ded230cdfccf51a11e1b75
FEATURES:
Push notifications working very well- without transform apps into system apps. WhatsApp and Co, however, must be defined as protected apps in the Akkumanager, must also be authorized in the Autostart Manager , and in the notification manager - as well as Wlan and mobile data must be switched on during sleep !
Further information in Post #2 - HOW TO SETUP SETTINGS FOR PUSH-NOTIFICATIONS: https://forum.xda-developers.com/showpost.php?p=71955546&postcount=2
K-Settings of KangV specially made for the b182
Callrecorder (manually per call - or in the dialing settings to automatic)
Dolby Atmos - works perfectly with Viper4Android - (Viper4Android is available in K-Settings and can be permanently displayed in the notification area for quick access via settings.)
Xposed Framework by Wanam 87.1 - Installer is available in K-Settings. It installs automatically with script the Xposed Framework and wipe Dalvik and Cache after (REBOOT as always about 10-15 MIN)
3 different EMUI 5 (Android 7) Themes are on board - besides a lot of other themes. To download new themes you need a login with the Huawei ID.
AdAway in the latest version installed (must be opened and activated)
MiXplorer in the latest version - this requires 3 permissions (root permissions for / root - access to internal storage and access to external SD must be approved)
Multiwindow-Mode further developed (more stable) If you open an app and then long click on the square symbol at the bottom of the navigation bar. In the middle of the split window is then a control, with which one can change the window from top to bottom or close the multiwindow mode.
and much more....
I have tried to activate VoLTE and WiFi-Calling, not sure if it really works. More information in Post #3:https://forum.xda-developers.com/showpost.php?p=71955547&postcount=3
INFO:
Only important GApps like Google App, Gmail and Chrome, as well as the Google core apps and services (which must be in ROM) installed. All the other GApps debloaded - everyone can use Playstore to install what is needed (Google Music, Drive, Maps ...)
To turn off the only Chinese letters in this ROM:
In K-Settings you will find the entries:
1) Notification Settings / Show statusbar lunar - deselect.
2) Lockscreen and desktop settings / Lunar calender + Desktop wheather lunar - deselect.
Permissionmanager is not allowed in "Oversea" regions - permissions can be set in Settings / Apps /Name of the App
Phone manager does not include Autostart Manager - but you can enable it with a little trick:
PM-Plus App is preinstalled. Once open, go to install - as soon as the message "succesful" comes, close it (can be uninstalled after) - now Phonemanager will also have the Autostart Manager!
Dont forget to activate in "Autostart" Messenger, chat apps, Netcall apps like WhatsApp, Viber, Facebook and Co... (otherwise no Push-Notifications)
2. Magisk Edition
The same features, but systemless rooted with the professional Root-Solution Magisk by @topjohnwu with his own superuser.
Download: https://www.androidfilehost.com/?fid=457095661767154746
MD5 (please check):0592971a6034a2414a8b893619eed4ed
Attention:If you are flashing Magisk Edition, you must install the manager for Magisk immediately after setting up (before opening any apps requesting root privileges). This can not be preinstalled because of special code cache and must be installed by the user (apk) http://tiny.cc/latestmanager
If you like to install the systemless Xposed Framework, you must do this from the Magisk Manager (SDK 23) - not from the "Xposed Installer" (Xposed installer is preinstalled for downloading, installing and managing the modules - see Homescreen). After installing the systemless Xposed REBOOT needs about 10-15 MIN
(There is no access to the Xposed Installer from Wanam in the K-Settings)
The Magisk edition was made primarily because of the alternative, very good Root-Solution - but it cannot really bypass safteynet yet!
This is probably only possible with a pure Stock Rom, rooted with Magisk - but even there not possible with installed Framework yet.
Magisk version 12 has a Root-hiding effect:
When set up, Huawei ID does not recognize that the device is rooted. And K-Settings also assume that the device does not have root - although it grants root rights, but only to apps that query that. So, for example, you can open Wifi-Password in K-Settings, because the root rights are queried and the Wifi-password is displayed.
However, a few components of K-Settings that do not make this query can not be used:
In More settings - 1) Flash recovery, 2) Block ad and 3) Disable google services. The latter two are intended for Chinese Rom, once this options would enabled Google Apps would not work. To block ad, AdAway is preinstalled (must be opened and activated). If you really want to flash Stock Recovery, you can do this via adb.
Xposed Framework can not be installed in the Magisk Edition from K-Settings - you must install the systemless Xposed from the Magisk Manager.
All the other K-Settings are working as usual.
Settings from Magisk:
The Magisk-Hide option is to be used with caution; it may happen that K-Settings are not invokable (since they should not be hidden from root). If it occurs, there is a solution.
Please do not use Magisk Core in settings.
The Busybox of Magisk does not necessarily have to be mounted to xbin, since there is already the installed BusyBox 1.26.2, which also uses Magisk. But can be switched on optionally, if needed for any reason.
For AdAway, you must activate systemless hosts in Magisk!
HAVE MUCH FUN WITH THIS ROM
At this Point I wanna thank KangV for his great K-Settings Framework
If you like RENOVATIO - fell free to donate KangV: https://www.paypal.me/KangVIP
And if you like my Work too, feel free to donate to me: https://www.paypal.me/Tecalote
Many thanks and credits to other great Developers:
@guitarededhero (Viper/Atmos) https://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
@wanam and @rovo89 and @DVDandroid for the Xposed Framework Development
@HootanParsa (MiXplorer) and @YashdSaraf (BusyBox arm64)
@topjohnwu (systemless Xposed Framework and Magisk)
@Chainfire - SuperSU
@dkionline - Custom Roms for P9
@Blackball - BlackPyramid Theme and Custom Roms for P8 and P9
@venom007 - IOSmix Theme
@maximax2795 - EMUI 5 Theme for EMUI 4
Push-Notifications - the right settings
Push-Notifications work without converting apps to system-apps!
But you need the right settings for Messenger, Chat-Apps, Netcall-Apps.... :
1) All those Apps has Login-Service:
Dont restore them from an Backup! Use the in-build backup function (saving on Google Drive for exampel) After setup your new installed ROM - install those apps with Playstore (WhatsApp, Viber, Skype...) - login and restore your chat-history from found backup.
2) In Phonemanager set the apps as "protected apps"
3) In Phonemanager enable the apps in "App auto-launch" - for some apps also in App-activation (a part of App auto-launch) More information about "App-activation" - here: https://forum.xda-developers.com/showpost.php?p=72005393&postcount=53 - It is an important step for Apps like Amazon!
4) In Phonemanager enable for those apps in "Notification center" - Allow notifications, Priority display, Status bar, Banners and Lock screen
5) In Phonemanager - Battery manager /settings: enable "Keep Wi-Fi on when sleeping always", "Keep mobile data on when sleeping" - but disable "close excessively power-intensive apps and dont enable Power-intensive prompt (cause if you are close those apps, Push-Notifications dont work)
6) In Setting / Apps /Name of the App (WhatsApp... etc) give those apps permissions.
7) In Setting / More / enable WiFi+ (if you forgot it during setup) - in mobile network enable "Mobile data" on, "Enable always-on mobile data" and Carrier aggregation
8) In Setting /WiFi Menu /Advanced settings enable "Keep Wi-Fi on during sleep" - but Network notification you can disable, it saves Battery
VoLTE and WiFi (IP) Calling
General information on the topic VoLTE and WiFi Calling:
To use VoLTE you must have a SIM card from your mobile network provider, which support this. Your call partner must have a SIM card, which support this. The phone must support it and then you can telephone with your call partner with VoLTE.
Calls are at the moment only supported between call partner in the same mobile network and cannot be done from one mobile network to another.
If these prerequisites are fulfilled, then phone calls work with VoLTE.
In the statusbar, only 4G / LTE is displayed on the network symbol during a phone call. If network symbol switch to 3G, 2G, or H - the call dont use VoLTE.
Possible are also Circuit-Switched Fallback problems on places, where LTE is not available. VoLTE is technically not yet mature
WiFi Calling is a Feature which works inside your home and outside, but only, if you are connected to a available WLAN - the inbuild function from Huawei called Wifi+ changes automatically in known networks between mobile network and WLAN. If you are outside and connect your phone with an available (not known) WLAN, Wifi+ disable mobile network if WiFi Calling is working on your phone. Wifi+ switch also back to mobile network if you left the WLAN. This cannot be done manually, because you cannot disable mobile network by yourself. Only with Flight-Mode, but with this setting WLAN cannot work on Huawei Phones. If WiFi Calling is not possible on your phone, WiFi+ enable both, WLAN and mobile Network.
WiFI Calling is dependent on the location and depends on the network provider.
Example: If your network provider is in Germany and you are in Germany, you can use WiFi Calling only (1) if Phone support it, (2) if your SIM card support it and (3) if your mobile network is not available. But if your provider is in Germany und you make a journey to Netherlands the WiFi Calling service In principle available (not only, if your mobile network is not available)
You see, there are many things that need to work together....
I tried to enable VoLTE and WiFi Calling in this ROM.
For this I spent many days and nights checking thousands of lines with code. Note: For most Countrys and European Countrys VoLTE and IP-Call is official not available in b182 Firmware!
But I saw that the Firmware b182 has inbuild support for VoLTE, but only for some regions. What I did is: I searched line for line in all regions and enabled there VoLTE and WiFi Calling - same, as it is enabled for other regions.
I cannot tell you at the moment, if it really works. Cause there are many facts to respect in order to find an answer. And I have not much time yet.
But anyway if VoLTE and/or WiFi Calling works in this ROM, I hope you enjoy RENOVATIO Thanks! And if I get more useful information or testing reports I will inform you.
Thx for this update,I come from NewWorld 7, does xposed framework work on this rom ?what about freedom bro ?
What's the difference between classic and Magisk Edition ??
Kimo2014 said:
Thx for this update,I come from NewWorld 7, does xposed framework work on this rom ?what about freedom bro ?
What's the difference between classic and Magisk Edition ?
Click to expand...
Click to collapse
Hello All your questions are answered in OP - just read the first Post please...
Except your question about freedom - don't know what you mean with it?
Tecalote said:
Hello All your questions are answered in OP - just read the first Post please...
Except your question about freedom - don't know what you mean with it?[/QUOTE
Alright,but Actually freedom app doesn't work,I can't buy with it, you tell me that it will be available in the next update.
Click to expand...
Click to collapse
Kimo2014 said:
Tecalote said:
Hello All your questions are answered in OP - just read the first Post please...
Except your question about freedom - don't know what you mean with it?[/QUOTE
Alright,but Actually freedom app doesn't work,I can't buy with it, you tell me that it will be available in the next update.
Click to expand...
Click to collapse
Yes I said I will try to find a solution for safetynet issues in future versions of my Roms, not directly with my next update - because it is very difficult and best developers haven't yet a solution for this in modified Roms.
Freedom will not work yet in Renovatio, sorry
Click to expand...
Click to collapse
Hi Tecalote, thanks for this ROM.
Do you plan to do a similar ROM based on EMUI 5.0 and Android Nougat ?
Salamender said:
Hi Tecalote, thanks for this ROM.
Do you plan to do a similar ROM based on EMUI 5.0 and Android Nougat ?
Click to expand...
Click to collapse
This question is even answered in OP, please read everything cause there are useful informations!
Yes, I make same Rom with Android 7 Nougat! The work is already in progress
Nice looking forward to the Nougat version.
From NW7 "start immediately" ? Only flash by twrp?
Wysłane z mojego EVA przy użyciu Tapatalka
darrr1 said:
From NW7 "start immediately" ? Only flash by twrp?
Wysłane z mojego EVA przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes, from NewWorld you can flash with TWRP, but read OP - you should do a Advanced Wipe of Dalvik, Cache, data and system.
If you make a TWRP Backup, restart TWRP before doing the wipe - after wipe flash the Rom
Ok. Thanks ? I suppose twrp is the same.
Wysłane z mojego EVA przy użyciu Tapatalka
Is volte working? Anyone tested??
kye04 said:
Is volte working? Anyone tested??
Click to expand...
Click to collapse
I am sure now, I did calls outside today and 4G didn't change to 3G, 2G - that means it works
Is wifi calling working? My provider offers this option but the p9 doesn't support it..
kye04 said:
Is wifi calling working? My provider offers this option but the p9 doesn't support it..
Click to expand...
Click to collapse
Hello I am sure now - WiFi Calling and VoLTE works I have tested now. Just enable WiFi + with Setup.
At home in my WLan I am only connected with WLan and not with mobile Network (4G, 3G, 2G not showing - same if I make a call)
Outside, if I call, only 4G is showing (not 3G, 2G) I called my provider yesterday and my contract support both.
I don't know if it works in all regions (I am in Germany) - but I enabled it for all regions) - but with Stock b182 and with NewWorld it wasn't enabled
xtcislove said:
Nice looking forward to the Nougat version.
Click to expand...
Click to collapse
The Nougat version is growing up
The right settings for receiving Push-Notifications you can find here:
https://forum.xda-developers.com/showpost.php?p=71955546&postcount=2
Tested VOLTE. It works. Yet i cannot confirm wifi calling. I understand in all phones, when you call someone using wifi call , it appears wifi calling in notification. To me nothing appear...
I think i shloud call someone and switch off the router in order to see if the call drops...
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- Latest Official: http://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.2.1 by @jemmini : https://mega.nz/#F!9VFh0AxR!tO5kJvsrtKhxJl5OpeEKsA
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
- Magisk (still via TWRP): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Oukitel K6 Android 7.1.1
Review Part 1 Part 2
How to update
Search your app draw for wireless update
When first released the phone was build number version oukitel_k6_v15_20171225
check for new update
download in app and install
Downloads
Flash tool
ROM
Latest software ROM for all OUKITEL smartphones
TWRP 3.2.1-0 for Oukitel K6 here or here
SuperSU for Oukitel K6 here or here
To Root Oukitel K6 with SU follow instructions here
To Root Oukitel K6 with Magisk only V.14 is working, download and installation instructions here
To Uninstall Magisk / Unroot open magisk manager and uninstall. Power off and use flashtool to flash boot.img from TWRP download above.
My Favorite (Root) Apps
Magisk Manager https://github.com/topjohnwu/MagiskManager/releases/
Root Checker https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
Root Essentials https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials
MTK Engineering Mode https://play.google.com/store/apps/details?id=com.themonsterit.EngineerStarter
Stubborn Trojan Killer https://play.google.com/store/apps/details?id=com.cleanmaster.security.stubborntrjkiller
Malwarebytes https://play.google.com/store/apps/details?id=org.malwarebytes.antimalware
System App Safe Remover https://play.google.com/store/apps/details?
id=com.jumobile.manager.systemapp
Battery Calibration [ROOT] https://play.google.com/store/apps/details?id=com.blogspot.superthomaslab.batterycalibration
Engineer mode
Huge list of developer options for testing touch,gps,wifi,display,etc.
*#*#3646633#*#*
Source [TrickTips] MTK Phones Dial & Secret codes!
Regards Andrew
I have tried installing Magisk Beta: v15.3 (code: 1531) both ways and it fails with a boot loop
Bug report here
Hi, thanks for your great work. I am asked for a password to decrypt data upon entering twrp. Any workaround to avoid restoring-formatting?
bootloop
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
00isolator said:
Hi, thanks for your great work. I am asked for a password to decrypt data upon entering twrp. Any workaround to avoid restoring-formatting?
Click to expand...
Click to collapse
remove your lock screen password/pattern/fingerprint/face and try again
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
For those trying to get Magisk to work on the K6 the latest Magisk doesn't work, However Magisk 14 works perfectly so get Magisk 14 it took me a while to figure it out so I tried 14 and it worked!
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
I followed magisk install precisely and even cooked my boot.img with superr's kitchen so I'm pretty sure I have found a bug with magisk, which by the way is the beta version 15.3(1531) here . My findings so far require me to dig deeper and send in some logs from a twrp install attempt to the magisk dev.
uncleabubear said:
I have tried installing Magisk both ways and it fails with a boot loop
Click to expand...
Click to collapse
rolandvb said:
I tryed to install magisk too and also ended up with a bootloop, so it don`t seems it does not work on the K6 ,or maybe we made a procedure error????
maybe it would be helpfull to make a tutorial how to flash and install Magisk ( if it really works)??
Click to expand...
Click to collapse
uncleabubear said:
I followed magisk install precisely and even cooked my boot.img with superr's kitchen so I'm pretty sure I have found a bug with magisk, which by the way is the beta version 15.3(1531) here . My findings so far require me to dig deeper and send in some logs from a twrp install attempt to the magisk dev.
Click to expand...
Click to collapse
Like I said in my quote try Magisk 14 and get back to me if it works.
Fltr said:
For those trying to get Magisk to work on the K6 the latest Magisk doesn't work, However Magisk 14 works perfectly so get Magisk 14 it took me a while to figure it out so I tried 14 and it worked!
Click to expand...
Click to collapse
ok thanks i'll try that although I will still report the bug as 15 has a lot of improvements
uncleabubear said:
ok thanks i'll try that although I will still report the bug as 15 has a lot of improvements
Click to expand...
Click to collapse
I wish 15 did work it has a lot more features on it because 15 worked on my Outkitel K6000 and it has a lot more modules.
Fltr said:
Like I said in my quote try Magisk 14 and get back to me if it works.
Click to expand...
Click to collapse
does it then upgrade ok to 15 in the magisk manager?
uncleabubear said:
does it then upgrade ok to 15 in the magisk manager?
Click to expand...
Click to collapse
no I've tried that, it installs then reboots but still says 14 is installed and says 15.3 is available.
Magisk bug reported
Anyone can help me?
I resistered IMEI on my carrier service company.
But APN settings are not saved and mobile data doesn't work yet.
I couldn't save APN settings.
Can anybody tell to unlock additional LTE bands.... And volte is not working for me
uncleabubear said:
Magisk bug reported
Click to expand...
Click to collapse
Common issue on latest Mediatek devices, the Magisk team should add a compatibility mode for those.
brightlee63 said:
Anyone can help me?
I resistered IMEI on my carrier service company.
But APN settings are not saved and mobile data doesn't work yet.
I couldn't save APN settings.
Click to expand...
Click to collapse
I guess the device isn't able to read your sim card properly then.
Just to double check, tell us the steps you are doing to save the APN.
nanduking2 said:
Can anybody tell to unlock additional LTE bands.... And volte is not working for me
Click to expand...
Click to collapse
Nope, you can't. LTE Bands are hardcoded on ALL devices and can't be modified.
MT6763 supports lte band 5 and band 40 , band 41, but firware doesn't allow it why?? False info given on official site that it suppports volte, it doesnt my previous leeco le 2 used to support volte for my sim, this one wont, it only supports data.....and most of the time switches off automatically in idle mode(when not using) every time i have to start again, but if screen is on it wont get switch off automatically, really this is weird phone...any solution??
nanduking2 said:
MT6763 supports lte band 5 and band 40 , band 41, but firware doesn't allow it why?? False info given on official site that it suppports volte, it doesnt my previous leeco le 2 used to support volte for my sim, this one wont, it only supports data.....and most of the time switches off automatically in idle mode(when not using) every time i have to start again, but if screen is on it wont get switch off automatically, really this is weird phone...any solution??
Click to expand...
Click to collapse
The chipset doesn't matter, the manufacturer provides a list of the supported bands, picture attached below. You must have checked it before.
{
"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"
}
As regards VoLTE, even though it supports it, it doesn't necessarily mean that your carrier accepts it on its network.
Ok but what may be the cause for auto switch off....if v get custom rom will v get other band support??
Thank you very much for your interest,
On my OIKITEL K6,
after inserting SIM card in slot 1,
I did it like this.
1.setting
2. more
3.mobile network
4.APNs
5. + (new APN)
6.editing : Name
7.editing : APN
8.editing : MMSC
9.editing : MMS port
10.editing : MCC
11.editing : MNC
12. tap 3 dots at top right
13. tap SAVE
and there's only one list of EMERGENCY CALL, and no list what I just saved.
So, I changed another SIM card which is working on another android smart phone, and it happens same situation.
And when the SIM card is moved into other (originally used) phone, it works well.
Two SIMs are same.
My SIM card also works well at my former android phone at now.
Please give me some more TIPs...
Thank you.
Alberto96 said:
Common issue on latest Mediatek devices, the Magisk team should add a compatibility mode for those.
I guess the device isn't able to read your sim card properly then.
Just to double check, tell us the steps you are doing to save the APN.
Nope, you can't. LTE Bands are hardcoded on ALL devices and can't be modified.
Click to expand...
Click to collapse
Custom firmware for FiiO M6, FiiO M7 and FiiO M9
Hi everone,
My hobby is modding and building ROMs so now I mod FiiO M6 and M7 firmware.
Why? Now you can install playstore and activate third party players like PowerAmp and Neutron or use streaming apps like Spotify or Tidal.
I hope you will enjoy my ROM
Installer Features
Installing MicroGapps and Playstore to download and activate third-party players (Requires my firmware to work)
Magisk Installer (Requires my firmware to work)
Mixplorer (File Manager)
Dark Theme Installing
Xpossed Framework Installer
Optimized Fiio Music App
Optional Tidal Installing
My Firmware Features
Improved sound (Editing system configurations, Alsa, Updated SoundLibs)
Optimized system resources
Magisk (Root)
Activated WiFi item in settings
Updated FiiO Music App
Fake Signatures support
Activated Init.d
Useful build.prop tweaks
Another Bootanimation
Changed font to Russia font (Ubuntu + Samsung One)
And many other improvements
How to install firmware: Youtube Instructions
M7 Firmware link: M7 Firmware
M6 Firmware link: M6 Firmware
M9 Firmware link: M9 Firmware
If you want to thank me financially:
Bitcoin: 1MeMen1FHZ5iut5KYmdJrQKBgk2e8hts7f
Ethereum: 0x4C90b19a78f19a6fbaA191C58cF0E87751588d3c
PayPal: http://paypal.me/antonixo
QIWI: https://my.qiwi.com/Konstantyn-YFrx47iPqT
Installation Instructions
1. Download my firmware and copy it to sd card
2. Go to recovery by off player and turning it on pressing next track and power if you use M7 or volume down and power for M6.
3. Wipe data using vol+ vol- and power buttons select "Wipe data/factory reset" paragraph
4. Press yes and reboot to recovery.
5. Go "Install update from sd card" and select archive with my firmware.
{
"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"
}
6. Now Aroma installer starts. To controll in aroma installer use combination of pressing Power+Vol+ Power+Vol- and Power.
7. Go next page by using Power+Vol+ and select any paragraph you need.
8. Power+Vol+ to start installation.
9. After installation press power and reboot to the system (First loading will take about 3-7 minutes)
FAQA: Player becomes laggy!
B: I cannot fix bad processor of FiiO M7. Lags because you start use player another way. You update FiiO Music, install Playstore. Apps require more performance hardware. Try reinstall with old FiiO Music and without Gapps
A: How to go back to original firmware
B: You can easily go back flashing stock rom for FiiO M7 from here - M7 Firmware or for fiio M6 from here - M6 Firmware. Just flash it from recovery like my firmware
A: Why, when entering Magisk, there is a notification about an additional installation?
B: Since the magisk was installed "by hand", he did not unpack the files he needed to the Data section. To fix the problem without the module and install this module
A: Why is there only only my language in the keyboard?
B: Settings - Language & input - Virtual keyboard - Simple keyboard - Language
Uncheck the system languages and put them in the languages you need
A: Stuck on logo/bootloop!
B: Hold the power and pause button, after the screen turns off, press the button down, in recovery, select Wipe data.
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Mentalmuso said:
Thanks for this, though I've been meaning around with it, magisk doesn't provide proper root, no root apps request and get granted root ever. Am I missing something?
Click to expand...
Click to collapse
Did you select magisk app in installer? You have M6 or M7?
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
AntonIXO said:
Did you select magisk app in installer? You have M6 or M7?
Click to expand...
Click to collapse
M6, it seems userdata doesn't mount so the magisk data files don't install. You have the correct platform etc for mounting, but I'm not sure why it fails. Otherwise it all works great.
dubsflyt said:
tried this on a m9 and no luck im afraid, just stuck at the fiio logo on bootup, left for 30 mins, rebooted to recovery and wiped data again, left for an hour and no difference.
Click to expand...
Click to collapse
Flash stock firmware through recovery
AntonIXO said:
Flash stock firmware through recovery
Click to expand...
Click to collapse
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
dubsflyt said:
Yeah sorry should have said, got it working again by flashing stock, but this rom didnt work unfortunately, happy to test again if you release another build or something
Click to expand...
Click to collapse
I've update rom. Try again.
cannot make it work even with new update:-(
unfortunately same result with the new update on the m9
any news?
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Paris333 said:
installed on my M6 working great, the only thing I cant get working is magisk, I read above about the module zip but can't understand how to install it, apart from that everything is perfect, keep up the great work.
Click to expand...
Click to collapse
Go to magisk, press cancel in window and install module from module menu
Please please update for m9...
Any news ?
m9 업데이트 해주세요 ... 제발 ..
Just tried today's version but it dows not install.
after installing statrs after 2 or 3 seconds it reboots
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Admiral_Face said:
I seem to have the same issue as Mentalmuso and Paris333; Magisk isn't giving out root permissions on the M6. When I try to flash module.zip via the modules tab in the magisk manager app I get:
Code:
! Unsupported/Unknown image format
! Installation failed
The magisk debug log is only full of:
Code:
su: request from pid={XXXXX}
su: request from uid={XXXXX}
su: request rejected (XXXXX)
for all of the root applications I tried to test it with
but when I go to the "superuser" tab it aggravatingly says "No app has asked for superuser permission yet."
My magisk app is the default non-updated version installed via the proshi_m6_en aroma installer. I did do full factory reset via the debug menu and followed all instructions, so the installation is very clean. Everything that doesn't need root works perfectly fine, xposed even shows up as active. I've tried a few things, like updating to the new v22 magisk app via the v22 magisk manager, but I always just run into the same boot.img unsupported error as above. Maybe I've missed something, let me know if you need anything tested, as I do have a few M6 to play around with that I don't mind bricking.
On an unrelated note: your paypal says you are not accepting payments.
Click to expand...
Click to collapse
try installing magisk manager v7.5.1 , im using that one with success. Getting root access now. I think half of it is actually the super lag we are getting with having play store, i have put together a very stripped down version of the stock firmware, removed a load of useless apps that all take up precious ram. I am simply downloading my preferred streaming app (deezer) and a couple of other useful apps (terminal, root explorer, magisk manager) and storing them all on my ext sdcard to install after clean install. I seem to be having a pretty fluid experience now.
anyone can fix da M9 file? it does not install any file to the device...