How to uninstall Magisk without accessing the operating system or enabling USB debugging?

samulksy commented 1 year ago

Hello.

I have a Moto G5S Plus phone that is stuck in an infinite loop, that is, it keeps restarting endlessly without being able to load the operating system. This happened after I moved Magisk from a system file to a regular file. Magisk is a tool that allows rooting the phone and modifying the operating system without changing the system partition. Rooting is for an anti-theft tracker to work on the phone's system. I've tried various ways to uninstall Magisk from my phone, but none of them worked. I can't access the operating system or enable USB debugging, which are requirements for most file-copying methods and device settings. Enter recovery mode or bootloader mode, which are special modes that allow accessing some advanced functions of the device is possible, but do not offer the option to copy the files. The recovery mode would be to delete all current files. Deletar novos arquivos não é o que eu I need. Installing a new ROM, performing a hard reset, or unlocking the bootloader, those features are accessible. I can only see the black screen with the Android robot, which presents the following options: qcom, bp tools, barcodes, factory mode, power off, recovery mode, and restart bootloader. None of these options allow me to uninstall Magisk or restore the original operating system. I have the IMEI of my phone, which is a unique code that identifies my device and can be useful for blocking or tracking my phone in case of loss or theft. I also have important data on my phone that I would like to back up before performing any procedures that could erase them. I would like to know if anyone from the Google community has any tips or solutions for my problem. I've already searched the internet and haven't found anything that helped me. I'm desperate and don't know what else to do. Please, if anyone can help me, I would be very grateful.

Thank you for your attention.

MagiskBot commented 1 year ago

Invalid bug report, automatically closed. Please report issues using the latest debug Magisk build (version code: 26301).

pndwal commented 1 year ago

You should stop spamming bug issues... please get such help in proper XDA forums in future as instructed in bug report template...

However, since it seems you've been messing with /system (this is fraught and Magisk itself doesn't do it being 'systemless'), dirty flashing your ROM should restore booting assuming nothing in data is too messed up... Might need to experiment with button presses to get fastboot mode etc...

samulksy commented 1 year ago

When I encounter more issues, I will send them to the XDA forum. The Magisk website indicates that contact should be made exclusively through Github. I sent more than three messages because a bot was indicating that they were not sent. I became skeptical that the messages were reaching you, so I decided to stop sending them. To my surprise, you responded to my messages. Please provide the complete procedure to be followed, as what you said was incomplete. Em domingo, 17 de setembro de 2023 às 04:42:18 BRT, pndwal @.***> escreveu:

You should stop spamming bug issues... please get such help in proper XDA forums in future as instructed in bug report template...

However, since it seems you've been messing with /system (this is fraught and Magisk itself doesn't do it being 'systemless'), dirty flashing your ROM should restore booting assuming nothing in data is too messed up... Might need to experiment with button presses to get fastboot mode etc...

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

samulksy commented 1 year ago

Another question: Can the procedure you are going to send be done without the USB debugger activated? If the procedure cannot be done without the USB debugger activated, please send the procedure for the USB debugger to be activated without direct access to the Android system. Thanks.

Em domingo, 17 de setembro de 2023 às 04:42:18 BRT, pndwal ***@***.***> escreveu:

You should stop spamming bug issues... please get such help in proper XDA forums in future as instructed in bug report template...

However, since it seems you've been messing with /system (this is fraught and Magisk itself doesn't do it being 'systemless'), dirty flashing your ROM should restore booting assuming nothing in data is too messed up... Might need to experiment with button presses to get fastboot mode etc...

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

ItsJustSomeDude commented 1 year ago

You say you cannot access Fastboot, but you did say you can see the Android Robot with all the different options. pndwal recommended a dirty flash, which is probably your best bet.

The way to do this is to download the stock Rom for your device to a computer. Then, boot into Fastboot, the screen with the robot and all the options you listed. Next, use fastboot flash on the computer to flash the stock Rom over your broken setup.

samulksy commented 1 year ago

Hello Pndwal, Thank you for your answer.

You didn't provide the procedure with the commands for me to update the corrupted configuration. I need a procedure of update that preserves the current configuration, files, and installed apps on the phone. If the update is supposed to delete the current configuration, files, and installed apps, I need you to provide the procedure for copying the configuration, files, and installed apps. I also need the procedure for enabling USB debugging without access to the operating system. I appreciate your understanding, and I need your guidance. Thank you for your attention. Em domingo, 17 de setembro de 2023 às 18:13:22 BRT, ItsJustSomeDude @.***> escreveu:

You say you cannot access Fastboot, but you did say you can see the Android Robot with all the different options. pndwal recommended a dirty flash, which is probably your best bet.

The way to do this is to download the stock Rom for your device to a computer. Then, boot into Fastboot, the screen with the robot and all the options you listed. Next, use fastboot flash on the computer to flash the stock Rom over your broken setup.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

pndwal commented 1 year ago

The Magisk website indicates that contact should be made exclusively through Github.

It doesn't... it says "GitHub is only source where you can get official Magisk information and downloads"

Further, the Magisk Issues/bug report instructions say 'don't ask here for instructions' and list several XDA forums for support... Yours is not a Magisk issue/bug...

I sent more than three messages because a bot was indicating that they were not sent.

No it didn't... Issue was received but bot closed it as invalid as you didn't follow template and include latest debug Magisk build version code in text body. 😬

Devs will close also for failing to follow other instructions like submitting logs generated from builds other than debug, but sometimes they'll actually re-open valid issues closed by bot and overlook initial requirements... This is not a valid Magisk issue however.

I became skeptical that the messages were reaching you, so I decided to stop sending them. To my surprise, you responded to my messages.

Some members are happy to help / share knowledge in dead issues... nb. when this happens the helpers are often just enthusiasts/modders from XDA forums etc... Magisk Devs are more strict with rules and, frankly, busy enough with real issues, regressions etc.

Please provide the complete procedure to be followed, as what you said was incomplete.

If you don't know how or have difficulty dirty flashing or obtaining a fastboot type ROM for your device, which usually requires a PC and device specific software, you'll need to get proper advice eg from XDA forums for your device in any case... My advice was complete for the purpose...

You didn't provide the procedure with the commands for me to update the corrupted configuration.

Seek device specific instructions as mentioned above.

I need a procedure of update that preserves the current configuration, files, and installed apps on the phone. If the update is supposed to delete the current configuration, files, and installed apps, I need you to provide the procedure for copying the configuration, files, and installed apps.

I said dirty flash ROM... that's the procedure that doesn't wipe data... Clean flashing basically includes factory reset and wipes/formats /data...

I also need the procedure for enabling USB debugging without access to the operating system.

Generally not needed for stock ROMs... Again, seek device specific advice...

samulksy commented 1 year ago

I understand, but the way you present it, I'm going to lose everything on my cell phone. Formatting will delete everything. I need copies of the files, copies of installed applications and a copy of the configuration on the cell phone. After the copies are saved, I accept the formatting. How can I copy files, applications and configuration? You haven't answered this question yet. Thank you. Em segunda-feira, 18 de setembro de 2023 às 03:12:00 BRT, pndwal @.***> escreveu:

The Magisk website indicates that contact should be made exclusively through Github.

It doesn't... it says "GitHub is only source where you can get official Magisk information and downloads"

Further, the Magisk Issues/bug report instructions say 'don ask here for instructions' and list several XDA forums for support... Yours is not a Magisk issue/bug...

I sent more than three messages because a bot was indicating that they were not sent.

No it didn't... Issue was received but bot closed it as invalid as you didn't follow template and include latest debug Magisk build version code in text body. 😬

Devs will close also for failing to follow other instructions like submitting logs generated from builds other than debug, but sometimes they'll actually re-open valid issues closed by bot and overlook initial requirements... This is not a valid Magisk issue however.

I became skeptical that the messages were reaching you, so I decided to stop sending them. To my surprise, you responded to my messages.

Some members are happy to help / share knowledge in dead issues... nb. when this happens the helpers are often just enthusiasts/modders from XDA forums etc... Magisk Devs are more strict with rules and, frankly, busy enough with real issues, regressions etc.

Please provide the complete procedure to be followed, as what you said was incomplete.

If you don't know how or have difficulty dirty flashing or obtaining a fastboot type ROM for your device, which usually requires a PC and device specific software, you'll need to get proper advice eg from XDA forums for your device in any case... My advice was complete for the purpose...

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

samulksy commented 1 year ago

Detail: I didn't follow the template and didn't include code from the latest debug build version of Magisk in the body of the text. I'm not familiar with posting messages on GitHub. I've never submitted a message on GitHub before.

Em segunda-feira, 18 de setembro de 2023 às 03:12:00 BRT, pndwal ***@***.***> escreveu: