Hey guys, I just recently did a systemless root of my pixel 2 XL and I haven't been able to get it to bypass safetynet, the only app I use right now that requires root is Adaway and I had tested to see if it was causing the trouble by uninstalling it which has proven fruitless, any ideas on how to get past safetynet would be great, even if it means rooting my phone again differently.
Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager
Pyr0x64 said:
Are you running a custom kernel?
Custom kernels will hide the bootloader unlock from SafetyNet
Is there a particular app you need to hide root from? if so you can do this with Magisk Hide in Magisk Manager
Click to expand...
Click to collapse
I'm not running a custom kernel, and the apps I want to use won't work even if root is hidden, one's my banking app for my bank back in england.
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too
Pyr0x64 said:
If you flash a custom kernel to hide the bootloader unlock, you should pass safetynet.
For your banks app to work, you need to pass safetynet and hide root
I'm running magisk with Flash kernel. My phone passes safety net and under Magisk Hide, I've selected my Halifax banking app so it works.
Click to expand...
Click to collapse
henderjr said:
Same here with Flash Kernel and Magisk Hide. Safetynet passes.
Edit: I'm running beta Magisk but regular v16 works too
Click to expand...
Click to collapse
Okay, I'll try doing that, will update on the results
No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.
Are you using Xposed?
No, I'm not using xposed
Brawler6216 said:
No luck, it all flashed fine but it's still not working.
EDIT: I don't know why my screenshot is so big.
Click to expand...
Click to collapse
Why are you flashing the dtbo.img???
Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Because is says so in the directions
Images (installation and upgrade):
Install the latest adb and fastboot:*https://developer.android.com/studio...orm-tools.html
Grab the boot and dtbo images from the download site above
(OPTIONAL) Patch the boot image with*Magisk*if so desired
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Do the same with the dtbo image:
Code:
fastboot flash dtbo <dtbo_image_name>.img
???
Reboot and profit!
Click to expand...
Click to collapse
Did it work?
Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.
Badger50 said:
Why are you flashing the dtbo.img???
Click to expand...
Click to collapse
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.
Brawler6216 said:
That's what the installation instructions were for installing flash kernel...?
I will point out I'm not anywhere near well versed in this.
Click to expand...
Click to collapse
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:
Badger50 said:
The post right before your by TonikJDK laid it out perfectly for you. It's exactly the same procedure I use. And SN passes just fine for me as well :good:
Click to expand...
Click to collapse
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.
Brawler6216 said:
K, I'll try his instructions, but I've not done it with twrp, so that'll be new to me.
Click to expand...
Click to collapse
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:
TonikJDK said:
Flash your system back to stock with the flash all bat file. Remove the -w from the bat file to save data.
Copy the magisk zip to your downloads folder.
Remove your pin and fingerprint.
Boot to twrp and install the magisk zip.
Reboot.
Check if the magisk app is installed, if it isn't grab the APK from inside the zip and install it. If you had to install it, reboot once more.
That is exactly what I do each time and I have root and I pass saftey net. Just did it a couple of hours ago.
---------- Post added at 03:03 AM ---------- Previous post was at 02:53 AM ----------
And while you are at it, grab 16.2 from the Beta thread.
Click to expand...
Click to collapse
Badger50 said:
Gotta learn sometime my friend. It's not near as hard as you might think. Here's a little more detail for you if it helps :good:
Click to expand...
Click to collapse
It passed! Awesome thank you, guys so much!!
Brawler6216 said:
It passed! Awesome thank you, guys so much!!
Click to expand...
Click to collapse
Congrats my friend. Well done! ???
Now you just need to dark theme that sucker! ?
Badger50 said:
Congrats my friend. Well done!
Now you just need to dark theme that sucker!
Click to expand...
Click to collapse
When you're too excited that it passed safetynet
Related
Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
You can use Flashfire.
nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?
Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?
Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.
fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again
nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....
FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
uutsav said:
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
Click to expand...
Click to collapse
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
tropicanapure said:
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
Click to expand...
Click to collapse
And you passed safety net
uutsav said:
And you passed safety net
Click to expand...
Click to collapse
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
tropicanapure said:
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
Click to expand...
Click to collapse
I tried flashing unsu and it asked me to flash the stock boot image in TWRP.... Any ideas mate..
I am sorry to keep bugging.... But I am lost
Look for boot.img in the ROM zip and flash it.
I was just about to say that myself. See
https://forum.xda-developers.com/showpost.php?p=63615067
Like the previous post said, you need a pristine boot.img and your ROM zip is the ideal place to find it.
Dirty flash your Beta27 again and it should be clean, THEN reboot and then install Magisk
Now i flashed beta 28, flashed recovery and flashed magisk again... While I was able to flash it... But getting safety net error....
My life is finished...
If you were able to install magisk then you should take this to the official magisk support thread. You are more like to get a better variety of suggestions there.
Just saying.
So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.
Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T Global (not Indian or European) version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own Global OP7T.
Link : https://androidfilehost.com/?w=files&flid=302500
has anyone tried this one yet?
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
damn i want to do it but i am afraid some of my apps will stop working cause idk if magiskhide will work at current time
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
23333 said:
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
Click to expand...
Click to collapse
ty for the reply i might grow a few and give it a shot hopefully magiskhide is working so certain apps cant detect that i am rooted
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
xrelic7 said:
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
Click to expand...
Click to collapse
Are you using Global or Indian HD65AA ? Not getting an option to directly install means somehow the patched image did not boot and the original imaged booted.
imakul8 said:
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
Click to expand...
Click to collapse
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
zeusofyork said:
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
Click to expand...
Click to collapse
Yes, that's what I have.
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
Click to expand...
Click to collapse
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
Click to expand...
Click to collapse
You're right. Just skip that step 3.
imakul8 said:
You're right. Just skip that step 3.
Click to expand...
Click to collapse
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
ricksrod said:
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
Click to expand...
Click to collapse
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you. ?
imakul8 said:
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you.
Click to expand...
Click to collapse
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
ricksrod said:
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
Click to expand...
Click to collapse
Just the first two. Not recovery mode.
imakul8 said:
Just the first two. Not recovery mode.
Click to expand...
Click to collapse
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
ricksrod said:
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
Click to expand...
Click to collapse
Stable is working for me, but good that you got it working. ?
Can someone check if magisk hide is working properly? Thanks
Jeens99 said:
Can someone check if magisk hide is working properly? Thanks
Click to expand...
Click to collapse
It works. Snapchat and my banking app don't like root. They're working fine.
Hi all, I am very confused. I am trying to figure out how to root this phone. I read the instructions for magisk and attempted to patch the boot.img file linked in the ArrowOS post (https://drive.google.com/file/d/1o-4T4hfEtxECIss-DVSSYAM1Kvy2iDN9/view?usp=sharing)
But whenever I flash that patched boot.img I am getting stuck on a bootloop. And then I found someone already patched the boot.img on August (this post) but that boot.img does not pass safetynet.
Can someone explain to me what I am doing wrong and how to properly root this phone? Thanks!
litetaker said:
Hi all, I am very confused. I am trying to figure out how to root this phone. I read the instructions for magisk and attempted to patch the boot.img file linked in the ArrowOS post (https://drive.google.com/file/d/1o-4T4hfEtxECIss-DVSSYAM1Kvy2iDN9/view?usp=sharing)
But whenever I flash that patched boot.img I am getting stuck on a bootloop. And then I found someone already patched the boot.img on August (this post) but that boot.img does not pass safetynet.
Can someone explain to me what I am doing wrong and how to properly root this phone? Thanks!
Click to expand...
Click to collapse
Open developers options enable usb debugging , connect pc type in CMD :
adb reboot bootloader && fastboot boot
( After fastboot boot space and then you drag and drop twrp file )
Phone boots into twrp , copy magisk from pc and paste to phone , press install in twrp and choose magisk. That's it , I make sure to leave inject twrp as disabled. If you want to install twrp first reboot into system make sure magisk works alright then boot into twrp again and install via advanced menu
Can you explain the "copy magisk from pc and paste to phone , press install in twrp and choose magisk" part? It is not very clear?
Is this a different method instead of patching the boot.img? If so, is this permanent or temporary and I need to use recovery every time to re-enable root?
Just flash the magisk apk file using twrp, yes you can flash apk file on twrp. Make sure 'inject twrp' is unchecked! Reboot then wait till magisk app appears on app drawer and run it then follow the steps it will tell.
Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?
litetaker said:
Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?
Click to expand...
Click to collapse
you really cant do anything about that now, google recently announced that they are implementing a hardware attest method for every phone. That means once you root the device, you wont be able to pass safety net, given that its hardware level now, its near impossible to find a solution now but im pretty sure there are some ways to trick it into giving the safety net a pass status, but im currently not aware of one.
litetaker said:
Ok, that worked. But the SafetyNet checks are not passing though! How can I make it pass?
Click to expand...
Click to collapse
You can enable MagiskHide in the settings
Noe367 said:
You can enable MagiskHide in the settings
Click to expand...
Click to collapse
Wow, I did not double check it after hiding magisk but it works now! Thanks!
litetaker said:
Wow, I did not double check it after hiding magisk but it works now! Thanks!
Click to expand...
Click to collapse
Be sure, to enable MagiskHide to the apps that needs it, otherwise you can also install the module "MagiskHide Props Configs"