Database Info

Adb in recovery

Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8

Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.

Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc

Yeah, I'll do that today
Sent from my One M8

Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc

Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.

Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working

Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.

Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?

Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.

Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????

MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.

Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm

Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet

Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?

MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.

Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really

MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.

Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.

MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:

xt1032 BootLoop (Android starting..) can't enter recovery or bootloader.

Hi everyone im stuck on the resurection of my device (moto g 2013 8GB updated to 5.1 with [5.1 GPE 1 click] from This forum.
I've tried everything or almost for now, cant get it out of that loop.
*Battery pulling.
*hard buttons combinations.
*fastboot and ADB. (not in fastboot mode so.. And as i did flash de 1click before the loop USB Dbgn isn't enabled)
*i think i've tried every toolkit on this forum.
*Raped google search for over a week trying every posible method-
*Only thing left is to take it to church for a blessing. but im not a believer D:
ADD: i've rooted with a "boot.img" from this forum i think it was a 2015 file.
before this i had not 1 issue with the phone. just unlockd the bootloader a few days ago and updated to 5.1 from 5.0.2 becouse of a wifi issue (unknow mac adress) i had to reboot it like 10 times until it appeared again (original mac adress from device, still wrote it down i have it somewhere.)
I think this would be my first post on this forum and it took me over a week to do it becouse this (asking you-comunity) is my last resource.
PS: i had it going betwen 5.0.2 and 5.1 like 4 times to try solving the wifi issue.. only thing it got me was the "line" on the screen like if it where a problem with vertical sync. (i think you are all very familiar with that issue after downgrading the kernel i think.)
the phone just turns it self on everytime. (everytime)
i was able to boot into recovery before the last flash touching the place were the hardware volume button goes (with a neddle) untill it didnt workd anymore and i send it to a store to repair the volume rockers. still no recovery or bootloader boot.
my pc (laptop with 7-32bit recognices it as xt1032. and the one with xp as MTP.)
I've installed every posible thing that i found to bring it back to life even the android sdk full every pkg from 5.0.2 to 5.1 and extras, Motorola drivers and ADB. tried online searching automated from windows and listing it from a folder with the google one. tried adding the hardware manualy and have every ADB thing that i found on device mng but everyone is wit a yellow triangle. (No USB Debuging enabled so why bother anymore.)
I think that's about it.

You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img​
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata​
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510

i m sorry for my english, isnt my native lang. And for making it over complicated.
i cant enter fastboot mode or give any order to the phone trough fastboot on a console.
I have installed a TWRP touch, just cant acces it. dont know if it is the hardware button (Vol -) or what.
so it dosnt show up on fastboot devices nor adb devices.
am i not understanding something ?
Thanks for replying and taking the time to help!

Enter fastboot mode by turning on phone while holding Volume Down.

lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.

dieguitwow1 said:
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
Click to expand...
Click to collapse
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.

If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
Click to expand...
Click to collapse
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?

dieguitwow1 said:
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
Click to expand...
Click to collapse
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.

lost101 said:
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img​
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata​
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
lost101 said:
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
Click to expand...
Click to collapse
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?

dieguitwow1 said:
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
Click to expand...
Click to collapse
If you power phone off completely, then no commands are remembered. The button is broken.

lost101 said:
If you power phone off completely, then no commands are remembered. The button is broken.
Click to expand...
Click to collapse
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a niddle until it stoped working is there a fix for it? :fingers-crossed:

dieguitwow1 said:
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a needle until it stopped working is there a fix for it? :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I can't help you with that. If you know someone good with a soldering iron, maybe they can fix it - otherwise, try another repair shop.

its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..

dieguitwow1 said:
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
Click to expand...
Click to collapse
adb reboot bootloader​

lost101 said:
adb reboot bootloader​
Click to expand...
Click to collapse
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]

dieguitwow1 said:
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
Click to expand...
Click to collapse
Yes, USB Debugging would need to be enabled.

lost101 said:
Yes, USB Debugging would need to be enabled.
Click to expand...
Click to collapse
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:

dieguitwow1 said:
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
Click to expand...
Click to collapse
I am not aware of any other options.

i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.

dieguitwow1 said:
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
Click to expand...
Click to collapse
What has changed? Did you get the vol button fixed?

Help fixing my bricked phone, I haven't seen a phone behave like this before.

When I try to boot the phone, either through the power button or bootloader, it tries to get into recovery over and over again but can never get in (to TWRP recovery). It always just gets to the TWRP splash screen but then goes black and repeats. The bootloader is unlocked. I am not sure what state the actual OS is in. ADB doesn't recognise the phone (adb devices shows nothing). Oh, and I can't get into recovery through bootloader either.
Can anyone offer any advice?
Thanks in advance

Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?

audit13 said:
Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?
Click to expand...
Click to collapse
Definately not a power button issue, it was fine before. What is fastboot mode and how would I get into it?

The power button issue can appear out of nowhere, at least it did for me. The constant reboots are also an indication.
To get into fastboot, power off the phone, hold volume up, volume down, and press power button.

I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
Corneliusvinyo said:
I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
Click to expand...
Click to collapse
Disregard this . I assumed you could get it into recovery . sorry

I think I may have just hard-bricked my G3. Is there hope?

I (stupidly) decided to repartition my Moto G3 using this guide. Now, when trying to turn my phone on, the screen stays blank and there's no indication that it's working but it reboots once every two to five seconds or so (telling you how I can tell it's rebooting would be a long story and I'm sure it's irrelevant to the issue).
Am I just hooped or is there hope?

Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)

HelpMeruth said:
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
Click to expand...
Click to collapse
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.

sensi277 said:
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
Click to expand...
Click to collapse
Try to connect it to your pc and see if adb/fastboot sees the device.

michkost858 said:
Try to connect it to your pc and see if adb/fastboot sees the device.
Click to expand...
Click to collapse
adb shell doesn't see anything.

sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...

Jewshua said:
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Click to expand...
Click to collapse
Or, since the battery is not officially removable, wait till the battery dies and then try to boot into bootloader.

Volume down broken
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?

tyty48 said:
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
Click to expand...
Click to collapse
Can you boot the ROM?
If so, you should be able to turn on usb debugging and run 'adb reboot recovery' and reflash from there
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
what about fastboot devices (with admin/root privileges) ?

Question Poco x3 pro Bricked, Stuck on logo no volume buttons

Hello, So I've recently tried flashing a specific custom ROM for my Poco x3 pro, but when I flashed it on twrp it said Failed To Mount Vendor, Failed To Mount Root and something else but I don't really remember, I watched a youtube tutorial to fix but when I booted into system it just showed the boot logo animation, it only goes off when it's out of charge, my volume buttons are broken too, I've went to several stores but they said they can't fix it, the thing is that when I connect my phone to the PC, it detects it in adb, but I'm unable to do anything because it's "unauthorized" should I just give up on the phone?

Jerjfo said:
Hello, So I've recently tried flashing a specific custom ROM for my Poco x3 pro, but when I flashed it on twrp it said Failed To Mount Vendor, Failed To Mount Root and something else but I don't really remember, I watched a youtube tutorial to fix but when I booted into system it just showed the boot logo animation, it only goes off when it's out of charge, my volume buttons are broken too, I've went to several stores but they said they can't fix it, the thing is that when I connect my phone to the PC, it detects it in adb, but I'm unable to do anything because it's "unauthorized" should I just give up on the phone?
Click to expand...
Click to collapse
What happens if you run "adb reboot recovery"?

DarthJabba9 said:
What happens if you run "adb reboot recovery"?
Click to expand...
Click to collapse
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo

Jerjfo said:
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo
Click to expand...
Click to collapse
Tried an older adb version and it now says "This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.

Jerjfo said:
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo
Click to expand...
Click to collapse
Unfortunately, if you can't use adb commands and your volume buttons are not functional, then you are out of options. Your priority should be to get the volume buttons fixed. If it is not possible to get them fixed, then you are stuck.

What about earphone volume buttons? That works.
DarthJabba9 said:
Unfortunately, if you can't use adb commands and your volume buttons are not functional, then you are out of options. Your priority should be to get the volume buttons fixed. If it is not possible to get them fixed, then you are stuck
Click to expand...
Click to collapse

Did you unlock the bootloader first? Sorry if this seems like a dumb question but you didn't indicate that you did.

@immortalwon exactly that was what i thought at the first reading this threat yesterday...

immortalwon said:
Did you unlock the bootloader first? Sorry if this seems like a dumb question but you didn't indicate that you did.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked with twrp on it, I flashed the wrong rom for my phone [Oxygen OS Port] And it got stuck on logo

Jerjfo said:
Yes, my bootloader is unlocked with twrp on it, I flashed the wrong rom for my phone [Oxygen OS Port] And it got stuck on logo
Click to expand...
Click to collapse
I know exactly what happened. Because you flashed the wrong rom, it replaced also your custom recovery so now you are full bricked. I am not sure if there is official unbrick tools from Xiaomi, but you prob need to find someone who can do remote flash repairs.
I would try this before anything: Hold all volume buttons and power button until screen turns off. If it does turn off, hold volume down and power button and try to get into fastboot menu.
This link may also help: https://new.c.mi.com/global/miuidownload/detail/guide/1

immortalwon said:
I know exactly what happened. Because you flashed the wrong rom, it replaced also your custom recovery so now you are full bricked. I am not sure if there is official unbrick tools from Xiaomi, but you prob need to find someone who can do remote flash repairs.
I would try this before anything: Hold all volume buttons and power button until screen turns off. If it does turn off, hold volume down and power button and try to get into fastboot menu.
This link may also help: https://new.c.mi.com/global/miuidownload/detail/guide/1
Click to expand...
Click to collapse
The thing is that my volume buttons are broken, I might fix them but I think fastboot got erased along with the recovery (not sure)

Jerjfo said:
The thing is that my volume buttons are broken, I might fix them but I think fastboot got erased along with the recovery (not sure)
Click to expand...
Click to collapse
Why would you even bother to flash stuff with broken volume buttons? That's asking for big trouble, which occurred to you. I would suggest fixing or getting a new phone

Jerjfo said:
fastboot got erased along with the recovery (not sure)
Click to expand...
Click to collapse
Fastboot can't get erased.
No worries there.