Question [Solved] POCO F3 - Unable to unlock bootloader/fastboot no device - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

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.

Related

Adb recognizes devices during phone on state, but not in fastboot.

Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs

Can't unlock bootloader. Device no longer detected the moment I open Mi Unlock Tool.

Sorry if this is the wrong thread.
Hello guys, I have a Redmi Note 5 (Global Version) with Snapdragon 636, and this phone is really amazing. I'd like however to unlock its booloader so I can install Pixel Experience on it, as I'd like to use other roms than MIUI. The issue is, well, I can't.
Something really strange happens: if I connect my phone via USB 2.0 to my computer, it is recognized as usual. It appears in Device Manager, is recognized by ADB, no problem. Then I reboot in fastboot mode and the device is still there. However, the EXACT moment I open Mi Unlock Tool, without clicking anything (Agree or logging in to my mi account) the phone is instantly disconnected and the "Press any key to shutdown" message appears on the top-left of my phone's screen.
Stuff I've tried:
- made sure OEM unlocking and USB debugging are on
- installed Mi Unlock tool in C:
- installed the ADB drivers in C:/Program Files
- disabled integrity checks from CMD
- installed and checked the MiUSBDriver umpteen times
- used 4 different versions of Mi Unlock Tool (1.0, 2.2, 2.3, and 3.3 - 1.0 halts at 50%, the other 3 won't detect my phone at all)
- made sure the device is bound to my Mi Account
I've tried using Hexerus' guide here (post #18) and everything seems to work fine, until step 6 when my phone instantly disconnects when opening Mi Unlock Tool.
Do you guys have any ideas? Thanks.
use usb 2.0 cable and port
devcon69 said:
use usb 2.0 cable and port
Click to expand...
Click to collapse
Used USB 2.0, didn't work
Happened with me before, and I looked Google and found some solutions like installing the drivers again and using old miunlock tool and using different USB Socket however, none of theme worked,
Next day I opened the laptop to try again and suddenly it worked!
I didn't know what exactly fixed it
After the 720 hours period, I have spent literally weeks of trying to unlock my device's bootloader and what I would add is to switch between computers. I'm running Windows 10 on my room computer and all I had with MiUnlock were errors such as device disconnecting once in fastboot, "Couldn't unlock" messages, chinese characters... Until I decided to use my 2005 Windows 7 desktop and wow !, device unlocked at first try ! No need any other trick
just uninstall Previous drivers or use Windows 7 PC,with latest drivers of ADB ,i also faced same problem:angel:

Is my supposed non-brickable ZUK Z2 bricked????

Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate
chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.
Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..
After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!

Question Bricked and EDL doesn't work

It was only a matter of time before my first brick with this phone. Earlier this evening I tried to factory reset from TWRP and clean flash latest OOS, but it spewed out a whole bunch of partition errors. After various efforts, here's the current status: It won't boot to the OS from either slot. TWRP says no OS installed. On Slot A, it won't boot to recovery either, and the only thing I can get to is fastboot. On Slot B, I can get to TWRP recovery, but all storage is gone (and I've since done a full wipe so there's nothing on it anyway). Any attempts to do adb push or sideload result in the error "adb: error: failed to get feature set: no devices/emulators found", so I can't install anything unless there's another way I'm not aware of.
I'm trying to get into EDL by powering off the phone, then holding down both volume buttons while I plug in the USB cable. It shows up in Device Manager for about 2-3 seconds as "Qualcomm QDLOADER 9008" and then disappears for a second before going directly into fastboot. I've rebooted my computer to disable device driver signing and install the latest Qualcomm drivers per this guide, but the latest drivers are already installed. I've tried a different USB cable and a different USB port.
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
terlynn4 said:
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
Click to expand...
Click to collapse
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Fishawy said:
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Click to expand...
Click to collapse
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
terlynn4 said:
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
Click to expand...
Click to collapse
You don't have to stick to one model. You can use MSM of 11.2.2.2 EU or 11.2.4.4 India for example, then flash the stock update of a different region, as long as it's an upgrade not the same version.
I did upgrade from 11.0.6.6 AA to 11.0.8.8 EU locally on my 8 Pro. I would imagine it's the same, haven't tested it on my 9 Pro yet though.
I finally got it flashed back to OOS via TWRP and booting normally again. However, it concerns me that I couldn't ever get EDL working, in case I ever really need it. I'll have to keep working on that "just in case".
After trying several things in various orders, I reformatted /data, after which adb push started working. I was able to push the latest full .zip and after a couple more errors I was able to flash it to both slots and reinstall TWRP. I did get an error when I went to reboot that said something like "No OS installed... are you sure you want to reboot?" however it booted into the OS that time.
Anyway, thanks to those who offered suggestions. I'll update again if I ever figure out what's wrong with EDL.
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Steve0007 said:
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Click to expand...
Click to collapse
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
terlynn4 said:
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
Click to expand...
Click to collapse
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Samuel Holland said:
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Click to expand...
Click to collapse
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
terlynn4 said:
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
Click to expand...
Click to collapse
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Samuel Holland said:
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Click to expand...
Click to collapse
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
terlynn4 said:
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
Click to expand...
Click to collapse
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Fishawy said:
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Click to expand...
Click to collapse
The one that worked for me was the 32-bit setup.exe file from this guide. I uninstalled the existing driver I had installed, rebooted, installed this driver, and then EDL worked right away.

Question SOLVED! Bricked Mi Pad 5 - tried almost everything I found

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.

Categories

Resources