Moto Z2 Force wont turn on after switching to slot B, not even bootloader - Moto Z2 Force Questions & Answers

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.

Related

[Q] Bricked Galaxy Nexus

Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.

[Q] Cannot Restore G3 To Stock Using Flash Tool

I tried to use a volume fix by changing the values in some system files on my rooted G3, rebooted and got stuck at the LG Bootlogo. Been trying lots of things, finally used this thread: http://forum.xda-developers.com/showthread.php?t=2799647 but the flash tool fails at 14 seconds saying failure to enter download mode. I have a D851C on T-Mobile, it is in download mode when I run the program and no change occurs on the screen save for the text log at the bottom. Upon booting into DL mode, it says USER B94. After unplugging and plugging it back in to start the unroot it changes to USER S0.0 AS0.0 B94 UHS then on the next line S U LG-D851 04.4.2 Hrev_10 and the next D85110c. It takes a good 50 seconds for the flash tool to change from saying awaiting connection, and then at 14 seconds it looks like the photo. The names of the dll and tot I am using are, respectively:
LGD851_20140611_LGFLASHv160
LGD851AT-01-V10c-310-260-JUN-20-2014+0
Yes I have set the port to 41 in device manager.
What the heck is wrong?
Someone please help I was supposed to fly out of state today but now I don't think I can without a phone and I can't afford a new one, I'm a student
Did you put your phone in download mode? It's not broken you just need to successfully flash it. It says download mode failed so here's a simple way to enable it if you ate having trouble. Pull out the battery then hold volume down and put it back it and plug in the cable. This should be done in a relatively fast manner to enable it if you are having issues getting into download mode.
Edit I know you said you put it in DL mode but I had a similar issue with my F400S so its worth a try.
Pilz said:
Did you put your phone in download mode? It's not broken you just need to successfully flash it. It says download mode failed so here's a simple way to enable it if you ate having trouble. Pull out the battery then hold volume down and put it back it and plug in the cable. This should be done in a relatively fast manner to enable it if you are having issues getting into download mode.
Edit I know you said you put it in DL mode but I had a similar issue with my F400S so its worth a try.
Click to expand...
Click to collapse
I tried it, same error at 14 seconds. Tried taking the battery out after the yellow ready button comes up to and doing it that way, nada
Did you try using LG PC Suite --> Tools --> Fix Upgrade Problems?
The steps can have different names (didn't remember the names) but something like that, worked for me when I messed up my system
kvanzuijlen said:
Did you try using LG PC Suite --> Tools --> Fix Upgrade Problems?
The steps can have different names (didn't remember the names) but something like that, worked for me when I messed up my system
Click to expand...
Click to collapse
LG PC Suite didn't recognize it before, does it need to be in download mode when I do that? Or is there another recovery mode?
*EDIT* Just discovered this log, maybe someone's familiar with the codes and has an idea what to do
Bump please help I don't want to use a warranty claim
Bump
DrPhill94 said:
Bump
Click to expand...
Click to collapse
I may have found the solution for another member, but it is untested from me, as I am at work at the moment. In flashtool did you change the action mode? if not try changing the action mode to board dl instead of what its set to. Let me know, because I got the same issue right now.
joeyhdownsouth said:
I may have found the solution for another member, but it is untested from me, as I am at work at the moment. In flashtool did you change the action mode? if not try changing the action mode to board dl instead of what its set to. Let me know, because I got the same issue right now.
Click to expand...
Click to collapse
Tried it a few times, no luck so far. Same error same time
DrPhill94 said:
Tried it a few times, no luck so far. Same error same time
Click to expand...
Click to collapse
damn, I'm on Sprint variant, only thing I haven't tried is lg suite and making sure my Flashtool is the latest version. I've tried everything else last night for 6 hours.
edit: my dl mode is working perfect. I see in your Flashtool, your error is slightly different. mine gets stuck at 93%. Then it reboots back to this
DrPhill94 said:
LG PC Suite didn't recognize it before, does it need to be in download mode when I do that? Or is there another recovery mode?
*EDIT* Just discovered this log, maybe someone's familiar with the codes and has an idea what to do
Click to expand...
Click to collapse
PC Suite won't recognize it if you don't use the correct version. The latest from LG's site is in fact the wrong version. You need the version that's about 223mb in size. Sorry, I'm not sure of the version and am currently busy fixing my phone with it, so can't check. Perhaps someone would kindly supply you with a download link.
Beylie said:
PC Suite won't recognize it if you don't use the correct version. The latest from LG's site is in fact the wrong version. You need the version that's about 223mb in size. Sorry, I'm not sure of the version and am currently busy fixing my phone with it, so can't check. Perhaps someone would kindly supply you with a download link.
Click to expand...
Click to collapse
Will it work even if my phone doesn't show up in explorer? My pc makes a sound when it is plugged in and unplugged in Download Mode but the only thing so far to recognize it is flash tool. If you can check the version please let me know but I'll look for it
Did you try a different USB port on your computer? Drivers get honked up easily using flashing tools and sometimes using a different port, or even a different USB cable can fix your problem. More likely another usb port, but I've also had a bad cable as well.
Ozark_8125 said:
Did you try a different USB port on your computer? Drivers get honked up easily using flashing tools and sometimes using a different port, or even a different USB cable can fix your problem. More likely another usb port, but I've also had a bad cable as well.
Click to expand...
Click to collapse
That's the problem is the only cable that works is the one that came with it, and I've used 3 of my 4 on my laptop, so I doubt it's the port
Ozark_8125 said:
Did you try a different USB port on your computer? Drivers get honked up easily using flashing tools and sometimes using a different port, or even a different USB cable can fix your problem. More likely another usb port, but I've also had a bad cable as well.
Click to expand...
Click to collapse
Also you have to realize the phone doesn't turn on. I get the LG logo, download mode, or factory reset. That's it
If that is the only cable that works - my guess is there's something probably wrong with the micro usb jack on your phone.. it shouldn't be that finicky where only 1 of 4 cables would work. If you do a warranty return, you might get lucky anyways. Several folks have posted on XDA that the stores where they returned phones were either clueless or didn't care about the status of the root code. Of course, YMMV.
Ozark_8125 said:
If that is the only cable that works - my guess is there's something probably wrong with the micro usb jack on your phone.. it shouldn't be that finicky where only 1 of 4 cables would work. If you do a warranty return, you might get lucky anyways. Several folks have posted on XDA that the stores where they returned phones were either clueless or didn't care about the status of the root code. Of course, YMMV.
Click to expand...
Click to collapse
You misunderstand: The cable that comes with the G3 is the only one GUARANTEED to work with these operations. Has nothing to do with the jack. Getting a new one in the mail tomorrow, can't tell if it's rooted if they can't access the filesystem

Twrp issue and can't even turn on phone

my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
LumberjackZac said:
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
Click to expand...
Click to collapse
Can you still boot into TWRP?
dhplap said:
Can you still boot into TWRP?
Click to expand...
Click to collapse
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
LumberjackZac said:
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
Click to expand...
Click to collapse
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
That is awesome. Been looking at Note 4's on ebay because.... not looking good
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
Hey buddy. I've been reading that qhsusb_bulk is a hard brick, possible fried bootloader. But I guess if you can make this unbrick.img on to a sdcard it may work. I'm scratching my head on what files go into this unbrick.img and if I can make it myself. Any ideas

Pie boot screen "verify mode is set to disabled"

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?

Question hardk brick. no fastboot. no recovery.

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.

Categories

Resources