Database Develop

Can't get OTG to work or show up.

So I put this phone away for quite a while, I recently took it out to use with my USB c earpiece from Xiaomi, but it wasn't connecting. So I tried plugging in a USB C Otg thumbdriver, it too did not show up.
I was running Pixel Experience when it had treble support. But given I thought it might be at play for why it's not detected, I wiped and reinstslled miui through TWRP. However after doing that it still didn't work. So I tried to see if TWRP could detect a USB C thumbdriver, it too didn't detect. I resorted to using Mi Flash tool to Flash the stock firmware of Mi Max 2, but still doesn't work.
Anyone know what I could possibly do to get it to work? Thanks

I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.

kirpi_e said:
I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.
Click to expand...
Click to collapse
Ah it's okay, I sent it to Xiaomi and got it repaired. Thanks!

kirpi_e said:
I have a similar issue not same. Similarly my phone stopped detecting usb flash disk on otg. Below is what i did,
To understand if your usb port is malfunctioning, connect your phone to PC and try to communicate through ADB interface. If it goes well than your configuration somewhere deep there sucks (which is my case) or else you have a hardware problem.
Click to expand...
Click to collapse
Please advise how did u fix this
Have installed pixel experience oreo rom on mi max 2 and then I noticed org was not working
Please advise

[HELP] Bricked phone while updating to Pie

So, I tried to update to Pie.
I was on Stock Oreo rooted without encryption.
Wiped everything except sdcard, installed Pie and the boot img for encryption fix.
Rebooted to TWRP, flashed the zip from verity fix, flashed latest Magisk.
Rebooted to system, stuck with the dots rotating.
Tried to redo it again, adding the step for the firmware flash.
But when wiping i accidentally wiped sdcard too, so I have no more the required files inside TWRP.
Tried to connect both TWRP and bootloader via adb/fastboot but phone is not recognized.
All the drivers are installed it always worked before (Win7).
Now everytime I try to connect the 3T to PC it says Unknown Device in Device Manager, but all the drivers are installed.
Apparently the phone is not sending its data, because in device properties i see VID & PID = 0000.
Trying to manually attach a driver to it (with right click, update driver) gives error, no driver available for the device (using any adb drivers .inf).
So basically now I'm stuck with a phone without files in it, but with only TWRP working.
How can I send the rom files without adb/fastboot? Any trick?
I also tried to use USB OTG from TWRP but apparently any usb stick is not recognized.
Tried different USB ports and different cables. Seems like a problem with the phone usbC port, not sure.
It's an hard brick at this point?

Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk

Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.

pitrus- said:
Just go with the Qualcomm factory restore mode/tools. Turn off phone, hold volume up while connecting phone to PC, install the drivers for the Qualcomm 9008 device and then run the factory recover tool. You can find out all this in the factory restore thread, just make sure you have the 3t and not the normal 3 as they have different firmwares for the hardware.
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
sandeep_kumar said:
Format the device in latest TWRP and reboot it back to TWRP then connect the USB cable to PC. It should ideally recognize your 3t. I never had any issue while recognizing the phone in TWRP menu.
if nothing helps, the final step is obviously try he Qualcomm factory restore mode/tools.
Click to expand...
Click to collapse
I already tried that too. It always appear as unknown device, even with that method.
Just to be clear, I never had problem before and I already used TWRP mount and fastboot/adb to load files without having a running ROM. I was always able to move file with any of them.
This is different, it seems like an hw problem, the phone it's not sending his IDs when connecting to CP so the PC can't identify what it is even if drivers are installed.
Now, I'm not sure if the problem lies in the physical USBC port or if the failed Pie upgrade ruined somethin in the bootloader or something else.

Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk

pitrus- said:
Then I'd say broken USB cable, have you tried with another cable or a shorter cable?
Skickat från min ONEPLUS A3003 via Tapatalk
Click to expand...
Click to collapse
Tried many cables, ports and PCs.
I also tried to clean the port with a wooden stick without luck.
At this point i believe it's the usbC port or the motherboard.
I think something at the USB MTP level went faulty, because charge works fine (dash charge too).
I just can't transfer files anymore. Not even with an OTG dongle.
Since there is no other way to trasnfer the ROM zip (network is not available inside TWRP) I requested an RMA and tomorrow OnePlus send a carrier to pick it up for repair.

I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.

i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries

sandeep_kumar said:
I have not still updated the device. I am on custom ROM. After reading your problem I am scared to install it on my device.
I think it is better to go to stock completely with locked bootloader with 5.0.8 and then accept update. After that, I can unlock the bootloader and root the device.
Click to expand...
Click to collapse
Don't worry, if the USB port is working you can always recover. Just be sure your PC recognize the device first, in case anything happens.
cmurder61 said:
i just recently had this problem dude, not even 20 mins ago, find and use a diffrent usb cable/port or if u have a usb hub use that along with ur new cable, it finally worked after hours of countless tries
Click to expand...
Click to collapse
I've been trying for the whole day with 5 different cables, 4 different PC and every usb port of them. I just didn't try with an hub because i don't have one, but i don't think it makes any difference. Anyway the phone i ready to be send for repair now.

if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol

cmurder61 said:
if that's ur lat hope, go for it, but the specific cable i used was a belkin usb cable from walmart, u should also update ur adb drivers, if i could id let u use my pc lol
Click to expand...
Click to collapse
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.

matrixino said:
Nah its not the cable or drivers, I test roms every 1/2 months and always been fine with uploading files with adb, fastboot or MTP. Nothing changed. Must be some hardware issue.
Oneplus already sent me the shipment code and i'm waiting for UPS to pick up the package today.
Click to expand...
Click to collapse
i see, well good luck to ya

I Messed Up My phone fastboot not working!!!!!

Hello Everyone, so 2 days ago i hard bricked my MI 8 with flashing an eu rom over global mi 8 rom with twrp then when i rebooted the phone it stuck at mi logo so i tried to goto recovery mode again but nothing happens when i press power + volume up its just mi logo and i tried to go to fastboot mode but not luck i get a black screen....................so i decided to connect it to a computer but no signs of anything(not detected).....so i searched google a little and i found a solution wich envolved disassembling the phone the method called EDL method with test point,,,,,,,so i opened my phone with my friends and tried to do the test points,,,when i joined the testpoints and then connecting the phone to pc.....nothing happened.....it should detect the phone but nothing happens.....please help guys!!!

Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone ?

mi_guel said:
Keep trying with edl, maybe it's a driver issue, but if you can't get it to edl I don't think you can recover your phone
Click to expand...
Click to collapse
I have been trying....but no luck till now:crying::crying::crying:

alandxaled said:
I have been trying....but no luck till now:crying::crying::crying:
Click to expand...
Click to collapse
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.

tsongming said:
You need to use QPST.
Also you didn't need to open the phone, that step is outdated.
Go ahead and read up on installing all of the needed drivers and as long as your phone is linked to you. That is you have the phone registered to your MiCloud account this issue should be fixable.
I dont have a lot of time today or tomorrow. but I am willing to try and help you figure this issue out.
Click to expand...
Click to collapse
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager

alandxaled said:
I installed the drivers...but the main problem is that when i connect it to the pc ....the pc did not recognize the phone not even in device manager
Click to expand...
Click to collapse
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.

@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.

tsongming said:
This could be an issue with the PC...happens all the time.
If the battery is not completely dead, or if the usb port is not completely fried you should be able to at least see the port.
It's also possible that you are not in EDL.
Simply Flashing the EU rom over Global will not brick your phone, I have done that myself many times. Was your bootloader unlocked? If not then you will probably need to take it to a Xiaomi Service center.
Does the phone mac any vibrations when pressing and holding both the volume up and down ( at same time along with the power button?
Have you tried alternate usb c cables?
If you have a newer computer with usb 3.0 ports you will need to use a Usb hub., which will downgrade the connection to usb 2?
Is ADB Installed on this computer along with generic android drivers?
is the computer up to date?
Have you tried an alternate user and are you using the admin account?
If you have a device that uses linux, see if Linux will see the phone.
If you have tried everything, and you still you see the phone, and the phone has not been exposed to an extreme amount of force or to water. It may be that your usb card in the phone is fried or there is a short in the internal usb flex cable. ( It's the wire that connects the usb card to the motherboard.
You can Google the steps to make your own deep flash cable, that would help rule things out much faster.
I am going to sleep now. Good Luck.
Click to expand...
Click to collapse
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"

alandxaled said:
1-My Bootloader was unlocked yes!
2-i flashed eu rom over evolution rom(Custom rom)
3-Yes It Does Vibrate
4-Yes I Have Tried Other Usb Cables
5-yes, adb installed with generic usb driver
6-yes its updated and i tried mutliple ports
7-i haven't tried linux
8-and i dont think that my usb card is fried because before that it was working
And Another Thing That Might Have A connection with the problem"Before i flashed eu rom over custom rom the unlocked text was shown in the display when booting with mi logo but now that text has gone"
Click to expand...
Click to collapse
The EU rom does not lock the bootloader, the developers actually removed the bit of code that will allow MiFlash to lock the bootloader. Whenever leaving or returning to Miui, storage must be formatted.
The problem with these custom roms for the Mi8 is that These mi8 developers do not work together ( like most do, on other threads) These developers are always fighting and arguing and accusing each other of stealing their code, while they do it themselves and they all have their own way of doing things. Ideally every rom should use the same device tree, firmware and vendor...The basics! But no, everyone does things differently.
I would suspect that your phone bricked due to firmware encryption or just corruption. Even though it seems that it can't be fixed, you will surely be able to fix it eventually.
Many people were eventually able to solve this exact issue in the past with success. so start with the basics., and dont give up when or if it fails, just try again on a different device, and be sure to disable Windows defender. Because it's possible you could have your computer setup in a way that it will make this process harder to resolve, temporarily disable the antivirus and firewall etc.
Download the All in One tool: https://forum.xda-developers.com/mi-8/development/tool-tool-one-driverstwrpfactory-t3895807 If it gets flagged, and completely disabled. then your computer is helping contribute to this issue.
If you can successfully install and open the tool, use it to update adb and android drivers and to apply system wide adb access. Next manually setup the phone , even if it claims to not see a fastboot device. and attempted to remove encryption. if this fails find a Linux machine to complete these tasks.
See if you can leave EDL, by pressing and holding the power and volume down. >>>>> Even if you dont see the fastboot screen the computer may see the phone in fastboot.
I definitely believe that you will have a easier path to getting this issue resolved sooner by using linux. If you can "format" ( not wipe) user data, install TWRP and root the rest will obviously be easy.
---------- Post added at 06:23 PM ---------- Previous post was at 06:22 PM ----------
Boiisxu said:
@tsongming Do you know why he bricked his phone? I mean he just flashed .eu.
Click to expand...
Click to collapse
He didn't format user data, or the file was somehow corrupted

Is Downgrade possible using stock recovery options?

Hello.
So a few days ago I updated my A2 with June security patch / update. After that I noticed one day my phone wont charge fast...even though it was plugged into the standard 5V inbox charger. It kept discharging even when plugged in.
Ultimately the battery drained completely and it shutdown. It wont turn on even when connected on charger. After a few hours of trying to switch it on it finally turned on but would still charge very slowly.
So I assumed it was a due to that update and thought of downgrading and hence decided to unlock the bootloader..... But...MY PC DOESN'T DETECT MY PHONE IN FASTBOOT.
I tried a lot of things like reinstalling drivers, reinstalling mi flash, reinstalling windows, three different cables and even tried two pcs. Adb is detected, i can transfer files, everything works except the fastboot part....where the pc doesn't detect anything, not even a sound, and nothing in the device manager. ?
So atlast I just want to ask if there is a way to downgrade my stock and locked Mi A2 currently on android 10 using adb commands or by using the stock recovery options i.e. apply update through adb and sd card.
Also if I wanted to know if flashing a older version of stock android Pie through stock recovery options can brick my phone ( ARB ).
Edit : Mi flash recognises my phone when phone is switched on and when i choose apply update through abd using stock recovery. Is downgrading possible using Mi flash without switching to fastboot mode?
Thank you.

Question My Mi 11 is not turning on (black screen) no edl mode

after seeing the new custom roms for the Mi 11 i jumped straight on and flash PE 12.1 and it bricked on me (gotta pay like 10 bucks), after that i went on another try with Evo X with no luck having no boot animation (only the Mi Boot splash) ,boot loops. after all of that i came back to xiaomi.eu 12.5.9 (twrp version) thats the end of the day. Next morning i tried my luck again leading to a brick with no solutions. i flashed twrp and reboot into the bootloader and it never wakes up again (no edl)

If you have windows PC and in device manager PC still recognize driver 9008 you are good to go. For another edl unbrick. If not , check your driver's and USB ports . Change ports etc

longxrt said:
after seeing the new custom roms for the Mi 11 i jumped straight on and flash PE 12.1 and it bricked on me (gotta pay like 10 bucks), after that i went on another try with Evo X with no luck having no boot animation (only the Mi Boot splash) ,boot loops. after all of that i came back to xiaomi.eu 12.5.9 (twrp version) thats the end of the day. Next morning i tried my luck again leading to a brick with no solutions. i flashed twrp and reboot into the bootloader and it never wakes up again (no edl)
Click to expand...
Click to collapse
The mi 11 can go to recovery mode ?

samarimama said:
The mi 11 can go to recovery mode ?
Click to expand...
Click to collapse
no and it doesnt show edl mode

Asnamus said:
If you have windows PC and in device manager PC still recognize driver 9008 you are good to go. For another edl unbrick. If not , check your driver's and USB ports . Change ports etc
Click to expand...
Click to collapse
it doesnt show the 9008 driver and it wont respond to any button combinations like fastboot or hard reset

Check some other USB port, or other PC - laptop. Reinstall driver, download latest. Restart PC. Use original USB cable that came with the phone. Make sure that cable is working....

Asnamus said:
Check some other USB port, or other PC - laptop. Reinstall driver, download latest. Restart PC. Use original USB cable that came with the phone. Make sure that cable is working....
Click to expand...
Click to collapse
i tried all even with a different cable, it doesnt work. i think i might need to shorten the pins

longxrt said:
i tried all even with a different cable, it doesnt work. i think i might need to shorten the pins
Click to expand...
Click to collapse
Ok., Open the back find the pins and shorten. I manage to do this, but couldn't install. For this you really need someone with authorized account that will get codes from manufacturer... Etc. Good luck

Try to remove the battery and press on the power button at least 2 minutes.

longxrt said:
after seeing the new custom roms for the Mi 11 i jumped straight on and flash PE 12.1 and it bricked on me (gotta pay like 10 bucks), after that i went on another try with Evo X with no luck having no boot animation (only the Mi Boot splash) ,boot loops. after all of that i came back to xiaomi.eu 12.5.9 (twrp version) thats the end of the day. Next morning i tried my luck again leading to a brick with no solutions. i flashed twrp and reboot into the bootloader and it never wakes up again (no edl)
Click to expand...
Click to collapse
Open your phone and connect edl pin points,
By the way, you need to have proper MIUI 13 installed before flashing thise roms, and if you used twrp to flash it, that's not the way to go

longxrt said:
after seeing the new custom roms for the Mi 11 i jumped straight on and flash PE 12.1 and it bricked on me (gotta pay like 10 bucks), after that i went on another try with Evo X with no luck having no boot animation (only the Mi Boot splash) ,boot loops. after all of that i came back to xiaomi.eu 12.5.9 (twrp version) thats the end of the day. Next morning i tried my luck again leading to a brick with no solutions. i flashed twrp and reboot into the bootloader and it never wakes up again (no edl)
Click to expand...
Click to collapse
XiaomiFireTool
XiaomiFireTool is specialised service Tool for ! Repairing Xiaomi Phones. It supports every single Xiaomi Phone out there in Market. It supports Flashing / Unlocking / Factory Reset / FDL/FRP/ Mi Account Remove etc. It works with both Qualcomm Chipsets...
xiaomifiretool.com