Hello, I recently updated to 10.5.8, kept magisk from previous version of oos, but then day after updating to 10.5.8 I updated Magisk to latest canary (was using canary before) and after reboot I lost my fingerprint scanner.
I have backup of Persist partition on root of my sdcard saved as Persist.img.
My question is: how do I restore it? As far as I know I have to convert it from sparsed to raw image. How can I do it? Can I do it on Windows? Maybe I can do it using unofficial twrp? Can I just flash it in twrp like it is?
Please help me, I don't want to send it back. I know there is way as I already have mine persist.img
Ouch, I lost my fingerprint scanner too after updating to 10.5.8, I didn't make a backup of this persist disk though, is that needed?
Unn113 said:
Hello, I recently updated to 10.5.8, kept magisk from previous version of oos, but then day after updating to 10.5.8 I updated Magisk to latest canary (was using canary before) and after reboot I lost my fingerprint scanner.
I have backup of Persist partition on root of my sdcard saved as Persist.img.
My question is: how do I restore it? As far as I know I have to convert it from sparsed to raw image. How can I do it? Can I do it on Windows? Maybe I can do it using unofficial twrp? Can I just flash it in twrp like it is?
Please help me, I don't want to send it back. I know there is way as I already have mine persist.img
Click to expand...
Click to collapse
can you explain to me the exact process of what you did step by step for that problem to occur? For example did you upgrade the magisk in TWRP? Or did you do it with the inactive slot method
---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------
xByt3z said:
Ouch, I lost my fingerprint scanner too after updating to 10.5.8, I didn't make a backup of this persist disk though, is that needed?
Click to expand...
Click to collapse
Same question for you as above if you don't mind~.
Burt Squirtz said:
can you explain to me the exact process of what you did step by step for that problem to occur? For example did you upgrade the magisk in TWRP? Or did you do it with the inactive slot method
---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------
Same question for you as above if you don't mind~.
Click to expand...
Click to collapse
Magisk update notification popped, so I went to magisk manager and flashed newest version to active slot as I wasn't updating oos, just magisk. I though it'll be fine, but after reboot I don't have fingerprint scanner.
This night I managed to restore persist.img using terminal, but my fingerprint scanner is still not working. I submitted RMA to my reseller, but it's weekend so they'll text me back on Monday. Maybe there is a way to restore this scanner to this time.
P.s. I don't have twrp, but can flash it if needed.
it seems some that people using magisk canary are having fingerprint breaks.
Can you try to uninstall magisk canary and install normal 20.4?
Nekromantik said:
it seems some that people using magisk canary are having fingerprint breaks.
Can you try to uninstall magisk canary and install normal 20.4?
Click to expand...
Click to collapse
If there is rooted boot.img for 10.5.8BA I could try.
I'm editing this post as it's actually worked! I just downgraded to 20.4 using magisk manager and rebooted, and my fingerprint scanner is working! I don't know if it has to do with me restoring persist earlier, bit it works! Thank You very much!
So conclusion is that Magisk canary breaks fingerprint scanner!
Burt Squirtz said:
can you explain to me the exact process of what you did step by step for that problem to occur? For example did you upgrade the magisk in TWRP? Or did you do it with the inactive slot method
---------- Post added at 03:58 AM ---------- Previous post was at 03:57 AM ----------
Same question for you as above if you don't mind~.
Click to expand...
Click to collapse
I lost my fingerprint access, after rooting my phone and then finding that Netflix won't work in HD so I wanted to rollback, so I flashed default boot image and then locked Bootloader and after that I can't get my fingerprint working. apparently it will be while before we get a fix.
Unn113 said:
If there is rooted boot.img for 10.5.8BA I could try.
I'm editing this post as it's actually worked! I just downgraded to 20.4 using magisk manager and rebooted, and my fingerprint scanner is working! I don't know if it has to do with me restoring persist earlier, bit it works! Thank You very much!
So conclusion is that Magisk canary breaks fingerprint scanner!
Click to expand...
Click to collapse
Canary is causing a lot of problems elsewhere too.
People need to let Magisk team know.
Unn113 said:
If there is rooted boot.img for 10.5.8BA I could try.
I'm editing this post as it's actually worked! I just downgraded to 20.4 using magisk manager and rebooted, and my fingerprint scanner is working! I don't know if it has to do with me restoring persist earlier, bit it works! Thank You very much!
So conclusion is that Magisk canary breaks fingerprint scanner!
Click to expand...
Click to collapse
Ok so first things first, regardless what anyone is doing, everybody really should back up that persist partition?
Correct?
Then if you lose FP
Restore your persist partition.
Then reverting (if root is still required) to Magisk 20.4
Then it should work?
Is all the above correct???
One last thing! Is each persist partition specific to each individual device or just to the region? IE: EU / US / INT
dladz said:
Ok so first things first, regardless what anyone is doing, everybody really should back up that persist partition?
Correct?
Then if you lose FP
Restore your persist partition.
Then reverting (if root is still required) to Magisk 20.4
Then it should work?
Is all the above correct???
One last thing! Is each persist partition specific to each individual device or just to the region? IE: EU / US / INT
Click to expand...
Click to collapse
As far as I know persist partition contains some certificates individual to each device, so flashing someone's else's persist could help with other sensors, but fp scanner it's using to protect our devices and have to be encrypted somehow.
Method I mentioned helped me, and some other member in other thread, but some people have this issue with magisk 20.4 and even without magisk... I don't know what's exactly causing this problem.
Unn113 said:
As far as I know persist partition contains some certificates individual to each device, so flashing someone's else's persist could help with other sensors, but fp scanner it's using to protect our devices and have to be encrypted somehow.
Method I mentioned helped me, and some other member in other thread, but some people have this issue with magisk 20.4 and even without magisk... I don't know what's exactly causing this problem.
Click to expand...
Click to collapse
I see, cheers
Well the reason I'm asking is because if we can't fix the problem, then maybe we can avoid if happening with precautions, least until it's fixed.
This is the first device I've ever had where I've held off unlocking and rooting.
most people have had fingerprint work again by simply going back to 20.4
only a few people still have issues after doing that
Ok Guys just flash magisk 20.4 zip my fingerprint is working again
grodri19721 said:
Ok Guys just flash magisk 20.4 zip my fingerprint is working again
Click to expand...
Click to collapse
Did you restore the persist partition? Or just flash magisk?
dladz said:
Did you restore the persist partition? Or just flash magisk?
Click to expand...
Click to collapse
Same thing happened to me like OP describes..I have my persist.img as a backup but I simply swithes canary to stable 20.4 and fingerprint works again! Great
Update from me, I switched the update channel in Magisk Manager from Canary to Stable and then just did a direct install. My fingerprint scanner restored functionality after downgrading back to stable then rebooting.
pyry666 said:
Same thing happened to me like OP describes..I have my persist.img as a backup but I simply swithes canary to stable 20.4 and fingerprint works again! Great
Click to expand...
Click to collapse
Ok thanks man. So no need to restore, just get off Canary, everyone needs to know this.
I haven't rooted yet but this was a huge issue for so many.
dladz said:
Ok thanks man. So no need to restore, just get off Canary, everyone needs to know this.
I haven't rooted yet but this was a huge issue for so many.
Click to expand...
Click to collapse
Problem is that few users used canary and they lost fingerprint, but instead of switching to stable magisk they've used msm..
And after that FP lost forever...
cultofluna said:
Problem is that few users used canary and they lost fingerprint, but instead of switching to stable magisk they've used msm..
And after that FP lost forever...
Click to expand...
Click to collapse
I;m in this boat. Just sent my back to be replaced.
polo2883 said:
I;m in this boat. Just sent my back to be replaced.
Click to expand...
Click to collapse
Exact reason why most phones are locked down.
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
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:
Currently out driving, but read that latest canary Verizon of magisk worked with android Q, so I went ahead and pulled the file to flash, no idea about the lastest TWRP but if you want to try ahere it is, obviously you can get it at the github repo also. Will try when I get home, please let me know
It will most probably not work:
https://twitter.com/topjohnwu/status/1105922417002799106
It was the aosp image should work fine if TWRP boots
Confirmed doesn't work manually patching boot image
I got a bootloop when I flashed via TWRP.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I was going to try, but I've been out and about all day - glad you all already tried.
I'm gonna remove root and play with Q for a while - maybe John will make some headway (or else that other dude that seems to have another way in can get it working).
pk92 said:
Confirmed doesn't work manually patching boot image
Click to expand...
Click to collapse
Mind sharing the patched boot image?
Subhojit said:
Mind sharing the patched boot image?
Click to expand...
Click to collapse
I said it didn't work; so I deleted the patched image. If you want I can create a new one?
bootloop just waiting
Maybe flashing the zip with a flasher like franco kernel manager or elementalx kernel manager while waiting for twrp?
TENN3R said:
Maybe flashing the zip with a flasher like franco kernel manager or elementalx kernel manager while waiting for twrp?
Click to expand...
Click to collapse
You'd need root to do that.
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Does removing screen lock security work?
Will try latest canary when I get home, when I got twrp to work with Q I had done a fresh install no security. Will try in an hour
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Thanks for the info - I'll try it right now.
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
Where did you read that?
Guys you should at least watch John Wu´s twitter. He is working on new biuld that will work, but its not out yet.
ANDR01DN00B said:
Apparently the latest Canary build (EDIT: of Magisk) works with the 1st and 2nd gen Pixels, but I can't get TWRP to decrypt my data so I can't test. How did everyone else get TWRP to decrypt data?
Click to expand...
Click to collapse
TWRP worked fine for me using my standard update procedure. I downloaded the ota, side loaded it with TWRP, reinstalled TWRP before rebooting and I can still decrypt with my swipe pattern by booting to recovery.
Mikulec said:
Guys you should at least watch John Wu´s twitter. He is working on new build that will work, but it's not out yet.
Click to expand...
Click to collapse
This. And reading is fundamental.
Would flashing oldkeymaster.zip bootloop me and if I can flash it could I use flashify or magisk to do it?
Upon inspection yes oldkeymaster will bootloop me. I'm guessing the only fix is wiping internal storage?
I haven't updated TWRP to -30 yet I'm still on -20 I think
Nevermind updating to -30 fixed it
Always use latest versions.... Basic rule.
Striatum_bdr said:
Always use latest versions.... Basic rule.
Click to expand...
Click to collapse
Yea messed up on that one, I don't know everybody was having issues on 10.0.0 so when I flashed it and everything just worked I left it be.
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