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
Three again. Verizon, Dutsche and every one else. Flashing now.
So far full images only, no OTA.
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
sliding_billy said:
OTAs are up too. Anyone see a change log or know if TWRP and SuperSU are working?
Click to expand...
Click to collapse
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
TonikJDK said:
I am still investigating, but it would seem SU is not working.
I ran flash-all.bat after removing the -w
Boots and runs fine.
fastboot booted twrp RC1 and flash SU 2.79 SR3
It is sitting here bootlooping now. I have reflashed and tried a couple of times. Same result.
Click to expand...
Click to collapse
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
sliding_billy said:
Thanks for taking one for the team. It felt like something was going to fail based on comments about rooting the developer preview.
Click to expand...
Click to collapse
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Kisakuku said:
Not sure what another build of 7.1.2 has to do with ODP1. Plus, SuperSU v2.79 SR4 w/delay works on ODP1 after some dual-slot magic.
Click to expand...
Click to collapse
Just was a gut feeling that whatever was going wrong in the developer build would somehow been implemented in the May build. I am sure they are unrelated, but that was why I asked before the OP was updated to include the SU break.
The VZ OTA will download if you set the date to May 4th.
just checked my phone and got Verizon update without changing date
My OTA for Verizon didn't hit yet. And moving the date forward didn't help. Hopefully soon.
what will happen to supersu if try to flash this full factory image via flashfire and
bush911 said:
what will happen to supersu if try to flash this full factory image via flashfire and
Click to expand...
Click to collapse
It will be gone.
Pixel users are reporting bootlooping on the May update after flashing TWRP only
https://forum.xda-developers.com/showthread.php?p=72121371
https://forum.xda-developers.com/showthread.php?p=72120712
What are the chances that this was done purposely? "Breaking root and twrp"
DR3W5K1 said:
What are the chances that this was done purposely? "Breaking root and twrp"
Click to expand...
Click to collapse
Anyone try Magisk? I imagine same result.
Sent from my Pixel XL using Tapatalk
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
itchy67x said:
if i try to go back to march update and to root it again, i got a bootloop. right now is no root for me anymore
Click to expand...
Click to collapse
Just use April's bootloader.
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
thx that works
Taebom said:
Just use April's bootloader.
Click to expand...
Click to collapse
Thanks, that works for the Pixel too. I flashed April's K bootloader on the May L version no problem. TWRP and SU work fine now.
dowlf said:
I sideloaded n2g47o ota, there were no errors but it didn't seem to take. Still shows n2g47e as the build. Something must have went wrong. I will hold off on trying again for now.
Click to expand...
Click to collapse
FWIW: sideload of n2g47o worked fine on my (stock) XL. Did you have any modifications?
https://developers.google.com/android/images
https://developers.google.com/android/ota
Has anyone flashed this factory image yet? Does it break TWRP and/or Magisk?
Sent from my Pixel 2 using Tapatalk
I haven't yet, but expect it to break things if you flash it like that. Though if you sideload and update from a factory image it'll do a full wipe unless you edit the flash script.
Tentatively the following process should work:
- Flash factory image after removing wipe flag
- Boot TWRP image
- Flash TWRP zip
- Flash kernel
- Flash Magisk
Everything should work normally at that point.
Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Sent from my Pixel 2 using Tapatalk
Hi, update received.
Diesel_Jeremiah said:
Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Click to expand...
Click to collapse
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.
Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!
guapinoy said:
Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!
Click to expand...
Click to collapse
Magisk and TWRP working correctly?
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Magisk and TWRP working correctly?
Click to expand...
Click to collapse
Yup.
Would love to see if this patches the Verizon bootloader unlock.
PuffDaddy_d said:
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.
Click to expand...
Click to collapse
Here is how I updated: [DEC 2017 to JAN 2018 Update] How I updated successfully
So far only one report of receipt via OTA? I had to sideload Dec, really hoping to just get these OTA going forward.
I've found that using old ADB tools will not flash the factory image properly. I was using a tool that an XDA member provided that had adb binaries from 2015 and kept getting errors when trying to use the flash-all.bat from the factory image. If you guys get stuck with something, update your adb and fastboot tools from the latest platform tools. It will save you a headache. If you want step by step instructions of what I did, I can provide them.
Hmm, I'm failing SafetyNet now.
Lightn1ng said:
Hmm, I'm failing SafetyNet now.
Click to expand...
Click to collapse
Did you follow Diesel's method or was this after you soft bricked your phone?
PuffDaddy_d said:
Did you follow Diesel's method or was this after you soft bricked your phone?
Click to expand...
Click to collapse
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data
Lightn1ng said:
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data
Click to expand...
Click to collapse
Formatting data decrypts it, that may or may not be why it's failing.
Telperion said:
Formatting data decrypts it, that may or may not be why it's failing.
Click to expand...
Click to collapse
Ooohhhhhh. How do I get it back to encrypted?
Lightn1ng said:
Ooohhhhhh. How do I get it back to encrypted?
Click to expand...
Click to collapse
Same as before, but don't format your data partition.
no OTA for me yet. I heard sideloading results in lag but who knows.
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:
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