Related
First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Please move the thread into guides/tutorial section.
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.
aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.
meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks
Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.
Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead
Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost me
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screwdriver.
I did NOT have success with deep flash cable myself, I had to use testpoint method (and sadly broke my LCD in the process). The deep flash issue might of been because I was in Windows 10 x64 or on a USB3 port. If you do go that route and can't get it working, try with a Windows 7 x86 VM and USB2 passthrough mode before last resort of taking device apart.
Hold power button for 20 sec then volume down and fastboot will apear
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
CosmicDan said:
Did you do factory flash mode? That's the only one that can recovery it, the other scripts won't flash everything.
Note that because you didn't backup partitions you will also wipe the IMEI, or so I've read (I backed up my whole device via emmcdl before brick so I was able to recover fine without miflash)
Click to expand...
Click to collapse
Actually I think I got scammed. It is Mi5x sold as MiA1. ****ing chinks! Anyway, I managed to install (Tiffany) on it and now it is booting to boot logo and bootlooping. I can get to fastboot and default (MIUI's) recovery by pressing button combos. But OEM is locked now so I cannot flash TWRP or other ROMs in it. I will have to EDL flash back to that MIA1 ROM to get it unlocked from fastboot. Otherwise MIUI unlocker asks me to link my miui account to this phone by going to settings, which I can't do because it is not booting up.
funny situation.
Bruce666 said:
Hi guys
At first - I tried a method given on this forum: https://forum.xda-developers.com/mi-a1/help/phone-goes-to-qualcomm-hs-usb-qdloader-t3757867
This method doesn't work for me, because after disconnect my PC doesn't recognize my phone.
Phone is in Qualcom HS-USB Diagnostics 900E mode after OTA update (Mi A1 April Update) - strange
So guys... I know there are some magicians who can do almost everything.. Any ideas what to do?
Click to expand...
Click to collapse
Facing The same Issue
---------- Post added at 10:42 AM ---------- Previous post was at 10:35 AM ----------
Phone Showing Charging Only
Can't Even Transfer Data
Not Detected on Pc
udaan said:
1. install all necessary drivers (adb, qualcomm's HS-USB Diagnostics 900E, xiaomi flash tool)
2. use test point method as suggested by @CosmicDan - lots of tutorial on web on how to do this. Carefully read this before actually attempting it.
3. When you successfully do the test point method you will hear the device recognized sound on your computer
4. when you hear it, open miflashtool and your device should show up in it.
5. if not, reboot your PC. You should reboot your PC after installing all the drivers. See #1. (reboot required)
6. Once you successfully see your device on miflashtool, you can flash the fastboot rom of your choice.
7. (you might get stuck on "Can't receive hello packet" dialogue which will prevent your device from flashing), in that case change the USB port, possibly to USB 2.0 and try the test point flash method again to get detected and try flashing again.
8. Test point method should be done everytime you disconnect the USB from your phone and computer, hopefully you only need to do it twice.
9. Sadly for me, I am still unable to flash stock roms with this method, my problem is kind of unique, after flashing it shows me "Your phone is destroyed, press power to turn off" dialogue. lmao
10. if you get the same message then you dun goof'd. Hopefully yours will successfully flash.
Oh and only one version of fastboot ROM actually revives the phone, other fastboot roms actually puts it to coma (vibrating every one second, no display, no nothing). Only one fastboot ROM allows me to go to fastboot and flash recoveries. But if I flash any ROM (stock or custom) it kills the phone again and I have to repeat the given method and try again with another rom. I think the phone is effectively dead. What a **** phone! lol
Click to expand...
Click to collapse
Im sorry, exactly with which ROM did you get to the fastboot?
Press power button for 15 sec
If you feel vibration then you are so lucky
boshell said:
Im sorry, exactly with which ROM did you get to the fastboot?
Click to expand...
Click to collapse
Fastboot rom for Mi5x because the phone is Mi5x.
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.
Hello! all. Im really nervous. THis never happened before, i dont know what to do. I was using an Custom Rom Miui Eu. And i decided today to went back to the official one for good. And when i was flashing the firmware in Miflash, the phone never reboot and MiFlash showed as "Flash Complete" in green color, so i removed the usb and the went all black and there is no way tu turn on the picture, i cant go to bootloader or fastboot. When i connect the phone to the PC. My PC recognize the phone as Qualcom 9008. But i cant flash and do anything. What can i do? i tried replacing the auth .elf file but im still having the error in MiFlash. The only way to fix this brick is doing that "test point" thing ?
First download the latest firmware and the correct one (global, chinese or whatever you had) for your device because you can only install higher version firmware using flash tool.
It seems your phone already is in EDL mode, hence there is no need for test point method.
Try another usb port. Try using a different PC. Change the location of the firmware folder to a shorter path like C:\ and try to reboot the phone a few times and then try.
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!