Related
Hello
My Nexus 6 is now in Qualcomm HS-USB QDLoader 9008 mode.
Here is the story:
1. I did Sideload OTA Update from 5.0.1 to 5.1
2. After few hours decided to jump to Cyanogenmod latest nightly (20150311)
3. I downloaded ZIP and Gapps.
4. Did Factory Reset with TWRP
5. Installed CM12 and Gapps
6. Pressed reboot, black screen and.... nothing happend. My Nexus doesn't start at all.
I can't boot into Recovery or Download Mode.
I'm unlocked.
Can anybody help me?
flash the stock img and see if that helps.
Thats what I would do....
t2noob said:
flash the stock img and see if that helps.
Thats what I would do....
Click to expand...
Click to collapse
How can I do that if I can't boot into Download Mode or Recovery?
maturb said:
Hello
My Nexus 6 is now in Qualcomm HS-USB QDLoader 9008 mode.
Here is the story:
1. I did Sideload OTA Update from 5.0.1 to 5.1
2. After few hours decided to jump to Cyanogenmod latest nightly (20150311)
3. I downloaded ZIP and Gapps.
4. Did Factory Reset with TWRP
5. Installed CM12 and Gapps
6. Pressed reboot, black screen and.... nothing happend. My Nexus doesn't start at all.
I can't boot into Recovery or Download Mode.
I'm unlocked.
Can anybody help me?
Click to expand...
Click to collapse
I'm in exactly the same situation but with QHSUSB_BULK, dis exactly what you did
maturb said:
How can I do that if I can't boot into Download Mode or Recovery?
Click to expand...
Click to collapse
First ensure that it's fully charged then retry.
Otherwise, sounds like you've created a dead brick of a nexus. Something similar happened to my N4 so I returned it to Google for a free replacement. RMA time.
ben_pyett said:
First ensure that it's fully charged then retry.
Otherwise, sounds like you've created a dead brick of a nexus. Something similar happened to my N4 so I returned it to Google for a free replacement. RMA time.
Click to expand...
Click to collapse
On mine cant even tell if it's charging. Feel cool to the touch so I'm guessing not
Stuck in the same boat. dammit dammit
coldconfession13 said:
Stuck in the same boat. dammit dammit
Click to expand...
Click to collapse
If we could get a .mbm file for the nexus 6 and drivers for qhsusb_bulk we should be aboule to use QPST to save our phones. Can't find them bloody anywhere though
I called motorola and got an RMA. I had to overnight my device so they can send the new device back to me faster. It's amazing they knew my imei without me knowing it. Creepy lol. So I guess we are screwed. I'm just mad now I lost all my files.
coldconfession13 said:
I called motorola and got an RMA. I had to overnight my device so they can send the new device back to me faster. It's amazing they knew my imei without me knowing it. Creepy lol. So I guess we are screwed. I'm just mad now I lost all my files.
Click to expand...
Click to collapse
I'm having to wait until tomorrow to phone motorola in the uk and then get it set to them. Or if it'll be quicker I'll send back to my carrier.
I'm going through something similar with a friend's Nexus 7. It crashed a few nights ago, and stuck on splash animation while booting. He left it there all night, and it ended up just running its battery down flat.
I plugged it in the next day, and it did the same thing being stuck on spash ani. Hard-powered it off, and absolutely no sign of life since.
The only promising thing is that it shows up as Qualcomm HS-USB QDLoader 9008 in device manager, and QPST picks it up in download mode. It looks like it can be flashed back with QPST, but we're gonna need the hex files for QPST.
If anyone knows how to put a working Nexus in diag mode, the eMMC contents can probably be exported in hex format and flashed to a bricked Nexus. If anyone knows how to do this, please lend your advice.
Please try this! Plug your phone into your or a friend's computer that is running linux. After this, run `sudo ls /dev/` if you see an SDX device with a bunch of numbers after it, there may still be hope. The qhusb download mode sometimes manifests itself in linux as a block device allowing you to dd the bootloader from the 5.1 tar. After that you should be able to install the 5.0 images and go back to CM.
Let me know if you actually can see the device blocks in linux
Sounds like this particular issue had been caused by a rogue CM nightly, which I understand was taken down, there are stories all over xda with people suffering dead devices
Sent from my Nexus 6 using Tapatalk
Here is what I think is happening, and only happening with CM
CM started implementing the bootloader and even radio? in their zips sometime during the kit kat era; to keep things consistent for each user. That way CM knew what bootloader was being used to avoid bug reports due to an old bootloader. As you cannot down grade your bootloader, when CM is flashing the bootloader that is where the issue lies.
simonsickle said:
Please try this! Plug your phone into your or a friend's computer that is running linux. After this, run `sudo ls /dev/` if you see an SDX device with a bunch of numbers after it, there may still be hope. The qhusb download mode sometimes manifests itself in linux as a block device allowing you to dd the bootloader from the 5.1 tar. After that you should be able to install the 5.0 images and go back to CM.
Let me know if you actually can see the device blocks in linux
Click to expand...
Click to collapse
no SDX
Hi everyone,
I have bricked nexus 6. It has a locked bootloader plus no bootloader, no recovery, no system no nothing.. If i boot up the phone it goes into bootloader kind of thing and pc can recognize it as a fastboot device but since it has locked and corrupt bootloader there is no command i could get it to run anything.
I know most of you think its simple bricked and cant work it again but refuse to believe that just because the simple fact that i couldnt get any answers from anyone relavent to this. I have been using android for years, basically from the beginning, i know i am not a developer but i think i know few things and i been in similar situations before but this is the first time i got stuck. I know it can be done since its a qualcomm device. There should be a way to put the device in edl mode flash with qfil or something. I know all the post about these kind issues i read them all. Whenever somebody asks about how to put it in edl mode the answer is always go check that post about how to recover from edl mode. Please understand i need to put it in edl mode first to get it out of there.
So if anyone knows a way to put this device in edl mode please help so i can try to recover from there..
I already tried modified fastboot so it can run "fastboot reboot-edl command" it doesnt work for me.
I also tried a custom cable for triggering edl mode on xiaomi devices. But it doesnt work either.
The only other way i know is the short test points on the board or on the chips legs itself.
Like i said there may be no way because the lack of information out there if it is please say so so i can rest
Thank you for your time patience.
The best I can do is point you to [FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1
If memory serves, there was a point when the adb reboot edl was patched in an upgrade. That was rather late in the device's supported lifetime. Maybe when Pie came out?
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan
TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm
TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.
I have managed to brick my Mi 8, I think due to trying to flash a Chinese rom but not sure exactly what I did, I had ultimately been trying to install LineageOS.
The phone will only go into a bootloop with the Mi symbol showing, I cannot get it into recovery or bootloader by holding the buttons as normal. I have taken the back off and I think managed to get it into EDL mode by shorting the pins as I can get it to show up in MiFlash.
However where do I go from here? I cannot use Miflash because it says my account is not authorised, and I have not been able to find a hacked elf file for this phone. I have found a supposed hacked version of Miflash that bypasses the authentication however this just comes up with a load of different errors when trying to flash with this so no progress there either.
I feel like I have run out of options. Is there anything else I cant try or is this phone a goner?
I ended up using a paid service on Telegram where a person with a subscription to some flashing software was able to flash my phone with a ROM from EDL mode using Teamviewer, so all good now and phone is working again. If taking this route be wary of who you use for this as I am sure there are some scams out there.
I was trying to flash a new rom and accidentally hit "boot to fastboot" in the pixel experience recovery
now when i try to boot it goes black and i cant get back into recovery at all
when i put it into fastboot it isn't detected by my computer.... am i screwed?
Worst case just blank flash
Arealhooman said:
Worst case just blank flash
Click to expand...
Click to collapse
How do i do that?
Download Mi Flash Tool and flash Stock.
JingleDraws said:
I was trying to flash a new rom and accidentally hit "boot to fastboot"....
Click to expand...
Click to collapse
Have you tried a very, very long press on power to start up?
Had you flashed already that new rom and pressed then boot to fastboot instead of boot to recovery?
Elinx said:
Have you tried a very, very long press on power to start up?
Click to expand...
Click to collapse
Hey @Elinx you try to help everyone. I like that
Laptapper said:
....you try to help everyone....
Click to expand...
Click to collapse
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Elinx said:
I try , like you do too, but sometimes I forgot my crystal ball to understand the question.
Click to expand...
Click to collapse
Yep....me too....but new members have a child protection
This just happened to me on the same recovery. I cleared my storage/cache ect then clicked boot to fastboot to flash a new recovery this then led to me just having a black screen.
Also mi flash seems to require fastboot in which my device is not showing.
Also thanks for any help anyone gives
WeeScottishMan said:
.... just having a black screen.
...
Click to expand...
Click to collapse
A black screen does mostly mean that the phone is started in EDL mode.
That is why I advice first to try a very long press on power.
You could check this inside device manager on PC, with or without the right USB drivers.
(Qualcomm HS-USB QDLoader 9008)
Flashing from EDL isn't possible without Mi authorisation as long there isn't a hacked firehose file.
Holding power seems to just be turning it off and on again. Also I cannot seem to find the phone on device manager although it plays the connection sound and refreshes when plugged in and turned on. Do you know where I would find it in device manager.
Thanks again for the help
oh wait yes it is in edl mode does that mean I am massively screwed :<
Thanks again.
WeeScottishMan said:
... yes it is in edl mode does that mean I am massively screwed....
Click to expand...
Click to collapse
If the phone does start black again after very long press.
Yes, you are screwed up with EDL and you need to go to a Mi service center, or try an "online unbrick service" with Teamviewer from a third party.
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
WeeScottishMan said:
I'll seek out an online unbrick service if I can since I do not live near any mi service centers.
I did suspect it might be EDL but I am glad I now know it is.
Thank you so much for helping and also for the amazingly quick responses I hope this helps out the guy who posted this thread.
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
I don't find the reason, in any of your posts, why it would be bricked. If your device is not really bricked, then to get it out, you have to press the three buttons at the same time for about 9 seconds, while you see the changes in device manager PC, so you can see in which mode it is. Eventually in the booting process, change the hardware buttons as if you will send it to fastboot or recovery mode, it doesn't matter the display is showing nothing, just check the device manager to have an idea.
Thanks for your suggestion.
I tried that yet it still shows the Qualcomm HS-USB QDLoader 9008 (COM3). I am also a bit confused why it has bricked since I really didn't think I had done anything wrong :/
mine appears in device manager, is that a good sign? what do i do from here
WeeScottishMan said:
I'll post an update if I get it fixed, I won't give up that easily
Click to expand...
Click to collapse
if you do get it fixed please let me know what they did so i can do it as well! thank you and good luck!! ...at least this isn't my main phone..
Be sure to try all the methods to get it in other modes, it's just a timing thing, while device goes from a state to another, then you should try one time to enter to fastboot, and in a new cycle reboot, try to enter to recovery mode, BUT If the device, can't definitely enter to recovery nor fastboot mode, and it always redirects to Qualcomm HS-USB QDloader 9008 (apart than shutting down), then it's bricked.
EDL mode, using MiFlash tool requires a Mi authorized account, just older devices can use it for free, this is not the case, unfortunately.
Instead, you can try with other Qualcomm flasher tool, like QPST, not sure if it still works for this device (for older it does), you should give it a try.
@SubwayChamp is right about that.
There is a difference if EDL came out of the box or after an attempt to update or other flashing attempt.
That is why to try all possibilities to get into fastboot or recovery.
So try Vol up+ Vol down+power, Vol up+power, Vol down+power and only power always first to see if you can get out of EDL.
You can try QPST too, but search for some HowTo with pictures, because it isn't the same as Miflash and is a bit complicated if you never used it.
There still isn't a modded firehose file (prog_ufs_firehose_sm7150_ddr.elf) for RN10P to pass Mi authorization, but there is a very small chance that QPST does work.