Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Please anybody respond!
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
PattasuBalu said:
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
Click to expand...
Click to collapse
There is no MSM tool for the device! I don't know how can I fix it
ArmashOnXDA said:
There is no MSM tool for the device! I don't know how can I fix it
Click to expand...
Click to collapse
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
PattasuBalu said:
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
Click to expand...
Click to collapse
Ahhhhhhhhh- That sucks. OnePlus isn't the same as it once used to be. Is OnePlus ever even gonna release the blessed keys to the public to help thelucky one's who managed to brick their device?
ArmashOnXDA said:
Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Click to expand...
Click to collapse
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
Could you explain it more in detail? Like giving me the exact instructions as to what i have to do.
Also, What do you mean by "adv"?
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
PattasuBalu said:
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
Click to expand...
Click to collapse
How long does the service center take to fix the device? Hours? Days? Months?
It usually takes 1-2 days. If you are lucky you get it fixed on the spot.
I had the same issue. Got a new device from my provider in exchange.
Maybe brom mode could work in your case.
Your build has to be A.14 or lower as A.15 received the patch.
Related
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?
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)
MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.
From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Finally, I solve the problem by flashing the e recovery image,and then low level forma data.
Hope it helps for someone have the same issue like me.
zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Click to expand...
Click to collapse
I have exactly the same Problem. Did you solve it already?
zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Click to expand...
Click to collapse
Can you still have access to erecovery : volup at power with USB cable plugged. If yes you can try a recovery but you will loose all your data
Can you have access to fastboot : vol down at power up. If yes you can try to flash by adb by following instruction from discussions in the forums.
zhu911203 said:
First, I was doing a full wipe in TWRP, But I realize I didn't back up my photos/Documents.
So I long pressed the power button to restart.
And now, i got a bricked phone...
Any one can help me?
I'd try this
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
But, I got stuck on the TWRP boot screen.
Also, I'm still available to use the fastboot mode.
Click to expand...
Click to collapse
Can you still have access to erecovery : volup at power with USB cable plugged. If yes you can try a recovery but you will loose all your data
Can you have access to fastboot : vol down at power up. If yes you can try to flash by adb by following instruction from discussions in the forums.
Schuchi said:
I have exactly the same Problem. Did you solve it already?
Click to expand...
Click to collapse
yes, I solved the problem, hope it will help you.
I've spent hours searching and cannot find a definite answer to my question. I see others have asked HOW to fix this issue, I just want to know if it is possible.
Is it possible to factory reset my device or not?
Bootloader is NOT UNLOCKED, and I am stuck on bootloader screen.
"Bootlinux Failed: Not started" when trying recovery mode.
"Slot Unbootable: Load Error" when trying to start.
My device is obviously not found under adb devices as it is locked, but does show up in fastboot devices.
My computer does recognize the android device as well.
Is it possible to factory reset my device or not?
Is there any way to flash a custom ROM and get it operational?
I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.
junglism93 said:
I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.
Click to expand...
Click to collapse
Thanks for your reply,
Surely Google or some super nerd would know how? But I think I am also out of luck.
Thanks though.
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
OilyBigMac said:
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
Click to expand...
Click to collapse
Did you tried to get to recovery from bootloader screen or with key combination too?
somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
somin.n said:
Did you tried to get to recovery from bootloader screen or with key combination too?
Click to expand...
Click to collapse
I do appreciate your help, but as I just mentioned, I am stuck in bootloader screen and get errors when trying to access recovery, download, start or any other option. Obviously using the hard reset only brings me to bootloader where I am stuck.
Is this what you're referring to with key combination?
OilyBigMac said:
Is this what you're referring to with key combination?
Click to expand...
Click to collapse
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck
somin.n said:
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck
Click to expand...
Click to collapse
Interesting, I get the same error message as I do when I try to enter Download Mode. So this is different than the power and volume down, and different than just restarting it.
So far I just keep getting back to bootloader screen saying operation denied. But might keep trying it here and there haha.
Thanks for your help.
I had the same problem. I was able to solve it by selecting the download mode in the bootloader. There was an error message. Then I fastboot flashing unlock on the console. Then the bootloader is unlocked. No idea why this worked.
Maybe this will help someone who encountered the same problem.
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.