Related
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
Tl;dr: DM-VERITY error after upgrading, SIM card not recognized. Can't get fastboot to work to try out a solution. Everything is going to ****.
So... this one's a doozy.
I tried to install the update by dropping it onto my phone and using TWRP to install it, which I ended up having to update. After I updated, I get a brief second popup screen when I reboot telling me that there is an invalid DM-VERITY (it only pops up for a second). When the phone loads, it doesn't recognize SIMs.
I did some research and it looks like the issue can be fixed by flashing the stock recovery. So I go to flash the stock recovery, which requires the usage of fastboot. Which I always have problems with.
Sure enough, adb recognizes my device but fastboot doesn't. I have all the drivers downloaded, so I go check on my device in device manager. For some reason, it's always listed under "Portable Devices" no matter what I do... no matter whether I enable/disable USB debugging, MTP/PTP/Charging, etc. I was under the impression that a device not being recognized by fastboot meant that you had to go find it under "other devices" and manually update the drivers. However, the only options here are ADB drivers, not bootloader ones.
So I did more research. Turns out that Windows 10 is ****ty and you have to disable secure boot to install unsigned drivers. So I went into my BIOS, disabled it, booted into safe mode, reinstalled the drivers, and... nothing.
So I'm basically where I started and for the first time in a while, I have no clue what to do. Nothing's working. I even tried to load an older version of OxygenOS and install it with TWRP (sideloading didn't work), which didn't work. I'm totally stuck and I have no idea what to do.
If you don't care about your data, just use the unbrick guide method 2. Don't know about the first one, I have never used that. That will get you to a like new phone. You could even get 4.0.3 version, using the newer unbrick toolkit.
Windows 10 x64 isn't that sh**y. I've never had issues with the drivers, and they all install automatically (fastboot, adb, unbrick tool). They all work with 4 phones without any issues: OP3, Nexus 5X, Nexus 5, Nexus 4.
True, I had just unbrick my op3 2 days back by method 2 .
Well this was wild
So I did try to unbrick and got the Sahara communication error.
But I ended up fixing my problem! Someone on Reddit correctly pointed out that the dm-verity screen often exists simply as a result of unlocking the bootloader. I was assuming that one symptom caused the other. They suggested just reflashing OnePlus's 4.1.3 full ROM. I did it exactly the same way as I had when I got the error (with TWRP) and... it worked!
I'm astounded. My phone wouldn't work with fastboot, wasn't recognized by the unbrick toolkit, and had a host of other issues. I did 7 hours of work on it and the solution ended up being that I just needed to reinstall the OS (again). My hypothesis is that there was some hidden issue that resulted in part of the firmware being incorrectly updated, and when I wiped my device as part of my troubleshooting process it was ready to be reflashed with the OS.
Thank you guys so much anyway!
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
dziedziol said:
Hello,
today I have a problem with my g4. When I first got this phone 2 years ago I instantly unlocked bootloader, installed supersu, xposed etc and I had no problems at all with this.
But couple weeks ago somethings happened to my snapchat so today I tried to unroot to login to my account on sc. Then i checked that I have to uninstall xposed framework too, but to do this from xposed installer app, root is needed. I thought "no problem, I will install root briefly, uninstall xposed, unroot and login to snapchat". Then I met first obstacle. I don't have recovery mode in phone. when I connect g4 by usb to pc and use adb (by typing adb reboot recovery) my phone reboots and shows green dead android with red triangle. I have to remove the battery to get phone back to life. I remembered that i always used fastboot commands to boot into custom recovery instead of installing TWRP, because flashing it never worked. But now when I try to execute any fastboot command, it only shows me "waiting for any device" in cmd. what do I have to do now? all essential drivers are installed on my pc. phone is showed as "LGE Mobile adb interface" in device manager. when I enter "adb reboot fastboot" it only reboots my phone and nothing else. Does anybody know a solution? I wouldn't like to wipe my g4 from all data. I have read many pages on google and nothing helps. I've tried fastboot on 2 different computers, one with usb 3.0 and one with 2.0 and results are the same. If someone could help me, thanks in advance.
Click to expand...
Click to collapse
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
uweork said:
Try another Cable. Even my original LG cable isnt working with fastboot/adb.
have you tried: https://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537
some more Information about Your Phone. usu´d or nornmally unlooked. Stock rom?
Click to expand...
Click to collapse
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
dziedziol said:
Tried with another cable and nothing changes.
I tried to do this method you sent. So when I enter download mode it goes into "firmware update" after couple of seconds, my phone isn't detected on pc and the first command in console "Send_Command.exe \\.\COMx" returns "FAIL".
My G4 (H815) is stock rom, bootloader unlocked normally, didn't do any usu or anything like this. I have only rooted it with supersu 2 times (one time maybe a 1,5year ago i log out from snapchat and had to unroot and root again), installed xposed framework and did nothing else. I don't know how is it possible that I used fastboot on this phone then and now I can't do it. Half a year ago I've installed custom rom on friend's G2 and installed some programs etc. on my pc (because installing this rom didn't went that well and I had to flash stock .kdz or something like that through LGUP/LG bridge/lg flash tool, I don't remember) and I thought that it did some mess but when I tried to use fastboot on another PC, where I've installed drivers freshly, the result was the same.
So what is about "firmware update"? It is obviously stuck on 0% and I have to remove the battery to leave this mode.
Click to expand...
Click to collapse
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
RuedasLocas said:
Try installing "adb universal drivers".
Also in your computer device manager, with the phone connected, uninstall the device, adb device, modem everything related with the phone. Reinstall and try it after install the universal drivers.
Hope it works, good luck!
Click to expand...
Click to collapse
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
You could Check if FWUL from SteadfasterX is helping You out with your Problem.
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
With the Installed Salt You cann Backup your Device.
dziedziol said:
Uninstalled everything lg-related from device manager, uninstalled everything lg/android-related through revo uninstaller, installed adb universal drivers, lg usb drivers, everything seems fine, when I type "adb devices" in cmd it shows my phone but, again, when I enter something related to fastboot, it only shows <waiting for any device>.
Is it even possible?? I have not seen any cases like mine in internet - somebody's phone every time was else bricked or somebody would try to flash something and errors like that happened, but I have used fastboot many times on G4 and G2, didn't reinstall windows and everything worked! Why I can't access recovery mode (dead android with red triangle) or enter fastboot or do something in download mode? What could happened?! Is it possible to fix this without wiping data from my G4? I haven't done factory reset for very long time and copying tens of thousands of photos and videos, quickmemo notes, music, voice recordings, chrome bookmarks and everything else to my PC would be a big pain for me.
After all, thanks for replies, and I hope that we will find solution for this.
Click to expand...
Click to collapse
<waiting for any device> because if windows don't recognizes the device as it should adb will never "see" it.
While on the process, pay attention to the device manager. When you get the message in cmd of <waiting for any device>, uninstall your device and make device manager search for devices.
If still shows you as the same device and adb still waiting, you might have to uninstall the device and install it manually choosing from a list. Now I don't remember how it is suppose to be detected...
During install and uninstall don't disconnect the device from the computer, and remember, use a USB2 port.
I already got that several time. Took me time but that's how I managed to fix it.
okay, guys, it is a shame for me... but I worked out what is wrong with my phone.. maybe not with my phone, but what is wrong with me.
all I needed to do to launch a fastboot was type "adb reboot bootloader" and everything is fine now.
Sorry that you had to give me so much tips and this problem turned to be my stupid mistake, but I'm glad that i won't have to install linux and play with virtual machines to repair my phone
Anyway, thanks for your kindness and will to help, greetings for everyone!
@edit: Turns out that i have one more question. I want to uninstall xposed framework. But there are many versions of uninstaller on their site. Is there any risk that i will "break" my G4 if I use the newest one? I have xposed version 87 and I don't want to do something stupid. thanks in advance.
somebody knows? if I can use the newest version of uninstaller no matter which version of xposed framework im using?
I don't know how this happened, I tried to update to MIUI 10 and now TWRP says I don't have an OS and fastboot just boots on & off, on & off for eternity.
How can I reset it? When I tried updating with TWRP I got some weird error and now this happened. Is it possible to do an ordinary factory reset from TWRP or fastboot? Also, I can't plug my Xiaomi MI6 into the computer with USB-C. Some time ago I dropped it with headphones connected to the USB-C and the connection ONLY works for charging. Headphones don't work, and I don't think it works on the PC either. UNLESS, there's so program I need for the computer to connect to the Xiaomi, but plugging it in to the PC it doesn't react or the computer says it doesn't know what it is.
download fastboot rom, and flash it with mi flash.
zilan said:
download fastboot rom, and flash it with mi flash.
Click to expand...
Click to collapse
Hi! I have the Mi Flash program, but when I connect my Xiaomi MI 6 to the computer, my computer keeps saying it doesn't recognize the device and I can't refresh in Mi Flash to find my phone
Bump.
Well I could not wait anymore, I bought a new phone but I still wanna try fix this phone to sell it.
Is this forum dead?
Similar problem here. Help guys!
Download a custom ROM and put it into a flash or sd card then connect it to your device through OTG and wipe system vendor cash data but DO NOT WIPE INTERNAL STORAGE, then just flash the rom and reboot .
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.