so I've installed magisk on 7.2.2 by creating a patched boot.img and flashing via fastboot.
All nice, until I installed a module that ended in bootloop.
I managed to recover by flashing the original boot.img, but I end up with no magisk/no root, and no means to uninstall the module, So if i reflash magisk, I end up with the bootloop.
Is there a new recovery compatible with 7.2.2 or anyone knows a way out of this?
There is no twrp for 7.2.2 yet. You can either delete /data/adb/magisk.img and install all your modules again
or
copy it to your phone while in recovery, rename the original (assuming you have magisk on your phone), copy it to the same location as above, flash the attachment to mount it, remove module from /magisk/, reboot to recovery (don't reboot to system!), cut the file off of the phone and rename the original back to magisk.img, you can then boot your phone.
thecoolkid said:
There is no twrp for 7.2.2 yet. You can either delete /data/adb/magisk.img and install all your modules again
or
copy it to your phone while in recovery, rename the original (assuming you have magisk on your phone), copy it to the same location as above, flash the attachment to mount it, remove module from /magisk/, reboot to recovery (don't reboot to system!), cut the file off of the phone and rename the original back to magisk.img, you can then boot your phone.
Click to expand...
Click to collapse
problem is I can't flash anything as I don't have a custom recovery.
do you mean flash the zip you posted via stock recovery? will it flash? what does it do? where does it go?
thanks
xd4d3v said:
problem is I can't flash anything as I don't have a custom recovery.
do you mean flash the zip you posted via stock recovery? will it flash? what does it do? where does it go?
thanks
Click to expand...
Click to collapse
I meant flash it on your phone, the second solution involves a second device as a surrogate. The zip just mounts magisk image to /magisk/ so you can browse it manually.
thecoolkid said:
I meant flash it on your phone, the second solution involves a second device as a surrogate. The zip just mounts magisk image to /magisk/ so you can browse it manually.
Click to expand...
Click to collapse
Sorry mate, not following you, why do I need a phone?
I'd be happy deleting magisk.img on the shield and loosing magisk config, but I can't access it without root or recovery.
xd4d3v said:
Sorry mate, not following you, why do I need a phone?
I'd be happy deleting magisk.img on the shield and loosing magisk config, but I can't access it without root or recovery.
Click to expand...
Click to collapse
Ok, I researched a little and the only thing that comes to mind, that isn't wiping the whole data position, is downgrading to 7.1 firmware and installing twrp. After you fix your issues you can update again.
yeah, good one, I was considering that as well, might try flashing just boot.img and blob from 7.1 and trying TWRP, then reflashing 7.2.
wish me luck
Heres an easier way, create a blank .disable_magisk file and place it in /data/cache
Then reboot, this will force magisk to start with "Magisk Core Only Mode" , which means magisk hide and modules will be disabled.
Then you can disable "magisk core only mode" when booted up, so modules and magiskhide is enabled again.
Then uninstall the module that is being the issue.
mLgz0rn said:
Heres an easier way, create a blank .disable_magisk file and place it in /data/cache
Then reboot, this will force magisk to start with "Magisk Core Only Mode" , which means magisk hide and modules will be disabled.
Then you can disable "magisk core only mode" when booted up, so modules and magiskhide is enabled again.
Then uninstall the module that is being the issue.
Click to expand...
Click to collapse
You need root or TWRP for that. I was thinking about it too, but he has no access to twrp in the new update and can't boot with root.
thecoolkid said:
You need root or TWRP for that. I was thinking about it too, but he has no access to twrp in the new update and can't boot with root.
Click to expand...
Click to collapse
You only need to use the developer boot without patching magisk to it, then through adb create a file there.
You can get root access through adb which allows you to create a file there
That's a brilliant idea. So the developer image allows root via adb?
xd4d3v said:
That's a brilliant idea. So the developer image allows root via adb?
Click to expand...
Click to collapse
Yep, hence why they call it "rooted" even though its not it dosnt have the su binaries by default, its more like unlocked compared to the ota builds.
You should be able to do the command "adb root" and then enter shell with root access.
I can't remember but you might need to do "adb disable-verity" and reboot before you can put stuff into the root partition "/system", "/data/cache" and so on.
Just remember when you patch the boot image with magisk again, you either first need to do "adb enable-verity" and then patch with "preserve avb 2.0/dm-verity" checked in magisk or keep dm-verity disabled then patch with "preserve avb 2.0/dm-verity" unchecked, else you gonna end up in a boot loop.
Related
tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?
Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.
Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?
Today I've installed the stock firmware version of Android Oreo 8.0 (the December Update) with Odin.
After that I've installed the TWRP also with Odin, the 3.2.3 version.
Then I wanted to root the devide so I start with the installation of Magisk (because I need to hide the root form some apps like Netflix), but it keeps failing with the ERROR 1. I've searched in this forum but none of the solutions worked. One solution requires the boot.img of the rom, but I can only get a boot.img.lz4 from the AP md5 file which i have no idea how to use.
Then I tried to install SuperSU (v2.82 SR5 version). I followed a guide but once I finished the flash of RMM State Bypass and SuperSU I rebooted only to be locked out of my phone. A message informed me that the integrity of the phone could not be checked (or something like that) and so I had to re-flash the stock firmware and the recovery with Odin.
Am I missing something? Am I doing something wrong? And where can I find the boot.img from the stock firmare?
I hope somebody can help me because I spent a lot of hours looking for a solution without having a working result...
lolovato said:
Today I've installed the stock firmware version of Android Oreo 8.0 (the December Update) with Odin.
After that I've installed the TWRP also with Odin, the 3.2.3 version.
Then I wanted to root the devide so I start with the installation of Magisk (because I need to hide the root form some apps like Netflix), but it keeps failing with the ERROR 1. I've searched in this forum but none of the solutions worked. One solution requires the boot.img of the rom, but I can only get a boot.img.lz4 from the AP md5 file which i have no idea how to use.
Then I tried to install SuperSU (v2.82 SR5 version). I followed a guide but once I finished the flash of RMM State Bypass and SuperSU I rebooted only to be locked out of my phone. A message informed me that the integrity of the phone could not be checked (or something like that) and so I had to re-flash the stock firmware and the recovery with Odin.
Am I missing something? Am I doing something wrong? And where can I find the boot.img from the stock firmare?
I hope somebody can help me because I spent a lot of hours looking for a solution without having a working result...
Click to expand...
Click to collapse
Try again and redownload magisk.
Also, did you wipe data?
iloveoreos said:
Try again and redownload magisk.
Also, did you wipe data?
Click to expand...
Click to collapse
I tried re-downloading Magisk (the latest and the version before) but nothing changed.
Yes I wiped the data.
I've added that I'm working on a A5 2017 SM-A520F.
lolovato said:
I tried re-downloading Magisk (the latest and the version before) but nothing changed.
Yes I wiped the data.
I've added that I'm working on a A5 2017 SM-A520F.
Click to expand...
Click to collapse
Hmm, did you reinstall stock firmware on it and try again? Error 1 happens when the zip is corrupted. What version of TWRP are you using, 3.2.3-0?
Um, did you flash no-verity 6.0.zip? https://forum.xda-developers.com/sa...velopment/recovery-galaxy-a5-a7-2017-t3815931
iloveoreos said:
Hmm, did you reinstall stock firmware on it and try again? Error 1 happens when the zip is corrupted. What version of TWRP are you using, 3.2.3-0?
Um, did you flash no-verity 6.0.zip? https://forum.xda-developers.com/sa...velopment/recovery-galaxy-a5-a7-2017-t3815931
Click to expand...
Click to collapse
I'm using 3.2.3-1.
I've tried to reflash with Odin the whole stock firmware, then I flashed the TWRP recovery 3.2.3-1 (I redownloaded every file), I entered the recovery and I flashed the no-verity 6.0.zip, only to be once againt cut out from my phone with the same message as yesterday saying that the integrity of the phone could not be checked and that I need to restore the phone.
I really don't understand what is going wrong...
I think I've made it? I don't know what I did differently this time, I'll post the solution here if someone needs it:
0a. MAKE A BACKUP OF YOUR DATA!
0b. Put in your SD-Card the version of Magisk you want to install and the no-verity-opt-encrypt-x.x zip file.
1. Flash the stock firmware with Odin, when the PASS! message appears and the phone starts to reboot unplug the device and quickly re-enter in download mode.
2. Flash the TWRP recovery with Odin, when the PASS! message appears and the phone starts to reboot unplug che devide and quickly enter in recovery mode.
3. In recovery click Wipe and select Format Data. Then go back, click Install and select from the SD-Card the no-verity-opt-encrypt-x.x zip file.
4. Reboot your phone to system, configure the devide (account, ecc.).
5. Turn-off the phone and go in recovery, click Install and select from the SD-Card the Magisk zip.
6. Reboot your phone to system, install Magisk Manager and you're done!
TWRP and no-verity-opt-encrypt zip file: click.
Magisk zip and Magisk Manager: click.
lolovato said:
I think I've made it? I don't know what I did differently this time, I'll post the solution here if someone needs it:
0a. MAKE A BACKUP OF YOUR DATA!
0b. Put in your SD-Card the version of Magisk you want to install and the no-verity-opt-encrypt-x.x zip file.
1. Flash the stock firmware with Odin, when the PASS! message appears and the phone starts to reboot unplug the device and quickly re-enter in download mode.
2. Flash the TWRP recovery with Odin, when the PASS! message appears and the phone starts to reboot unplug che devide and quickly enter in recovery mode.
3. In recovery click Wipe and select Format Data. Then go back, click Install and select from the SD-Card the no-verity-opt-encrypt-x.x zip file.
4. Reboot your phone to system, configure the devide (account, ecc.).
5. Turn-off the phone and go in recovery, click Install and select from the SD-Card the Magisk zip.
6. Reboot your phone to system, install Magisk Manager and you're done!
TWRP and no-verity-opt-encrypt zip file: click.
Magisk zip and Magisk Manager: click.
Click to expand...
Click to collapse
That is how you are supposed to do it.
Test version of custom Team Win Recovery Project version 3.5.2_11.0 for OnePlus Nord N100 (Android 11 Only).
Everything works, except for:
MTP, .img firmware (for this you need to flash the full super.img image) and decryption of the Data section.
If anyone can modify this version of the recovery, we are very grateful to the future.
In the meantime, whoever wants to test or try it out, an image will be attached to the post. You can both boot (fastboot boot twrp.img) and flash (fastboot flash recovery_a twrp.img and fastboot flash recovery_b twrp.img).
I ask you to answer about all the problems found and write either to me personally or in this topic.
Is there any newer version of this? i find this one freezes the phone a lot. thanks
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
onlycash said:
I ran this TWRP for the OnePlus N100 in fastboot and it worked but I can't see any files. I've installed Android 11.
I'm trying to install Magisk zip but in TWRP I only see the folder tree and no files.
Do I need to install TWRP and not just run it from fastboot?
If I need to install it do I pick slot a or b or both?
Thanks for any help.
Click to expand...
Click to collapse
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Halphix said:
do not install it. I installed it and it bricked my device. I needed to flash the stock recovery.
Click to expand...
Click to collapse
It installed fine on my BE2013. Not extremely useful without the missing features though.
thomaskmaagaard said:
It installed fine on my BE2013. Not extremely useful without the missing features though.
Click to expand...
Click to collapse
Can you install Magisk zip with this TWRP on your BE2013?
.
onlycash said:
Can you install Magisk zip with this TWRP on your BE2013?
Click to expand...
Click to collapse
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
thomaskmaagaard said:
Honestly I haven't even tried flashing anything because I already have magisk and i had some issues with safety net that I didn't want to risk having to fix again.
Click to expand...
Click to collapse
How did you install the Magisk zip file?
.
onlycash said:
How did you install the Magisk zip file?
Click to expand...
Click to collapse
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
onlycash said:
Thanks.
That's very interesting...
You've given me a few good ideas.
I'll report back and let you know if it worked.
.
Click to expand...
Click to collapse
If you go with the boot image method I wouldn't mind helping you out.
thomaskmaagaard said:
I didn't. I patched firmware boot image and flashed through bootloader. However I just tried flashing from TWRP.
I put the zip on external SD because this version doesn't support decryption of data partition. I then entered the "mount" menu in TWRP and mounted external SD and then tapped "select storage" and selected external SD.
You should be able to flash it now. It didn't give any errors, but i didn't uninstall magisk first so don't know how well it actually worked.
I also don't know if you can do anything without external SD or without root access already.
Click to expand...
Click to collapse
I had high hopes...
I fastbooted the TWRP, I didn't install it but I don't think that would make a difference.
I put the Magisk zip on the external SD card and from within TWRP I had no problem mounting the SD card but I still couldn't see any files, just a folder tree, and every folder empty.
When you run TWRP and mount the SD card can you see the files within the folders on the card?
.
onlycash said:
When you run TWRP and mount the SD card can you see the files within the folders on the card?
Click to expand...
Click to collapse
Yes. It is important that you tap "select storage" and select "micro sd". After i did that i entered "flash" and immediately saw folders and zips on my external sd. In file manager i could see all files and even deleted some from there.
From root directory it's in /external_sd not in /storage.
Edit: Even though i also don't think installing TWRP makes a difference, i don't know if that's the case.
I should mention i used "fastboot flash recovery xxx.img" not "... recovery_a" or "... recovery_b".
I don't know if this changes something with access
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
thomaskmaagaard said:
Honestly patching boot image is probably less of a headache. I can even send the images pre-patched if you want. Just one fastboot command
I'd need to know your phone variant and update version.
Click to expand...
Click to collapse
Well, I don't think you have the file I need.
My N100 is a model BE2015, build number 11.0.1BE82CF
I just fastbooted TWRP again and I'm mounting and selecting external_sd but still zero files.
If I flash the TWRP with "fastboot flash recovery xxx.img" is there a way to reverse it if I ever need to?
Again thanks for the help.
.
onlycash said:
My N100 is a model BE2015, build number 11.0.1BE82CF
Click to expand...
Click to collapse
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
thomaskmaagaard said:
Well that might be the problem. That's a carrier locked phone, right? I'm not really familiar with those. I just know they are complicated to mod.
Not sure if you'll even be able to flash recovery and I'm surprised you can fastboot boot. But in theory, (at least on unlocked phones) if you can flash TWRP, you can flash stock recovery from firmware package.
I saw a quite extensive and fairly complicated guide to fully unlock a carrier phone here on XDA, but don't know how well it works or if you have followed any of these steps.
Edit: Also found this, looks like it works with your device: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4245499/
Click to expand...
Click to collapse
Let me start by saying my phone is both SIM unlocked and bootloader unlocked.
The post you linked is talking about the same phone as me but the last post in that thread has an ominous post from someone on Android 11 bricking after trying that. I'm not sure if that works if you're already on 11.
I still can't understand why the TWRP can't see files on my SD card. I think the two missing elements are the fact that you have TWRP flashed to your phone and you're rooted already.
I really can't understand why being rooted would have anything to do with TWRP seeing the files on the SD card so I'm leaning toward it being flashed that's the difference.
I would like to try flashing TWRP but I'm still unsure how, plus I'm guessing I have no recovery if that goes awry.
If I could just get the zip fashed it should patch my boot.img and give me root fairly easily.
Does anyone have any suggestions as to ways back if the TWRP flash goes bad plus just what command do I use to flash it and what happens to the other slot?
.
Okay, so...
I have now tried flashing stock boot and stock recovery on both a and b, verified no root access, then trying "boot twrp.img"
Still able to see files on micro sd.
I then attempted to flash magisk zip to verify this method working.
Didn't seem to work at first, but i think this was due to me messing something up with active slot. Fastbooted into twrp again and flashed magisk again and it works.
So, in short; This absolutely works on a BE2013, but this recovery might not play well with your BE2015.
OP asks about potential problems so maybe you'll have luck messaging him and you could investigate together? Just a suggestion.
I'm sorry, but I really don't know how to help with that model. It's problematic that there's no firmware payload available. If you find one or if you can somehow dump the boot image from the phone then I'd be optimistic and happy to help any way I can.
onlycash said:
How did you install the Magisk zip file?
.
Click to expand...
Click to collapse
I have the BE2011 model. Useful on this variant?
I would like to install the latest Google OTA update but also keep root.
I heard you can do the following to retain root:
Open magisk
Click on "uninstall magisk"
You will then be asked if you want to "completely uninstall" or (restore image). You will choose to restore image
This restored image allows you to update your phone and you still retain root AS LONG AS YOU DON'T RESTART. So you do just that, you update and DON'T restart
After the update go back to magisk manager and press install. You will be asked how you want to install it (patch boot image, direct install etc). Select inactive slot.
Reset phone and enjoy!
But I walk against a wall against at step 3
Magisk never backed up my original boot image as I flashed it through fastboot. Where do I place the original image for magisk to find it? And what will my file have to be called? Magisk is probably looking for a certain file name
Then I also have a problem with step 5. I only get the option to direct install and patch boot image. I am not given the option to install it in an inactive slot.
What do you guys do to update your phone? Install it manually through fastboot? I would just prefer to skip the fastboot part going on. I just the commands so rarely that I always forget them and always have to look them up xD. Just seeing if this community know something I don't
I have a poco f3 using lineage os
So I updated Magisk to 26.1 and zygdisk wasn't working so I deactivated the modules via magisk in order to try to make it work. But the phone never rebooted it got stuck on bootloop. I tried to delete the modules via twrp but it didn't work, the phone would not boot and it showed the fastboot screen. Then I tried via orange fox, and i got the same problem. The thing is that all of my files are still in my phone and i made the stupid mistake of not doing any backup because i was travelling when i updated magisk.
Even if i try to do i dirty flash, add or delete anything via recovery the files do not get erased or installed. Everything stays the same after i restart.
bemuratt said:
I have a poco f3 using lineage os
So I updated Magisk to 26.1 and zygdisk wasn't working so I deactivated the modules via magisk in order to try to make it work. But the phone never rebooted it got stuck on bootloop. I tried to delete the modules via twrp but it didn't work, the phone would not boot and it showed the fastboot screen. Then I tried via orange fox, and i got the same problem. The thing is that all of my files are still in my phone and i made the stupid mistake of not doing any backup because i was travelling when i updated magisk.
Even if i try to do i dirty flash, add or delete anything via recovery the files do not get erased or installed. Everything stays the same after i restart.
Click to expand...
Click to collapse
I would try this:
Download magisk 26.1
Place into a folder
Make a copy of it in the same folder
Rename one copy to magisk.zip
Rename the other copy to uninstaller.zip
(example: magisk.apk would be renamed to magisk.zip, you want to make sure you're changing the file type from an apk to a zip)
Boot into recovery
Your pc should recognize your phones storage to transfer things in recovery
Transfer folder to phone (if needed)
Flash uninstaller.zip
Clear cache
See if your phone boots
If it does, you can boot back into recovery and try to flash the magisk.zip. If bootloop still, flash uninstaller.zip again
Zinnz said:
I would try this:
Download magisk 26.1
Place into a folder
Make a copy of it in the same folder
Rename one copy to magisk.zip
Rename the other copy to uninstaller.zip
(example: magisk.apk would be renamed to magisk.zip, you want to make sure you're changing the file type from an apk to a zip)
Boot into recovery
Your pc should recognize your phones storage to transfer things in recovery
Transfer folder to phone (if needed)
Flash uninstaller.zip
Clear cache
See if your phone boots
If it does, you can boot back into recovery and try to flash the magisk.zip. If bootloop still, flash uninstaller.zip again
Click to expand...
Click to collapse
I did what you said, uninstalled magisk then reboot system and it goes straight to the fastboot screen. Then I boot recovery again and there's no sign of the folders, it is like everything is the same as when the phone had its first bootlopp
bemuratt said:
I did what you said, uninstalled magisk then reboot system and it goes straight to the fastboot screen. Then I boot recovery again and there's no sign of the folders, it is like everything is the same as when the phone had its first bootlopp
Click to expand...
Click to collapse
Have you tried booting from the other slot? If you're on a switch to b, or vise versa
Yes I did, but partition B shows no files even with twrp or orange fox. It's like nothing gets actually deleted or written on the phone.
I don't know what to do. Because whatever i'm flashing be the recovery, be magisk, be any folder whatsoever, it doesn't stay in the device after rebooting
bemuratt said:
I don't know what to do. Because whatever i'm flashing be the recovery, be magisk, be any folder whatsoever, it doesn't stay in the device after rebooting
Click to expand...
Click to collapse
And even if i try to uninstall magisk, and the folders go away, its always there when i boot recovery again
Hi,
In fastboot, re-flash the original boot.img of your installed rom, maybe it'll work.
Good luck.
I did that, no success. I'll make a nanodroid backup, a clean flash and see what i can save from the backup!
Guys, I solved it.
I found out that the bootloop happened because I deactivated magisk module for android Auto. The system wouldn't start if the app didn't find the module. So I was trying to deleted via recovery, but it was not possible as I mentioned above.
So i did a backup with orange fox of the data and internal storage. Wiped the phone back to factory settings and reflashed the lineage os from scratch and rooted it again. Then i went back to recovery, restored everything and i was able to delete android auto and the phone booted with everything in it, all my pics, chats you name it!
Thanks for the help guys!