Related
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
The January updates are up.
OTA is live too. Just 50.8 MB for 1st Gen XL.
ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now
ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.
Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!
Does anyone have the January pre-rooted boot.img?
BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
^^^
This is a 1st.........never seen anyone ask for it........LoL
BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...
crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work
I've been stressing all day to fix my 6T. I wiped my phone countless of times and every time I flash TWRP and magisk after, I lose WIFI. I don't know how to fix this, it never happened before. I tried resetting it in settings, nothing happened. I really need WIFI as my data is literally finished. This was after I clean installed 10.3.0. I literally have nothing in my phone and my data is backed up thankfully.
I have found a fix for this. If you have updated to 10.3.0 or new update or going to. Install it via download or local upgrade. and follow this method. Once I followed this method, my WIFI was fixed.
Quote:
Originally Posted by jp0469
Here's the simplest way to upgrade:
1. Flash latest full OTA via Local Updater [DON'T REBOOT]
2. In Magisk Manager, flash latest TWRP installer zip (the one called unofficial installer) from mauronofrio [DON'T REBOOT]
3. Still in Magisk Manager, Install (next to "Magisk is up to date") > Install > Install to inactive slot
4. Reboot
As an update: This method worked when I updated from 10.3.0 to 10.3.1. Everything was working fine.
There is an issue I have found. This method will make your system to boot into slot b, it still works as normal.
But if it bothers you that its slot b and not a, just redo the method again. It worked for me
Hey, thanks for crediting my post. I didn't know this would help with anyone's WiFi issue but I'm glad it did.
jp0469 said:
Hey, thanks for crediting my post. I didn't know this would help with anyone's WiFi issue but I'm glad it did.
Click to expand...
Click to collapse
Yeah, I literally been trying for hours to find a solution online to no provail. Luckily I found your post and I used it as a last resort. I was about to give up at that point. Your method is quite good actually, I can install a new android 10 update, TWRP and magisk at the same time. and reboot with everything there. No more repeated reboots for TWRP and magisk
Same problem
Could not turn my wifi on, couldnt place calls, snap pictures, set alarm. Im so glad i found this post, because it did help me and I didnt lose any data. I was already rooted.
chicoman21 said:
Could not turn my wifi on, couldnt place calls, snap pictures, set alarm. Im so glad i found this post, because it did help me and I didnt lose any data. I was already rooted.
Click to expand...
Click to collapse
Yeah, I honestly haven't found any posts about this. I just used the method as a last resort, I was honestly planning to give up and move to IOS ?.
Installing the 10.3.0 again via local upgrade will just remove TWRP and magisk, but if you follow the method you'll get TWRP and Magisk installed with WIFI working . I thought that using the old method from Nougat, Oreo to Pie would work with Q/10. Nope, now we have found a way to have root with verything working
raghu46j said:
Flashing Custom Kernels will fix the wifi issues,
I'm using BluSpark Kernel.
Click to expand...
Click to collapse
Ok, I didn't know that. But I don't use custom kernels tbh, I like to keep my device close to stock. I just have root, magisk modules, swift black stuff, TWRP, rooted apps which just improve the device and that's fine for me. I'm glad that it worked for you
raghu46j said:
Flashing Custom Kernels will fix the wifi issues,
I'm using BluSpark Kernel.
Click to expand...
Click to collapse
But BT keep disconnected and connected
Extreme_Ninja2099 said:
2. In Magisk Manager, flash latest TWRP installer zip (the one called unofficial installer) from mauronofrio [DON'T REBOOT]
Click to expand...
Click to collapse
I'm confused, how are you flashing from Magisk Manager?
OMGLOLetcetc said:
I'm confused, how are you flashing from Magisk Manager?
Click to expand...
Click to collapse
You can flash TWRP zip in modules. You press on modules, click on the plus button, find your TWRP zip file and press it. Then magisk will flash the zip, but don't reboot
Extreme_Ninja2099 said:
You can flash TWRP zip in modules. You press on modules, click on the plus button, find your TWRP zip file and press it. Then magisk will flash the zip, but don't reboot
Click to expand...
Click to collapse
Ah, that's the issue, I don't have the Modules option.
could anyone be kind enough to lead me to the zip? all i can find is the img for the unofficial twrp
TacTieTee said:
could anyone be kind enough to lead me to the zip? all i can find is the img for the unofficial twrp
Click to expand...
Click to collapse
Its in the download section of the recovery thread. Its called TWRP 3.3.1-30 Unofficial Installer by mauronofrio. Its not hard to find
https://androidfilehost.com/?fid=4349826312261677893
Hello everyone. I'm back. I'm gonna install 10.3.1 on my 6T. I'll try the method and let you guys know
@Extreme_Ninja2099 - How did you get on?
Cam we go straight from a rooted 9.0.17 to rooted 10.3.1 using the above mentioned method?
Static-Noise said:
@Extreme_Ninja2099 - How did you get on?
Click to expand...
Click to collapse
Its at the start of the thread. The method worked from 10.3.0 to 10.3.1. But my slot changed to B. I changed it back to A by re-doing the method again. Everything is fine with 10.3.1.
Goormeetsingh said:
Cam we go straight from a rooted 9.0.17 to rooted 10.3.1 using the above mentioned method?
Click to expand...
Click to collapse
I'm not sure tbh
Hello all,
When still on Android 10 I had Magisk stable installed and working.
Now, after upgrade to Android 11 I cannot get it to work.
Here's what I did:
- first off, I have factory reset the phone (without erasing external storage) because of WiFi not working anymore on Android 10 (Omega kernel problem maybe?).
- update the phone to Android 11 in Settings, System, System updates (now I'm on Android 11 build IN2023_15_200930)
- install Magisk Manager from here
- download the firmware from here
- extract boot.img from firmware zip file
- copy boot image from pc to mobile
- patch boot image with Magisk manager
- copy magisk_patched.img from mobile to pc
- flash magisk_patched.img
Code:
❯ fastboot flash boot magisk_patched.img
Sending 'boot_a' (43464 KB) OKAY [ 1.824s]
Writing 'boot_a' OKAY [ 0.131s]
Finished. Total time: 1.966s
- reboot the device
Now, when I open Magisk Manager, it says Magisk Installed ' N/A' and I expect to be able to install Magisk using 'direct install'.
However this option 'direct install' is not shown, only Download Zip Only & Select and Patch a File.
What is missing here?
Any help is appreciated!
Edit: I got it working using canary build of magisk manager in stead of the stable build.
Got the same issue plus the phone sometimes turn into a bootloop.
saphirrot said:
Got the same issue plus the phone sometimes turn into a bootloop.
Click to expand...
Click to collapse
I got it working using canary build of magisk manager in stead of the stable build.
lvbaal said:
I got it working using canary build of magisk manager in stead of the stable build.
Click to expand...
Click to collapse
I tried both, same result
saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Flash to both slots. Not just one.
Fastboot flash boot_a "name of boot IMG"
Fastboot flash boot_b "name of boot IMG"
saphirrot said:
I tried both, same result
Click to expand...
Click to collapse
Maybe Wipe Cache in recovery? I did that anyway
Tried wiping Cache and flashing to both Slots.. still bootloop..
saphirrot said:
Tried wiping Cache and flashing to both Slots.. still bootloop..
Click to expand...
Click to collapse
Sorry for you man! Maybe this than?
Uploaded some logs, maybe someone can helpView attachment 2020-10-11_16.00.zip
@saphirrot
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.
dladz said:
Quite possible it's the magisk patched image you're using, obtain another, best to extract it yourself.
Click to expand...
Click to collapse
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..
saphirrot said:
Patched my own boot.img, still the same issue... thats so Strange, because I havent modified anything after the o11 Update..
Click to expand...
Click to collapse
Don't flash twrp whatever you do it'll end up in crash mode, not suggesting you will but a chap I was helping did it and that's what happened. Forced him to use MSM tool.
Try another patched image, if you're on EU/UK then I have one in my thread in the guides section. Just don't do anything else. If needs be I can upload a stock boot.img if your get stuck in a boot loop, least then your can boot.
What version of magisk did you use to patch?
Also what was the commands you used to flash it in fastboot?
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Dont flash your image just boot it first. And if it boots and you have root you can install magisk from manager permanently
Had to factory Reset the Phone, now root works fine
Same Problem
yeah same problem here... you can exit the bootloop by flashing the stock boot.img on it.
But still, neither canary or the standard does work for rooting.
saphirrot said:
Using the canary magisk Version, latest ofc. Also tried all patched boot.img posted around here. Also extracted my own working boot.img and Patched it with magisk. Then flashed IT via Fastboot and bootloop again. The logs should help to find my problem
Click to expand...
Click to collapse
Were you using lucky patcher?? Sounds a lot like you are.
dladz said:
We're you using lucky patcher?? Sounds a lot like you are.
Click to expand...
Click to collapse
So you're saying that lucky patcher is the problem?
MrZaga said:
So you're saying that lucky patcher is the problem?
Click to expand...
Click to collapse
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.
dladz said:
Lol well that depends mate, are/ were you using it.
Lucky patcher breaks so much when it's used, bootlooping is one of those symptoms.
I intend to make a thread saying do not use it as you're the fifth person I've seen now with issues I've troubleshooted and the culprit was that stupid app.
Click to expand...
Click to collapse
As it sounds, uninstalling doesn't help then. But do you know why it bootloops only when using the patched img, and not when using the stock img?
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.
MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.
Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?
Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches
What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.
It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.
h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541