Related
Hello, I've been trying to install systemless root, suhide, systemless xposed, etc. on Sultan's rom with my OP3 (most recent update 12/11/16) - [method found here: http://forum.xda-developers.com/showpost.php?p=69651636&postcount=314] but I keep running into a problem. I flashed the update so I got a clean version of the rom which removed any previous root stuff, I go through the systemless code for the terminal and flash SuperSU, but every time it won't boot. Simply goes to the CM logo and pulses.
Is there something I'm doing wrong? I've tried a few different methods of flashing but always the same. When I reboot back into recovery and re-flash the rom, it boots up just fine. I also tried locating the /su files to delete prior to doing any installing but they aren't there.
Really just looking to get a systemless root set up on my OP3! Any help would be greatly appreciated if anyone has a process that works on Sultan's. Thank you very much in advance!
Don't use suhide with latest November security update, it bootloops. But this is also mentioned in the suhide thread.
meiser said:
Don't use suhide with latest November security update, it bootloops. But this is also mentioned in the suhide thread.
Click to expand...
Click to collapse
Thanks for the info. Unfortunately, I haven't even been able to get that far. It seems now any time I try to flash root (currently trying SuperSU v2.79) it boots to the CM screen, reboots, then just hangs at the CM screen and won't boot past that. I have to go back in and reflash CM13 in order to get it to boot. Any thoughts on why?
Is there another work around for system/systemless root & Xposed that works with Pokemon Go and Android Pay?
I've tried removing all instances of root, but when I use Root Checker Pro Free it tells me that I'm not rooted but:
Stage 1: Superuser App not installed
Stage 2: Superuser binary files installed
Stage 3: Root User Account: Success
I can't figure out why exactly...
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.
For this procedure is necesary unlock the bootloader?
Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.
Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!
And how are we gonna unlock the bootloader?
Is there a way to do that?
Magisk Hide doesn't seem to work on the DirecTVnow app. Has anybody else been able to watch shows on a rooted device?
Is anybody rooted using only SuperSU and can turn off Superuser and watch shows? (This works on my Galaxy Tab S2)
I attempted to root only using SuperSU before and my phone went into a recovery loop. It would not boot back into Android.
Any other solutions are appreciated.
Did you ever figure this out? I am having the exact same issue on the exact same device.
drt054 said:
Magisk Hide doesn't seem to work on the DirecTVnow app. Has anybody else been able to watch shows on a rooted device?
Is anybody rooted using only SuperSU and can turn off Superuser and watch shows? (This works on my Galaxy Tab S2)
I attempted to root only using SuperSU before and my phone went into a recovery loop. It would not boot back into Android.
Any other solutions are appreciated.
Click to expand...
Click to collapse
Have you tried magisk hide? It's in the menu of the magisk app
Forgot all about this. Using latest Magisk and Hide I am able to use the DirecTVnow app. Although just updated to Pie and Magisk won't yet pass safetynet check so Hide may not work on some apps.
drt054 said:
Forgot all about this. Using latest Magisk and Hide I am able to use the DirecTVnow app. Although just updated to Pie and Magisk won't yet pass safetynet check so Hide may not work on some apps.
Click to expand...
Click to collapse
I'm using Magisk version 16.7(1674) and Flash Kernel 3.01 on Pie. Magisk passes safety net and I can use the DirecTV app without problems.
Samsung Galaxy S8+ (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8+ (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.09-B01-DREAM2QLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-DREAM2QLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Could you boot an AOSP rom off of it?
Slypnslyde said:
Yessssss finally a solution. But I can't do it lol I'm running Oreo
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
psych0r3bel said:
So downgrade - flash PartCyborg's rom, I think it's doable while on Oreo. Don't quote me on this though. I'll just be very sad if it's not possible.
Click to expand...
Click to collapse
Totally possible
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Cool I hope it do it right
Sent from my SM-G955U using Tapatalk
ParisInLove said:
Totally possible
Click to expand...
Click to collapse
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
gerryl432 said:
Just to clarify, when I downgrade from 8.0 to 7.0 to obtain root, boot the rooted ROM then
install busybox and safestrap.apk before reflashing Oreo and that will run alongside Rooted QL1 in a second ROM slot under safestrap?? I apologise if I misread instructions, it's been a while as I haven't used safestrap since my s3 years ago
Edit: just saw the ROM slots not working, and the new Oreo modified thread. Lol
Click to expand...
Click to collapse
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
siulmagic said:
Were is this oreo thread you mention? iv been searching for it, but i cant find it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
gerryl432 said:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
Click to expand...
Click to collapse
thank you.
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
kirito9 said:
@afaneh92 Do you have sources for this recovery? As in how did you get it to work with android 7 when safestrap support ended in KK. I'd like to boot it on LP+.
Click to expand...
Click to collapse
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Would this allow us to flash magisk? Or a custom kernel?
afaneh92 said:
Here its
https://github.com/mohammad92/android_bootable_recovery-safestrap
We have permissive root on S8, S8+ and Note 8 thats why its working on 7.0+
Click to expand...
Click to collapse
Thank you. So as long as you can get root and make the selinux permissive it should work?
TacoTuco said:
Would this allow us to flash magisk? Or a custom kernel?
Click to expand...
Click to collapse
No.
kirito9 said:
Thank you. So as long as you can get root and make the selinux permissive it should work?
Click to expand...
Click to collapse
I think yes.
afaneh92 said:
No.
I think yes.
Click to expand...
Click to collapse
Could a Dev make a DT and possibly build a rom with this new freedom to flash things? Cause as far as I know all you need is a DT and a way to compile and you should be fine right? Or will the whole no custom kernel thing prevent that.
Would I be able to install this on Nougat, and then update to Oreo and keep it installed?
Then from there add a Nougat ROM with root so that I could update it and use my root stuff.
This is awesome! Recovery is working great so far! Pls let me know of any roms working with this method I can't wait to try it out!
So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.
NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's
NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.
NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename
NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.
In the meantime, is someone running GSI as a daily driver?
sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.