Hi Mates,
I have 1789-06 variant with unlocked bootloader.
I installed the pie version via flashall, all were OK.
but upon rebooting the splash screen prompted for "verity mode is set to disabled".
no matter what I tried, all failed - the phone reboots to the fastboot screen.
then I was wondering BP Tools mode where on the screen it was showing "disabled".
somehow I enabled and attempted to reboot - the screen went total black!
is there anything that can revive the phone?
thanks in advance for the support.
cheers.
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
41rw4lk said:
Connect to your pc and simply try holding the pwr btn for a minute to see if it will boot, if not, try holding vol dwn + pwr for a minute to see if that will boot it. Listen and look to see if your pc is detecting the phone at all while you try. Also you can check your device manager to see if it is showing there.
Click to expand...
Click to collapse
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
beefytr said:
thanks bro for the prompt response.
however, no connection, no booting, no sound of device connection to the PC.
what can be the next mate?
Click to expand...
Click to collapse
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
41rw4lk said:
Unfortunately, the black screen has been a bit of a fiasco with pie updates, especially for those who have tried pie on variants not intended for the firmware. No solution has been found yet, but I haven't heard of it happening by enabling bp tools. Connect to a 2.0 port and double check your device manager. Look for unknown devices, hs usb 9008, and try various button combos while trying to power and watch your device manager for new devices. In short you might be SOL, but if you're lucky and your pc recognizes the phone you might be able to blankflash.
Click to expand...
Click to collapse
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
beefytr said:
ok thanks.
actually, my phone was set to get the OTA.
the OTA s'mpy did not install without any reason saying "something went wrong".
anyways, the strange thing is that all happened after the BP tools thing.
I will see what I can do with USB 2.0.
this whole thing does not seem to be a brick, right?
Click to expand...
Click to collapse
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
41rw4lk said:
Actually it kind of does. On oreo, it seemed the worst that would happen is you would soft birck. Basically a black screen but the phone would connect to the pc as a 9008 device and you could blankflash your way back to good. Since pie, something is happening and the exact reason hasn't been pinpointed. Usually it's those who have tried to flash pie for a variant it wasn't intended for. Some have lost their baseband and are still waiting for a solution to that, and a couple have full on bricked. At least there hasn't been any sign of life nor a way to do anything about it. Granted the bp tools thing is weird, but maybe a dav will pick up on this and maybe understand just what is happening and what is causing it.
Click to expand...
Click to collapse
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
beefytr said:
we'll wait and see!
thanks.
by the way, how do you "blankflash"? just in case...
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
All the best mate.
Thanks.
41rw4lk said:
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
what if what you advise does not work at all?
then it is a dead one?
beefytr said:
what if what you advise does not work at all?
then it is a dead one?
Click to expand...
Click to collapse
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
41rw4lk said:
Yeah, the whole blankflash hinges on the fact that it is already in edl mode, but considering your circumstance, it is most likely dead like the few others. As of now there is no known way to revive them besides a jtag (untested and not confirmed) and you would need to tear your phone down to even try that, which isn't a viable option for most. Sorry I can't offer anything more.
Click to expand...
Click to collapse
thanks bro.
I will not bother for JTAG as it is - as you have rightfully said - untested.
my phone is still under warranty and I will try a replacement or a refund then.
cheers.
What did you do to boot your device.. Even mine is bootlooped.
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
What did you do to boot your device.. Even mine is bootlooped.
... Is it bootlooping or does it just not power on at all?
Related
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
souvenir1977 said:
Hi, I tried to flash 20b through twrp tonight.
I did factory reset, then flashed the bootstack, then flashed the system. But after that, my phone won't power on. I tried to remove the battery, holding power button for a long time, or power+volumn down.
The phone just does not respond at all. Can anybody help? Thanks!
Click to expand...
Click to collapse
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Still_living714 said:
take the battery out and put it back in and try to power it on. Repeat a few times, if that doesn't help we'll try other things.
Click to expand...
Click to collapse
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
souvenir1977 said:
Thank you Still_living714, I tried this multiple times, but it does not work. Anything else I can try?
Click to expand...
Click to collapse
have you tried putting it into download mode?
Still_living714 said:
have you tried putting it into download mode?
Click to expand...
Click to collapse
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
hmm very weird. I had a similar problem were the phone wouldn't boot unless I had it plugged into the charger or my computer,give that a try.
---------- Post added at 12:12 AM ---------- Previous post was at 12:10 AM ----------
souvenir1977 said:
If you are talking about holding volume button up and plug into computer, I tried that and the phone does not respond either...
Click to expand...
Click to collapse
when I had that problem I figured out that it was the battery that was making the phone act weird. Since LG sent me another battery when they had the promotion I used the other spare and that fixed it for me.
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
souvenir1977 said:
This happens right after I flashed the new system, I doubt it is the batter problem. If I plugged into the computer it still won't power on.
(If I remove the battery and plug into computer, the screen of the phone does show some symbol, probably regarding missing memory).
Let me try to see if I use kdz flash to reinstall the system. Thanks for the help.
Click to expand...
Click to collapse
well it's hard to say but without the phone being able to boot there's not anything you can do.....
you are right, flashing need the download mode....
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
jkjambo said:
You're getting adnroidserial xxxx in device manager when you connect it to pc?
i think you bricked phone
Click to expand...
Click to collapse
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
souvenir1977 said:
No it just shows regular LGE com port and I am not able to flash anything. You are right, it's hard bricked I am not sure what went wrong with my twrp flashing procedure though. Will contact with LG for repair.
Click to expand...
Click to collapse
that's what i mean , lge serial xxx , don't remeber exactly . it's in qhsusb mode , hardbricked ...
there is some indian guys who do that , some for free, some for little amount of money ...
search for lg g3 unbrick Qhsusb 9008... don't waste time on tutorials , non of them works with D851 ... i'm in same boat (again ) and tried everything .. nothing works , unless you're connected to lg servers directly , search for people which fixs them
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
jkjambo said:
http://forum.xda-developers.com/lg-...1-d855-qhsusbbulk-t3101435/page2#post60751870
here you go.
this guy helped me for free , you can contact with him
Click to expand...
Click to collapse
souvenir1977 said:
Thanks! Currently my phone is at LG service since it is still in warranty. I will definitely try that next time (knock on wood...)
Click to expand...
Click to collapse
This is why You don't flash the boot chain unless you absolutely must. I was running 20B with the old boot chain (other than rpm, that was updated) and it ran just fine. If you get a bad flash on the boot chain your sol.
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
Try hold power and volume down for like 30 seconds ,to try to get into bootloader
cwalker0906 said:
Try hold power and volume down for like 30 seconds ,to try to get into bootloader
Click to expand...
Click to collapse
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader
cwalker0906 said:
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader
Click to expand...
Click to collapse
i tried while pluged, how else would i recognize the sounds in windows. Hmm i really dont know if the pixel is on or off, so this could take weeks... is it hard to open it and unplug battery ?
Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...
molletit said:
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...
Click to expand...
Click to collapse
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
tried it, doesent make any difference, screen is still black, no flicker, nothing.
molletit said:
tried it, doesent make any difference, screen is still black, no flicker, nothing.
Click to expand...
Click to collapse
You might have to wait until the battery runs out to see if when it's plugged in to charge to see if anything happens!
I've never had an issue with a force reboot unless it's just a screen issue, which could be addressed with Google or whom you got it from
Sent from my Google Pixel XL using XDA Labs
Try it on a different PC. Worked for me, when I bricked my Nexus 6, the same Way you did. Hope it works.
If you tried to boot slot b without first flashing a bootloader to slot b then you're screwed. That's a legit brick.
molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.
then iam screwd, normally fastboot should install it on both slots, or iam wrong ?
its a hard brick, not softbrick because i cant load bootloader
the_rooter said:
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.
Click to expand...
Click to collapse
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
molletit said:
then iam screwd, normally fastboot should install it on both slots, or iam wrong ?
Click to expand...
Click to collapse
you would have had to flash Imgs to your non active slot and you didn't do that correct?
molletit said:
its a hard brick, not softbrick because i cant load bootloader
Click to expand...
Click to collapse
yeah it's a hard brick I know someone personally that did the same thing you did.
Tigerstown said:
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
you would have had to flash Imgs to your non active slot and you didn't do that correct?
yeah it's a hard brick I know someone personally that did the same thing you did.
Click to expand...
Click to collapse
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
I never heard of a soft brick being unfixable in my life period. I need to google it lol that's funny. Soft bricks are easy fixes. Why don't you fix it for him?
the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
Maybe you should read more carefully. Hes not getting sounds from the phone itself. The computer makes a sound when he plugs it in cuz it recognizes a USB charging device. The phone can still recieve power from the computer regardless of the bootloader. However because he has no bootloader on his active slot he's toast.
molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
It sounds like you may be booting into a low level Qualcomm boot mode. It is possible to recover with Qualcomm tools, but you would almost certianly need Google's specially signed versions.
Inorder to install OTA (not installed yet), i switched to slot B via booting TWRP, then i reboot but blank screen. Even not starting the botloader, not charging, Just its like a dead phone. Please Help ASAP!
smartybro7788 said:
Inorder to install OTA (not installed yet), i switched to slot B via booting TWRP, then i reboot but blank screen. Even not starting the botloader, not charging, Just its like a dead phone. Please Help ASAP!
Click to expand...
Click to collapse
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
fast69mopar said:
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
Click to expand...
Click to collapse
I'm having the same issue and for me and my PC doesn't detect my phone
fast69mopar said:
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
Click to expand...
Click to collapse
nope its just dead. If its even on i can do something but its just dead. I tear down phone and ejected battery on pure power source tried to switch it on again but no luck.
No detection by PC no notification sound. Now it is a device like of hardware without any softwares in it.
Marcowe said:
I'm having the same issue and for me and my PC doesn't detect my phone
Click to expand...
Click to collapse
Yup still waiting for some help!!!
Switching to another slot might solve the problem, but how to make it detect by pc.
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
41rw4lk said:
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
Click to expand...
Click to collapse
It is serious problem which is unsolvable till date, i already tried different combos while plugging to PC, but no luck.
But in my case it is due to blank slot for sure.
Still waiting for help!
As it could occur on another devices too, a solution should be invented, as of now we are not qualified but the senior experienced members could help to resolve the issue as this is the case of A/B empty slot switching.
smartybro7788 said:
It is serious problem which is unsolvable till date, i already tried different combos while plugging to PC, but no luck.
But in my case it is due to blank slot for sure.
Still waiting for help!
As it could occur on another devices too, a solution should be invented, as of now we are not qualified but the senior experienced members could help to resolve the issue as this is the case of A/B empty slot switching.
Click to expand...
Click to collapse
Anybody can help regarding how to force phone to enter into edl mode when phone is completely dead.
41rw4lk said:
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
Click to expand...
Click to collapse
Bro please can you provide me with emmc dump image file, i'm in dire need, thanks.
I was trying xiaomi.eu on my global alioth. the current version for global is 12.5.4 but the one on xiaomi.eu is 12.5.8
using fastboot to update my phone, after a few minute phone went to the black screen forever. I can't even go to fastboot or recovery anymore.
although it's only showing a black screen, have you tried plugging phone in and running cmd 'fastboot devices' to see if phone shows at all?
also, have you tried holding power down for a good 20-30secs to reset/reboot device?
EDIT: read too quick... xiaomi.eu, no miflash used...
reg66 said:
although it's only showing a black screen, have you tried plugging phone in and running cmd 'fastboot devices' to see if phone shows at all?
also, have you tried holding power down for a good 20-30secs to reset/reboot device?
EDIT: read too quick... xiaomi.eu, no miflash used...
Click to expand...
Click to collapse
I'm thinking he didn't try those things normally they would respond saying I tried all of that.
Techguy777 said:
I'm thinking he didn't try those things normally they would respond saying I tried all of that.
Click to expand...
Click to collapse
maybe, yeah. hopefully he/she is busy with a fix.
EDIT: actually, thinking about it, was your bootloader even unlocked? @keaheng
keaheng said:
I was trying xiaomi.eu on my global alioth. the current version for global is 12.5.4 but the one on xiaomi.eu is 12.5.8
using fastboot to update my phone, after a few minute phone went to the black screen forever. I can't even go to fastboot or recovery anymore.
Click to expand...
Click to collapse
Sorry to tell u this but mobo died bro. I have the same problem 3 month ago and when i send my device to guarranty, he tell me mobo died....
X0PIRAT3 said:
Sorry to tell u this but mobo died bro. I have the same problem 3 month ago and when i send my device to guarranty, he tell me mobo died....
Click to expand...
Click to collapse
I bet you anything you and him had something go wrong with your PC. I restart my PC right before I flash anything and I close all application's and stop everything. While it flashes I don't touch my computer at all. I would assume that you guys might play on your PC while it's trying to flash thinking it's fine. Also you should use data cable or cable that came with it. Cheap cables are junk that's why they are cheap.
There is option to try EDL testpoint method when your phone is totally dead. It means you open your phone, connect testpoints and your phone would be visible for pc in device manager as qc9008 port.
Next step- you cant flash the rom by yourself, it requires authentication. There are "helpers" for that. I found one in Telegram and it took about 20usd and 20 minutes to boot the phone from dead brick (MI9T davinci).
ptr21 said:
There is option to try EDL testpoint method when your phone is totally dead. It means you open your phone, connect testpoints and your phone would be visible for pc in device manager as qc9008 port.
Next step- you cant flash the rom by yourself, it requires authentication. There are "helpers" for that. I found one in Telegram and it took about 20usd and 20 minutes to boot the phone from dead brick (MI9T davinci).
Click to expand...
Click to collapse
If that's true that's awesome. How do you find these helpers? Do you have a link? I don't even know what EDL is I am wondering if it ever happens to me
Cant remember anymore where I found it, so many keywords were Google'd. Maybe it was some russian content. Im pretty sure I cant post telegram link here so if someone wants it, I would PM.
Hi thank you guys for the concern. Phone has been fixed. There is a remote service guy who helped me by using TeamViewer. If you guy out there who has the similar problem, you can go on YouTube and search "Xiaomi qc9008"
Techguy777 said:
I bet you anything you and him had something go wrong with your PC. I restart my PC right before I flash anything and I close all application's and stop everything. While it flashes I don't touch my computer at all. I would assume that you guys might play on your PC while it's trying to flash thinking it's fine. Also you should use data cable or cable that came with it. Cheap cables are junk that's why they are cheap.
Click to expand...
Click to collapse
Working in IT for years, and all I can say if it would be true, we would have serious issues. It's not like windows 98 anymore, you can actually use your computer as a multitasking device. Like there aren't like 10000 processes without playing games. It's always easier to blame them, for doing "wrong" things while flashing. The only "wrong" thing you can do while flashing is pressing cancel or the reset button.