yashsingh1/xdaforums huggingface dataset:
[Magisk] A.Ahmed79:
thank you very much for your reply, i can't flash using odin as my phone isn't going into download mode nor getting detected in my pc due to this, it just stays stuck on the samsung logo.

can you please tell me how do i go about flashing the boot.img in my case?
[Magisk] ineedroot69:
via Fastboot
[Magisk] teknomedic:
SUCCESS... OMG... I'm not sure why the "backup" images refused to work.

I'm lucky that I have two identical V30s. The only thing that worked was backing up my boot from my other V30, copied the files over... and then...

...I couldn't install the backup from the other phone. It refused to give me an option to select which partition to install on.... however.... I found this thread:

https://xdaforums.com/t/twrp-no-partitions-selected-for-restore.2932954/

Basically... TWRP backs up the files one directory too deep into a directory with the date/time of the backup. Simply moving the three backed up files UP one directory finally gave the option to select my boot partition.

As an example...

TWRP\BACKUPS\"phone name"\"date&time" (backup files location) --this is too deep--

TWRP\BACKUPS\"phone name" (move backup files to here)

Once the files are moved everything worked and I'm back up and running. heh

It's kinda f'ing dumb that TWRP can't restore files from the directory it makes itself, just saying.
[Magisk] A.Ahmed79:
thanks again, well i was able to somehow get into the download mode, can i use odin to flash the stock boot.img?

secondly, will doing this wipe my phone? i have many important files saved on my phone which i need to save at all costs. :(
[Magisk] ineedroot69:
provably you need to add the stock boot.img on odin as AP

no flashing boot.img would just result too being unrooted and your device would (hopefully) run again also if flashing stock boot.img doesn't fix your issue you might want togo full onboard flash stock rom xD

Do you have TWRP installed?
[Magisk] A.Ahmed79:
i really dont mind losing the root as long as all the data is still intact and safe.

yes i have the gui/touch version of TWRP installed, but i can't seem to go into it.. after a couple of hours i finally managed to get into this download mode from being totally stuck on boot screen with the samsung logo on it.

and how would it help if i did somehow manage to get to the TWRP recovery? can't i basically flash the boot.img from odin anyways?
[Magisk] stremmler:
magisk 22.00 update kills the galaxy s10 too. It gets stuck in the bottloader. Opening twrp normally is not possible. connect to the pc via usb cable and then with bixi and volume + it boots into recovery. I then flashed with twrp magisk 21400 and the phone boots.
[Magisk] RigoF:
For the Oneplus 8 pro with 11.0.4.4.IN11AA I had to get a boot.img (for 11.0.4.4IN11AA) and flashed it with adb via fastboot (from PC), then my phone started up without root but still unlocked (and none of my data was lost). I reinstalled Magisk 22.0 (apk) and then put the boot.img on my sdcard and used Magisk to patch my boot.img and then i booted into fastboot and and flashed the patched boot.img via adb fastboot(from my PC). I never orginally had Magisk hidden so not sure why my phone lost root after the Magisk 22.0 update. Hopefully this helps someone onto the right path.
[Magisk] A.Ahmed79:
thank you sooooooooooooooooooooo much! :)(y)

i did exactly as you wrote and my phone is working again.

thanks once again for taking the time and explaining that here. :coffee:
[Magisk] Didgeridoohan:
I see that you already got this up and running again, but I just wanted to point out that the backed up boot image is compressed and need to be unpacked before flashing. Just renaming it does nothing...

As long as the other device is using the same OS it's perfectly fine using the boot image on another device of the same model. It's not a unique file for every individual device...
[Magisk] teknomedic:
That would explain the backups not working then, ha. Is there a built in unpacker in TWRP?

TWRP is great, don't get me wrong, but there have been plenty of times little things like this just bother me from a programming perspective. What's the reason for not including the ability of TWRP to read the compressed image natively or at least offer the option of unpacking the image as a step to installing? Instead it simply does "something" that maybe worked...but then on testing didn't. No error message or indication that it's unable to do what's needed... so I reboot and nothing?.. but it did something... yes? Nope. heh.

Similar to TWRP putting backups that itself can't even use unless you move the files to another location first, lol. Oh well.

Want more fun... my other V30 actually updated without issue... and after fixing my other one with a donated boot backup... now both are running v22 without further work.

Same phones, root, OS version, etc, etc... one bricked. The other perfectly fine. :unsure:
[Magisk] brianforever:
just rename Magisk-v22.0.apk to Magisk-v22.0.zip..boot into TWRP Recovery and flash this and it should work
[Magisk] krbbrk:
This worked perfectly for me. I wasn't having any issues with updating. I hadn't even tried any of the methods yet. I just didn't want to encounter any problems with the update to Ver. 22.

I unhid the Magisk app, booted to TWRP, flashed Magisk-v22.0.zip (which I renamed from Magisk-v22.0.apk), and rebooted to System. My custom kernel loaded its settings successfully, and SU rights were granted to apps appropriately. I opened the new Magisk app, and everything was successfully updated to Ver. 22. SafetyNet checks were successful. I rehid Magisk with no issues.

I'm on a OnePlus 6, running OOS 10.3.8, with TWRP 3.4.0-11.

If you're nervous about attempting to update from within the app on your OnePlus device, I recommend brianforever's advice.
[Magisk] jatzio:
What happened on my case:

See magisk update, update it directly from the magisk manager. Reboot.

After reboot, the magisk manager and magisk app icon has changed (i use custom iconpack). When I opened magisk, it always closed. When I open magisk manager, the status said: magisk is not installed.

Then I read the magisk 22 update description; "unhide magisk manager before update", which i forgot to do. And now my phone is not rooted and can not flash the renamed magisk apk to magisk zip from custom recovery.

Should I clean flash? reroot doesnt work either.
[Magisk] weazie:
Soo.. Sry for possibly repeating this, but how do you root these days after fresh ROM install? When everything is packed in payload.bin? Do I really have to install python and Payload Dumper on either PC or phone to extract boot.img? Or.. Does the abovementioned flashing magisk-v22.0.apk as .zip in recovery root my phone? Sorry, it's been a long time since I last rooted.

Magisk 22 direct install took my phone into bootloop (Moto G6+). I sorted it, but I think I should somehow patch boot.img the next time I'm trying to root.

Edit: Sorted. Renaming the .apk as .zip and then flashing it through recovery works.
[Magisk] techware7:
You can't just rename the file. Is a compressed file. You have to extract the .gz file and then you can flash the boot.img
[Magisk] brianforever:
You are very much welcome, glad I could help :) This is the best way to install Magisk v22 imho :)
[Magisk] pulsarone:
Incroyable qu'une telle mise à jour pourrie reste en déploiement avec un millier de personnes qui vont se retrouver en panne au démarrage ... j'ai passé 4 heures à tout remettre en place avant de tomber ici sur le bon sujet, merci encore à toute votre aide, et honte à le dev.

Mod translation

Unbelievable that such a rotten update is still being deployed with a thousand people who are going to break down at the start ... I spent 4 hours putting everything back in place before coming across the right topic here, thanks again to all your help, and shame on the dev.
[Magisk] fullydeveloped:
I had the same issue. I restored my own boot.img backup (already patched with magisk v21.4). It booted fine, modules and root working - but of course with the Magisk "App" v22.0 installed rather than manager. Thankfully the 22.0 "App" works with a 21.4 patched boot.img.

Should I bother flashing 22.0 through recovery? I'd rather not create yet another issue to resolve. Especially since the original error, when attempting to update "Magisk" through the 22.0 "App": Unsupported/Uknown image format has not been resolved.
[Magisk] mario0318:
Excuse me but this comment really ticks me in a not so funny way. Shame the developer for a "milestone" update which a subset of its user base had some trouble installing? It may be considered stable but in the bigger picture you are still very much dealing with experimental hacking software, my friend. Shame on the dev? No. How about you put down that pitchfork and have shame on yourself for not only taking an astonishing 4 hours to restore your device, shaming topjohnwu, and not bothering to translate your own post to English. Sheesh!
[Magisk] Xdpker06:
I am also stuck in a Fastboot loop on my Oneplus 7 pro. Clicking into recovery from fastboot brings me back into fastbook. Computer isn't recognizing the phone as a fastboot device so I can't even use the fastboot boot recovery.img command to get into recovery and flash a new boot image. Any tips?
[Magisk] newkydawg:
Make sure you have installed the usb drivers for your Oneplus 7 Pro. I had the same issue with my Nexus 6P. After I installed the drivers, fastboot recognized my Nexus and I was able to flash the boot.img and TWRP.
[Magisk] Xdpker06:
Yeah, I installed drivers that somebody recommended on the 7 Pro forum. Still not recognized by the computer. Exclamation mark on the device in device manager. I have also used ADB and fastboot on this computer and this phone before.
[Magisk] Xdpker06:
Is it possible for fastboot to get corrupted somehow? Tried on 2 different computers, same problem. Oneplus 3T gets recognized no problem with the fastboot devices command.
[Magisk] fullydeveloped:
You should be able to hold the power + volume down buttons while powering on to boot into recovery mode. Hard to imagine a corrupted boot.img would break that functionality.
[Magisk] Xdpker06:
Yeah, unfortunately it goes right into fastboot. Selecting the recovery option in fastboot also brings it right back into fastboot.
[Magisk] fullydeveloped:
It looks like power + volume down actually sends you to (most likely) fastboot, where they expect you to select recovery from there. Try power + volume up, or last option all 3 buttons. Obviously ensure you're holding them the entire time, from before the device powers off until it's fully on.

If OP7 doesn't have the hardware buttons available to enter recovery directly, that's indeed a huge oversight.

In the meantime keep scouring online for people with fastboot connecting to pc issues - there might be a solution out there.
[Magisk] Xdpker06:
The 7 pro does have hardware buttons, but I tried different combinations, no joy. This morning the phone woke itself up and now I can't even turn it off. Selecting power off in the bootloader will just turn off the phone momentarily before the phone boots right back up into it.
[Magisk] Zincoshine:
Had my phone not failed with the updated 22.0 manager I would have updated magisk itself as well and ended up with a brick. Holy crap I am so thankful to my phone right now. Time to make a backup.
[Magisk] DJBhardwaj:
Don't use Minimal ADB, it might be using outdated binaries of platform-tools.

Download the latest binaries from here and launch the command-line inside the working directory.
[Magisk] aaanonymous:
Experienced a similar issue with my Moto G Power XT2041-4 (sofia) after flashing the January update (QPMS30.80-63-6-8-5) a few days ago. Flashing the the Magisk v22.0 patched boot.img causes bootloop. Then flashed Magisk v21.4 patched boot.img results in bootloop as well. Flashing the stock boot.img from this update allows phone to boot normally but, of course, without root.

The phone worked fine with the November update (QPMS30.80-63-6-8-3) running Magisk v22.0. I updated from v21.4 to v22.0 using the Magisk app direct install while on this update.

I suspect there may be some changes in the new boot.img that conflict with the changes Magisk makes when patching it.

Any thoughts???
[Magisk] ineedroot69:
Flash stock boot.img
[Magisk] mon0theist:
This happened to me too on my LG V30. I was able to get into TWRP and re-flash my stock ROM zip. Not sure if I should try Magisk v22 again or just stick with 21.x
[Magisk] Aashirg:
this solution worked for me, thanks very much
[Magisk] naveen_reloaded:
I did and now twrp doesnt mount slot a or b..

also currently i tried to install twrp latest version (twrp-3.4.0-10-guacamole-) ,it installed on both slot a and slot b as per the messages/logs it showed , but when i boot into recovery its showing "twrp-3.4.0-09-guacamole" , one version older .. and its failing to load both slot a and b , so where is twrp booting from or into ?

Please help.. being without phone for past two days and its killing my day to day activity...
[Magisk] naveen_reloaded:
I extracted the boot.img from havoc OS which my phone was last running. After that twrp fails to load both the slots since they are encrypted(?)
[Magisk] naveen_reloaded:
Even tried to change slot using fastboot and trying to boot - its showing circle animation only. :(

The boot.img i flashed changed something ? or isnt showing the right path for twrp to boot properly ? twrp only boots into "unmodifid system partition" , from there i cant mount userdata / internal storage
[Magisk] naveen_reloaded:
Solved :

extracted Boot.img was one version older than the one on the phone.. so after flashing correct boot.img through fastboot , i was able to get the phone back on..

Thanks to a kind heart on telegram.
[Magisk] aaanonymous:
------------------------------------

Anyway, I discovered the solution to my dilemma mentioned above by searching thru forums and Youtube. This may be helpful to those who have flashed the latest ROM update for their phone, then flashed the Magisk patched boot.img and now the phone is unable to boot to the OS.

It appears that the bootloop caused by flashing the 'Magisk_v22.0_Patched_boot.img' was due to installed Magisk modules. This is what worked for me:

1. Boot into TWRP from fastboot.

2. Using the File Manager in TWRP navigate to the '/data/adb/modules/' folder where the Magisk modules reside as folders. Delete all of them.

3. If Magisk is NOT installed then flash 'Magisk_v22.0_Patched_boot.img' as Boot or 'Magisk_v22.0.zip' in TWRP and boot phone to the OS.

4. Open the Magisk app to configure Magisk and install the Magisk modules.

5. Reboot.

The phone is now running the latest ROM, rooted with Magisk v22.0, passes safety net all without erasing user data...
[Magisk] choppedartisan:
Let me add my update. I didn't read all the comments.

I came across the same situation. Now my phone works. It's mediatek. It also has a messed up usb connector pin. I thought my phone was bricked when I flashed Magisk with Twrp. I couldn't boot into recovery. I could only get into fastboot. I am not sure if the reason why I couldn't flash boot.img or recovery.img was because of the wonky usb connector. I even tried SP flash tool, but to no result. By then, it was hard bricked, compared to soft bricked when I flashed Magisk 22. I left my phone on the shelf for a few days.

I had read somewhere that if I open up my phone (in hard brick state) and do some tinkering, I could force it to boot. I went and bought a screwdriver set today. It was wasted money. I tried a last time to boot before opening the phone up. SP Tool detected my phone. I flashed the boot.img and recovery.img. It's fine now. I did some quick research for the uninstall file for Magisk and came across this thread.
[Magisk] naveen_reloaded:
For those who are still searching for an answer .. Here

https://xdaforums.com/t/latest-magi...thout-losing-everything.4238147/post-84546903

REMEMBER ONE THING ..

You should extract the boot.img file from the ROM which was used on the phone before bricking. In my case it was "Havoc-OS-v3.12-20201219-guacamole-Official-GApps"

Download payload extractor

Open your ROM zip file and extract payload.bin file

Copy this file into payload extractor "input" folder and run the extractor. It will extract the boot.img to "output" folder

now use this boot.img to flash . remember to place the boot.img file in android sdk folder or where your adb.exe and fastboot.exe is installed folder.

put phone into fastboot mode. If you cant , try "Tool All in One" tool , which might help you to put phone into fastboot mode/Bootloader , or from twrp reboot into bootloader.

After than connect phone to pc and run following commands. "better to start cmd inside the folder where adb , fastboot and boot.img is residing."

then run the following commands

Thanks to "D E E P" on TG for the following

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

fastboot reboot

When done properly , this will now boot into your OS and from there dont touch anything . Reboot into TWRP and follow instructions from here https://xdaforums.com/t/latest-magi...thout-losing-everything.4238147/post-84546903

Many thanks to @

ghost323

D E E P on TWRP TG group.
[Magisk] piekny:
I am a total layman. Please help.

How to flash twrp.zip after booting the phone through

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

fastboot reboot

from the post above

Put fone in fastboot mode ?

What commands?

fastboot flash recovery xxx.img

and then

fastboot boot xxx.img

fastboot reboot ????

Maybe other commands. I'm totally lost. I will be grateful for any explanation.

Maybe this is good:

WARNING Magisk v22 soft bricks Oneplus 6T !!!! · Issue #3924 · topjohnwu/Magisk

Hey guys. Was running magisk over years without major issue. Sadly v22 bricked my Oneplus 6T phone and others: https://forum.xda-developers.com/t/rom-stock-fastboot-op6t-stock-fastboot-roms-for-one...

github.com
[Magisk] mon0theist:
Hey OP see my thread here:

https://xdaforums.com/t/psa-magisk-v22-seems-to-soft-brick-stuck-in-fastboot.4241553/
[Magisk] Nikos2k:
I have the same exact problem as the OP with my ONEPLUS 8 PRO

I downloaded the firmware from oneplus's website (11.0.4.4.IN11BA) and extracted the boot.img with the payload dumper, and flashed it through fastboot (fastboot flash boot boot.img)

But it still will not boot to system

When i reboot it, it goes up to the boot animation and then restarts, repeating this several times until it gets to fastboot again

Any ideas?
[Magisk] bobbarker2:
I've always done the following to update my Pixel 4a and I've had it since launch.

1. Download factory image from google

2. Extract boot.img and patch using Magisk. Copy patched_boot.img to PC.

3. Disable/Uninstall all Magisk modules

4. Reboot

5. Reboot to bootloader

6. Flash factory image from google but edit flash-all.bat "fastboot -w update image-sunfish-rq2a.210305.006.zip" to "fastboot update image-sunfish-rq2a.210305.006.zip" - removing the "-w" so it doesn't wipe user data.

7. Let phone boot, then reboot to bootloader.

8. fastboot flash boot patched_boot.img

And then I have updated and achieved root.

But this time phone will not boot after flashing patched_boot.img.

I followed instructions for v22 and unhid Magisk. I was on V22 before flashing March update too.

During google boot animation I can adb, I've even done

adb shell

magisk --remove-modules

Anyone got an idea? I noticed the Security Update says March but the Google Play Services Update is February. Don't think this has anything to do with it though.
[Magisk] mrsweet1991:
I'm on Magisk Canary (Galaxy S8 Plus) and when I updated I had two restarts before a successful boot and since then I've had full random lock ups and "system UI has stopped working" thought I'm lucky I can still access TWRP so I'll re-install Magisk.zip

Also, I noticed a few people stating they couldn't get Fastboot to detect the phone. I couldn't get it to detect either, I've used Minimal ADB, I've tried platform tools straight from the Android Developer website. I even installed Android Studio but Fastboot never detects the phone. I don't see any issues in Device Manager, I've even disabled driver enforcement signiture as I noticed one of the drivers failed to install before but despite everything I've tried, Fastboot will not work. ADB works perfect.. Samsung USB drivers installed as well.. Nothing works lol.
[Magisk] QVA:
My phone has also been damaged. The camera has stopped working. Upgrading to Magisk v22 will smash your system files!
[Touch Diamond, MDA Compact IV Themes and Apps] chattyuk:
I was looking for the Orange UK tf3d theme but i couldnt find it after doing a little search. I did manage to find a post with it for download but the link didnt work. I then realised it was the themes for TouchFlo3d thread but it was an earlier version of it before it was edited, the current OP doesnt have the orange theme there at all. Does anyone know where I can find it? or was there something wrong with it and it had to be taken down?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] 964rs777:
read the forum.as posted earlier today the uk orange mobile hasn't

got the orange theme it ships with htc black theme due to problems with orange theme on uk phones.
[Touch Diamond, MDA Compact IV Themes and Apps] chattyuk:
sorry i havent seen this post. Also why was this theme available to download a while ago on these forums then??
[Touch Diamond, MDA Compact IV Themes and Apps] 964rs777:
it wasn't a uk orange theme.it caused problems thats why it's not here anymore.
[Touch Diamond, MDA Compact IV Themes and Apps] chattyuk:
Im sure it was a orange uk theme as iv seen screenshots of it around here before. Here is the old post I was talking about http://xdaforums.com/showthread.php?t=409901&page=8 Scroll down the page and you will see it and if you click screenshot you will see another picture of it.
[Touch Diamond, MDA Compact IV Themes and Apps] 964rs777:
are you a retard.

the link you gave shows an orange theme in german.

listen good:THERE IS NO UK ORANGE THEME.

orange ships uk phones with htc black theme.

end of.

good job i cant swear on here.:rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] chris.berks:
haha, I was just gonna ask this same question, glad I did a search first!

Gutted, I really like the orange theme too. Us Brits always get the ****ty end of the stick!
[Touch Diamond, MDA Compact IV Themes and Apps] bry1977:
Just to confirm, I work for Orange UK & I have a Diamond on my staff plan. I have just got back from the Orange phone acadamy. There was a offical Orange theme but they had too many issues so went back to the Black theme. They are still working on it but i wouldn't hold your breath :), p.s Orange UK are releasing the HTC Touch HD mid November 12 week's before any other UK network ;)
[Touch Diamond, MDA Compact IV Themes and Apps] adempozhari:
here is an orange theme....

http://htc-diamond.sosref.com/?p=111
[Tilt, TyTN II, MDA Vario III General] jbevan:
I have downloaded and installed this program several times over last 2 days, and I just cannot find any sign of when it is installed! Am using an HTC TytnII with WM6, with TM installed to device memory. Help anyone. Thanks. (PS Sorry if I am being thick - which is very possible)
[Tilt, TyTN II, MDA Vario III General] DaveShaw:
Most add a setting into the System Tab (called X Button or task manager) under Start > Settings. The actual task manager is in the top right of your device, when you are on the today screen. Press the screen where the "X" usaually is and a list of open "programs" will appear.

If this isn't the case, which CAB did you install?

HTH

Dave.
[Tilt, TyTN II, MDA Vario III General] jbevan:
Fab, thanks, found it and its there just as you said! BTW I have being trying to find a today plug-in I must have downloaded a few months ago - that sits at bottomof screen nad allows you to view and close all open apps - c, deleted it by mistake, cant remember program name and cant find it! Doh! Any ideas?
[Tilt, TyTN II, MDA Vario III General] DaveShaw:
It might be an O2 plugin, but I'm not sure. I only had my stock ROM for 2 weeks :)