My MI Max (3gb/64gb 2016) completely bricked out after installing a CM13 rom, it was rooted and had TRWP installed (and working). Screen is black, no Led's.
I've tried connecting it to my Windows 10 (64 Bits) PC, turned Driver Signature off. It recognizes something when I connect my MI Max but cannot load the correct USB (Serial) drivers so I cannot use MIFlash to restore the firmware. Who can tell me what drivers I need to install (tried a lot of Qualcomm drivers but non are recognized by windows and therefor not working for MI Flash (Beta)). It is driving me crazy.
The device manager states Unknown USB Device (Device Descriptor Request Failed)
PLEASE HELP
hey buddy just follow this guide exactly and you'll be up and running like nothing happened before.heres the link http://en.miui.com/thread-3282-1-1.html. if the device doesn't get into edl mode with the mentioned button combo (as it happened to me).press the volume up+vol down + power (all 3 buttons simultaneously) and let go once u feel a vibration.once u get into edl mode the screen will be blank,no button or notification lights,just will show up in ur PC device manager after u install the drivers.I personally used this guide and the linked files to upgrade my mi max hydrogen (3gb ram/32gb) from global stable to global developer on win 10 64bit
Any luck?
[deleted]
i wonder why people post questions and disappear.
maybe he solved his problem...
Hello, I have also managed to brick my Mi Max while trying to flash RR ROM with TWRP.
My phone is completely dead, when trying to get into EDL mode the phone doesn't respond as mentioned in this thread.
The PC therefore doesn't recognized phone as HSUSB_BULK only as "unknown..." how to proceed ?
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
"I know that I won't get any unlock at the moment as the wait period is not over. "
You managed to start the unlock timer using the tool though?
I think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after. (you load fastboot with power - & volume?)
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
sathariel74 said:
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
Click to expand...
Click to collapse
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google... Then click on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mother_Teresa said:
You managed to start the unlock timer using the tool though?
Click to expand...
Click to collapse
Well, I don't see any timer in the tool. However the new flash tool doesn't seem to promising (that batch one). Also in XiaomMiTool I don't see any timer. So maybe the registration is already messed up?
Mother_Teresa said:
think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after.
Click to expand...
Click to collapse
Well, this one does not work for me as it is locked...so I suppose this is a dead end at the moment. Tried this in Linux (I am more comfortable with).
Mother_Teresa said:
(you load fastboot with power - & volume?)
Click to expand...
Click to collapse
Yes, I actually do that usually (besides of the automatic Fastboot loading from XiaoMiTool).
Mother_Teresa said:
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
Click to expand...
Click to collapse
Yes, it gives some connected sound in both modes (normally booted - can even mount the phone storage - and in fastboot). Not sure about the device correctly installed when in fastboot - I tried to follow some threads/videos on that but somehow it looked different for me.
X0PIRAT3 said:
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google..; Clique on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
sathariel74 said:
...
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
Click to expand...
Click to collapse
Yay, well done.
I kept default MIUI and rooted with Magisk (install this in Magisk app to fix safetynet pass).
More details here.
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
sathariel74 said:
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
Click to expand...
Click to collapse
Not to bash etc but what is so bad?
I installed my preferred launcher (Nova) and it works for being a familiar front-end.
Options and tweaks are mostly there these days in the settings (fe. flashlight on double-press) and if not there is root.
is it bloatware? (if so, can we fix it? )
Lineage is of course a safe bet and I probably end up trying some but I need some encouragement .
BTW: beware the Miu Flash tool not enabling 'lock device' when flashing.
edit: how to use smileys. Now it seems super happy but without it seems so serious....
Well, besides of lack of trust (which is most likely just my issue), I really dislike that "all at startscreen" quite a lot. And yes, those 20-30 apps that I was able to delete plus the 20 apps I would like to delete are another thing showing me that this ROM is not for me. Especially that memory manager stuff that enables your "high performance game experience" is a sign to better stop using MIUI. There are also some bugs (strange behaviour I saw/felt - can't even really describe) I didn't like.
I like to manage my stuff myself, even if this is more work. But I somehow know how its "glued" together. So LineageOS is what I like. Or some of the other AOSP ROMs available.
Hello
Hope someone can help I cannot find a definitive answer hopefully in layman's terms for this problem.
Redmi Note 8 Pro Bergonia 6gb ram 128gb storage Miui 12 Global
Tried CFW 2020 Anti-Brick Corvus ....., Afterwards Phone booted then went completely dead apart from power light when connected to usb
Came accross SP Flash Tool this did help, phone now boots, all seems ok apart from when in fastboot when connecting usb to PC/laptop (tried several cables with a PC and laptop using USB 2.0 all worked prior to trying CFW) all with same result phone stays in fasboot for approx 20 seconds then reboots. Don't know if this is relevant, if I put the phone into fastboot and do not connect to usb, fastboot remains on. Is there anyway I can install twrp and root, or am I stuffed?
Thanks
Smokes
Smokes68 said:
Hello
Hope someone can help I cannot find a definitive answer hopefully in layman's terms for this problem.
Redmi Note 8 Pro Bergonia 6gb ram 128gb storage Miui 12 Global
Tried CFW 2020 Anti-Brick Corvus ....., Afterwards Phone booted then went completely dead apart from power light when connected to usb
Came accross SP Flash Tool this did help, phone now boots, all seems ok apart from when in fastboot when connecting usb to PC/laptop (tried several cables with a PC and laptop using USB 2.0 all worked prior to trying CFW) all with same result phone stays in fasboot for approx 20 seconds then reboots. Don't know if this is relevant, if I put the phone into fastboot and do not connect to usb, fastboot remains on. Is there anyway I can install twrp and root, or am I stuffed?
Thanks
Smokes
Click to expand...
Click to collapse
1/Try flash with Miflashtool
2/Try unbrick hardbrick method. You can find on many: Youtube, Telegram, Github, XDA,... Keep phone in EDL mode by bypass and flash by Sp flash tool.
Thank you SP flash tool and a newer driver fixed it.
Use USB 2.0 ports. (use usb 2.0 hubs if you dont have usb 2.0 ports)
Install drivers properly (it should say Android Bootloader Interface in Device Manager)
Hello friends,
I would kindly ask you to try to help me un-brick my Mi Pad 5 (nabu). Thanks in advance.
First of all, let me give you some info what happened and what I have/haven't tried:
HOW IT GOT BRICKED:
1. Installed Awaken OS, it went great and fast and was setting up the tablet
2. Installed Magisk Module and activated it, it went great
3. Started installing modules which I use, it went great
4. Found a post on Awaken OS thread from the user nabulsi08 about some modules that he uses and decided to try Mi Sound and Miui Core which he attached and claimed that it was safe to use with that ROM.
5. My tablet was connected to my computer via USB and it asked to re-confirm that I would like to have USB debugging ON, but I ignored the notification in hurry and rebooted the device in order to activate mentioned modules.
6. Phone got stuck on MI logo, not forwarding to boot animation of the ROM at all.
WHAT HAVE I TRIED:
1. I have tried to clean re-install the ROM, but now, when I wanted to check ADB devices, it is not showing my device at all since USB debugging was left unticked.
2. I was able to enter FASTBOOT and downloaded Mi Flash Tool (latest version and also tried several older versions) and Fastboot ROM (both v13 and v12.5), installed all drivers, started flashing the Fastboot ROM(s) but it was all successfully done in less then 3 seconds and nothing was changed, still stuck on MI logo.
3. The same thing whichever option I select - Clean all / Save user data / Clean all and lock in Mi Flash Tool
4. Found some tutorials online, changed the location of Fastboot ROM to C:/, renamed the rom to short name, nothing helped, 1-3 seconds and it says success but nothing changes
5. Also tried to change USB cable, USB port, nothing helped.
6. Also tried copping all files from IMAGE folder to ADB folder and tried starting flash_all.bat script but it does not start at all.
7. CMD command fastboot devices shows my device, but command adb devices does not show anything (again, due to the USB debugging off)
8. After something that I did, not sure what, I think that I was able to restore stock recovery, as I now can see the recovery screen (with TWRP it is not possible, you do everything via CMD) and options like Wipe Data, Mi Assistant, etc.
9. Found online a way to enter EDL mode (if I am not wrong), it restarts from fastboot and enters the recovery screen but the tablet is again visible in Mi Flash Tool just like when you are in fastboot mode, tried flashing Fastboot ROM from EDL as well, again 1-3 seconds and ''success'' without any actual success.
WHAT WAS NOT TRIED:
1. I do not know how to flash file by file from IMAGE folder using CMD as you need to know what file represents what exactly (for example: fastboot flash system ____________,img, - not sure which file represents system, and this is the case for all files). My knowledge is not that high.
2. I am using Windows 11, I will try tomorrow on Windows 10 as well, maybe that will fix the issue.
3. Whichever is not mentioned above and you suggest
My device is not shown under Device Manager of Win11. All drivers installed as requested by Mi Flash Tool.
I am not sure if this is soft or hard brick of the device, seen online that if you are able to enter Fastboot and/or Recovery it should not be hard brick of the phone/tablet, but really not sure because of that USB Debugging thing. I have had so much similar issues in the past with Xiaomi and with other brands of phones, but was always able to fix the issues with online tutorials. In this case, I think that I tried almost everything that I have found, but nothing helps. Just wanted to mention that before Awaken OS, I was using ArrowOS for several months, and just wanted to change and try Awaken as I have seen that it gets good feedbacks from users. Also, it is not needed to mention but I will anyway, bootloader is unlocked, but you knew that since I was doing the customizations already.
So guys, all in all, I spent 3 full days trying everything I was able to find, in a very cold room where my PC is located without any success, but I might be able to catch a cold. I would really need your help, assist, support, suggestions.
Thank you all in advance for reading this awfully long post and for your kind suggestions.
I had a similar problem when going from AwakenOS (without magisk) to MIUI.
It seemed impossible to flash with different methods, though fastboot mode working on the tablet.
Finally I was able to restore MIUI (fastboot version) with the latest Mi Flash Pro (Win10), see here.
UniNick said:
I had a similar problem when going from AwakenOS (without magisk) to MIUI.
It seemed impossible to flash with different methods, though fastboot mode working on the tablet.
Finally I was able to restore MIUI (fastboot version) with the latest Mi Flash Pro (Win10), see here.
Click to expand...
Click to collapse
I have also tried that Mi Flash Pro, today, but on Win11, it gets me to the same place with Mi Flash Tool, and I again have the same issue - done in less then 3s and false "success". Thanks anyhow, I will be able to try with Win10 tomorrow, maybe it makes some difference.
Shoomyrovich said:
Hello friends,
I would kindly ask you to try to help me un-brick my Mi Pad 5 (nabu). Thanks in advance.
First of all, let me give you some info what happened and what I have/haven't tried:
HOW IT GOT BRICKED:
1. Installed Awaken OS, it went great and fast and was setting up the tablet
2. Installed Magisk Module and activated it, it went great
3. Started installing modules which I use, it went great
4. Found a post on Awaken OS thread from the user nabulsi08 about some modules that he uses and decided to try Mi Sound and Miui Core which he attached and claimed that it was safe to use with that ROM.
5. My tablet was connected to my computer via USB and it asked to re-confirm that I would like to have USB debugging ON, but I ignored the notification in hurry and rebooted the device in order to activate mentioned modules.
6. Phone got stuck on MI logo, not forwarding to boot animation of the ROM at all.
WHAT HAVE I TRIED:
1. I have tried to clean re-install the ROM, but now, when I wanted to check ADB devices, it is not showing my device at all since USB debugging was left unticked.
2. I was able to enter FASTBOOT and downloaded Mi Flash Tool (latest version and also tried several older versions) and Fastboot ROM (both v13 and v12.5), installed all drivers, started flashing the Fastboot ROM(s) but it was all successfully done in less then 3 seconds and nothing was changed, still stuck on MI logo.
3. The same thing whichever option I select - Clean all / Save user data / Clean all and lock in Mi Flash Tool
4. Found some tutorials online, changed the location of Fastboot ROM to C:/, renamed the rom to short name, nothing helped, 1-3 seconds and it says success but nothing changes
5. Also tried to change USB cable, USB port, nothing helped.
6. Also tried copping all files from IMAGE folder to ADB folder and tried starting flash_all.bat script but it does not start at all.
7. CMD command fastboot devices shows my device, but command adb devices does not show anything (again, due to the USB debugging off)
8. After something that I did, not sure what, I think that I was able to restore stock recovery, as I now can see the recovery screen (with TWRP it is not possible, you do everything via CMD) and options like Wipe Data, Mi Assistant, etc.
9. Found online a way to enter EDL mode (if I am not wrong), it restarts from fastboot and enters the recovery screen but the tablet is again visible in Mi Flash Tool just like when you are in fastboot mode, tried flashing Fastboot ROM from EDL as well, again 1-3 seconds and ''success'' without any actual success.
WHAT WAS NOT TRIED:
1. I do not know how to flash file by file from IMAGE folder using CMD as you need to know what file represents what exactly (for example: fastboot flash system ____________,img, - not sure which file represents system, and this is the case for all files). My knowledge is not that high.
2. I am using Windows 11, I will try tomorrow on Windows 10 as well, maybe that will fix the issue.
3. Whichever is not mentioned above and you suggest
My device is not shown under Device Manager of Win11. All drivers installed as requested by Mi Flash Tool.
I am not sure if this is soft or hard brick of the device, seen online that if you are able to enter Fastboot and/or Recovery it should not be hard brick of the phone/tablet, but really not sure because of that USB Debugging thing. I have had so much similar issues in the past with Xiaomi and with other brands of phones, but was always able to fix the issues with online tutorials. In this case, I think that I tried almost everything that I have found, but nothing helps. Just wanted to mention that before Awaken OS, I was using ArrowOS for several months, and just wanted to change and try Awaken as I have seen that it gets good feedbacks from users. Also, it is not needed to mention but I will anyway, bootloader is unlocked, but you knew that since I was doing the customizations already.
So guys, all in all, I spent 3 full days trying everything I was able to find, in a very cold room where my PC is located without any success, but I might be able to catch a cold. I would really need your help, assist, support, suggestions.
Thank you all in advance for reading this awfully long post and for your kind suggestions.
Click to expand...
Click to collapse
Hey,
firstly as long as you can enter Fastboot Mode, your device isn't completly Hard Bricked. In WHAT I'VE TRIED I see that you tried flashing the stock ROM. This was the solution that came into my mind first and actually it should be the only solution to unbrick your device. 3 seconds and succes? This should take like 450 seconds. The device Manager doesn't to recognize your device you said. That's weird but if the Mi Flash Tool recognizes the device in Fastboot Mode, flashing should work anyway. The Windows Version should not be the problem. I've done that with Win 10 and 11. It's hard to say what to do now and that's why I would ask you to tell me if you have Discord. You could share the screen. It would be much easier for me to see what the problem is and I can write with you there. And please try installing the latest Mi Flash Tool from here: https://xiaomiflashtool.com/ Download the latest Version with the Label NEW. Extract the folder into C:, not the extracted folder into another folder. Hope we will get your device working again soon.
nabulsi08 said:
Hey,
firstly as long as you can enter Fastboot Mode, your device isn't completly Hard Bricked. In WHAT I'VE TRIED I see that you tried flashing the stock ROM. This was the solution that came into my mind first and actually it should be the only solution to unbrick your device. 3 seconds and succes? This should take like 450 seconds. The device Manager doesn't to recognize your device you said. That's weird but if the Mi Flash Tool recognizes the device in Fastboot Mode, flashing should work anyway. The Windows Version should not be the problem. I've done that with Win 10 and 11. It's hard to say what to do now and that's why I would ask you to tell me if you have Discord. You could share the screen. It would be much easier for me to see what the problem is and I can write with you there. And please try installing the latest Mi Flash Tool from here: https://xiaomiflashtool.com/ Download the latest Version with the Label NEW. Extract the folder into C:, not the extracted folder into another folder. Hope we will get your device working again soon.
Click to expand...
Click to collapse
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Shoomyrovich said:
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Click to expand...
Click to collapse
Okay. I've edited the Comment with the Modules too so hopefully nobody gets the same issue as you.
Shoomyrovich said:
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Click to expand...
Click to collapse
I have created a Server you can join so you can share your Screen. Just join this: https://discord.gg/ufD9dsZ7
nabulsi08 and myself tried several different roms and things to fix it but without luck. After the call I managed to find Win10 PC and now it is going, 500s elapsed and counting hopefully, it will be done, but now I get more and more optimistic. It was just about Windows. Do not do the flashing on Win11.
Shoomyrovich said:
nabulsi08 and myself tried several different roms and things to fix it but without luck. After the call I managed to find Win10 PC and now it is going, 500s elapsed and counting hopefully, it will be done, but now I get more and more optimistic. It was just about Windows. Do not do the flashing on Win11.
Click to expand...
Click to collapse
Windows 11 may not to be to blame.... Were you using a Ryzen pc/laptop originally? That can sometimes affect things, was the Windows 10 device Intel based? Also using USB 2.0 rather than 3.0 can affect things too...
So dude, what's the verdict... Are you fixed now?
reg66 said:
Windows 11 may not to be to blame.... Were you using a Ryzen pc/laptop originally? That can sometimes affect things, was the Windows 10 device Intel based? Also using USB 2.0 rather than 3.0 can affect things too...
So dude, what's the verdict... Are you fixed now?
Click to expand...
Click to collapse
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Shoomyrovich said:
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Click to expand...
Click to collapse
Oh wow, to my knowledge ryzen can sometimes be the issue. Surprised it came down to a windows 11 issue, but we live and learn! I'm also on awaken with a windows 11 pc, hope I don't have the same issues when i change...
Really glad you're up and running again tho bud. Happy flashing
reg66 said:
Oh wow, to my knowledge ryzen can sometimes be the issue. Surprised it came down to a windows 11 issue, but we live and learn! I'm also on awaken with a windows 11 pc, hope I don't have the same issues when i change...
Really glad you're up and running again tho bud. Happy flashing
Click to expand...
Click to collapse
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Shoomyrovich said:
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Click to expand...
Click to collapse
Not encouraging you to, but I was using Magisk Delta when I had the same issue with Miui Core module. After changing to Magisk 26 official all was good again and have Miui Core plus MiSound module working now for Dolby...
Shoomyrovich said:
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Click to expand...
Click to collapse
Just want to say I am sorry again. Still don't know what the issue was. I've tried to figure it out. @reg66 seems to have no issues with any of those Modules too.
reg66 said:
Not encouraging you to, but I was using Magisk Delta when I had the same issue with Miui Core module. After changing to Magisk 26 official all was good again and have Miui Core plus MiSound module working now for Dolby...
Click to expand...
Click to collapse
I have edited the Comment with the Modules so everybody knows that I am not responsible for any bricks. I've mentioned that it doesn't seem to work with Magisk Delta too.
Shoomyrovich said:
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Click to expand...
Click to collapse
I have to say that I don't think Windows was the issue. I've flashed everything on both Windows Versions several times and never had any issue. It may be the PC that has something that causes this problem. At least we got your device working again.