Hi, I wanted to try the debloater module, so i installed it on my Oneplus 7 Pro. After the installisation and reboot, the device always stayed on the bootlocker warning screen really long. After that it always startet to fastboot.
My first try was to flash the module uninstaller: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242.
-> Flash was sucessfull, but it did not work at all.
Second try was to delete the modules via TWRP File explorer, so i deleted the folder of the module.
-> Still same problem, boots from bootloader unlocked warning screen directly to fastboot.
My next try was to flash the magisk uninstaller.
-> Flash sucessful, phone running again.
After that i reflashed magisk.
-> Problem started again.
Next step was flashing the uninstaller and then booting to android, to delete the magisk Manager. After that reflashing magisk.
->Same Problem as in the beginning. But there is no module when i have a look at /data/adb
Right now my device is running, but i have no idea how to reinstall magisk. Is there anybody who could help me?
I'd like to get magisk back and would prefer not to factory reset or wipe any sd data...
If there are no modules installed, there's likely something else going on...
Examples of things to do/try:
Don't install TWRP. Leave the boot image untouched and just boot TWRP to install Magisk (there's been instances where Magisk and TWRP conflict).
Reflash just the system images and leave data untouched.
Ask for advice in your device's forum. That's usually where you'll get the best device specific help.
Thank you for the advice!
So you mean i should flash the stock recovery again? And then sideload TWRP, or simply patch my boot image and flash it via ADB?
But why did i not have any problem with TWRP and magisk all the time before? Everything startet with the reboot after installing a new module?
I will also post my question in the OP 7 Pro forum!
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
GeekMcLeod said:
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
Click to expand...
Click to collapse
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
I just wanted to debloat the oneplus galerie, so i could install an older version from apk mirror, that still has the never settle stamp.
6nchris said:
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
Click to expand...
Click to collapse
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
GeekMcLeod said:
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
Click to expand...
Click to collapse
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
i came from 3T to the essential phone. I Think modding the OP 3T or the OP 7Pro is much easier than the essential PH1...
6nchris said:
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
Click to expand...
Click to collapse
Ahh, sad too say but I can't help with that. I don't take calls often so never noticed anything like that.
Related
EDIT:
I was being stupid, wasn't reading the screen properly - novice mistake, should know better
I can get into bootloader and fastboot can see phone
Extracted boot.img from oreo.zip and phone boots
ben_pyett said:
I downloaded and flashed the latest Oreo update - happy days - this booted fine.
I subsequently flashed TWRP and then superSU ever since the device fails to boot, just stays on the oneplus screen, powered by android splash screen...
I was able to get into recovery (TWRP) so I tried to reflash the oreo update by adb sideload, this failed and crashed adb on my Windows 10 PC
At this point I thought that possibly reverting to stock recovery might be an idea, not the best I've had! After this I seemed to go backwards...
I'm using the latest platform tools from google, adb and fastboot cannot find the device.
I am unable to get into the bootloader, by holding volume down and power
Only able to effectively power cycle the device, can't get into recovery or bootloader and the PC can't see the device
Any help or guidance greatly appreciated - getting desperate.
Click to expand...
Click to collapse
Why not try mega unbrick?
Droidcore said:
Why not try mega unbrick?
Click to expand...
Click to collapse
on that now, cheers
I may need this as well. What's Mega Unbrick and where do I find it?
I managed to install open beta 16 successfully, and tried flashing magisk ..but it gets stuck at the boot logo(even after 20 mins)..I tried flashing super su..the same error occurs..please suggest a solution..how to root Oreo ob16 using magisk?
tvakshaykumar said:
I managed to install open beta 16 successfully, and tried flashing magisk ..but it gets stuck at the boot logo(even after 20 mins)..I tried flashing super su..the same error occurs..please suggest a solution..how to root Oreo ob16 using magisk?
Click to expand...
Click to collapse
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
inasar said:
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
Click to expand...
Click to collapse
I keep reading lots of posts where people root Oreo, but whenever I try, even using latest superSU SR5 I get stuck booting.
Any ideas what I'm missing?
ben_pyett said:
I keep reading lots of posts where people root Oreo, but whenever I try, even using latest superSU SR5 I get stuck booting.
Any ideas what I'm missing?
Click to expand...
Click to collapse
How were you able to get into TWRP from your oneplus splash screen?
inasar said:
How were you able to get into TWRP from your oneplus splash screen?
Click to expand...
Click to collapse
AT the options screen, just before the splash screen , make use of the volume buttons to select fastboot and then flash TWRP, reboot fastboot and then choose recovery
inasar said:
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
Click to expand...
Click to collapse
SuperSU SR5 works with the newest beta.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
ben_pyett said:
EDIT:
I was being stupid, wasn't reading the screen properly - novice mistake, should know better
I can get into bootloader and fastboot can see phone
Extracted boot.img from oreo.zip and phone boots
Click to expand...
Click to collapse
thank u, could have used this an hour ago, but i used the mega unbrick and all is well, but thank u, b/c i may mess around with it later.
ben_pyett said:
AT the options screen, just before the splash screen , make use of the volume buttons to select fastboot and then flash TWRP, reboot fastboot and then choose recovery
Click to expand...
Click to collapse
yeah tried that. No cigar. The phone gets stuck on the oneplus logo and nothing happens.
I guess going the unbrick-qualcomm tool way is the only option left now. I was so dreading this...
inasar said:
yeah tried that. No cigar. The phone gets stuck on the oneplus logo and nothing happens.
I guess going the unbrick-qualcomm tool way is the only option left now. I was so dreading this...
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...b16-nougat-t3689356/post74173258#post74173258
Can anyone tell me,how to install TWRP recovery in redmi 4 without PC.
I dont know for sure, but i think Xiaomi still has some aspects of the phone locked even when the bootloader is unlocked.
I'm also getting in to the Xiaomi fastboot screen, and keep using the fastboot commands from pc to boot into TWRP.
But TWRP prompts for a app update when Android is booted (so in my eye's it seems that TWRP is installed correctly!?)
The same goes for handeling of the SDcard, it keeps pointing to: /storage/****-**** instead of the usual: /storage/emulated/0 (or whatever other phone manifactures make of it).
So managing the SDcard with a 3rd party app is also something that doesnt work with custom roms.
Still i think these minor shortcomings are fine, as long as you dont need to force use the bloaded MIUI roms
And once you have flashed a working rom, you don't really need to boot that often in to TWRP (maybe to update to a new version,but that also isn't that often).
I feel a bit off a dumbass
If you press: vol up + vol down + powerbutton, you boot in to recovery!
Someone else on this forum posted this, sorry don't know which post, but just wanted to point out, that it isn't mine finding
To boot into TWRP Recovery
When the device is off.
Press power + volume up buttons.
You will find yourself in a recovery with chinese characters. Press the lowest right option to change the language to english.
Select recovery.
After automatic reboot, you are in TWRP.
cheers.
First,unlock your bootloader,and get your device root.
Second,download an APP called FLashify.
Third,flash your twrp img file by this APP.
I have did it in this way,I am not sure whether it will work.Sorry for my terrible English,I'm Chinese.May it will help you.
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
DarkusRattus said:
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Click to expand...
Click to collapse
This happened to me too, I originally thought if was the Rom however dirty flashing the Rom again didn't fix it nor did dirty flashing stock image
What I do know is, this happened to me as soon as forced stopped gms services and removed GMS dose from magisk. As soon as I rebooted, this happened
Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It's kinda strange because I didn't touch anything for some days, and after a normal reboot this happened.
I tried restoring the stock boot.img from fastboot -> same issue
Reflash entire factory image without the "-w" so without wiping -> same issue
Even reboot in safe mode -> same issue
I don't think it's magisk fault because happened randomly the last 2 times, but I'll give your method a try if this happens again
It sure is giving off system UI crashing vibes. I definitely agree that this is an issue caused by something you did, not something inherent to the Pixel 4. Like suggested already, I would uninstall magisk as a next logical step since you've tried many of the other things I would have suggested. I wholeheartedly agree with Tulsa that this is a bad flash. Since you didn't wipe userdata when you flashed the factory image, the bad flash is still present so it's pretty safe to assume that you have a bad module installed or a bad combo of modules that don't like working together.
Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
DarkusRattus said:
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
Click to expand...
Click to collapse
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Tulsadiver said:
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Click to expand...
Click to collapse
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
DarkusRattus said:
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
Click to expand...
Click to collapse
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Tulsadiver said:
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Click to expand...
Click to collapse
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
DarkusRattus said:
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
Click to expand...
Click to collapse
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Tulsadiver said:
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Click to expand...
Click to collapse
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
DarkusRattus said:
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
Click to expand...
Click to collapse
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Tulsadiver said:
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Click to expand...
Click to collapse
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
DarkusRattus said:
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
Click to expand...
Click to collapse
I don't know how old your phone is but the slots are used for when you receive firmware updates and don't change unless you receive one over the air. You can change it manually in fastboot
fastboot --set-active=a
Try that then install your firmware again. It should now just reference B a few times.
TENN3R said:
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Click to expand...
Click to collapse
Did you have FDE.AI installed by any chance? And what kernel were you using?
DarkusRattus said:
Did you have FDE.AI installed by any chance? And what kernel were you using?
Click to expand...
Click to collapse
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
TENN3R said:
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
Click to expand...
Click to collapse
I also feel that it's the issue, although I was using the FDE.AI app, so I guess both methods of installation can cause it. After the nth time resetting my phone, I just changed kernels and uninstalled FDE.AI and for a solid week now I've been booting fine.
Edit: wow I just looked at the thread and it looks like something went down over there.
Hi,
Please indulge me if this it a bit silly, but I am confused about installing magisk from recovery. I flashed the patched image to recovery partition, as per the github guide (https%3A//topjohnwu.github.io/Magisk/install.html%23boot-image-patching, sorry for the encoding, system forbids me to post link cuz I am new). Yet at this point I am unsure about what to do next. This is what I see now when I boot my phone to recovery using key combo:
- Reboot system now
- Apply update from ADB
- Apply update from internal storage
- Wipe data/factory reset
- Wipe cache partition
- Mounts a storage
If I select "Reboot system now", nothing seem to happen and it all looks like a normal startup.
In short, I would like to know how to run to a ystem with Magisk enabled.
Thanks in advance!
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference:
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Didgeridoohan said:
You're not actually supposed to boot to recovery. You need to release the key combo once you see the splash screen. Reference: ...install.html#magisk-in-recovery
Edit: and don't worry... Everyone's a noob at some point or another.
Click to expand...
Click to collapse
Right, this is the part where I get confused. I did follow the link you mentioned. After pressing [power] & [volume up] for about 8 seconds, I feel a vibration and the screen lights up, thats when i released the keys. I ended up getting that menu i describe above...(tears)...
Ideally, what should I see if things go right?
NeoHiPPy1980 said:
Didgeridoohan is right: It sounds like you're booting into your phone's stock recovery, instead of your custom recovery.
Forgive my presumptions, or if I sound condescending, but if you happened to have patched and flashed your partition mods with a PC, you might want to check if you even have a custom recovery installed. (I know that some phones aren't capable of having a custom recovery flashed, so your situation might be different.) If you don't have one, that would be the first step (most folks use TWRP). Once you can boot into your custom recovery, though, you should be good.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Wubwubdubdub said:
No worries. Any suggestion is much ppreciated. Just to be sure (correct me if i m wrong), I thought that patching an image file is an independent way of installing magisk in case custom recovery is not available. So that s my case.
Anyhow, I would really like to learn a bit more about the situation where recovery partition contains both the stock recovery and custom recovery/patched image. There doesnt seem to be any difference whether i release the key combo or not once I see a splash screen. I always end up with that blue menu in recovery.
Click to expand...
Click to collapse
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
[Solved] by flashing boot image instead of recovery image
I am still puzzled by the complications with booting into recovery mode. To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains. Anyways, a big thanks to Didgeridoohan and NeoHiPPy1980. Knowing that someone will provide help is what stopped me from giving up.
NeoHiPPy1980 said:
If you don't mind my asking, which model of phone do you have? Most phones have a similar button combo, but are a bit quirky to get into the recovery.
Ex: On my LG V20, I have to hold Vol-, and Power, but release the power button at the splash screen for 0.5-1 seconds (while still holding Vol-) and then press/hold the Power button again...
As a suggestion, you may want to see if your phone has a similar quirk, depending on the make /model.
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 20.4), using Tapatalk
Click to expand...
Click to collapse
I have a Ulefone, not sure if you ve heard of it
But that won't matter. I managed to get it working another way (see to my last post). I should probably have done that before making this post. Thanks for your assistance!
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Didgeridoohan said:
Great to hear you got things working, but why did you think you needed to use the recovery image for your device? Was any of the installation instructions unclear and in need of improvement (I'm just trying to learn for future reference)?
Click to expand...
Click to collapse
Frankly, I find the Magisk Installation Guide to be one of very few documentation that is concise, coherent and user-friendly for both regular user and developer. So a big thumb up for you all! For your reference, here is the process of how I was lead to believe I needed the recovery img:
1.
I followed the instruction on "know your device" (https%3A//topjohnwu.github.io/Magisk/install.html#knowing-your-device). The first command returns nothing and the seconde comand returns true. Naturally, I assumed this means that my device is using system-as-root on a non-A/B device.
2.
I then read:
If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device. Follow the instructions in Boot Image Patching, but instead of using your boot image, use your recovery image. "
Click to expand...
Click to collapse
(https%3A//topjohnwu.github.io/Magisk/install.html#getting-started)
I am not sure if I misunderstood sth. At this point I still believe that according to the instruction I should have patched my recovery image. I do not know what system-as-boot actually is...
Yes, it does seem like your device is A-only system-as-root, which would normally mean you need to use the recovery image.
Unfortunately, with the Android ecosystem being as fractured as it is there will always be exceptions...
Thanks for the detailed response.
Hi Guys
Wubwubdubdub, I have got a question for you. I followed the same instructions as you mentioned in first post and ran into problems as well. How did you get around this problem? What is the difference between the two ways you mentioned here? (I believe I used the first way).
Wubwubdubdub said:
I flashed the patched image to recovery partition, as per the github guide
Click to expand...
Click to collapse
Wubwubdubdub said:
To work around it, I attemped installing Magisk using boot image patch and succeeded. Objective achieved yet question remains.
Click to expand...
Click to collapse
Thanks in advance!
MM