Related
Hi,
I bought this phone some mounts ago and I had some problems with one of the preinstalled apps . I'd like to root the phone the only problem is that I m a nooby and don t quite know how to do it , can someone give me some info or instructions on how to do it .
And can u tell me what is the difference between A55ML and e9pw(A53ML).
Thx
TheDarkOne1 said:
Hi,
I bought this phone some mounts ago and I had some problems with one of the preinstalled apps . I'd like to root the phone the only problem is that I m a nooby and don t quite know how to do it , can someone give me some info or instructions on how to do it .
And can u tell me what is the difference between A55ML and e9pw(A53ML).
Thx
Click to expand...
Click to collapse
Hi Brother
There Are 2 Methods To Root Your Phone
First
1 Unlock Your Bootloader (You Should Go To HtcDev.Com And Follow Their Steps)
2 Flash TWRP RECOVERY With ADB
3 And Then Flash SuperSU.Zip
The Second Method
1 Download KingRoot App
2 Open It And Hit Root!
But My Choice Is Method 1
Cause Then U Can Make Nandroid Backup And Etc.
Then,A55 Is HTC One E9+
But, A53 Is HTC One E9
If You Have Any Question, I'm Glad To Help You!
There's another option - go to HTCdev to unlock your bootloader, It's a simple procedure, then find a TWRP for your device (mine is A55ML), and go to Magisk thread. Flash Magisk as per instructions - it has it's own built-in root and init.d simulator. The best part is that Magisk will let you run everything in systemless mode - with Magisk you'll have root, xposed, busybox, and various other modules. All of them without touching the system partition. It's very easy to unroot if you decide to do so for some reason. I even got to install Viper Audio. Also there's module that enables writing on external sd card. Since i got Magisk i got to modify a lot of things with systemless xposed. Good luck!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vanshee said:
There's another option - go to HTCdev to unlock your bootloader, It's a simple procedure, then find a TWRP for your device (mine is A55ML), and go to Magisk thread. Flash Magisk as per instructions - it has it's own built-in root and init.d simulator. The best part is that Magisk will let you run everything in systemless mode - with Magisk you'll have root, xposed, busybox, and various other modules. All of them without touching the system partition. It's very easy to unroot if you decide to do so for some reason. I even got to install Viper Audio. Also there's module that enables writing on external sd card. Since i got Magisk i got to modify a lot of things with systemless xposed. Good luck!
Click to expand...
Click to collapse
But With Magisk There Is No Way To Use Lucky Patcher!
It Runs Like For A Non-Rooted Device
Mohammad_pd said:
But With Magisk There Is No Way To Use Lucky Patcher!
It Runs Like For A Non-Rooted Device
Click to expand...
Click to collapse
true, but i never had the need to use lucky patcher anyway. I'm sure there's other options. With the lack of a custom rom for this phone, Magisk is the closest you can get in modding your device without brick it. I mean, most of the stuff is systemless so less chance to brick it. With all the xposed goodness only option i miss in MM is a doze. Currently i have 27 xposed modules.
vanshee said:
true, but i never had the need to use lucky patcher anyway. I'm sure there's other options. With the lack of a custom rom for this phone, Magisk is the closest you can get in modding your device without brick it. I mean, most of the stuff is systemless so less chance to brick it. With all the xposed goodness only option i miss in MM is a doze. Currently i have 27 xposed modules.
Click to expand...
Click to collapse
Lucky Patcher To Patch Poweramp Or Something Else...!
What Modules You Use?!
Can U Say Them?
Mohammad_pd said:
Lucky Patcher To Patch Poweramp Or Something Else...!
What Modules You Use?!
Can U Say Them?
Click to expand...
Click to collapse
Careful! Apps like Lucky Patcher are not very welcomed over here. There's plenty of free apps to try. Personally i'm using AIMP with Viper Audio. It works miracles compared to built-in options. Oh, and xposed modules i currently use: Adblocker, All notifications expanded, Amplify, App settings, Always expandable notifications, Awesome pop-up video, Clarity, DS Battery saver, Fix LP Memory leak, Greenify, Handle external storage, Notification manager, Sense Toolbox, Xinsta, Youtube adaway, Youtube background play. That's the ones always active. And i play many more to try them out. The list grows with time.
vanshee said:
Careful! Apps like Lucky Patcher are not very welcomed over here. There's plenty of free apps to try. Personally i'm using AIMP with Viper Audio. It works miracles compared to built-in options. Oh, and xposed modules i currently use: Adblocker, All notifications expanded, Amplify, App settings, Always expandable notifications, Awesome pop-up video, Clarity, DS Battery saver, Fix LP Memory leak, Greenify, Handle external storage, Notification manager, Sense Toolbox, Xinsta, Youtube adaway, Youtube background play. That's the ones always active. And i play many more to try them out. The list grows with time.
Click to expand...
Click to collapse
I Used Sense Toolbox Before, It Reduces My Device Speed, But I'm Using Normal Framework,Not The Systemless One...
You Are Making Me To Go And Install Magisk...???
vanshee said:
There's another option - go to HTCdev to unlock your bootloader, It's a simple procedure, then find a TWRP for your device (mine is A55ML), and go to Magisk thread. Flash Magisk as per instructions - it has it's own built-in root and init.d simulator. The best part is that Magisk will let you run everything in systemless mode - with Magisk you'll have root, xposed, busybox, and various other modules. All of them without touching the system partition. It's very easy to unroot if you decide to do so for some reason. I even got to install Viper Audio. Also there's module that enables writing on external sd card. Since i got Magisk i got to modify a lot of things with systemless xposed. Good luck!
View attachment 4046740 View attachment 4046741 View attachment 4046742 View attachment 4046743
View attachment 4046748 View attachment 4046749 View attachment 4046750 View attachment 4046751
Click to expand...
Click to collapse
I'm currently using E9pw_Android5.0_Sense70_E1 rom with TWRP v2.860, and to be honest the ROM is decent but that's all to it. i tried in the past to install xposed but failed multiple times. I saw your comment on Magisk and i was wondering if i could install it on my ROM as well.
what ROM are you using currently? is it an updatable ROM?
I'm from South East Asia btw thanks.
some details of my htc:
HTC E9pw a55ml dtul
arm64 architecture
Ok. And a fair warning - Everything you do is on your own risk. I'm not responsible if you brick your device. As that being said, i'll give you links and tell you exactly what i did to make it work.
First and most important - do yourself a favor - make a complete backup in TWRP.
I see you're using old version of TWRP, here's the new one - it works way better. https://forum.xda-developers.com/one-m9/one-e9/recovery-twrp-recovery-3-0-0-1-t3321147
Flash the image trough recovery and reboot into recovery to load the new one. Now you can do a new backup with the new recovery or just move on. I did a new recovery - it might be a slower way to do things like that but it is way safer like that.
Next - Magisk, https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest Magisk, and uninstaller as well, put them in the root of your sdcard. Download xposed and it's uninstaller from here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
In recovery flash Magisk and then xposed. Reboot and you're good to go. You might want to clear cache and dalvik/art. At least that's the way i did it. Magisk installs it's own systemless root so no need for searching for SuperSU or other. Whatever happens - TWRP will say there's no root and will ask you to install - do not do that. Magisk will root your phone but TWRP can't detect it - never install other root if you do install Magisk!!!
With magisk and xposed installed in systemless mode it's up to you what other modules you will use.
There's another way to do that but i never used it. Download the Magisk Manager app from play store and it offers to do everything from within the app.
If everythig goes well go say thanks to the devs in their threads. Don't thank me - i just save you time not to search thing all over the XDA.
dude127 said:
I'm currently using E9pw_Android5.0_Sense70_E1 rom with TWRP v2.860, and to be honest the ROM is decent but that's all to it. i tried in the past to install xposed but failed multiple times. I saw your comment on Magisk and i was wondering if i could install it on my ROM as well.
what ROM are you using currently? is it an updatable ROM?
I'm from South East Asia btw thanks.
some details of my htc:
HTC E9pw a55ml dtul
arm64 architecture
Click to expand...
Click to collapse
I Suggest You NOT To Use Magisk
You Can Say Why...?!
Cause With Phh Superuser You Can't Use Many Things, For Example To Make A Swap File For Ram By Ram Expander And Something Else.
The Only Point That Magisk Have, It's About Viper4Android Fx, But Htc Devices Speakers Are Great Without It Too.
Other Point Is To Be Systemless, But If You Are Very Sensitive On Your Device, Make A Nandroid Backup, And Enjoy Your Full Controlled Device.
If You Are Worry About OTA Updates, Don't Worry, If HTC Release Updates, Just Flash Your Boot Image, Recovery Image And Then System Image By ADB, Then Check For Updates, Let Phone Update, And Then Install TWRP And More...!
Good Luck!
Sorry all, but I will no longer be able to create stable/testable builds. My phone died and I ended up getting a Pixel 2 XL instead. I tried to continue building but compilation has been failing and I can lo longer test anything.
Latest update: 2018-10-13 To view a changelog, you can visit https://review.lineageos.org/#/q/status:merged+branch:lineage-15.1 for a rough idea up to the build date.
{
"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"
}
Hi all. I was able to compile this stock build of LOS 15.1 thanks to the efforts/hard works of @bhb27 and those over at Lineage OS. It has some minor extra features (like RR) including notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps. It is otherwise stock LOS 15.1. The other authors/devs and I assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
Sometimes on the first install it will not find your network/sim card. If so, restart your phone and/or wipe cache.
My recommendations to install:
Install TWRP if you haven't already
3.2.3 - https://www.androidfilehost.com/?w=files&flid=39562 (forum:http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308)
Perform a backup of your current system/ROM (if coming from another ROM).
Perform a factory reset/wipe (if coming from another ROM).
Install the .zip
Install the appropriate google apps.
http://opengapps.org/. I would think nano or micro is best, ARM, and 8.1
Wipe dalvik/art cache if you install another kernel (best is fgl27's: https://androidfilehost.com/?w=files&flid=278501)
Reboot and enjoy
Here is the link to the latest ROM on the hosting website:
[2018-10-13]https://androidfilehost.com/?fid=1322778262904026799
Previous Builds:
https://androidfilehost.com/?w=files&flid=278725&sort_by=date&sort_dir=DESC
Optional Components:
BHB27 Kernel: https://androidfilehost.com/?w=files&flid=278501
BHB27 Kernel Adiutor: https://www.androidfilehost.com/?w=files&flid=48767
Remove SU/Root: https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip (Lineage OS extras:https://download.lineageos.org/extras)
TurboToast: https://play.google.com/store/apps/details?id=com.bhb27.turbotoast
I'll be back to post updates fairly regularly (~ every few weeks), but I also work full time in addition to being a dad (those of you who are know how that is ) and won't really be able to respond to PMs very well. The sources I used can be found under the post on XDA here at https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3811195 (device, vendor, and kernel trees). Thanks and God bless.
Thanks. Besides @bhb27, you've been one of the really consistent contributors for Quark.
Thanks!
Omg, there isn't words.
Thank you BHB27, Calsulfer and all the community.
Hi again all. Here's another update with major fixes (including working bluetooth audio) thanks to @bhb27!
https://androidfilehost.com/?fid=5862345805528043867
Hi, i don't knwo why I have selinux and trust systems alerts, somebody have the same trouble.
Wow thanks so much guys!
Bugs I've found: Magisk v16.6 doesn't work (breaks installing things from the playstore error 963), and using Supersu v2.82 I'm unable to restore apps using Titanium Backup.
rammx said:
Hi, i don't knwo why I have selinux and trust systems alerts, somebody have the same trouble.
Click to expand...
Click to collapse
Selinux is currently permissive, so it will give you a warning until bhb27 can finish the security policies (slightly less secure until then).
Also, the lockscreen bug will be fixed in the next release (kernel issue). You can flash bhb27's custom kernel to fix this with the current version of the ROM as well.
darkghost568 said:
Wow thanks so much guys!
Bugs I've found: Magisk v16.6 doesn't work (breaks installing things from the playstore error 963), and using Supersu v2.82 I'm unable to restore apps using Titanium Backup.
Click to expand...
Click to collapse
Supersu is probably giving you issues since root is already built into the ROM. You would most likely have to remove it using the link in the first post (optional components section). I don't know it's compatibility at that point though.
calsurferpunk said:
Supersu is probably giving you issues since root is already built into the ROM. You would most likely have to remove it using the link in the first post (optional components section). I don't know it's compatibility at that point though.
Click to expand...
Click to collapse
I was having problems with Magisk, not SuperSU. In any case, I removed SuperSU using the script and added back root using the Lineage Root ARM extras script, and I'm still having the same problems trying to restore app data or freeze system apps using Titanium Backup.
darkghost568 said:
I was having problems with Magisk, not SuperSU. In any case, I removed SuperSU using the script and added back root using the Lineage Root ARM extras script, and I'm still having the same problems trying to restore app data or freeze system apps using Titanium Backup.
Click to expand...
Click to collapse
Where you able to make magisk work or just sicked with the built in Su? I was looking for Magisk cause R-tard banks make apps that doesn't work with a rooted phone and magisk can solve that.::cyclops:
E398 said:
Where you able to make magisk work or just sicked with the built in Su? I was looking for Magisk cause R-tard banks make apps that doesn't work with a rooted phone and magisk can solve that.::cyclops:
Click to expand...
Click to collapse
I wasn't able to get Magisk to work, and currently I'm running on built-in Su. I'm waiting for the ROM to get updated in someway that will hopefully fix Magisk compatibility.
Another bug I've found is that sometimes upon reboot it says I have no SIM inserted and I get no cell service. A second reboot usually fixes the issue, but still something to potentially look into.
Hi again all. Here's another update with all of the latest changes:
https://androidfilehost.com/?fid=5862345805528047834
calsurferpunk said:
Hi again all. Here's another update with all of the latest changes:
https://androidfilehost.com/?fid=5862345805528047834
Click to expand...
Click to collapse
Thank you! Your hard work is much appreciated
FYI: This latest update did not fix Magisk (v16.6) compatibility for me. With Magisk flashed, installing apps from the app store fails with error 963, and I can't even install local apks from my sdcard. Uninstalling Magisk and flashing the LineageOS extra SU zip fixes the issue. I prefer Magisk to integrated SU because there are some Magisk modules I like.
darkghost568 said:
Thank you! Your hard work is much appreciated
FYI: This latest update did not fix Magisk (v16.6) compatibility for me. With Magisk flashed, installing apps from the app store fails with error 963, and I can't even install local apks from my sdcard. Uninstalling Magisk and flashing the LineageOS extra SU zip, fixes the issue. I prefer Magisk to integrated SU because there are some Magisk modules I like.
Click to expand...
Click to collapse
Thank @bhb27. He does all the hardest work ?. For the little that I do putting the code together, you are welcome though.
@calsurferpunk
I just tried your new ROM and I really like it. But I too had a problem with the sim not being recognized therefore, no cell service. I drive for a living and have to have reliable service. Don't know if you can solve that, but I'll keep trying your newer updates. Thanks again for all of your hard work.
nnjimmy59 said:
@calsurferpunk
I just tried your new ROM and I really like it. But I too had a problem with the sim not being recognized therefore, no cell service. I drive for a living and have to have reliable service. Don't know if you can solve that, but I'll keep trying your newer updates. Thanks again for all of your hard work.
Click to expand...
Click to collapse
Bhb mentioned this happening before and apparently resetting the cache helps. If not that, sometimes reinstalling clean fixes it. I wouldn't know what causes it, but that's what I had to do when it happened to me once on an older version. I'm on Verizon and it's currently still working for me.
I've done two clean installs and wiped cache and Dalvik cache numerous times. It recognizes my sim card for a few minutes, I make a call successfully, and then I lose service. Any help would be greatly appreciated.
nnjimmy59 said:
I've done two clean installs and wiped cache and Dalvik cache numerous times. It recognizes my sim card for a few minutes, I make a call successfully, and then I lose service. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Were you using the stock kernel (included with ROM) or bhb's (https://androidfilehost.com/?w=files&flid=278501)? I always flash his afterwards (also requires cache reset)
Also, I flashed over the previous ROM version (non clean/dirty flash), so I don't know if installing that first, then the current makes any difference.
{
"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"
}
How to get EdXposed working on 7T/7T Pro (Also Pixel Always On Display Module)
Outdated Method
Requirements :
Custom Magisk - Solohsu (After installing nornal magisk Change Update Channel to custom in Magisk settings - Paste the below link - Update Magisk and Magisk Manager ) Note : I couldn't Pass safety net with Solohsu Magisk though
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Riru Core 15+ (Magisk Module)
EdXposed Sandhook v0.4.6.0+ (Magisk Module)
Edxposed Manager (app)
AOD Module by RetroFX
https://www.coolapk.com/apk/com.retrox.aodmod
Tested on OOS 7T and 7T Pro
Blacklist Chrome and Webview in EdXposed if Chrome crashes.
How to get out of a magisk module bootloop without data loss https://forum.xda-developers.com/showpost.php?p=80654897&postcount=3
EDIT 1 :
Taichi 5.1.5+ is working flawlessly along with safetynet passing. Bootloop issue is fixed. (Official Magisk build is supported)
Modules i tried and working fine :
AOD (works better with taichi compared to EdXposed)
MINMINGUARD
INSTAPREFS
RE ENABLE SCREENSHOT
EDIT 2 : (23 Jan 2020)
New EdXposed supports Official Magisk build
https://forum.xda-developers.com/showpost.php?p=81543921&postcount=62
I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!
sk801 said:
I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!
Click to expand...
Click to collapse
Appreciate the info. I also gave it a try when I got my device yesterday.
If you don't want to have to wipe your device after tinkering around with Magisk modules, you can use fastboot to boot the image "fastboot boot image-new.img" (not flash) created by Tulsadiver in this post(https://forum.xda-developers.com/showpost.php?p=80547561&postcount=46), then delete the modules in Magisk Manager, and reboot. No data lost.
Thanks to your post i tried to install Xposed and it worked, but no module is working. I don't know how to set SELinux to permissive and if this solves the issue
I've read something about a custom Magisk Version to allow "those sepolicies present" but you have to flash this via TWRP - which we don't have on the 7T ... hm, i'm pretty lost
sk801 said:
I managed to get Edxposed v0.4.6.0 (YAHFA) installed with Riru-Core on my OnePlus 7t. Any earlier versions of Edxposed made my phone unable to boot.
I wasn't able to get any modules to work though. The logs kept saying "Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found"
After some quick google-fu I found this bug report with the same issue: https://github.com/ElderDrivers/EdXposed/issues/310
It sounds like it might be an issue with SELinux. I attempted to set SELinux to permissive, but am unsure if it worked. . . . Long story short, I gave up and wiped my phone clean.
Hope this helps someone out that is smarter than me with this stuff!
Click to expand...
Click to collapse
Thanks for sharing info!
Maybe I would give a try to Tai Chi. I badly want AOD with no notification LED in our device.
cucumbersmell said:
If you don't want to have to wipe your device after tinkering around with Magisk modules, you can use fastboot to boot the image "fastboot boot image-new.img" (not flash) created by Tulsadiver in this post(https://forum.xda-developers.com/showpost.php?p=80547561&postcount=46), then delete the modules in Magisk Manager, and reboot. No data lost.
Click to expand...
Click to collapse
That's super helpful! I'm definitely going to try that the next time I mess around with things.
For anyone wondering, Tai Chi module is not working as well. Reboots into fastboot.
I gave Edxposed v0.4.6.0 (Sandhook) a try and it boots to the bootloader, as I suspected it would. Tried with both Magisk v20 and Magisk Canary.
From what I've read they have xposed working on the OP7 and OP7Pro. Haven't read anything about the OP7TPro yet, but I'm guessing it'll boot to the bootloader like the OP7T does.
Hopefully OnePlus sent or will send out phones to one of the devs who uses xposed like C3C076 who created Gravitybox.
Updated OP to get XPOSED and AOD working.
Does it work with Greenify? I tried it with normal YAHFA EdXposed and Greenify didn't recognize the module while EdXposed did "activate" it... Weird
Aswin08 said:
Note : I couldn't Pass safety net with Solohsu Magisk though
Click to expand...
Click to collapse
You can use the No Device Check xposed module (https://repo.xposed.info/module/com.pyler.nodevicecheck) to at least get "ctsProfile: true". Unfortunately, basicIntegrity will still be false.
Hey OP!
The OP7T Pro has an installer for those that aren't rooted yet and want the modded Magisk version for EdXposed compatibility and it should work on the 7T non-pro.
[Magisk][ROOT][EdXposed]Auto install tool - Magisk Installer for OnePlus 7T Pro = (https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471)
I was already rooted, so haven't tried it myself, but it may speed up the process for those who aren't yet rooted.
cucumbersmell said:
Hey OP!
The OP7T Pro has an installer for those that aren't rooted yet and want the modded Magisk version for EdXposed compatibility and it should work on the 7T non-pro.
[Magisk][ROOT][EdXposed]Auto install tool - Magisk Installer for OnePlus 7T Pro = (https://forum.xda-developers.com/7t-pro/how-to/magisk-auto-install-tool-magisk-t4001471)
I was already rooted, so haven't tried it myself, but it may speed up the process for those who aren't yet rooted.
Click to expand...
Click to collapse
Yeah I checked it, but am not sure if they have used same custom version of Magisk like here or different.
If its same thn safetynet would fail again.
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
Which one did you use? I am looking to install Greenify also...
PD: Have you noticed (although I think it is too soon to ask) any battery improvements with Greenify?
sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
I got what you got in post#2. So, wondering what's your steps now?
sk801 said:
Edexposed is up and running! For some reason my safetynet has no problems. I have no idea why.
So far I have MinMinGuard and Greenify working. GravityBox doesn't work, but I can definitely live with that for now.
Click to expand...
Click to collapse
Are you using this as your Update Channel in Magisk?
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Which version of EdXposed are you using?
EdXposed-SandHook-v0.4.6.0_beta.4471
or
EdXposed-YAHFA-v0.4.6.0_beta.4471
Gravitybox is the main reason I use xposed, but I've also got modules for Burnt Toast Revived and Smooth System Progress Bars running with no issues.
It's great getting xposed features through EdXposed so quickly on newer android versions! I remember the wait for xposed back in the day.
Poesini said:
Which one did you use? I am looking to install Greenify also...
PD: Have you noticed (although I think it is too soon to ask) any battery improvements with Greenify?
Click to expand...
Click to collapse
zyu0090 said:
I got what you got in post#2. So, wondering what's your steps now?
Click to expand...
Click to collapse
cucumbersmell said:
Are you using this as your Update Channel in Magisk?
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Which version of EdXposed are you using?
EdXposed-SandHook-v0.4.6.0_beta.4471
or
EdXposed-YAHFA-v0.4.6.0_beta.4471
Gravitybox is the main reason I use xposed, but I've also got modules for Burnt Toast Revived and Smooth System Progress Bars running with no issues.
It's great getting xposed features through EdXposed so quickly on newer android versions! I remember the wait for xposed back in the day.
Click to expand...
Click to collapse
So after about 24 hours of running edexposed I started noticing some bugs. Mainly I stopped receiving text messages until I rebooted my phone. I experienced the same thing and worse on my last phone the Essential PH-1 when things like this weren't really supported. I don't know what causes it. So be wary and don't blame me if a bricked phone happens or your alarm stops working and you're late for work. (Don't ask me how I know )
Nevertheless I followed what @Aswin08 has in the first post:
Update Magisk through Solohsu channel:
https://raw.githubusercontent.com/solohsu/magisk_files/master/custom_builds/release.json
Install Riru-Core through Magisk download
Install EdXposed-SandHook-v0.4.6.0_beta.4471
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0
sk801 said:
Install EdXposed-SandHook-v0.4.6.0_beta.4471
https://github.com/ElderDrivers/EdXposed/releases/tag/v0.4.6.0
Click to expand...
Click to collapse
I'm running the YAFHA version and was trying to determine if one is performing differently than the other in regards to Safety Net, modules that work/don't work, etc.
cucumbersmell said:
I'm running the YAFHA version and was trying to determine if one is performing differently than the other in regards to Safety Net, modules that work/don't work, etc.
Click to expand...
Click to collapse
Have you noticed any instabilities on YAFHA? With any modules or the system in general?
It would be nice to a have GravityBox working and stable on this device.
This morning Magisk notified me about the update available (from 23.0 to 24.1). To cut the long story short, it was a complete failure and I was able to revert back to 23.0.
First upgrade went unsuccessful. Magisk stopped loading. Root was lost. Yet it has succeeded to write something into boot, so uninstalling app and reinstalling 23.0 didn't help. Reboot into patched BL didn't give 23.0 root permissions to patch the BL. I have succeeded to patch stock BL with 24.1 and boot into that, then install 24.1. This has root but fails safety net. Now you need to manually flash safetynet-fix-v2.2.0.zip because Magisk does not do magisk hide anymore. That is lost and module library is lost, plus safety net check tool is lost too. OK, with the fix it can pass the basic check, but for example Citi mobile app sees the root anyway. I have decided to downgrade to 23.0 because I only see a loss in functionality without any benefits.
Now you cannot patch BL with 23.0 if you have 24.1 there. You cannot do it if you flash stock BL but have traces of 24.1 app. The only thing which worked for me: in the functional 24.1 app select 'uninstall magisk', 'complete uninstall', then do root from start: install app 23.0, boot into patched with 23.0 BL, direct install from the app. Half a day is lost.
To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github. So long as the project is there that shall work.
Bottom line: beware magisk above 23.0!
Bro , you got wrong, just upgraded magisk 24.1,
please read the changelogs of new version ....
https://github.com/topjohnwu/Magisk/releases
{
"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"
}
unknow91 said:
Bro , you got wrong, just upgraded magisk 24.1,
please read the changelogs of new version ....
https://github.com/topjohnwu/Magisk/releases
View attachment 5522143View attachment 5522145View attachment 5522147
Click to expand...
Click to collapse
I was not happy with the whole experience and with the final result when it was finally working. If someone is like me here is the warning and the way to downgrade or prevent an upgrade.
Then an important thing to note: this is the point when the author went to the other side of the barricade, which is reflected in the changelog. From this point it will be a completely different app.
magisk hide not working?
So bad. Same Problem. Magisk Sygisk not working with XPosed. I need Xposed and Magisk Hide/Sygisk.
Thats a wrong change. Wjy they do that? Its so bad. It was wokring and in a new version not. Bad change in Magisk history.
To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github.
Click to expand...
Click to collapse
@rampitec, can you please share the link?
MasterBody said:
magisk hide not working?
Click to expand...
Click to collapse
It is removed from magisk. That's in the whatsnew.
thexile said:
@rampitec, can you please share the link?
Click to expand...
Click to collapse
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json
MasterBody said:
magisk hide not working?
Click to expand...
Click to collapse
setting, configure denylist
@rampitec:
You're my liberator after I spent hours with that crap. I wonder how you came up with the URL as I could only find the resolved host topjohnwu.github.io mentioned a Wireshark capture to see what the Magisk app tries to retrieve when the default "stable branch" is selected. Maybe I was overcomplicating things.
Anyway, while I might be missing something here in general, it is difficult not to indulge oneself in a rant because what kind of a retarded bull**** is that to remove a feature (whether being replaceable by that Zygisk stuff with yet again addition effort or not yet to be seen) which allows to get apps at least halfway running by hiding the fact of having root access (whereas the necessity also only arises thanks to moronic programming and nowadays pseudo-security paranoia, especially by insecure-by-definition banking apps on the very same device) with no damn easy way to downgrade again or at least select the version one wants.
It is beyond comprehension why also that Magisk manager doesn't offer to simply select the version of preference in case a newer one breaks what was working before. God forbid, instead, even the version 23.0 apparently tries to load parts of the newer 24.1 one now which leads to (non-working) duplicates of the manager ("Magisk" & by default "Settings" then) instead of repackaging itself to only one instance of course.
It is annoying enough that regular application providers forces users into that constant having-to-update-crap but it is almost real life satire for me that even nominally sophisticated ones such as that John Wu Magisk guy* follows the same idiocy.
* who owes me hours of my lifetime while I owe you at least a beer, rampitec!
Everyone needs to start posting their devices and if they are 64 bit ONLY or 64 bit and 32 bit capable because Magisk 24.1 does not support any device that supports 32 bit. If you subscribe to TopJohn Wu, on Twitter, you get notifications with explanations.
https://twitter.com/topjohnwu?t=e4SCxqjXOBnGIqQLc1uNJg&s=09
We can not understand why you get the results you have unless we know your device and OS and you need to know if your device is 64 bit ONLY, or 64 bit and 32 bit capable.
Pete R
little-endian said:
@rampitec:
You're my liberator after I spent hours with that crap. I wonder how you came up with the URL as I could only find the resolved host topjohnwu.github.io mentioned a Wireshark capture to see what the Magisk app tries to retrieve when the default "stable branch" is selected. Maybe I was overcomplicating things.
Click to expand...
Click to collapse
Not much of my work really. Found a link on youtube how to set the channel to some version. Go to github magisk repo, browse for needed version, select view file, select "raw", copy the URL of the page. This is the update channel.
Thank you! It worked for me. After going back to 23, I have changed the update channel url to 0.0.0.0, so there is no update at all. And it's back to normal again.
rampitec said:
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json
Click to expand...
Click to collapse
Application hiding process is done, thank you very much. I've been editing the 23.0 version with apktool m for hours. I couldn't think that only the url link would be the solution to get rid of the version upgrade, I was surprised and a very good idea came to my mind. I will integrate the url into the classes.dex file. The new version is a complete disgrace, too bad, don't install it. Tr to En Google Translate
Have you ever seen that Magisk 23 recognizes the root but when update it gets N/A and the app doesn't work but SuperUser still get access. I tried to do trough Path Boot andZip Odin(S7 Edge Android 8.0)
I formatted the device, re-do Stock Rom but dont work.
the App 24, 24.1 or Canary keeps not working (N/A). Less than 8.0.7 work normally
I applied a custom with Android 10,11 and 12. It works
You can patch boot.img over magisk 23.0 apk installer in android and flashed this patch_magisk_boot.img over fastboot / adb on pc. Magisk 23.0 is now work. Downgrade 24.1. Magisk Hide is back and edxposed works.
tI tried to do this, but the magisk 23 app doesn't allow me to patch without updating to 24.1 first..
RootPoG0 said:
tI tried to do this, but the magisk 23 app doesn't allow me to patch without updating to 24.1 first..
Click to expand...
Click to collapse
uninstall magisk befor. magisk root and app.
rampitec said:
...Half a day is lost...
To prevent it from offering any further upgrade I went into app settings, selected custom update channel and pasted there a link to the 23.0 manifest from github. So long as the project is there that shall work.
Bottom line: beware magisk above 23.0!
Click to expand...
Click to collapse
rampitec said:
That's the stable 23.0 from github: https://raw.githubusercontent.com/t...4e59f631280cc26ccc6d40a7cf04f7f37/stable.json
Click to expand...
Click to collapse
Thank you! I had a feeling something weird was going on and I was ignoring the update notification for a few days now. Good thing I did some digging before installing magisk 24.1.
Hello! I'm on a galaxy s9+ running android 10.
I didn't pay attention and clicked on update, and i regret it so much!
i am on magisk 24.1 with zygisk and ramdisk both set to "yes".
I have the uiversal safetynet fix v2.2.1 and google play services and play store hidden on the denylist
I can't pass safetynet, it fails on "basic integrity" and on "cts profile match"
so upset i updated!
{
"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"
}
isn't it yet to be sold and aquired?
more_than_hater said:
isn't it yet to be sold and aquired?
Click to expand...
Click to collapse
I believe it is out in China already
JPower123 said:
I believe it is out in China already
Click to expand...
Click to collapse
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Wasim_Bu said:
Yes, it is out in China and launching on Feb 7 here in India! I'm interested in this phone...
Click to expand...
Click to collapse
What about USA? EU?
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
Pretty sure it's also Feb 7 for USA, not sure about EU, but probs same
I am also waiting for India, to install OOS.
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
H4X0R46 said:
What is kernelSU? I'm wondering if Magisk works on it, it SHOULD being that it's just a patched boot image. But I'm curious to know
Click to expand...
Click to collapse
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
luckychukiye said:
What about USA? EU?
Click to expand...
Click to collapse
It's launching on Feb 7th for USA and UK!
huangsijun17 said:
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
H4X0R46 said:
A new root solution? Does Magisk not work on the OnePlus 11 or are they both viable options? I'm confused now.
Click to expand...
Click to collapse
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
huangsijun17 said:
A new root solution, can run with Magisk at the same time.
Because when I just got the phone, there was no TWRP and ZIP flashing package. I'm having a hard time installing Magisk directly. But after I gave Magisk Manager Root permission with KernelSU, I installed Magisk directly.
Click to expand...
Click to collapse
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
toolhas4degrees said:
When you root with magisk. You need to unlock the bootloader. Then install magisk manager app. Pull your stock boit.img from stock firmware and put it on phone. Open magisk manager and select install then patch boot.img . Then copy the generated image magisk patched image to computer adb folder. Then reboot phone to fastboot. On computer type fastboot boot (name of patched boot.img).img phone will reboot and have root. Go back to magisk and select direct install then reboot.
Click to expand...
Click to collapse
No. I never exported boot.img or boot_init.img from my phone. There is also no unpacking payload.bin to extract them. After installing KernelSU and KernalSU Manager, I use KernelSU to give Magisk Manager a root privilege. Magisk Manager will automatically install Magisk.
In addition, Magisk needs to patch boot_init.img in devices pre-installed with Android 13, and the flash command is also fastboot flash boot_inti boot_init.img.
huangsijun17 said:
View attachment 5804063
Click to expand...
Click to collapse
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
loshabih said:
Hi,
can you pleaaase try this app if it works with root or no??
CIB Egypt Mobile Banking - Apps on Google Play
The CIB Mobile Banking app is designed to meet all your banking needs.
play.google.com
Click to expand...
Click to collapse
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
huangsijun17 said:
View attachment 5811645
View attachment 5811647View attachment 5811651
Three interfaces: GKI supported, GKI not supported and already installed. In addition, for devices that do not support GKI, it is also possible to compile the kernel yourself.
Click to expand...
Click to collapse
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
loshabih said:
thanks for your reply,
my main question was if you have kernelSU can you try the app that i mentioned and see if it works or no?
other question can you share any tutorial how to build GKI kernel ?
Click to expand...
Click to collapse
For devices that support GKI 2.0, you can directly download the corresponding version of boot.img from Github Action to flash in.
huangsijun17 said:
I installed Magisk and KernelSU at the same time, so I can't test the APP for you. But in theory, KernelSU uses a whitelist system, and unauthorized software cannot detect the existence of the su file.
Click to expand...
Click to collapse
can you lock the bootloader while you have kernelSU? as the app is checking the bootloader status?