Related
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?
C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird
zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon
well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
I'm right there with you. Literally did the exact same thing. I'm stuck in DFU mode on my 2017U.
UnsecWifi said:
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
Click to expand...
Click to collapse
Use this thead https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
And remember NOT USE ZADIG DRIVER FOR MIFLASH, use the driver from the thead.
Tell me if it work
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
use another computer have windows 7 32 bit(try use windows 10 32 bit)
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
If it sees it you should be alright, just close the MiFlash, or even better reboot your computer. Then try to reset ur axon by holding power button and then when it fails enter EDL again using the combo.
The MiFlash works best on a freshly booted EDL where u did not attempt and fail to flash stuff before. So always reboot the EDL fresh before using the tool.
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory::laugh::victory: Awesome. Thanks to everyone.
UnsecWifi said:
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory:[emoji23]:victory: Awesome. Thanks to everyone.
Click to expand...
Click to collapse
Did it work on win 10 or 7?
Also what drivers did you have installed? I'm afraid mine is a lost cause
Did it on my desktop with Win7. Used qualcom bulk drivers. And the only file to work for me was B15-NEW_FULL (Nougat). Unpack it and select the A2017U_B15-New_twrp_edl folder, refresh so you see your COM port and flash it.
If it doesnt work try going back into EDL mode, closing and reopening the MiFlash utility, switch USB ports etc. And use the cable that came with your phone. Make sure to charge it first with the original charger.
I have tried to upgrade my Xiaomi to Android 8.1 through flashing. I rebooted the device after fastboot. Now every time i hold the power button it vibrates like a heartbeat and stops when i let go of power button. When it is plugged in with the cable it doesn't stop vibrating (like a heartbeat). I don't know what is going on, hard bricked?? Is there a way I can fix this. Thank you...
I have the same problem after a flash with Miflash Plug in USB in phone keeps the phone vibrating but don't start up. Put the phone in EDL mode by test point method stops vibration.
daveve said:
I have the same problem after a flash with Miflash Plug in USB in phone keeps the phone vibrating but don't start up. Put the phone in EDL mode by test point method stops vibration.
Click to expand...
Click to collapse
If I can get the phone taken apart I could something but the thing is a pain to take apart. It is very difficult for me.
Check my posts
kendziorix said:
Check my posts
Click to expand...
Click to collapse
That don't solve it for me. The vibrating stopped but phone don't boot up. Only what I got is white blinking led.
daveve said:
That don't solve it for me. The vibrating stopped but phone don't boot up. Only what I got is white blinking led.
Click to expand...
Click to collapse
Actually got the phone booted up to TWRP recovery and fast boot but cant get a ROM that actually works for it. Would be nice if anyone made a backup of their rom and sent it to me then i can save my Xiaomi
daveve said:
That don't solve it for me. The vibrating stopped but phone don't boot up. Only what I got is white blinking led.
Click to expand...
Click to collapse
White blinking LED = EDL mode. You can flash in MiFlash in this, with the right driver.
Check my thread, something called "Mi A1 Low-Level Backup Tool" or similar (i'm on phone) for details about EDL mode.
Just flash stock ROM in EDL mode, if it doesn't fix it then you have some serious issues (like damaged hardware).
CosmicDan said:
White blinking LED = EDL mode. You can flash in MiFlash in this, with the right driver.
Check my thread, something called "Mi A1 Low-Level Backup Tool" or similar (i'm on phone) for details about EDL mode.
Just flash stock ROM in EDL mode, if it doesn't fix it then you have some serious issues (like damaged hardware).
Click to expand...
Click to collapse
Tried multiple roms and all of them didn't work. Always got system has been destoryed after every flash
CosmicDan said:
White blinking LED = EDL mode. You can flash in MiFlash in this, with the right driver.
Check my thread, something called "Mi A1 Low-Level Backup Tool" or similar (i'm on phone) for details about EDL mode.
Just flash stock ROM in EDL mode, if it doesn't fix it then you have some serious issues (like damaged hardware).
Click to expand...
Click to collapse
@CosmicDan I know that white blinking led is EDL mode but for me it is something different.
I put my phone in EDL mode by test point method and the phone got recognized as USB 9008 or something like that. Than I open Miflash and my phone got successful flashed with stock rom. but after that it don't start up but only thing I see is white blinking led when I connect it to a charger.
daveve said:
@CosmicDan I know that white blinking led is EDL mode but for me it is something different.
I put my phone in EDL mode by test point method and the phone got recognized as USB 9008 or something like that. Than I open Miflash and my phone got successful flashed with stock rom. but after that it don't start up but only thing I see is white blinking led when I connect it to a charger.
Click to expand...
Click to collapse
So something else is broken then, something the stock firmware doesn't flash. Dunno sorry, could be hardware issue for all I know.
CosmicDan said:
So something else is broken then, something the stock firmware doesn't flash. Dunno sorry, could be hardware issue for all I know.
Click to expand...
Click to collapse
Oké thx I think I have to send him to a service center
Can anyone backup a rom of mi a1 using twrp? Then I could fix my Xiaomi
Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
There's this tool for the Redmi Note 4 that can get your phone recognized by MiFlash if you can get into Fastboot. Is there something like this for the Axon 7? I couldn't find anything.
https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Penoro123 said:
Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
Click to expand...
Click to collapse
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Oki said:
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Click to expand...
Click to collapse
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
I'll try this and I'll try using a deep flash cable.
There's a guy that went through the very same thing and was able to get it working again using an homemade cable.
https://www.reddit.com/r/Axon7/comments/9hc9gu/your_device_is_corrupt_it_cant_be_trusted_and_may/
Penoro123 said:
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
Click to expand...
Click to collapse
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
Thank you, Oki. I'll surely try tomorrow and post again if that one or any method works for me.
You can try enter the FTM mode: https://forum.xda-developers.com/showpost.php?p=69604257&postcount=7
It worked for me when I did the same like you. I also had the universal bootstack linked in the OP of the LOS15.1 and flashed a wrong recovery.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Penoro123 said:
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Click to expand...
Click to collapse
Nice. So just to confirm, you have a G model and the wire trick worked?
tdm said:
Nice. So just to confirm, you have a G model and the wire trick worked?
Click to expand...
Click to collapse
Yeah, it did, but now I can't even get into fastboot to shut down the phone or let it discharge. It boots into MiFlavor, then the screen goes black but it's still on.
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Penoro123 said:
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Click to expand...
Click to collapse
Bro please put the all the details briefly here so that everyone can learn and save their device from brick
I know how QHSUSB_BULK is used because I had a brick but what happened with my cell phone is that when I flashed it I stopped recognizing it. uninstall everything to start again and when I connected my cellphone, QHSUSB_BULK did not appear anymore. I think I install a rom that is not.
When QHSUSB_BULK did not appear, my computer recognized as UNKNOW DEVICE. but when installing the drivers I only recognized the Qualcomm HSUSB QDLoader 9008. because the android is still in UNKNOWN DEVICE. USB \ UNKNOW USB \ VID_0000 & PID_0000.
There is no recovery, no FTM, no load, no turn on.
I can not switch to EDL mode
Start Sending Programmer
Download Fail: Unable to download Flash Programmer using Sahara Protocol
Download Fail: Sahara FailSahara Fail
Finish Download
I can not flash again,
Would the emmc be damaged or did it lose its format?
Excuse my english, I'm using google.
Sorry about that, what's your Compilation number?
nvizync said:
Sorry about that, what's your Compilation number?
Click to expand...
Click to collapse
V1.0.0B13 BBversion Z835H01
isaac ballesteros said:
V1.0.0B13 BBversion Z835H01
Click to expand...
Click to collapse
Ok, you need to charge your device, at least 70%, even if no logo, sign of life, or whatsoever is need to be showed, then remove the battery, wait at least 5 or 10 minutes, put the battery back and inmediatly connect the usb cable holding vol down, so that way, you gonna force your phone to boot into FTM mode, don't be scared, that happened to me also, trying to flash a V1.0.0B13 with V2.0.0B10, and with this way i successfully make my phone come back to life again.
nvizync said:
Ok, you need to charge your device, at least 70%, even if no logo, sign of life, or whatsoever is need to be showed, then remove the battery, wait at least 5 or 10 minutes, put the battery back and inmediatly connect the usb cable holding vol down, so that way, you gonna force your phone to boot into FTM mode, don't be scared, that happened to me also, trying to flash a V1.0.0B13 with V2.0.0B10, and with this way i successfully make my phone come back to life again.
Click to expand...
Click to collapse
No charge, no FMT but i will try it.
isaac ballesteros said:
No charge, no FMT but i will try it.
Click to expand...
Click to collapse
I know, it can be scary but try, even if it's all black
i have blank screen too how to fix?