Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF
Related
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
Well, i'm kinda scared because i already installed a lot of custom rom's and everything works fine every time. Yesterday i installed the MIUI 12 Beta chinese version and after i saw that have one global beta version so i download the global one, installed the pre loader to prevent the bricked device and installed the twrp recovery to install the global rom. I wiped everything as always, installed the rom and reboot the phone... Now he doesnt show nothing, just died, he doesn't stuck at boot loader, if i connect him to the power the charging led turns on, he vibrate if i click at the power button but no image at all, nothing...
I tryed to connect to pc and turn it on at fastboot thinking that the ldc pannel was burned but no, the pc iddentifies a divice and 1 sec after he just unplug itself...
Can someone help me?
jhrolife said:
Well, i'm kinda scared because i already installed a lot of custom rom's and everything works fine every time. Yesterday i installed the MIUI 12 Beta chinese version and after i saw that have one global beta version so i download the global one, installed the pre loader to prevent the bricked device and installed the twrp recovery to install the global rom. I wiped everything as always, installed the rom and reboot the phone... Now he doesnt show nothing, just died, he doesn't stuck at boot loader, if i connect him to the power the charging led turns on, he vibrate if i click at the power button but no image at all, nothing...
I tryed to connect to pc and turn it on at fastboot thinking that the ldc pannel was burned but no, the pc iddentifies a divice and 1 sec after he just unplug itself...
Can someone help me?
Click to expand...
Click to collapse
What device shows up? Can you do a lsusb (if you're under linux or can run a linux distro)? If you press Vol+ does anything happen? Does SPFT work?
Beware some people reported problems using the preloader with Android 10.
MOD EDIT: Content removed
Si, ele vibra pero no aparece nada!
u8ububu said:
What device shows up? Can you do a lsusb (if you're under linux or can run a linux distro)? If you press Vol+ does anything happen? Does SPFT work?
Beware some people reported problems using the preloader with Android 10.
Click to expand...
Click to collapse
Well im not using a linux distro but i can install ubunto if needed!
If i pres vol + or - and power after like 10 sec he vibrates but nothing happens...
What is SPFT ?
follow this guide
https://forum.xda-developers.com/redmi-note-8-pro/help/hardbrick-rn8p-t4064637
and use the files from this for your corresponding device
https://www.cyanogenmods.org/forums/topic/how-to-unbrick-redmi-note-8-pro/
please dont flash the indian preloader or the lk files or itll be bricked again, use orange fox recovery for andoid 10 as recovery as to avoid bootloop in using reboot to recovery option. (saving you guys some money and time, had to reflash my phone a couple times before just sticking to miui 12 with custom recovery
jhrolife said:
Well im not using a linux distro but i can install ubunto if needed!
If i pres vol + or - and power after like 10 sec he vibrates but nothing happens...
What is SPFT ?
Click to expand...
Click to collapse
SPFT is Mediatek's flashing tool. It is used when their phones hardbrick. You should read about it now.
If the phone vibrates, you most likely have some preloader flashed, the question is which. You should follow the instructions mentioned in iRayn's post above. If you still got the factory preloader, you're in luck, the guide will definitely work.
If you don't have it, you'll likely need to use an authorized account, but first try getting a ubuntu image (you don't need to install it, just run a live version); there's some useful info that can be gathered from lsusb. Particularly if you see 0e8d:0003 in lsusb's output when pressing Vol+, try again with SPFT while pressing Vol+.
iRayn said:
follow this guide
https://forum.xda-developers.com/redmi-note-8-pro/help/hardbrick-rn8p-t4064637
and use the files from this for your corresponding device
https://www.cyanogenmods.org/forums/topic/how-to-unbrick-redmi-note-8-pro/
please dont flash the indian preloader or the lk files or itll be bricked again, use orange fox recovery for andoid 10 as recovery as to avoid bootloop in using reboot to recovery option. (saving you guys some money and time, had to reflash my phone a couple times before just sticking to miui 12 with custom recovery
Click to expand...
Click to collapse
IT WORKS! My RN8P is alive !!! Thanks alot !!!! You really help me out!
jhrolife said:
IT WORKS! My RN8P is alive !!! Thanks alot !!!! You really help me out!
Click to expand...
Click to collapse
good to know, save files and links for future bricks
A desperate owner here, I recently tried to install a custom rom and to my surprise everything went wrong and to try to fix the problem I tried to flash my device through QFIL and now it doesn't get out of that anymore ...
I tried countless different ones but always the same result.
Can someone help me????
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.
Hello, i tried helping my grandmother by installing the global rom on her Xiaomi Mi Pad 5 Pro WIFI, however as it didn't work i tried forcing the rom onto it by flashing it manually using fastboot, after this i am not able to power it on, or reach fastboot. It's just a black screen it doesn't matter how long you hold the power key it's just completely black.. Is there something i can do???? Or is it completely destroyed?
Global ROM is not available for PRO version. Probably you flashed a wrong one. Try flashing back the CN one matches your model.
mkcs said:
Global ROM is not available for PRO version. Probably you flashed a wrong one. Try flashing back the CN one matches your model.
Click to expand...
Click to collapse
Ahh thats the thing, it won't even power on now, i cannot even access fastboot
desyncccccccc said:
Ahh thats the thing, it won't even power on now, i cannot even access fastboot
Click to expand...
Click to collapse
long press "Volume Down" + "Power" for a few seconds at the same time and then release only"Power" once the fastboot logo appears, finally release "Volume Down" to enter the fastboot mode
Its for xiaomi mi5
Maybe helps
Is there anything I can do? Brick help
My Xiaomi mi5 does not turn on. No lights, fastboot is not accessible, resetting it does not do anything. Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead. However, when I...
forum.xda-developers.com
Keyvannn said:
Its for xiaomi mi5
Maybe helps
Is there anything I can do? Brick help
My Xiaomi mi5 does not turn on. No lights, fastboot is not accessible, resetting it does not do anything. Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead. However, when I...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah so the only problem with this is that mine won't even show up even though i have said drivers installed.. I'm starting to think it's hard bricked
Hello, yes same as me. The tablet are in the 9008 edl state when you put it on your computer. there are many flashing tools out there, the problem are the flash authentification from xiaomis side. i prepared a empty pc with windows 10 and loaded the last fastboot image. then i got a telegram contact from a russian guy who was able to use the xiaomi auth procedure, cost me 30 dollar and 3 days to find out this crap
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
desyncccccccc said:
Hello, i tried helping my grandmother by installing the global rom on her Xiaomi Mi Pad 5 Pro WIFI, however as it didn't work i tried forcing the rom onto it by flashing it manually using fastboot, after this i am not able to power it on, or reach fastboot. It's just a black screen it doesn't matter how long you hold the power key it's just completely black.. Is there something i can do???? Or is it completely destroyed?
Click to expand...
Click to collapse
When it's plugged into the PC, is it recognised with "fastboot devices" or "adb devices"?
If it is you should be able to wipe with "fastboot -w" and start again.
Google detailed instructions.
mikefnz said:
When it's plugged into the PC, is it recognised with "fastboot devices" or "adb devices"?
If it is you should be able to wipe with "fastboot -w" and start again.
Google detailed instructions.
Click to expand...
Click to collapse
Unfortunately no, i do not get any response from fastboot whatsoever, there's no device detection in either fastboot or device manager. I even tried on my laptop which is brand new still no sign of life
fritzeman said:
Hello, yes same as me. The tablet are in the 9008 edl state when you put it on your computer. there are many flashing tools out there, the problem are the flash authentification from xiaomis side. i prepared a empty pc with windows 10 and loaded the last fastboot image. then i got a telegram contact from a russian guy who was able to use the xiaomi auth procedure, cost me 30 dollar and 3 days to find out this crap
Click to expand...
Click to collapse
Where would i be able to get in contact with someone like that??
desyncccccccc said:
Unfortunately no, i do not get any response from fastboot whatsoever, there's no device detection in either fastboot or device manager. I even tried on my laptop which is brand new still no sign of life
Click to expand...
Click to collapse
Try different cable & different pc usb slot?
Try flashing using * Xiaomi professional pro tools . Buy credit and all done,
mikefnz said:
Try different cable & different pc usb slot?
Click to expand...
Click to collapse
Unfortunately any cable/pc i try i get the same result, i'm debating wether i should just get a new one for her with global rom instead
desyncccccccc said:
Unfortunately any cable/pc i try i get the same result, i'm debating wether i should just get a new one for her with global rom instead
Click to expand...
Click to collapse
Don't give up yet!
Charge the tablet with another cable that you know works.
Make sure that you have the most up to date version of Platform Tools.
Make sure that when you're in the Command Prompt that you are in the Platform Tools folder.
Check connections with another device....
mikefnz said:
Don't give up yet!
Charge the tablet with another cable that you know works.
Make sure that you have the most up to date version of Platform Tools.
Make sure that when you're in the Command Prompt that you are in the Platform Tools folder.
Check connections with another device....
Click to expand...
Click to collapse
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully
desyncccccccc said:
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully
Click to expand...
Click to collapse
Buy an EDL Cable For Qualcomm 9008 Mode for deep flashing
desyncccccccc said:
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully
Click to expand...
Click to collapse
Have you got the most up to date version of Platform-tools installed and are you checking the connection from a CMD prompt in that Platform-tools folder?
mkcs said:
Buy an EDL Cable For Qualcomm 9008 Mode for deep flashing
Click to expand...
Click to collapse
Could you please link me one of those? I'm over in the EU so maybe they'll be fairly easy to find?
mikefnz said:
Have you got the most up to date version of Platform-tools installed and are you checking the connection from a CMD prompt in that Platform-tools folder?
Click to expand...
Click to collapse
Yeah, i've been doing all of that. I just now found out that there's an EDL cable specifically made for flashing in that mode