I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Also get magisk to root rather than SuperSU. You can install twrp from magisk in oos with the correct installer but first you have to root correctly with modded boot.img. Can make your own or get from the one post in here. I'd suggest getting the newest oos also.
Brettroth said:
When you get it to reboot did you try holding volume down as it starts? Should get you into recovery then bootloader.
Click to expand...
Click to collapse
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Brettroth said:
Probably need to flash a stock boot of 11.1.1.1 to unbrick. You can try booting to the newest twrp from fastboot I'm not sure if it works anymore.
Click to expand...
Click to collapse
Couldn’t fastboot into twrp, since device got corrupted while trying to flash multiple things. Thankfully while tinkering, my desktop recognised my device as qhusb qloader 9008, and all I had to do was boot my device into edl mode (which was also a pain tbh!). After trying numerous key combinations and timing it perfectly, device booted into edl and I could use the msm download tool to unbrick my device. Now device has rebooted into iOS 10.3.5 (same version as msm tool version) and I have somehow breathed a huge sigh of relief that my device could be resuscitated. Will be updating to 11.1.1.1 now (I see the latest is 11.1.2.2) and setting up my device now.
Thank you a lot for looking into my issue and suggesting solutions. In my younger years, I was a technology enthusiast and often rooted/flashed, but have pursued medicine since then. Now am out of touch completely to the tech scene and it was a grave blunder on my part to have used my primary driver to try and root/flash again.
Have a great day, my friend and please know that it means a lot to me to have received help from the community.
Jeet77 said:
I was on A11.1.1.1 , when I decided to root my device. Tried to install Twrp but failed, then unlocked boot loader and flashed magisk using Adb from my windows 7 desktop. Phone restarted, went into bootloop, then restarted naturally - however I couldn’t turn on Wi-Fi. Downloaded SuperSU, which showed device was rooted. In an attempt to revert back to stock os, I flashed another boot image, and phone went into continuous boot loop. So I searched the web and downloaded Qualcomm hs-usb QDloader 9008, and MsmDownload tool v 4.0 in an attemp to unbrick my device and installed them. However, my desktop doesn’t recognise my phone as Qhusb_bulk or as Qualcomm qhusb qdloader9008 in devicemanager. So I m unable to use the MSM tool to un brick my phone. Tried reinstalling the drivers on desktop , but the phone doesnt show up on device manager still. Only shows up as “pci simple communications controller” under other devices.
When i turn on my phone, it shows the OP logo going round and round for 5mins, then the screen goes blank. If I keep the power off button pressed for quite sometime, phone restarts into boot loop again. Can’t get into boot loader, nor does adb on my desktop recognise the device.
i m at my wits end as to how I m gonna unbrick my phone, as this is my primary phone. Kindly guide me step by step as to how to unbrick my OP6t. Any help is appreciated.
Click to expand...
Click to collapse
This happen to me several times and the first time it happened I thought my phone would not be unbricked after numerous attempts with the msm tool!
My issue was that my phone was a renewed amazon phone and amazon listed it as a unlocked international but it actually was a t-mobile variant and when i downloaded the correct msm tool with firmware it worked!
You need to get the phone into edl mode. For edl, when phone off press both volume buttons and plug in the usb while connected to your pc and the qualcom driver should pop up in device manager. After that finding the right msm firmware will be your next issue but with enough searching you should find it!
Let me know your progress with the driver and I can try and post some links to different msm firmware for the oneplus 6t!
Related
Accidentally bricked my phone while trying to unlock the bootloader on my phone. I was doing this in an attempt to root my phone again after removing the root in an attempt to update Oxygen OS. After TWRP was unable to flash the update I gave up and tried to root the phone again using kingo root but kept failing. I checked whether or not the bootloader was locked and sure enough it was but after attempting to unlock it again, the phone was bricked and could only go into fastboot mode. Flashing the stock OS didnt work since the bootloader was locked. I tried using a unbricking method posted to oneplus forums that invloves downloading qualcomm diagnostic drivers and using a unreadable download tool but couldn't find the driver the method mentioned Qualcomm 9008. After some more searching other methods were similar but used the driver Qualcomm HS-USB Diagnostic 9006. Once that driver was installed i launched the MSMdownload tool which was taking hours with no progress bar whatsoever so i decided to go to sleep. I woke up to an unreadable notification from the download tool and my phone's battery was dead. The phone wouldn't go into fastboot mode but was still being detected in device manager. All the phone responds to is the power button and volume down button being pressed which just causes the phone to display a low battery notification and then stops charging a minute later. I then tried using an unbricking method that involves installing the qdloader 9008 driver and running a program called QFIL but this method failed to unbrick the phone. Is there any way to factory reset my oneplus 2 and put the stock OS back on to it? please keep in mind that the bootloader is locked. i cant post links to the methods i used as the site wont let me
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
You must post in Q/A not here
Tapatalké depuis mon OnePlus 6T Havoc OS avec FP !
What were u exactly trying to do while this happened ?
Extreme_Ninja2099 said:
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
Click to expand...
Click to collapse
You can restore you device using fastboot rom. Search for oos 6t fastboot rom.. There are guides for installation.
P.S. It will give a whole bunch of error in the cmd during installation but don't interrupt the process as your device will be restored in the end
Use Mnm tool to fix your phone. It can fix hard brick devices and guidance is there how to use .
PS: this is not right place post next time post on Q/A section.
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
parker.stephens said:
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
Click to expand...
Click to collapse
Hold down every button till it shuts off, then force reboot to bootloader, then select power off to make sure it's off. Then do as I instructed above to fix it. Sometimes u can just run a fastboot rom to fix it, or boot twrp and flash a rom. I do this multiple times a day sometimes.
fullofhell said:
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Click to expand...
Click to collapse
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Extreme_Ninja2099 said:
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Click to expand...
Click to collapse
Everybody, it's called the MSMDownload Tool. It cannot be used in Fastboot Mode or Qualcomm CrashDump Mode, it can only be used in EDL Mode (Emergency Download Mode).
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
CaptionNixx said:
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
Click to expand...
Click to collapse
Power off use msm. Done.
fullofhell said:
Power off use msm. Done.
Click to expand...
Click to collapse
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
CaptionNixx said:
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
Click to expand...
Click to collapse
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Extreme_Ninja2099 said:
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Click to expand...
Click to collapse
Yes i did that and driver is fully installed Qualcomm HS-USB QDloader 9008 and there is No yallow sigh in driver
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Extreme_Ninja2099 said:
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Click to expand...
Click to collapse
Thanks brother its done
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Voldemort13 said:
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Click to expand...
Click to collapse
did yoy got any solution
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
I have tb-x304f that I unlocked and flashed TWRP and then tried three different custom roms that all failed to boot. I am trying to restore stock firmware but it is not working. I have installed firmware with qdl in Linux and with QFIL and Lenovo Rescue and Smart Assistant in windows. All three methods report success. After allowing time to boot it ultimately boots into 900E Diagnostic mode after a brief stint as MTP device. The boot logo shows on display, the little Lenovo tone chimes and a progress bar with powered by Android starts. Bar gets about one third of the way and it goes black, then it's 900E Diagnostics again. Use hardware buttons to put it in QDLoader 9008 mode and flash again, same results every time.
I am lost, with successful flashing with no errors, but it won't boot. Do we have a Qualcomm expert in house that can help me figure this one out ?
Hi, first of all, sorry for my English, I don't write it very well.
I have a Lenovo Tab4 A 10 x304l actually it is in bootloop, because I tried to install a Custom ROM and never boot it. I tried to install two stock ROM, that I download to diferent sites, but the tablet after a minute reboot it's self continiusly. I need your help, if Is possible, because I don't know what to do.
My WhatsApp Is ±5354161215, I apreciate any help.
Thanks very much...
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Ezzell said:
Hello, I was going through stage to unlock bootloader, it was previously unlocked but a flashing error caused me to flash stock through MSMTool, I forgot to close/stop the tool after it was complete and upon one of the reboots it started the install again.. without realizing I attempted to boot the phone which caused the download to stop incomplete and booting to screen “upgrade download failed” I did select OEM unlocking in developer options as well as usb debugging although now it will not unlock bootloader; I can boot to bootloader not recovery and attempting to hold volume buttons while plugging into pc just pushing it to boot into the same fail screen. Is it possible to get my device into EDL mode so MSMTool can restart the install for stock? Thank you for any time given to help explain or direct.
Apologies if this is in the wrong thread
Click to expand...
Click to collapse
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
HolyHog said:
Try using the MSM tool already started and the hold down VU/VD/Power until MSM grabs it.
Click to expand...
Click to collapse
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Ezzell said:
This just boots to bootloader, from power off, any other combination instantly boots to same error page
Click to expand...
Click to collapse
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
HolyHog said:
It doesn't really matter what it does if you have it hooked up to your computer and have MSM turned on with start button. It can find your phone in a between mode and start installing. It works for me every time, just hit all 3 buttons from wherever you are as long as MSM is in the start mode, it will find it and start installing.
Click to expand...
Click to collapse
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Ezzell said:
It doesn’t seem to recognize the device at all in MSM only in bootloader I get fastboot devices command response and all in one tool recognizes it but says fail due to missing flash all zip or bat thanks for the advise though
Click to expand...
Click to collapse
If MSM does not recognize your phone there is something wrong with your PC.
Make sure that you read the full post:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Use another USB Port and/ or another USB cable.
Dont use Windows11
Install latest Universal ADB Driver
Install latest Qualcomm Drivers
Install latest OnePlus drivers.
In fact the last thing that will NOT work is MSM. If MSM does not work your phone is completly dead. (Which yours is obviously not because it boots into bootloader) This means if MSM does not work, there is something wrong on your end.
Talking about dead devices, be etremly careful what you do in Fastboot mode!
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Anything you do in the OS, like allowing OEM unlocking has **nothing** to do with MSM. In fact, a MSM flash will relock the bootloader. You will have to unlock again if you want to run anything except stock.
You have to boot the phone into EDL mode. Start MSM, then while holding the volume bar down, (UP and down, the entire button) plug into usb. Dont use the power button. (You may let volume keys go once done) There will be a dark screen, the only way to tell if in EDL mode is to check your device manager for the correct device. If you see anything on the screen you are not in EDL mode. I did use USB 2.0, do not use a hub.
I ask to start MSM first because on my Oneplus8, the EDL mode wont stay active for too long, unless MSM finds the phone.
If that does not work, put the phone into EDL mode and check your device manager (ports COM anf LPT) for QDLOADER 9008. Anything else, and the driver is not installed correctly and MSM won't work, If adb is working you can issue "adb reboot download" but the button press seems more applicable in your case.
There is a lot in the link below, it is for A10, I believe there is now a MSM for A11 but I have no experience with them.
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
I have tried all these and msm will not recognize the device in any state so Iv reverted to using a repair shop msm was successful in making the device stock the problem came from rebooting the device while msm was still connected and running. Pressing any button would lead to the download failed screen where the device is not recognized or into bootloader where oem is locked and even though before boot I checked unlocking enabled the fastboot command would not unlock the bootloader, if the store fix it I will try get details on what they did