Related
bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!
Hello everybody,
First off, I hate people who don't search on google before making a post, I have been searching for 4 days and I feel that it's appropriate to ask now.
I will make 2 parts to this thread, one will be a very fast explanation of what I did and the second part will be the same but a very thorough with a step by step process of what I messed up...
TL;DR: I was tired, late in the evening I flashed for some reason a Partition table of a Mi Note 3 on my Mi A1... I am now bricked and cannot access anything, fastboot, ADB, recovery nothing! I guess my phone is in EDL mode cause when I plug it in it flashes its led. "Qualcomm HS-USB QDLoader 9008" Is what I see in my device manager.
What do? oh, I forgot! I cannot access anything through any combination of buttons. I am stuck here, where I am!
The full thorough explanation for people who are bothered to read fully. (Includes my excuses for making noob mistakes, might be fun to read idk.)
Young me on a Sunday evening decides to reinstall magisk but this time with twrp cause I did it without twrp (yeah yeah I know). I was left without OTA's and after uninstalling anything that had something to do with Xposed or magisk I trashed it all. and stupid me thought that maybe? maybe? just maybe deleting Dalvik Cache would help me get my OTA's back after injecting my original ROM. This is where the fun begins.
I was not wanting to go through reinstalling magisk and all that to wipe the Dalvik Cache, I thought that that was my mission now, so I decided to search for methods that don't require root or being in the system, so some kind of fastboot or ADB command or something idk. I tried installing twrp and without my understanding that failed miserably and then I read some post where someone said that they flashed a mi note 3 partition table on their phone and something worked. Being the naïve little boii that I am, let's do that hey? Bam! bricked! I read somewhere I can open the phone and remove the battery and not having the tools is a mess, having to ask friends for some and voiding my warranty for something that probably won't work and after reading I understood that I'm in "EDL 9008 recovery" or something like that. I cannot boot into anything, I only have EDL 9008 to work with. I tried using Xiaomi's flasher tool and it would never respond to the initial hello packet (duuhh! I can't use ADB nor fastboot).
I know that this was stupid, I know! I learnt my lesson. If there is nothing we can do can I at least somehow get my internal storage data back? I deleted the backups from google drive for a short amount of time but randomly 5hrs prior to this sad story. All I have safe are now my contacts.
I hope you guys have some ideas! I feel like I'm fked but maybe with EDL 9008, there is a little glimmer of light?
P.S. If you guys somehow get me into fastboot I can flash a correct partition table back. My PC has all drivers so I can do this!
Sincerely, Micheal.
There is a way although i did tried it yet.
First of all sorry for my English.
Download latest MiFlash tool and qualcomm driver, this package contain both but not latest MiFlash so you should download lastest version from official site.
https://www.fshare.vn/file/H3R8M6OMRP2R
Download lastest stock rom.
You will need a good USB type C cable, dont use the one come with phone because you dont want to cut it in half.
Yes, that exactly what i said. Cut it in half, there are 4 small wire (or maybe 5 with type C?), remove it outer plastic and reconnect them.
Join the green and black cable, like you short circuit them, then plug your phone into PC with that cable without release green and black, wait for 5 sec then seperate them, the green and black.
Check device manager on your PC, you should hear device connect sound and qualcomm HS-USB QDLoader show up under Ports.
Open MiFlash and try to flash it.
You may want to check this video, although it in Vietnamese but you should understand the usb cable part.
https://www.youtube.com/watch?v=d5-1I9rWTiw
Hi, interesting situation. What about following this guide: http://en.miui.com/thread-235865-1-1.html ?
Its for some other phone, but try instaliing some drivers and you may get some signal of life.
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
m1shka said:
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
Click to expand...
Click to collapse
Yes, thats what I meant. Well, I dont know how to help you, wish you luck. I remember how I flashed wrong ROM for my S3 Mini and it was completly trashed, I'm glad that Xiaomi gives us at least some signs of life and hope.
And btw. I would rather charge the phone somehow - I hope it charges even in EDL mode, because if your phone dies while flashing with MiFlash, things can be even worse.
EDIT: I also found this guide, you can try it out: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
m1shka said:
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
Click to expand...
Click to collapse
Wish you luck:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
did you try to hold more than 30 second ? and also , do you have flash log ?
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
So did you flash official stock ROM? Because I dont understand why doesnt it work... btw. when you flashed the ROM, did you lock bootloader?
Cant be battery dead?
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
EDIT: Maybe consider locking bootloader? Try it if youre on official stock.
EDIT 2: By flashing that ROM I guess you lost all data, but you can try to boot in TWRP without installing it and browse in file manager to see, if there is any data.
TrueMS said:
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
Click to expand...
Click to collapse
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
m1shka said:
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
Click to expand...
Click to collapse
As I said, you can try it, but when I flashed my Nougat stock ROM, i lost all the data. Or you can boot into TWRP and connect with USB to your computer to see the data in phone.
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
GVN.Gallus said:
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
Click to expand...
Click to collapse
None of the passwords I used worked.. I just factory reset it, thanks alot everybody. And now I will be more careful, don't flash anything weird. And backup!
I understood why I can't get the data back, if android fails at the encryption it jsut deletes everything!
My fone also in 9008 please can you guide me
I did the same what you have and it's on 9008 my flashing is successful but still my fone is not opening help me
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
How did you fixed i'm stuck in EDL?
SevenSlevin said:
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
Click to expand...
Click to collapse
i am in Qualcomm HS-USB QDLoader 9008 but i can't flash, it doesn't matter if the phone is on fastboot mode or turned off (i can't even turn it on)
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.
Hello dear community,
I've been playing with my 6t for a long time, hundreds of custom roms, kernels, etc..
Lastly I went to official oxygen 10. I tried to install twrp via fastboot but every time I tried to push the files, I would get a error. I reinstalled drivers, tried different ports, different tools..
I got mad and blindly followed some article where someone suggested putting "persist" in the fastboot command, I tried it, I thought it is some kind of "force push" the file and that is how I probably corrupted persist partition. DUMB
Phone not booting of course and I went to restore it with Msmdownload tool.
It did not fixed it.
I tried different versions of msm, I tried going to Hydrogen, tried different USB ports, tried type C ports, different PCs...
No luck, phone is stuck at bootloop, with no TWRP and bootlocked.
I read somewhere that Msmdownload tool is not flashing persist partition and I assume that is the reason why my phone can't be restored.
Fastboot commands are not working anymore and EDL mode is probably the only possible way to communicate with the device.
I live in Montenegro and I can't send phone to oneplus to repair it.
I searched the threads and noticed that some users with similar problem eventually succeed to restore the phone by flashing it with Msm multiple times. I am still trying to do it but no luck.
I would really appreciate help from dev mastermind.
Thank you!
If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
But maybe i'm wrong and someone else know the sollution.
Deurklink73 said:
If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
Click to expand...
Click to collapse
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...
Papagaj said:
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...
Click to expand...
Click to collapse
You are correct. Msm tool will work on locked bootloader.
Man that sucks. Seems like you might be screwed. I screwed up a couple times getting to A10 but I was able to get msm tool to work for me. You are using it while your phone is powered off, correct?
Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool
GeekMcLeod said:
You are using it while your phone is powered off, correct?
Click to expand...
Click to collapse
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
jamescable said:
Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool
Click to expand...
Click to collapse
I tried several versions. I was hoping to find Android 10 tool for oneplus 6t but it is still not available.
Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead. Not saying that it would work for you but it might. In my case it was a Qualcomm tool. If you still end up with nothing but dead ends today, I'd initiate a chat with OnePlus on this page (select your country at the bottom of the page first).
Wrapped with delicious Fajita [emoji896]
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.
amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
Click to expand...
Click to collapse
@Papagaj do this....thats the only fix....I purposely wipe persist for to test something and I did that to recover from the boot loop.. persist store sensor information that vital to getting phone to boot....that's why it not booting..kernel is look for the sensor info but can't find it
Timmmmaaahh said:
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead.]
Click to expand...
Click to collapse
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
8.- If you have an IMEI backup, just follow this guide
Click to expand...
Click to collapse
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
GeekMcLeod said:
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.
Click to expand...
Click to collapse
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Papagaj said:
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Nope....just rewrite you IMEI with a Qualcomm tool..quite a few available
Papagaj said:
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Oh. The few times I used it I just powered off my phone and connected it to my computer. Started msm tool and it did its thing.
Papagaj said:
this A/B partitions really gave me headaches
Click to expand...
Click to collapse
You and me both! ? lol...
I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.
All right, here is the situation.
I finally managed to boot up the phone. amt911 gave working instructions on post #10. Thank you bro, you are awesome, and Thank you Tech_Savvy for confirming the method, you are badass who deletes partitions just for fun!
All right I got the phone booted up but as amt911 mentioned, I lost my IMEI numbers, without IMEI numbers you can't dial numbers, receive calls or use mobile data.
BACKUP IMEI NUMBERS FOLKS, you never know when the partitions will screw you over!
I was dumb one without backup and I had to contact Oneplus support for help. I was suprised how quickly I got into communications with one of the assistants.. in less than 10 seconds.
They ask you to do full reset via stock recovery and some other basic troubleshoots, after nothing, obviously, fix the missing IMEI they will arrange remote session to get your phone fixed.
You have to persist on remote session as some of assistants told me that I have to send the phone to repair.
Before they arrange session for you, you need to show them "proof of the purchase" ALSO KEEP THAT FOLKS I lost mine long time ago but luckily I found photo of invoice I took when I bought phone, phew*
I didnt have it at first when I contacted them and they say there is nothing they can do without a proof! DON'T STEAL PHONES FOLKS and then ask for support...
They will contact me for session within 48 hours and I will share the experience here.
Thank you again people!
JTVivian said:
I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.
Click to expand...
Click to collapse
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.
Papagaj said:
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.
Click to expand...
Click to collapse
Ah you're right, i wasn't sure if that was the case but i thought i'd throw out the suggestion anyways.
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