Related
So I've now got a bricked Desire Z and have had to go back to my reliable and fairly beaten up old G1 again.
The ROM it was running was Virtuous Unity 2.39.0 with a particular kernal that allowed me to record phone calls.
What was I attempting before it became a massive paperweight? A ROM backup via ClockworkMod Touch.
What does it do now? Absolutely nothing! When I plug it into an AC charger or the USB cable it gives absolutely no sign of life, trying a different battery makes no difference as the two I've tried, work in a dusty old faulty Desire Z.
I can no longer reach the bootloader.
Any ideas would be appreciated.
Plug it in with the phone off and turn the phone on while holding the volume down button it will go into fastboot mode.
From there you will have fastboot access and select recovery if it does not work then flash a new recovery by doing the following
1) Download the correct clockwork mod recovery image (should be something like recovery.img) I believe there is one on the first page of the development section which supports touch.
2) while on fastboot (first sentence of this post), type the following
fastboot flash recovery c:\recovery.img
where recovery.img is the location of your recovery, you will need to be inside of the android sdk tools directory where adb and fastboot commands are located.
A_Elizondo said:
Plug it in with the phone off and turn the phone on while holding the volume down button it will go into fastboot mode.
Click to expand...
Click to collapse
There's a massive problem with your solution. It won't turn on AT ALL thus making said solution useless.
When plugged into either an AC adapter or a USB cable connected to the PC it gives zero sign of life.
As useless as the solution itself was in this instance, I've never actually used ADB to flash a recovery image before so it was still a little helpful.
Any other ideas?
Bricked - sounds like it may be only revived by flashing it via JTAG hardware interface. See if you find one around that is capable of this..
Mike
MIkeRD03 said:
Bricked - sounds like it may be only revived by flashing it via JTAG hardware interface. See if you find one around that is capable of this..
Mike
Click to expand...
Click to collapse
I'll leave the JTAG flashing up to the boys and girls at HTC since I'm not confident enough with a solder gun to attack it myself, even if no solder gun is necessary I still may have difficulty remembering what screws went where whilst re-assembling it.
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..
So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?
randhackr said:
So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?
Click to expand...
Click to collapse
I don't know about it.
michal383 said:
I don't know about it.
Click to expand...
Click to collapse
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.
randhackr said:
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.
Click to expand...
Click to collapse
Yes Warranty falls if the bootloader unlocked. Test Point could help.
Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.
Schlengge said:
Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.
Click to expand...
Click to collapse
Well since it broke after I flashed b160 firmware I am most likely SOL. Since I had twrp flashed they will find out that it was modified..
My advice is not to mess with fastboot mode. Flash twrp and be careful with what you flash.
Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Potato997 said:
Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yup. It's completely dead. No fastboot mode, no recovery or erecovery. It simply does not turn on (or enumerate in a computer either).
If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install
LiaquateRahiman said:
If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install
Click to expand...
Click to collapse
He can't enter in recovery or fastboot.
Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Have you tried to enter fastboot or recovery solely using the button combos? or did you try using adb as well? It's possible your battery deep-discharged, or your power adapter/connectors are faulty.
Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.
randhackr said:
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.
Click to expand...
Click to collapse
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!
LiaquateRahiman said:
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!
Click to expand...
Click to collapse
That is for samsung phones. I gave on trying to fix the phone. Next week I'm going to send it to a phone repair shop and see what they can do.
Edit: The phone repair guy says that the only way it can be repaired is by replacing the emmc or replacing the motherboard. So for now the phone will sit in the drawer until I manage to get a new board.
Hello
I had the same problem with my honor 7, the only solution is to replace the motherboard :/
If the phone is completely dead, warranty will accept it just because they will change your motherboard if they can't turn it on. I had the same problem last week, probably an hardware fail, I gave it to them saying that the phone simply turned off and they changed the whole motherboard (bootloader unlocked, twrp and root).
Well I tried sending it to the repair center. Two days later they replaced the whole phone, they said that there was an issue with the power ic.
B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?
ivanwong1989 said:
B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?
Click to expand...
Click to collapse
I'm starting to think so, I've flashed the replacement and it didn't brick. May or may not be related to the headers, but I don't want to be creative right now since I need the phone lol.
What is b160 can you explain
Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.
Ouh....DFU? I think this thing is totally bricked.
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...
twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.
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