Hi guys,
I want to fix my friend's Redmi 3s. He was trying to update system, but he get bootloop (lol).
I can turn on fastboot mode or even service mode. I was trying to flash system via MiFlash (download mode>flashing) but all the time I got massage in MiFlash "Can not send to COM..." or "Can not read from COM...". Reinstalling drivers etc doesn't help.
+when I'm trying to go to the recovery the screen shows me some picture Redmi + USB cabel, and that's all.
What can I do? Please, help me. Thanks in advance. Peace!
I am assuming you are dealing with MIUI 8. Is the bootloader on your friend's phone locked or unlocked? If it is unlocked, press Volume Up + Power buttons simultaneously then select Download to enter Emergency Download mode. You should be able to flash from there with MiFlash. If the bootloader is locked, you have to use an Engineering or Deep Flash cable like in this guide http://en.miui.com/thread-316728-1-1.html.
Good luck!
Related
Hi all.
I had unlock bootloader.
I just changed my recovery to twrp. It worked !
Then I upgraded my p9 lite to nougat android version.
It works too !
But now I'm stuck. I moved root su file on my sd card and wanted to go back in TWRP... I cannot anymore.
I Power off my phone and I Power On by Pressing Power Button- VolUp Button Simultaneously => no TWRP.
Plus, it's not easy because of huawei message, that device has been unlock.... but I hold volume button before message and until it disapear... It goes to to android OS. or stay stuck on "device will boot"
If I do the same with +button, it shows me huawei recovery ...
More rarely, it tells me that software install failed (maybe it is trying to install su root package ?)
SO : I cannot use TWRP, and I cannot go to fastboot to flash recovery again.
No change in my drivers, still the same as when I flashed it first time (yesterday) and no new software install.
I'm still trying again and again ... :S
Maybe you could help me ? Thank you.
Hey there!
First of all... Wrong forum section, this is only for Development and not trouleshooting. But I see you are new so just keep it in mind for the future
To your problem:
You need to install the Nougat TWRP. It is the only one that works once you flashed a Nougat ROM.
To access the bootloader, turn OFF your device and then HOLD the VolDown button and while holding it connect the phone to your PC. Bootloader mode should show up.
Then flash Nougat TWRP with fastboot and you should be good.
problems are always easy when they are solved
Thank you, and truely sorry for wrong section error.
hello help me please
hello,
before all, thanks for helping people around the world about solving problems in their zte phones
I have a zte axon 7 A2017G it worked perfectely until i download the nougat 7.0 version i install it via twrp and my phone is stuck in the logo zte without access to neither bootloader nor recovery.
The problem is that i tried many tpoics from xda but when i try to flash a stock firmware using the qualcom tool wich recognize my phone i dont find the xml file in the stock firmware and i dont know how to do to get it functional again.
i am stuck in this point since 10 days now and i hope you will help me repair my zte axon
can someone send me a link to a tuto or to explain me the steps to install a stock firmware and the tool i should use please
Thanks a lot
Imad
You can try booting to FTM mode by powering off your device, press and hold your volume down and power button till you get in FTM mode, then your computer should detect it. From there, you could install TWRP by following the instructions on https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379. Once you installed TWRP, you could install the bootstack and stock system of the version you want at https://www.androidfilehost.com/?w=files&flid=112651. Been through the same thing when I tried upgrading my A2017G to nougat, and I thought I was f*cked till I remembered you could boot your device to FTM mode XD
MahathirMohamad_ said:
You can try booting to FTM mode by powering off your device, press and hold your volume down and power button till you get in FTM mode, then your computer should detect it. From there, you could install TWRP by following the instructions on https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379. Once you installed TWRP, you could install the bootstack and stock system of the version you want at https://www.androidfilehost.com/?w=files&flid=112651. Been through the same thing when I tried upgrading my A2017G to nougat, and I thought I was f*cked till I remembered you could boot your device to FTM mode XD
Click to expand...
Click to collapse
Thanks for youn answer. and your support.
have you been in the same situation ? is it what we call a hard brick ? The FTM is the factory test mode is it?
Thanks a lot
Hello guys, I need your help please!
I bricked my phone ! When I press the Power On Button it says COOLPAD POWERED BY ANDROID and after 10 sec it swicht off. Also when I try to boot to recovery and to the bootloader or fastboot, it swicht automatically off. Even if the mobile is connected with the computer.
My computer does not recognize when I boot to fastboot. I try install many drivers but it doesn't work.
I try to boot to Qualcoom Mode (QFIL or MIFLASH) to flash new TWRP and my Cool1 start to the recovery and also switch off automatically after 10sec. :crying: So it can't boot to anything! I try also YGDP and Coolpad Assistant. By YGDP I try to flash back to EUI but it doesn't work because I'm now on the newer version. Coolpad Assistant can't does not recognize my phone! Please help me or I have to spend 2 months without a phone. ! :crying::crying:
Thank you!!!
did u solve it?
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
disassemble again, force EDL and flash the corresponding rom
bornlivedie said:
disassemble again, force EDL and flash the corresponding rom
Click to expand...
Click to collapse
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash
Click to expand...
Click to collapse
In Windows 10, does the device manager detect the phone as Qualcomm 9008 inside the ports section? It is the way Windows detects a phone in EDL mode. You may have also some driver issue in Windows. If it is detected as BULK then you only need to install the latest Qualcomm drivers. You can find the details in this guide.
nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
I had the no hello package message in Win10 with a A2017U, for me the solution was to setup to run MiFlash in Administrator mode (look for the check box under the compatibility tab), and then replugin the USB cable and restart EDL fresh.
There seem to be all kinds of cases of this occurring for various phones on the internet with various solutions, but this one worked for me this time.
It seems to be a YMMV thing.
BTW if you have an unlocked bootloader flashing the Recovery with the suitable version of Nfound's TWRP Exclusive allows a choice of rebooting into EDL(9800).
This makes getting back into EDL relatively convenient.
nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
I have now used the Axon7Toolkit with Option 11 (Restore to stock) and after this flashed the 2017G with MiFlash. And it works. Don't know why.
But the Topic with the Bootloader is still open. So I'm not able to root and istall TWRP:
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
that's a bad connection, you must have let go of the contact too son
make sure it gets detected in your pc, hold it a couple of seconds more and then let go
Use the ADB command "adb reboot edl" instead as its the most sure fire way to ensure you are actually in EDL mode. The button combination method sometimes doesn't work as I've experienced this myself on more than one occasion.
I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.
> 4: Then i again lock the boatloader using fastboot oem lock.
This is the fatal step that bricked your phone in EDL mode. Reason: To relock bootloader, your phone must be full stock first:
stock ROM, stock recovery. But you was with TWRP = custom recovery!
Fortunately, the Axon 7 is "unbrickable". And your phone is still in EDL mode, this is not the worst brick status (DFU mode).
Note: if ever your were in DFU mode, there is still DFU tool to unbrick your phone (search appropriate topic in forum).
To unbrick in EDL mode, try to EDL flash entire stock ROM corresponding to your model (A2017, A217U or A2017G), Nougat recommanded (not Oreo: not supported by many tools; not Marshmallow: too old).
Recommended tool to flash:
Axon 7 EDL tool (it has link to full stock ROM for different models)
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Note: I never get "No hello packet received error" when using Axon 7 EDL tool. Miflash is not necessary nor recommended for me (overkill, various versions).
Some advices:
- always launch Windows Device manager and monitor it to check phone connection status (COM HD-USB QDLoader 9008, or DFU, or Android device).
- try using latest stable Qualcomm HD-USB QDLoader Driver, if possible signed version. E.g. version 2.1.1.2.
- of course charge the phone fully if possible before flashing.
- check and use good USB connection cable.
- you may need to set Windows in "test mode" first (disable driver signing) to avoid "No hello packet received error"
https://answers.microsoft.com/en-us...est-mode/27b555ca-852a-44c7-b42f-c84b8eec06f2
I have a really similar issue. After updating to Oreo ROM B03, I tried to enter EDL to flash twrp (but I didn't get to this).
I couldn't boot to bootloader using the recovery options (the system was just normally starting). I tried with vol+, vol- and power at one time. After the red led blinks I released all buttons. I guess I got to EDL, but I can't quit it now.
The QDLoader 9008 (driver version is exactly 2.1.1.2) is visible COM4, but I can't do nothing with it. Same error with Miflash, Axon 7 EDL tool stopped on "Loading the programmer". I tried all combinations vol+, vol-, power to boot to the system again, but without luck. Black screen and no reaction.
After night, when I hold power the red led blinks and that's all. When I connect cable to laptop the red led starts blinking, no QDLoader 9008 visible now.
Anyone has an idea what to can I do?
I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.
Click to expand...
Click to collapse
Hi,
same issue here. Using the Axon7_EDL_Tool doesn't work for me: While flashing A2017G_B03_OREO_FULL_EDL via "Flash FULL EDL" it stops with the output: Loading the programmer: prog_ufs_firehose_8996_ddr.elf
Does someone know the solution?
same thing happening today, anyone found the solution yet?
Hi. my huawei p9 lite vns-l22 it gets stuck in your device is booting now.
And no, drain the battery dont works in this case.
And i can enter in my custom recovery TWRP, or in the bootloader.
Only in the stock recovery and the update mode.
Please i need help. And sorry for my bad english.
Veget4 said:
Hi. my huawei p9 lite vns-l22 it gets stuck in your device is booting now.
And no, drain the battery dont works in this case.
And i can enter in my custom recovery TWRP, or in the bootloader.
Only in the stock recovery and the update mode.
Please i need help. And sorry for my bad english.
Click to expand...
Click to collapse
Hi dude,
if you're on stock rom try this:
reboot in bootloader/fastboot mode, connect the device to your PC,
open the prompt and type fastboot reboot.... you should solve.
Instead if you're on custom rom let me know.
If you installed some software/app and stucked into bootlooping,
you should be aware of which app you installed last and booting in recovery mode (TWRP)
try to delete it manually.
Cheers
Well
Dadditz said:
Hi dude,
if you're on stock rom try this:
reboot in bootloader/fastboot mode, connect the device to your PC,
open the prompt and type fastboot reboot.... you should solve.
Instead if you're on custom rom let me know.
If you installed some software/app and stucked into bootlooping,
you should be aware of which app you installed last and booting in recovery mode (TWRP)
try to delete it manually.
Cheers
Click to expand...
Click to collapse
Thats the problem.
I can enter in the bootloader, the phone have the TWRP, are now whats happen but i can enter in the custom recovery.
The screen turns black and grey.
youtube com/watch?v=h9oMBpD0MZQ&feature=youtu.be
The phone dont have a custom rom, is the stock rom.
I erase the system and data in the TWRP, because a problem with my google acount in the phone. but it was worse for the phone.
The only thing i have to do is enter in the stock recovery, and the software installer(vol+ vol - and power).
I cant use the ADB minimal and fastboot. The phone is reconized by the PC, but the program no.
I think this is the only possibility, i download many firnwares, but in all the screen shows "Software install failed incompatible with current version"
In the 3% or 10%.
Veget4 said:
Thats the problem.
I can enter in the bootloader, the phone have the TWRP, are now whats happen but i can enter in the custom recovery.
The screen turns black and grey.
youtube com/watch?v=h9oMBpD0MZQ&feature=youtu.be
The phone dont have a custom rom, is the stock rom.
I erase the system and data in the TWRP, because a problem with my google acount in the phone. but it was worse for the phone.
The only thing i have to do is enter in the stock recovery, and the software installer(vol+ vol - and power).
I cant use the ADB minimal and fastboot. The phone is reconized by the PC, but the program no.
I think this is the only possibility, i download many firnwares, but in all the screen shows "Software install failed incompatible with current version"
In the 3% or 10%.
Click to expand...
Click to collapse
Wow, you erased system and data ? that's the reason because it will not boot dude.
Fortunately fastboot mode and twrp works and i think that will help you
bring your device back to life.
Do you remember latest firmware of your device ?
Which TWRP version are on ?
mmm
Dadditz said:
Wow, you erased system and data ? that's the reason because it will not boot dude.
Fortunately fastboot mode and twrp works and i think that will help you
bring your device back to life.
Do you remember latest firmware of your device ?
Which TWRP version are on ?
Click to expand...
Click to collapse
Firnware version mmm.
I dont remenber the firnware version.
Are now this help, but the phone in Fing(an app to see who is in your WiFi network).
The Phone model are G9. A P9 Lite G9. Is a VNS-L22 of latin america(i think).
And the phone is in Android 6.0 stock, and the TWRP version is 3.1.0-2
Fastboot mode ?
The vol + vol - and power combination ?
And no, the TWRP dont works, dont enter in there. The phone stucks entering in the custom recovery. But the stock recovery works. The custom no, the stock yes.
Veget4 said:
Firnware version mmm.
I dont remenber the firnware version.
Are now this help, but the phone in Fing(an app to see who is in your WiFi network).
The Phone model are G9. A P9 Lite G9. Is a VNS-L22 of latin america(i think).
And the phone is in Android 6.0 stock, and the TWRP version is 3.1.0-2
Fastboot mode ?
The vol + vol - and power combination ?
And no, the TWRP dont works, dont enter in there. The phone stucks entering in the custom recovery. But the stock recovery works. The custom no, the stock yes.
Click to expand...
Click to collapse
You flashed the TWRP but don't work ?
Fastboot mode is bootloader mode so.....
what happen if you turn off the device and restart it
holding vol - and power button until it boot into system/bootloader ?
And vol + vol - and power buttons = three buttons aka DLOAD method are used to flash a firmware
but only in android 6.
Without know the latest firmware you was running on your device
it's very difficult to revive the phone, regardless of the type of device...
Another way to try to revive the phone is a rebrand but it is a bit difficult
and you need the correct files with a working TWRP...
Sorry dude i think i cannot help you anymore...
I wish you the best
Dadditz said:
You flashed the TWRP but don't work ?
Fastboot mode is bootloader mode so.....
what happen if you turn off the device and restart it
holding vol - and power button until it boot into system/bootloader ?
And vol + vol - and power buttons = three buttons aka DLOAD method are used to flash a firmware
but only in android 6.
Without know the latest firmware you was running on your device
it's very difficult to revive the phone, regardless of the type of device...
Another way to try to revive the phone is a rebrand but it is a bit difficult
and you need the correct files with a working TWRP...
Sorry dude i think i cannot help you anymore...
I wish you the best
Click to expand...
Click to collapse
A the fastboot is the bootloader.
I think it was a different things.
I still try to fix this phone.
Well, thanks for the help
Veget4 said:
A the fastboot is the bootloader.
I think it was a different things.
I still try to fix this phone.
Well, thanks for the help
Click to expand...
Click to collapse
you fixed this problem? I have same phone so i want to fix your phone if it still stuck.