Hello everyone,
I recently bought a Zuk z1 and I tried to install TWRP recovery with the TWRP manager.But when i tried Access the recovery mode my phone stuck on a dark screen..I turned it off by pressing the power off button.After that my phone boot without any problem, but now when I'm trying access the recovery mode my phone will reboot in normal mode...Any thoughts???
Sorry for any grammar mistake...btw i'm greek
Backup your data and try flashing via all in one tool kit. Worked for me.
Is there anything i can do without pc???
Thank you all for your "help", I'll figure it out myself
please make use of adb commands using pc itself .
it is the safest method of flashing recovery and unlocking boot loader.
and one information ,In ZUK Z1 to go to recovery from power off mode is by pressing both volume up and down + power button for 10 odd seconds
I did try to use a pc and the tool all in one ( http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563 ) but my pc doesn't seem too recognize my phone when i boot it at the bootloader, I installed the drivers from the tool all in one ( the lenovo usb drivers) but still nothing. Im using win7 starter 32 bit.
Hi,
have tryed to install twrp 3.0everything is ok till superSU install ... In TWRP recovery click Install Zip and select SuperSu zip after rebooting entered in Rescue mode Func 11 Error 2, and dont know what to do more...
Tryed to flash stock.img via flash... now it appears to be in normal fastboot & rescue mode but adb doesn't recognize devices... i can enter in erecovery by huawei via erocevery on phone or in pc hisuit but when i try to transfer update, in phone its "failed" in pc appear the message (your device doesnt support Erecover).
Now if i turn phone normaly its stuck logo loading, if vol- + Power enter fastboot & rescue...
Any help how i can bring my phone to life!?
Best Regards!
UPDATE!: Tryed stock firmware w/APP, vol+, vol- power... starting install and 90% get stuck... any clues?
Thnks in advance!
try2me2 said:
Hi,
have tryed to install twrp 3.0everything is ok till superSU install ... In TWRP recovery click Install Zip and select SuperSu zip after rebooting entered in Rescue mode Func 11 Error 2, and dont know what to do more...
Tryed to flash stock.img via flash... now it appears to be in normal fastboot & rescue mode but adb doesn't recognize devices... i can enter in erecovery by huawei via erocevery on phone or in pc hisuit but when i try to transfer update, in phone its "failed" in pc appear the message (your device doesnt support Erecover).
Now if i turn phone normaly its stuck logo loading, if vol- + Power enter fastboot & rescue...
Any help how i can bring my phone to life!?
Best Regards!
UPDATE!: Tryed stock firmware w/APP, vol+, vol- power... starting install and 90% get stuck... any clues?
Thnks in advance!
Click to expand...
Click to collapse
Since you have flash twrp you won't be able to update firmware locally. Go in twrp and mount system(If it's not mounted) and then restart your phone.
Greetings all,
I recently got a P9 Lite but I bricked it trying to install a newer firmware on it (tried to go from 6.0 to 7.0). I've read various unbricking guides over the past two days but to no avail. I'd like to know what my options are at this point and if it is possible to unbrick it and bring it back to a usable state even if on a different rom.
How I got here:
The firmware that came with my phone was L23C605B120. I tried to update it to L23C605B362 and downloaded 2 zips (update.zip and update_data_full_VNS-L23_hw_la.zip). I unzipped update.zip into the dload folder of my sdcard and updated it via the dialer. The update installed and my device rebooted but now to this bootloop state.
What I can do:
If booting up normally, I end up in Huawei's erecovery. I can also boot to recovery mode where I can either "Wipe data/factory reset" or "Wipe cache partition". I can boot to fastboot & rescue mode but it says my phone and frp are locked. When pushing all three buttons I can boot to where the phone will attempt to update with the dload folder in the sd card again.
Stuff I have tried:
In erecovery when I select "download latest version and recovery", I can connect to my wifi but it always fails at "Getting package info failed". In recovery mode the factory reset fails and I don't think wiping the cache partition did anything meaningful. In fastboot & rescue mode it tells me to open HiSuite where there is a recover option but clicking it says "Your device is not supported for system recovery". I can see my device using fastboot on my computer but it seems almost useless here since its useful commands fail with "command not allowed" probably because my bootloader is locked. On my computer I installed the USB drivers adb needs and rebooted but adb cannot see my device presumably because I hadn't enabled USB debugging prior to getting bricked. At this point I'm downloading different roms to my sdcard and trying to flash with the 3 buttons method but pretty much all of them fail at 5% or 7% including the rom with the same version that my phone came with. The only one that doesn't fail at 5% or 7% is the rom I tried to flash that bricked my phone which fails at 99%.
So I cannot flash TWRP because my bootloader is locked, I cannot unlock my bootloader because adb cannot see my device, adb cannot see my device because I probably never enabled USB debugging and I cannot enable USB debugging because I cannot boot to the OS. At this point my only option seems to be trying to flash a working rom with my sdcard but I have yet to find one that works.
Where should I go from here and what are my options at this point? Is there a specific rom I should be looking for? Is there some intermediate downgrade rom I have to flash or is there a way to undo the update I just did? Is there a way to somehow enable USB debugging or to unlock my bootloader without it (perhaps via an exploit)?
Any help would be much appreciated!
TL;DR: title
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?
My phone was rooted nad has an unlocked bootloader
today, i got prompted to update magisk. I had done this previously with no problem, but something must have changed with magisk, because after rebooting the phone got stuck in fastboot mode.
I tried the "hold power and volume down until the phone reboots 6 times in a row", but it didn't work. I plugged the phone to the pc and it entered download mode
is there a way to fix it myself? is download mode the same as 9008 mode?
the phone is a AWM model cross flashed to ulm, running android 9
nevermind, got the phone to 9008 mode too (detected by pc as Qualcomm HS...)
I have same problem, i get download mode but when i open lgup there is no option to choose kdz or select refurbeshed
So how did you fix it?