Related
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device
xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)
dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread
Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt
Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip
I'm a little lost on the differences between the shield and every other android phone I've owned. What difference does the developer image offer compared to simply unlocking the bootloader and installing magisk through TWRP on the shipped firmware?
Ultimately I want to root for all the obvious reasons, but also use magisk hide to keep PSVue and the like still working with root undetected. It seems that the developer image is pre-rooted, can that be hidden?
Thanks for any clarification
tstack77 said:
I'm a little lost on the differences between the shield and every other android phone I've owned. What difference does the developer image offer compared to simply unlocking the bootloader and installing magisk through TWRP on the shipped firmware?
Ultimately I want to root for all the obvious reasons, but also use magisk hide to keep PSVue and the like still working with root undetected. It seems that the developer image is pre-rooted, can that be hidden?
Thanks for any clarification
Click to expand...
Click to collapse
No it is not, as long as your bootloader is unlocked and you follow the directions on the thread how to install Magisk you will achieve root
jionny said:
No it is not, as long as your bootloader is unlocked and you follow the directions on the thread how to install Magisk you will achieve root
Click to expand...
Click to collapse
You don't get true root with the ota firmware though.
You won't have write access to the root dir.
Which you will if you use the developer image through adb, or by disabling dm-verity.
You won't be able to do that on the ota.
mLgz0rn said:
You don't get true root with the ota firmware though.
You won't have write access to the root dir.
Which you will if you use the developer image through adb, or by disabling dm-verity.
You won't be able to do that on the ota.
Click to expand...
Click to collapse
So on non dev if I disable dm verity with magisk, I can write to system.
Or is it not that simple.
Sent from my SM-G965F using XDA-Developers Legacy app
Largewoodenspoon said:
So on non dev if I disable dm verity with magisk, I can write to system.
Or is it not that simple.
Sent from my SM-G965F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No you won't be able to get write access on the non dev.
mLgz0rn said:
No you won't be able to get write access on the non dev.
Click to expand...
Click to collapse
I was referring to the Pro version
jionny said:
I was referring to the Pro version
Click to expand...
Click to collapse
Does not matter if it's the pro version or not.
You can only get write access to the root dir using the developer image.
mLgz0rn said:
Does not matter if it's the pro version or not.
You can only get write access to the root dir using the developer image.
Click to expand...
Click to collapse
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2
jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
On what firmware version?
I doubt you can write to the /system and /data dir if you are on 7.2+.
---------- Post added at 14:37 ---------- Previous post was at 14:31 ----------
Roamin64 said:
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2
Click to expand...
Click to collapse
Which image was that?
You can't get write access on the ota that comes with the updater on the shield without modifying the kernel and build.prop.
Hence why they are making a developer image that is prerooted.
jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
mLgz0rn said:
On what firmware version?
I doubt you can write to the /system and /data dir if you are on 7.2+.
---------- Post added at 14:37 ---------- Previous post was at 14:31 ----------
Which image was that?
You can't get write access on the ota that comes with the updater on the shield without modifying the kernel and build.prop.
Hence why they are making a developer image that is prerooted.
Click to expand...
Click to collapse
It was the boot.img posted by ACiDxCHRiST in that post : https://forum.xda-developers.com/showpost.php?p=78496132&postcount=163
He has since taken down the boot.img file, but I had saved it in my pc when he posted it. I never flashed it , because I didn't want to brick anything. That is why I had only "fastboot boot boot.img" . Worked fine on 7.2.1 , and then again worked fine on 7.2.2. I haven't tried to root 7.2.3 yet. If you need that exact file to test , I can provide it to you in a few hours when I get back home.
Roamin64 said:
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2
Click to expand...
Click to collapse
Exactly and I also use x-plore
Roamin64 said:
It was the boot.img posted by ACiDxCHRiST in that post : https://forum.xda-developers.com/showpost.php?p=78496132&postcount=163
He has since taken down the boot.img file, but I had saved it in my pc when he posted it. I never flashed it , because I didn't want to brick anything. That is why I had only "fastboot boot boot.img" . Worked fine on 7.2.1 , and then again worked fine on 7.2.2. I haven't tried to root 7.2.3 yet. If you need that exact file to test , I can provide it to you in a few hours when I get back home.
Click to expand...
Click to collapse
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .
mLgz0rn said:
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .
Click to expand...
Click to collapse
That boot.img was patched , most probably by magisk itself. Anyways, sent you the link via PM.
mLgz0rn said:
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .
Click to expand...
Click to collapse
magisk makes the modifications,, you patch the boot img with magisk then transfer it to your pc then abd fastboot flash boot patched_boot.img... really is that simple.. Has nothing to do with the developers image
Hi, just got around to rooting my Kindle. Currently using SuperSu, curious if anyone has used Magisk with this tablet? Any reason not to do so?.
Thanks in advance.
I've debated doing this as well, as I don't like having to default grant everything root access.
As far as I understand though, none of your root apps/su requests can modify the system partition, so I haven't tried it yet.
@diplomatic is this true for the bootless root method without dm-verity?
No, you can modify /system if there's no dm-verity, @Kctucka
diplomatic said:
No, you can modify /system if there's no dm-verity, @Kctucka
Click to expand...
Click to collapse
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Kctucka said:
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Click to expand...
Click to collapse
Thanks, guys!
SuperSU access workaround
Kctucka said:
I've debated doing this as well, as I don't like having to default grant everything root access.
.....
Click to expand...
Click to collapse
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Dan_firehd said:
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Click to expand...
Click to collapse
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Kctucka said:
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Click to expand...
Click to collapse
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Yeah will do! I'll probably try it tomorrow or the day after.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
So far, all of my root apps detect root, except for titanium backup. I've messed around with it for a bit but haven't been able to figure it out. I'm guessing it has something to do with the location of the su binaries.
Also of note, FlashFire did not work at first. I realized that this is because the timebomb method we used along with the older app version, was from before Magisk existed. I grabbed the latest version of FlashFire from apk mirror, and it started without issues. I haven't tested by flashing anything yet though.
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
All in all, this is a pretty solid root method, but obviously non ideal due to the locked bootloader.
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Kctucka said:
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
Click to expand...
Click to collapse
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into this after so long I feel like a n00b again.
koop1955 said:
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into thhis after so long I feel like a n00b again.
Click to expand...
Click to collapse
That option was all I did to remove SuperSu. Then I followed the instructions here:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
Didn't take long to get it working.
And the time change was to get the version of FlashFire working that was compatible with the version of SuperSu we could run. See this post for more info if you're curious:
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-xposed-t3722252
But with this new method, the most recent version of FlashFire works, as it's compatible with Magisk. The older version of FlashFire I had is not.
Also, I'm a noob myself. That's why I tagged diplomatic again, to correct the dumb things I might have said
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
koop1955 said:
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
Click to expand...
Click to collapse
That's awesome! Would that pass signature verification? Or would it be through hacked fastboot?
Also, that'd make it much easier to set up the device after a softbrick. FlashFire would be good to flash backups right away.
Kctucka said:
.....
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
.....
Click to expand...
Click to collapse
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Dan_firehd said:
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Click to expand...
Click to collapse
My kernel tweaks were done with KA Mod Reborn, using the "apply on boot" setting:
https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105
I added 260 MB ZRAM with a swapiness of 10. You can also tweak low memory killer, laptop mode, and a whole bunch of other dials that I don't mess with as I don't fully understand what they do.
Kernel changes could also be done with a number of different apps that do similar things.
Unfortunately, the bootless root method doesn't give root on boot, so it and also most Magisk modules won't work. Can't think of a workaround currently.
Kctucka said:
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Click to expand...
Click to collapse
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
That's super beneficial then, you can swap back and forth easily depending on what you need.
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
How about just swapping the install-recovery.sh script for suboot.sh on devices that don't have dm-verity?
I think that's pretty much what SuperSU does as well.
That would give root much earlier during boot and not depend on the extra App.
Probably doesn't even need to run mtk-su each boot then either.
Yeah, that's on the right track, @k4y0z. What you can probably use is a modified SU_MINISCRIPT section of suboot.sh, at least as a starting point. That is the code that needs to be run as root. What should be changed is the path to the magiskinit & magisk binaries. Those could be placed somewhere on /system. You would only need mtk-su if selinux needs to be permissive. But I suspect it does for the 'magiskpolicy --live' call. (But then how does SuperSU handle it with enforcing?)
Hello guys!
I came here to ask help for rooting and get TWRP working on A20s device...
If anyone could help, you're welcome!
On Telegram group, we are trying to boot TWRP (yes, it does flash but get stuck on boot with the error "SECURE CHECK FAIL: recovery.img").
I already tried to flash it with null vbmeta and patching the entire AP file via Magisk but got no success (with magisk patching it says "SECURE CHECK FAIL: for every element that is verified on boot (boot.img, recovery.img, vbmeta.img)"
Any news, tip, help or if you just wanna laugh about this device, join our group > https://t.me/GalaxyA20SS
codeblvnc said:
Hello guys!
I came here to ask help for rooting and get TWRP working on A20s device...
If anyone could help, you're welcome!
On Telegram group, we are trying to boot TWRP (yes, it does flash but get stuck on boot with the error "SECURE CHECK FAIL: recovery.img").
I already tried to flash it with null vbmeta and patching the entire AP file via Magisk but got no success (with magisk patching it says "SECURE CHECK FAIL: for every element that is verified on boot (boot.img, recovery.img, vbmeta.img)"
Any news, tip, help or if you just wanna laugh about this device, join our group > https://t.me/GalaxyA20SS
Click to expand...
Click to collapse
Did you disable dmverity?
ninjasinabag said:
Did you disable dmverity?
Click to expand...
Click to collapse
Yes, i compiled a kernel for it with dm verity disabled and our dev built a TWRP with it.
codeblvnc said:
Yes, i compiled a kernel for it with dm verity disabled and our dev built a TWRP with it.
Click to expand...
Click to collapse
Is it now rootable?
codeblvnc said:
Yes, i compiled a kernel for it with dm verity disabled and our dev built a TWRP with it.
Click to expand...
Click to collapse
No, there's a package to disable dmverity.
You can't just tack it on to a recovery.
The OS needs removal of encryption and bit checking for stability before it'll load with a custom recovery installed, otherwise your device will read as insecure and will refuse to load.
physwizz said:
Is it now rootable?
Click to expand...
Click to collapse
Not yet, my friend
ninjasinabag said:
No, there's a package to disable dmverity.
You can't just tack it on to a recovery.
The OS needs removal of encryption and bit checking for stability before it'll load with a custom recovery installed, otherwise your device will read as insecure and will refuse to load.
Click to expand...
Click to collapse
Oh, understood...
But how can i do this? Any guide or tip?
codeblvnc said:
Not yet, my friend
Click to expand...
Click to collapse
Keep working on it
physwizz said:
Keep working on it
Click to expand...
Click to collapse
Sure!
a twrp is available on telegram a20s channel
Techmaestroke said:
a twrp is available on telegram a20s channel
Click to expand...
Click to collapse
The problem is that you can't flash it with Odin