Related
My mac is unable to detect my phone since I flashed Cyan 6 Test 8 Koush, as such I am unable to use adb. Given that I use a mac I assume this is not a driver issue. Phone is able to recharge via USB and USB debugging is enabled. I have found this issue (USB Brick) for the desire on this site but it involves flashing a rom unique to that device. Any ideas on how to resolve issue? Other than USB brick issue, everything is in order.
My card reader is able to read SD card and I have copied to my HD, so I assume issue is with USB on phone.
The only thing I can think of is that your phone somehow got stuck on "Charge Only" mode. In the stock version you can go to Settings, Connect to PC and then change some options there... I do not use this rom though so I'm sorry I can't help you other any further (I'm sure you likely already knew about the above info... if no one responds to you with an answer within a couple days I'd consider asking the Indian Prince of Roms himself... and I know he uses a Mac).
I assume you are mounting your system in recovery while trying to get adb?
Sent from my Incredible using Tapatalk
Yes. Device is not found. Can't view contents via finder either. When I pop out SD card and insert into reader contents are visible.
Sent from my Incredible using XDA App
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
This should also fix usb bricks.
Referencing:
http://forum.xda-developers.com/showthread.php?t=691639
Obviously you will need to try it from a terminal emulator.
I recently had the same issue - on a PC - where my CM6 test 8 install would charge but not register as a USB device and give me device malfunction warning messages. Turns out it was a problem with a non-HTC branded micro USB cable I was using.
Odd thing is it worked fine for a month or so, then decided to not work anymore out of any USB port. Switching over to the original cable fixed the problem. Now the other cable is relegated to the stock charger.
This should also fix usb bricks.
Referencing:
Obviously you will need to try it from a terminal emulator.[/QUOTE]
Thank you. I am on the road, so I won't be able to implement your solution until later. The procedure you outlined seems simple enough. I will reread. Is it ok if I email you with any questions, or would you prefer that I address my questions via this forum?
tdiman said:
I recently had the same issue - on a PC - where my CM6 test 8 install would charge but not register as a USB device and give me device malfunction warning messages. Turns out it was a problem with a non-HTC branded micro USB cable I was using.
Odd thing is it worked fine for a month or so, then decided to not work anymore out of any USB port. Switching over to the original cable fixed the problem. Now the other cable is relegated to the stock charger.
Click to expand...
Click to collapse
Funny thing is that I did not notice the problem until I changed cables. I was using a third party w/no problems, problem only surfaced when I used original cable. Hopefully I will have same luck as you, if not, adrynalyne posted near idiot proof instructions. I just hope that I am brighter than your average idiot, no promises.
adrynalyne, if my hboot is .77 could I simply flash PBI131.img to revert back to original? If not, could I use terminal emulator on my phone to execute necessary commands?
Answer from adrynalyne was "Well, yeah. the PB31IMG.zip should work, as long as it lets you. The other method would need to be done if it won't."
I was able to resolve the problem by switching usb cord to a 3rd party from htc, go figure. Nevertheless, the USB issue has been cited in other forums and if anybody else runs into the problem, follow directions above, i.e. follow links.
TY to all who gave me advice, esp. adrynalyne.
hey, umm.. im having a similar problem. when i try to plug in my droid incredible with the leaked 8/1 froyo rom, nothing comes up on my PC, i am able to acces my sd card by going to computer, and then clicking my sd card. but when i did this, i also noticed that there was a new cd drive, which comes from my phone. does anyone know if this is a usb brick?
Apparently there is a vzw ISO. There are instructions on how to remove in another post. Search USB bricked. I can't post links otherwise I would.
Sent from my Incredible using XDA App
Well, i tired it, but it didnt fix my auto start problem... and now, the cd drive doeant have a name, its juat cd drive:f
Hi
I would appreciate any input/help on this issue.
I bought the Korean Note 10 + 5g exynos (SM-N976N), specifically for the purposes of being able to root it. I would prefer to use the Magisk approach, because I would like to be able to use Google Pay, amongst others
Try as I might, I cannot get my PC to "see" the android phone. I have engaged developer mode, checked USB debugging, checked the the USB connection as MTP mode, and gone through several cables, going by the advice of "experts" I consulted. I even went as far as returning my original phone and buying a new one, again, on the advice of an "expert" who determined that my original phone was faulty (unlikely, since I had literally taken it out of the box and attempted the rooting before trying to load my multiple software). I am using Windows 10, 64k, with all current Microsoft updates.
I have reloaded the Samsung USB drivers, rebooted both the phone and PC several times, to no avail. When I connect, in download mode, the USB cable between the two devices, I hear the "ping" on the PC, indicating that the two have made contact, but then - nothing. I have established that the cable works fine, by connecting my Note 8 to the PC, where it shows up as a device with two drives (int and SD card)
I have installed Magisk on the 10+, and modified the stock ROM with Magisk, and then copied that over to the PC, as advised by the rooting solution; the problem is that I cannot use Odin to flash that modified ROM because Odin does not recognize any phone attached to it!
Help, Please!!
Could be the Odin version your using
Perhaps, I hadn't thought of that. I am using 3.13.1. Do you have a suggestion about using a more stable/useful one? My only issue with your answer is that it's not just Odin that isn't responding- it's the entire computer - it's as if the phone doesn't exist when connected.
I'm guessing you are using a USB 3.0 port on pc? If you have access to USB 2.0 try that....
Next thing I'd suggest (with note plugged in while in download mode)....go into device manager (right click This PC)
Find device under Modem, open properties Ports tab, Advanced Settings and manually change the port setting to a lower port assignment (preferably between 1 & 5). Reboot pc and just for kicks reset the phone into Download Mode again....Give odin a try now.
Hope one or a combination of these methods help.
Sent from my [device_name] using XDA-Developers Legacy app
Hello,
My mother's phone (redmi note 8 pro 64GB global version) keeps disconnecting and connecting to laptop (Windows 10, Ryzen 5 3500U, both on USB 2 and USB 3 ports) when plugged in via USB cable (used 2 different cables), so basically cannot copy files from the phone.
Tried the same laptop and same cables with a Redmi Note 8T and a Samsung A70 and both worked just fine (so it shouldn't be because of the USB ports nor the cables).
The question is, does anyone know if there are needed any additional drivers loaded apart from what Windows sets up? Did anyone experience this(if so, was there any fix found)?
I have seen a similar post on Acer forums (it was on a Ryzen 5 3550H laptop) so I guess it might be an incompatibility between the MTK driver and AMD processors (Unfortunately there was no usefull information regarding fixing the problem).
I think it has the official MIUI 11 with android 10 installed (not sure if the update was performed or not, I can ask my mom later to confirm).
Unfortunately, the best I could do was to connect remotely to the laptop as I am not able to go and get physical access to the phone.
If I missed any usefull details, I will try my best to find out and fill the gaps.
I have the exact same problem with my laptop which has a ryzen 5 3550h, was wondering about this for days,finally someone asked the question, oh and i also know of the post on acer forums,unfortunately I haven't found a solution,but if someone does,please let us know.
edit: I've also seen a lot of people saying it's a windows 10 issue,but I assure you,it isn't,I've tried on linux as well,except on linux the phone isn't even detected,which further goes to show that it isn't a driver issue,but rather some sort of incompatibility with ryzen based usb hubs and this phone,the zenfone max pro m1 has a similar issue(only occurs during fastboot).'
I'm don't have a wifi connection and my data is limited,but could you try and see if it works with a custom ROM,if it does we can report the issue to xiaomi.
Have you tried plugging into an multi port external usb hub as most have their own chipset and that will sit between your phone and your pc, It`s worth a shot.
Also some motherboard uefi bios you can select a usb 2.0 mode or some type of compatibility mode.
Don't have one ?
Tinderbox (UK) said:
Have you tried plugging into an multi port external usb hub as most have their own chipset and that will sit between your phone and your pc, It`s worth a shot.
Also some motherboard uefi bios you can select a usb 2.0 mode or some type of compatibility mode.
Click to expand...
Click to collapse
Unfortunately don't have a usb hub nor do I think it's worth buying one for this issue (as it is not that bad, I could be using some wireless file transfer I guess but it would be a bit more complicated to set it up remotely xD).
When I'll have the chance, I will try to guide my sister through bios to see what's in there.
pksenpai said:
I have the exact same problem with my laptop which has a ryzen 5 3550h, was wondering about this for days,finally someone asked the question, oh and i also know of the post on acer forums,unfortunately I haven't found a solution,but if someone does,please let us know.
edit: I've also seen a lot of people saying it's a windows 10 issue,but I assure you,it isn't,I've tried on linux as well,except on linux the phone isn't even detected,which further goes to show that it isn't a driver issue,but rather some sort of incompatibility with ryzen based usb hubs and this phone,the zenfone max pro m1 has a similar issue(only occurs during fastboot).'
I'm don't have a wifi connection and my data is limited,but could you try and see if it works with a custom ROM,if it does we can report the issue to xiaomi.
Click to expand...
Click to collapse
Unfortunately I can't do this (as it is not my phone neither do I have access to it)
pksenpai said:
I have the exact same problem with my laptop which has a ryzen 5 3550h, was wondering about this for days,finally someone asked the question, oh and i also know of the post on acer forums,unfortunately I haven't found a solution,but if someone does,please let us know.
edit: I've also seen a lot of people saying it's a windows 10 issue,but I assure you,it isn't,I've tried on linux as well,except on linux the phone isn't even detected,which further goes to show that it isn't a driver issue,but rather some sort of incompatibility with ryzen based usb hubs and this phone,the zenfone max pro m1 has a similar issue(only occurs during fastboot).'
I'm don't have a wifi connection and my data is limited,but could you try and see if it works with a custom ROM,if it does we can report the issue to xiaomi.
Click to expand...
Click to collapse
Huh, weird. Never heard of a usb device not detected on linux (unless it's a hardware problem like a faulty cord). When you say it doesn't show up, I suppose you mean in lsusb? Does dmesg say anything weird?
u8ububu said:
Huh, weird. Never heard of a usb device not detected on linux (unless it's a hardware problem like a faulty cord). When you say it doesn't show up, I suppose you mean in lsusb? Does dmesg say anything weird?
Click to expand...
Click to collapse
i don't think it's a faulty cord,i've tried multiple,on ubuntu the device connects,but charges only,and doesn't appear to be detected,to me it seems like some sort of hardware incompatibility issue between mtk and certain ryzen hubs, as for dmesg,i'm not very familiar with it,but i'll let you know once i understand how to use it.
I do own acer 2500u laptop and on one usb 2.0 port i do observe same behaviour. It is some incompatibility with ryzen/mediatek devices.
What about 3.0 ports?
My laptop has only one usb 3.0 port and it is working fine with the rn8pro.
florynwk3 said:
Hello,
My mother's phone (redmi note 8 pro 64GB global version) keeps disconnecting and connecting to laptop (Windows 10, Ryzen 5 3500U, both on USB 2 and USB 3 ports) when plugged in via USB cable (used 2 different cables), so basically cannot copy files from the phone.
Tried the same laptop and same cables with a Redmi Note 8T and a Samsung A70 and both worked just fine (so it shouldn't be because of the USB ports nor the cables).
The question is, does anyone know if there are needed any additional drivers loaded apart from what Windows sets up? Did anyone experience this(if so, was there any fix found)?
I have seen a similar post on Acer forums (it was on a Ryzen 5 3550H laptop) so I guess it might be an incompatibility between the MTK driver and AMD processors (Unfortunately there was no usefull information regarding fixing the problem).
I think it has the official MIUI 11 with android 10 installed (not sure if the update was performed or not, I can ask my mom later to confirm).
Unfortunately, the best I could do was to connect remotely to the laptop as I am not able to go and get physical access to the phone.
If I missed any usefull details, I will try my best to find out and fill the gaps.
Click to expand...
Click to collapse
Have you tried installing the MTK USB driver correctly?
try to check again in the device manager when you connect the device Redmi Note 8 Pro is there a name portable devices there?
in my opinion it's not the fault of the RN8P device because the RN8P still uses Quallcom hardware for chargers and USB and it's universal..
To be sure to try again another Xiaomi device and is it connected?
Coffeemi said:
Have you tried installing the MTK USB driver correctly?
try to check again in the device manager when you connect the device Redmi Note 8 Pro is there a name portable devices there?
in my opinion it's not the fault of the RN8P device because the RN8P still uses Quallcom hardware for chargers and USB and it's universal..
To be sure to try again another Xiaomi device and is it connected?
Click to expand...
Click to collapse
Every other xiaomi device works perfectly fine, tested the redmi note 7 pro, redmi note 4 and the redmi 7a,as for installing the driver, I've done that several times on different versions of windows as well, if it were a driver issue on windows, it should still work on linux, right? but it isn't even detected, as for device manager, I can't exactly see any new device or anything, but there is a connection sound and a disconnection sound playing on loop(on windows only). I was considering downgrading my bios, but then I found another user with the same laptop on an earlier version claiming to have the same problem.
pksenpai said:
Every other xiaomi device works perfectly fine, tested the redmi note 7 pro, redmi note 4 and the redmi 7a,as for installing the driver, I've done that several times on different versions of windows as well, if it were a driver issue on windows, it should still work on linux, right? but it isn't even detected, as for device manager, I can't exactly see any new device or anything, but there is a connection sound and a disconnection sound playing on loop(on windows only). I was considering downgrading my bios, but then I found another user with the same laptop on an earlier version claiming to have the same problem.
Click to expand...
Click to collapse
if so is it possible that the RN8P device hardware is having problems ??
make sure to return with another computer / laptop and also make sure the data cable is still functioning, also use the USB View application to see all connections on your PC / laptop. You can see and delete several devices that are often connected.
Coffeemi said:
Have you tried installing the MTK USB driver correctly?
try to check again in the device manager when you connect the device Redmi Note 8 Pro is there a name portable devices there?
in my opinion it's not the fault of the RN8P device because the RN8P still uses Quallcom hardware for chargers and USB and it's universal..
To be sure to try again another Xiaomi device and is it connected?
Click to expand...
Click to collapse
I will try to install the MTK USB driver manually and check if it is working. With Redmi Note 8T works fine (but it has the Qualcom Snapdragon).
I will also ask my sister when she has time to try and connect to our desktop (an old intel pentium 4 xD running on windows 7)
florynwk3 said:
I will try to install the MTK USB driver manually and check if it is working. With Redmi Note 8T works fine (but it has the Qualcom Snapdragon).
I will also ask my sister when she has time to try and connect to our desktop (an old intel pentium 4 xD running on windows 7)
Click to expand...
Click to collapse
It'll probably work an an intel computer, it works on my intel core i3 5005u laptop just fine.
I don't think installing mtk usb drivers manually is going to be fruitful but do let me know what happens
Well, the phone connects well on the old intel desktop, on the ryzen laptop even after manually installing the driver is the same issue.
I checked now and the phone is on android 9 MIUI 11.0.3.0 (if that helps).
I guess they'll use either the old computer to copy the videos/photos or I will just help them set up wireless connection.
florynwk3 said:
Well, the phone connects well on the old intel desktop, on the ryzen laptop even after manually installing the driver is the same issue.
I checked now and the phone is on android 9 MIUI 11.0.3.0 (if that helps).
I guess they'll use either the old computer to copy the videos/photos or I will just help them set up wireless connection.
Click to expand...
Click to collapse
I have the same issue, same circumstances, except that I have an intel i7-5500U Laptop. I reinstalled the USB drivers too and there was no effect on the issue. My RN8P keeps connecting and disconnecting from my laptop making file transfer nearly impossible. I also fear to change the recovery of my device in case it disconnects while the process is working. I encountered this issue in November when I first bought the device and I assumed it was a power issue from my laptop's USB port or something. It occurs irrespective of the USB C cables I use as well.
I tried and tested the phone with a cheaper laptop I got from university. It has an Intel M3 CPU I think. In my brief testing, I found no disconnect issue on that device. I am entirely confused as to why this happens. Blame mediatech I suppose.
Oh one more interesting piece of information. My phone appears as a collection of network drives, not as a flash drive. Even my Sd card appeared as a network drive. Could this have something to do with it? (Edit i just tested this again, and the phone now displays my drives as flash drives... weird)
I really want this issue to be fixed haha. I want to flash this phone soon.
pksenpai said:
i don't think it's a faulty cord,i've tried multiple,on ubuntu the device connects,but charges only,and doesn't appear to be detected,to me it seems like some sort of hardware incompatibility issue between mtk and certain ryzen hubs, as for dmesg,i'm not very familiar with it,but i'll let you know once i understand how to use it.
Click to expand...
Click to collapse
Again, what do you mean by "doesn't appear to be detected"? Does the kernel detect it? i.e. does it show up in lsusb and/or dmesg?
In case you're not familiar with those tools, just run lsusb and dmesg (no other options needed) before and after plugging in the device and check if anything changed in the output.
pksenpai said:
I have the exact same problem with my laptop which has a ryzen 5 3550h, was wondering about this for days,finally someone asked the question, oh and i also know of the post on acer forums,unfortunately I haven't found a solution,but if someone does,please let us know.
edit: I've also seen a lot of people saying it's a windows 10 issue,but I assure you,it isn't,I've tried on linux as well,except on linux the phone isn't even detected,which further goes to show that it isn't a driver issue,but rather some sort of incompatibility with ryzen based usb hubs and this phone,the zenfone max pro m1 has a similar issue(only occurs during fastboot).'
I'm don't have a wifi connection and my data is limited,but could you try and see if it works with a custom ROM,if it does we can report the issue to xiaomi.
Click to expand...
Click to collapse
Hii dude i have the exact same problem. I have a redmi note 8 pro and an acer aspire 7 which has a ryzen 3550H chip . I have bought a usb hub and tried it and it worked . But it won't work in fastboot mode . When you turn the device into fastboot mode and connect the device to pc via a usb hub it keeps connecting and disconnecting . I want to install a custom rom on my RN8pro . I some how able to unlock the bootloader and now I'm trying to install custom recovery but because of this issue I can't install it . I have tried installing a lot of adb drivers , Xiaomi drivers, media tek drivers also every drivers on the pc but i think it's not the pc problem. I think it's the phones problem. If you find a solution for this please inform me . If you just want to transfer files from phone to pc then you can buy a usb hub then the phone storage will appear on the pc . But i have better solution. You can download a application called feem it is a wireless file transfer app and It works fine .
pksenpai said:
i don't think it's a faulty cord,i've tried multiple,on ubuntu the device connects,but charges only,and doesn't appear to be detected,to me it seems like some sort of hardware incompatibility issue between mtk and certain ryzen hubs, as for dmesg,i'm not very familiar with it,but i'll let you know once i understand how to use it.
Click to expand...
Click to collapse
I have bought 3 usb c cable . It doesn't work it is not cable problem. It's the phones problem. Media tek drivers and ryzen processor is not compatible
My first Poco F3 is completely unlocked and running a custom rom, still able to connect to PC even now.
I have a second Poco F3 that I was able to originally connect to my PC to debloat, hadn't needed to connect it to a PC till now. Today was the day I could unlock it but when I connect it via USB cable, original or otherwise, no usb options appear on phone and nothing shows on PC. I can use the same cable on my first Poco F3 and everything works fine. I've tried multiple cables, reinstalling drivers, restarting phone and PC, trying a different PC, enabling debugging tools, etc.
Nothing shows in "My Computer"
Nothing shows in Device Manager
No usb options on phone (default is set to File Transfer)
Nothing shows in CMD with "adb devices"
Charging still works
Is there anything I can do to at the very least unlock the bootloader? Or is this not fixable?
long shot... check the usb C port for dirt/dust/fluff blocking connection...
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Alin45 said:
Most probably u debloated an app responsable for media transfer. If u can, revert what u debloated.
Click to expand...
Click to collapse
Did a factory reset thinking that may have been the case, still no good.
Tried cleaning out the port and still no good either
I still think it's Windows. Please can you try putting Ubuntu (or another Linux distro) on a USB, booting from that, installing platform tools (ADB/fastboot etc) and then running ADB devices. Windows is very finiky sometimes.
Edit: when you plug in your phone to the PC do you get a notification saying charging? Or is there no notification? Also does it start charging the phone?
There is a delay before it begins charging and the charging animation plays but yes it does. But then there is no usb notification. Will try ubuntu and report back
Booting into Ubuntu, before installing platform tools the first phone that I knew worked showed up and showed up in adb devices when platform tools was used. The second still didn't show up, exactly the same as on windows
Try downloading the installed stock miui rom from the update menu in the miui update menu and re-install it on the phone
Unfortunately reinstalling latest package didn't help
Can't think of anything else to suggest. Sorry
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Are you sure the USB cable you're using support transfert file?
Cjayy said:
If the usb connection continues to be nonexistent, is there any way to at least unlock the bootloader without using the Xiaomi Unlock tool on the PC?
Click to expand...
Click to collapse
Nope
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
do you have a type c usb-otg?
If yes then see if it is detected by the phone
X0PIRAT3 said:
Are you sure the USB cable you're using support transfert file?
Click to expand...
Click to collapse
Yes. Used 4 different cables, 1 of which is the cable that comes with the phone. None work on this phone but do on the first phone.
Alin45 said:
Hmmmmm.....strange! I'm running out of ideas....try different USB ports on PC. Maybe it's a faulty USB-C port on phone after all.
Click to expand...
Click to collapse
Tried different ports across 2 PCs. I'm starting to think it is a faulty port, though it worked fine a week ago.
arifqur said:
do you have a type c usb-otg?
If yes then see if it is detected by the phone
Click to expand...
Click to collapse
I honestly don't know if any of my cables are usb-otg, how would I check?
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
X0PIRAT3 said:
Try to use this version of Mi FLash Tool (only for drivers) : https://xiaomiflashtool.com/download/xiaomi-flash-tool-20210226
Extract and launch the executable then drivers install
Click to expand...
Click to collapse
Tried this and still no good.
arifqur said:
Something like this. You can plug in any usb stick and see if it is detected. Another way to check whether the port on the phone is working for data as well
Click to expand...
Click to collapse
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Cjayy said:
Tried this and still no good.
I don't have anything like this but that reminded me of the usb-c to headphone adapter and that also doesn't work. Sound just plays out of the speakers.
Trying with Android Auto in the car, the car doesn't register a device connecting at all either.
Either the data transfer portion is somehow disabled on the device itself (which I would love to know how to enable it again if that's the case) or it's a damaged usb port. Just strange that it worked a week ago.
Something I forgot to mention, when I went to unlock the bootloader yesterday the phone did not show up anywhere except for in the ADBFastbootTools to debloat the software as a OnePlus device but then never showed up again.
Click to expand...
Click to collapse
I have the same problem, did you solve it ? I replaced the usb board of the phone, still not working.
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.