Hi all,
A strange thing happen to me, my Zuk Z1 ran out of battery and I've put it to charge and when I boot it up again it kept boot looping.
My Zuk Z1 is the international version and I have tried all of the below solutions
Clear all caches and media - No luck
Use QFIL with original rom - No luck keeps boot looping and most of the times gives an error at the very end of the QFIL ( Download Failed QDloader .... )
Used QFIL with ZUI rom - Works but most of the functions don't work, no wifi, bluethooh and so on
Erased sdl1 with fastboot ( that made the phone to seem dead, had to open it and remove the battery in order to be able to install QFIL rom again )
ADB sideload, stops at 47% everytime and the phone reboots and keeps doing the boot loop.
I can get ADB and Fastboot working but I'm running out of ideas!
Also I was thinking on rooting the phone to allow me to install Cyanogenmod to see if it works but don't know how to achieve this, Kingroot needs internet and I have no way of getting it to work.
Any idea would be very welcome !
Thanks
UPDATE:
I was able to flash TWRP and CYANOGENMOD 13, it boots but its the same as in ZUI, no wifi or bluetooth, I'm guessing it was the motherboard that fried !? The mac address displayed on the WLAN is 02:00:00:00:00:00 and i've tried several options in developer mode which didn't work.
Click to expand...
Click to collapse
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the ZTE logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
mvortex3710 said:
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the Axon logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
Click to expand...
Click to collapse
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
mischa_martin said:
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
Click to expand...
Click to collapse
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
mvortex3710 said:
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
Click to expand...
Click to collapse
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
mischa_martin said:
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
Click to expand...
Click to collapse
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
As you are in EDL now you have some options.
First I would try to flash a recovery and boot image that is proven to be working fine e.g official twrp https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 or some A2017G stock boot.img
If that doesn't help you could get in contact with @jcadduono to be a tester for that miflash method. (As your device is already pretty badly bricked)
I don't exactly know how EDL flashing works if it depends on a exact GPT table or not.
But I can say that I flashed every single part of the A2017U bootloader except for NON-HLOS (modem) on my A2017G for each B29 and B15 and it worked just fine. So maybe we just have to exchange the modem file in the EDL package :silly:
If you don't want to take that risk you also could try sending it back to ZTE and hope they don't check the bootloader :fingers-crossed:
(Just a thought: Maybe if the EDL package won't work on your device it will be so heavily damaged ZTE can't check for bootloader unlock and accept it as a warranty case, but don't take that too seriously )
Regards,
Martin
mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
If you are not afraid then try to use my package for A2017G with MiFlash: https://mega.nz/#!88BjXKhA!TnVSobBw5PkmShSqZ-Ni8MCCbnhJP2SWRNvvXqYHSjc
I really appreciate all this advice!
Looks like the MiFlash is promising. I was able to load the phone into MiFlash from the [EDL] thread. I have just tried the A2017G package provided by djkuz and will report back with any updates.
Just got to the mifavor screen, charging the battery from empty, although quickcharge appears to be functional again.
The charging battery logo is different from before so appears that this bootstack has done the trick.
The flashing red light has gone now, appears to be loading Lineage as before! I'm so grateful for all this help
However, now the unlock pattern is coming up as 'wrong pattern'. Is there anything that can be done? My settings appear to be saved as before (wallpaper and quick settings are the same).
I will attempt to reinstall twrp recovery and fix the lockscreen over adb. Thanks very much for the help. The brick has gone!!
I have lenova a6000 8 gb black phone
I have problem when i went to do factory reset because of network problem.but it stuck on erasing screen and moght be goes in loop as its shows erasing screen frequntly and cant start any mode or normal os.what should i do. I tried to connect to pc but it was never detected in any pc .
Give solution
Hear is link for problem video
Youtu.be/sTajWR7OV6Y
mrohb12 said:
I have lenova a6000 8 gb black phone
I have problem when i went to do factory reset because of network problem.but it stuck on erasing screen and moght be goes in loop as its shows erasing screen frequntly and cant start any mode or normal os.what should i do. I tried to connect to pc but it was never detected in any pc .
Give solution
Hear is link for problem video
Youtu.be/sTajWR7OV6Y
Click to expand...
Click to collapse
Did you installed drivers for your lenovo a6000 In your PC.
If no install driver and install twrp and erase your data
Still problem remaining
Yess i have installed lenoa usb driver for this mpbile but its not detected even in device manager also.
I have also ttied using port setting but still problem remaining.
Can u say another method to detection
mrohb12 said:
I have lenova a6000 8 gb black phone
I have problem when i went to do factory reset because of network problem.but it stuck on erasing screen and moght be goes in loop as its shows erasing screen frequntly and cant start any mode or normal os.what should i do. I tried to connect to pc but it was never detected in any pc .
Give solution
Hear is link for problem video
Youtu.be/sTajWR7OV6Y
Click to expand...
Click to collapse
I am really sorry to hear about what's happened.
You may consider flashing the stock ROM of your Lenovo A6000 to resolve the issue.
If you prefer the KitKat ( Which I highly recommend. I tried all kinds of Custom ROMs for years but now I am back to the stock, it's the best and the most compatible for our device. ), you can download the package from the link given below. All the tools needed are there including the instructions.
Code:
http://www.mediafire.com/file/vlw8t6yv0jzay1b/Lenovo_A6000_S040_150805_8G_ROW_by.reda%40gem-flash.com.zip
However, if you wish to flash Lollipop stock ROM which has many bugs, you can download the other package below. It also includes instructions and tools needed.
Code:
http://www.mediafire.com/file/dhwu78g9llbv133/Lenovo_A6000_S062_Q102113_20161223.zip
If you are still having problems, please let me know. I may be able to help you further.
Regards,
xda_borj
If I start my phone without sim card, it won't boot. And if I start it with sim card, it will ask for the pin code and freeze at 2-3 seconds with a reboot. I tried a lot of stock versions, even flashing in edl mode without success. The only way I got my phone working was by flashing the MIUI port, but the sim was broken there too. I've been following some tutorials here in xda and it semms that my efs is broken (?). I tried to fix that in qualcomm software download tool and it doesn't detect my phone in miui.
Could anybody help me?
Follow the link...
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Same here and mistake with mi flash bootloader relocked :crying:
Any suggestions ?
I have a bricked redmi 3s prime. It is having locked bootloader.
First I had search for local repair center to fix it. But the shop guy said me to replace motherboard of device. But I'm not sure what is the exact issue with device, because I can still use recovery option as well fastboot.
I'm bit technical, so I thought it is software issue. So I thought to un-brick it myself. So I had tried almost many methods to un-brick it but not getting any success till yet.
The methods I have tried mentioned below.
1) From recovery, simply wipe data storage and try to turn on device. Waited for 20 mins on mi logo screen. No Success.?
2) Enter into fastboot mode (Device detected as some random string on PC) and simply try to flash both fastboot roms (Global and Developer) using MiFlash beta Tool. Even fastboot mode unable to flash those official roms. No Success.?
3) Enter into EDL mode using TestPoint method (Device detected as COM6 on PC). Again try with both roms MiFlash. After flashing each rom I had waited over 30 mins on MI logo screen, but nothing happens. No Success.?
One thing common while trying all above methods is that battery power less than 10%. I can not full charge device, because there is no way to turn off device if I'm not succeed with my steps.
So is there anything I'm still missing? Can someone help me with this?