Hi,
I have a new Zuk Z2 (plus), it's a month old now. I'am running AEX
Yesterday i would charge the phone but the phone would not charge. (see screenshots).
I tried 4 different charges including the orignal charger. Every charge gives the same result. 4 different USB-C cables including the original.
The fith charger (an old ipad 10W charger) works, the phone is only charging with that charger.
If i connect my PC the phone gives the same results. I can't see the device in device manager or using linux in lsusb.
When i poweroff the device and i plug in a USB cable the phone boots, and hangs.
Must user volume up and the powerbutton the reset the phone.
Even in fastboot mode i don't see the phone in my device manager or in under lsusb in linux.
I already tried to update from AEX 4.5 to 4.6, same result.
Tried to change the kernel from AEX to Heliox, same result.
Is the phone in a safe state? Why does android see that's connected but not charging, why is it charging with the iPad charger? Why is safeboot not working?
Does anyone have a idea to fix this? so that i can charge it with every charger again an can connect it with my computer?
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try to flash stock ROM with QFIL. Thus relocking your bootloader can fix it
Relocking the bootloader will not help, try a factory reset if you still haven't.
TanajiKC said:
Try to flash stock ROM with QFIL. Thus relocking your bootloader can fix it
Click to expand...
Click to collapse
I already tried to get it in EDL, it looks like it isn't working ether (i can't use ADB for this, so I'm trying it with the volume up, power button and wait 0.5 sec trick)
visheshjain25 said:
Relocking the bootloader will not help, try a factory reset if you still haven't.
Click to expand...
Click to collapse
What is the best way to factory reset the device without USB.
(TWRP is working, but ADB is not working in TWRP)
I smell a faulty usb connector or port.. Try different cable and see
HungryPetal said:
What is the best way to factory reset the device without USB.
(TWRP is working, but ADB is not working in TWRP)
Click to expand...
Click to collapse
You don't need a USB to factory reset, just head to settings and search for factory reset and go from there
vbvn said:
I smell a faulty usb connector or port.. Try different cable and see
Click to expand...
Click to collapse
That's the stange part, charging works with two different iPad chargers (tried also my gilfriends iPad charger today).
But not with any other charger while using the same cable.
The iPad chargers also works with 2 other USB-C cables, including the original ZUK cable.
visheshjain25 said:
You don't need a USB to factory reset, just head to settings and search for factory reset and go from there
Click to expand...
Click to collapse
Today I tried the factory reset without luck.
So a "normal" reset isn't working.
Bro, try sometime more on getting to edl mode, if you terribly fail then don't take the phone in that condition to service centre. 1st discharge the battery completely so that even the sc guys can't charge and boot it, so they never see the unlocked bootloader, then probably they'll change the motherboard because they ain't got talent to repair. Good luck, hope you can get to edl next time you try.
The.Night.King said:
Bro, try sometime more on getting to edl mode, if you terribly fail then don't take the phone in that condition to service centre. 1st discharge the battery completely so that even the sc guys can't charge and boot it, so they never see the unlocked bootloader, then probably they'll change the motherboard because they ain't got talent to repair. Good luck, hope you can get to edl next time you try.
Click to expand...
Click to collapse
Thanks for the tip.
I connected to ADB using wifi and "adb connect" and reboot the phone with "adb reboot edl".
So i'am sure that my phone is in EDL mode, but USB still not working.
The iPad charge i'm using is 5.1V and the rest of the chages has other voltages, so i think the voltage regulator is broken.
I'm not sure where to get service in Europe and even if i can get service. I bought this device new on Gearbest.
Has someone a tip to get service?
Same thing happened to me also my phone only charges with a car inverter or car charger but doesn't with stock or any other charger. But my pc do recognise it as media device. Going to stock ROM and submitting to service centre tomorrow!
Related
So basically i download go launcher, it has been working for quite some time. Now i had been holding out on these updates for some time but thought it best to update the launcher. I updated it and it instantly turned black. However i could still click turn off, so i restarted the kindle. Now since yesterday it wont go past the boot loading kf orange screen. I have tried overnight, 30 sec, and 60 sec restart all to no avail. I have the kfu utility drivers installed but i only have removable drive E. I probably wont buy another kindle after this(to limited), but want to get my data off this thing. It is rooted, but doesnt have twrp,fff or anything as it never works.
helpmeoutplz said:
So basically i download go launcher, it has been working for quite some time. Now i had been holding out on these updates for some time but thought it best to update the launcher. I updated it and it instantly turned black. However i could still click turn off, so i restarted the kindle. Now since yesterday it wont go past the boot loading kf orange screen. I have tried overnight, 30 sec, and 60 sec restart all to no avail. I have the kfu utility drivers installed but i only have removable drive E. I probably wont buy another kindle after this(to limited), but want to get my data off this thing. It is rooted, but doesnt have twrp,fff or anything as it never works.
Click to expand...
Click to collapse
like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there animation or unchanging screen?
have tried following Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
Don't need the fastboot cable if kindle is in Fastboot mode (unchanging kindle fire screen)
sd_shadow said:
like this
is there animation or unchanging screen?
have tried following Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
Don't need the fastboot cable if kindle is in Fastboot mode (unchanging kindle fire screen)
Click to expand...
Click to collapse
sorry for late reply. its like the picture. the kindle fire icon is displayed but never changes, it does have a change with a glow over the letters. Thats it. It actually did show the screen to unlock when the battery was at 1%. Now i have charged it and it is not better. I will try your fastboot video.
I think it s working again
Well the battery has died again, but this time it actually let me in and i saw the new updated user face(not updating again after this mishap) but hopefully when it charges again it will work. What i did was take it off the charger and hold the button for 60sec, after that it worked hopefully.
Confirmed.
I have now confirmed its working. I however have not rebooted my kindle, and wont for some time. I suggest letting the battery drain to near zero(plug it into the charger and you will hear the almost dead sound) and hold power button for 60sec. I probably might just buy a new kindle not because of need but for new features.
helpmeoutplz said:
I have now confirmed its working. I however have not rebooted my kindle, and wont for some time. I suggest letting the battery drain to near zero(plug it into the charger and you will hear the almost dead sound) and hold power button for 60sec. I probably might just buy a new kindle not because of need but for new features.
Click to expand...
Click to collapse
Draining the battery to 0% is one of the worst things you can do, some battery power is needed to power the charging software.
Alright so just try randomly pressing the pwr button for 60 sec.
I tried rooting my D855 with this method, however it caused my phone to go into a boot loop, so I pulled the battery and tried turning it on, now I get a "boot verification failure"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This error appears when you try boot, enter download mode, or you try factory reset, after the error the screen turns back and the notification light flashes blue and red.
I can't find any way around this, please help!
**UPDATE**
The only time I could get my phone turned on with something on the screen was with the battery out and connected to the PC, however the phone shows up as Unkown USB Device (Device Descriptor Request Failed)
It happen to me. Still waiting for help or another tutorial...
I had similar one but I could still go to download mode by plugging cable when off and golding volume up. If that doesn't work I don't really see any way to unbrick since you're unable to push or execute any files to it. Maybe some way to hard reset it, probably the only hope.
un4tural said:
I had similar one but I could still go to download mode by plugging cable when off and golding volume up. If that doesn't work I don't really see any way to unbrick since you're unable to push or execute any files to it. Maybe some way to hard reset it, probably the only hope.
Click to expand...
Click to collapse
Yes, if we could entered download mode we can pushed the kdz file or tot file.
This problem won't let me stay on download mode, it straight goes to black screen and blinking led.
And now, ended with "relink usb hs qloader 9008" on device manager.
Already try the method on xda with no luck, now i sent my phone to friends who has jtag.
Hope it will boot..
wiwid.colgate said:
Yes, if we could entered download mode we can pushed the kdz file or tot file.
This problem won't let me stay on download mode, it straight goes to black screen and blinking led.
And now, ended with "relink usb hs qloader 9008" on device manager.
Already try the method on xda with no luck, now i sent my phone to friends who has jtag.
Hope it will boot..
Click to expand...
Click to collapse
Since I don't have a JTAG available near me I may have to try the hard brick fix by shorting the pins.
ceeenek said:
Since I don't have a JTAG available near me I may have to try the hard brick fix by shorting the pins.
Click to expand...
Click to collapse
Shortwire? It succeed??
Sol
Sent from my Mi 4i using Tapatalk
wiwid.colgate said:
Shortwire? It succeed??
Sol
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
I went with the shortwire method and the phone is now fixed and running MM.
ceeenek said:
I went with the shortwire method and the phone is now fixed and running MM.
Click to expand...
Click to collapse
Finally.
Mine still won't boot up.
Pls check your inbox, i've sent you a PM.
Sent from my Mi 4i using Tapatalk
Finally, alive again... Thanks @ceeenek
Sent from my Mi 4i using Tapatalk
Facing the same problem...
Tried to use LGUP to reflash but in order to do so it will try to reboot the phone, which will cause it to be stuck in the red/blue LED.
I only have access to download mode, how did you solve this?
Short wire, boarddiag, and then lg flash tools
Sent from my LG-D855 using Tapatalk
Hey XDA!
I found somewhere in web stock rom for QFIL, that you can flash when your phone is hard bricked (like mine was) or when you want to remove Add-X for free. Here are the downloads:
Qualcomm 64Bit drivers
Full Qualcomm flashing suite
QFIL image
My mirror of QFIL image (use when AndroidFileHost is slow for you)
Here are the steps to flash it:
1. If your phone is in 900E mode and you can't reboot to 9008, get a spare USB type C cable or microUSB to USB-C adapter.
1a. If your phone can boot into 9008 mode without problems by holding all 3 buttons, go to step 5.
2. Now you must cut your cable like this (image credit: [email protected] from MIUI forums)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Burn plastic on green and black cable
Something like that:
4. Now when your phone is fully turned off (you can get back cover off and disconnect battery), connect cable to your pc, short green and black cables together and connect it to your phone. After about 10 seconds separate the wires. Now your phone will boot into 9008 (aka EDL) mode. If you will get Unrecognized USB device prompt, connect battery when phone is turned on into 9008, detach EDL cable and connect normal cable.
5. Launch QFIL and set it like that:
6. Click "Download" and wait until finish. If QFIL will error with "system.img/cache.img/userdata.img not found" create empty files named "system.img", "userdata.img" and "cache.img" in stock rom folder.
7. When QFIL will finish flashing, hold power button in your Swift 2. It should boot to system now. If not, try to flash TWRP/Stock rom via fastboot, doing factory reset in Cyanogen Recovery or "fastboot format userdata".
Credits:
Me
Mike's Tech Life from http://mikestechlife.blogspot.com that posted stock QFIL rom, Add-X removal tutorial (http://mikestechlife.blogspot.com/2018/01/removing-add-x-from-wileyfox-swift-2-2.html) and QFIL Screenshots
[email protected] from MIUI Forums EDL cable images
I have long written the exact same guide. What is yours for?
JavaVOBIS said:
I have long written the exact same guide. What is yours for?
Click to expand...
Click to collapse
I see your point about duplicate but I guess you could say @puszekkkkk added photos and info on kicking into 9008 ...your guide was the inspiration or first but both guides are useful to people ...hopefully i won't need either but neat trick with spare usb to get into qfil mode
This destroyed my computer :'-(
I'm sad/frustrated to report that I attempted to follow this guide and completely destroyed my desktop computer in the process! ? I made the cable exactly as instructed and made sure everything was carefully wired with nothing touching anything it wasn't supposed to. I tried repeatedly to get my ZTE device to boot into EDL mode but it simply would not. And then, when I was trying once again, holding the green and black wires together for a few seconds, I suddenly noticed an electrical burning smell. Looking at my beloved little mini-desktop PC, I noticed a very bright orange-yellow piercing light coming from within and then realized this was a flame!! ? I quickly unplugged the PC and ripped the case off, and then blew out the small flame that had started to burn a specific chip on my motherboard. I think this chip must have something to do with USB-port power supply/support. It's a very specific chip and not one I can find online to purchase to repair/re-solder myself. My device is four years old now and is unfortunately out of warranty. I called the tech support center for my device anyway (ASUS) to see if they could do anything, and also wanted to inform them that their product had caught on fire, but they just took my information and said they were sorry but that they couldn't help me with this at all.
So now I am without my main desktop PC. ???
And my stupid ZTE device is still a useless paperweight... ?
richaardvark said:
I'm sad/frustrated to report that I attempted to follow this gu ?
... Homemade cables are a bad way to enter edl
Use fastboot :
fastboot oem edl
Using test point:
Search on YouTube for a video on how to open your phone and "shorting" two contacts to enter edl ( this is the method used by technicians and manufacturers)
Click to expand...
Click to collapse
Hello, Friends from XDA
So long story short, I was trying to fix my Redmi Note 8's charging issue (slow charging and charges only when booted to OS). Then I decided to install a new rom from twrp (current was MIUI China, trying to install Xiaomi .eu) hoping that it might solve the issue but dumb me accidentally wiped the "system" partition during the wiping proccess. Now I am greeted with "The system has been destroyed" message". Cannot boot to twrp anymore. I really regretted doing that.
P.S. tried fastboot, doesn't work, ask for more
Anyone, please help. All suggestions are welcome.
When flashing a ROM you have wipe the system as well. This will fix that issue you are having(flash this after flashing ROM. This is a VBmeta.img):
https://mega.nz/#!r54FzQIZ!LgD3zSOBm1gOIzY6w8r8l-A8GChgWk_Z7HIN6y_bVLc
Use this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I suggest that you join the Telegram group as that's where I got this file from. Plus you will get help much faster.
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
That is alarming, so your device can boot into fastboot mode but won't be recognized by the PC?
Try using it on another PC because if you can't use fastboot or Recovery, the only thing that will save you is the EDL mode, and I have heard people say that the only way to access that is with an authorized account (which only xiaomi service centers have) or you will have to open the back of your phone and short circuit the EDL Chip.
LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy
Zulfi said:
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy
Click to expand...
Click to collapse
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized
Judroidz said:
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized
Click to expand...
Click to collapse
In SS you can see the cover on device clearly
Zulfi said:
In SS you can see the cover on device clearly
Click to expand...
Click to collapse
Oh sorry I didn't see that. OP did you get anywhere with fixing your device
Judroidz said:
Oh sorry I didn't see that. OP did you get anywhere with fixing your device
Click to expand...
Click to collapse
Well bro, I'm still trying. Going to give the EDL mode a try and as you can probably tell, I am a newbie.
Any precautions, maybe tips that I should know about?
here's what I've gathered
1. Remove back cover
2. Find the edl testing points
3. Short circuit the testing points
4. Plug the device to pc (asap after shorting)
5. Flash using MiFlash (Hopefully recognizes the device)
So, it seems like you need an Authorized Account for flashing in EDL. I was hoping to find a diy solution but things get complicated. Well, I'm just going to send the device to a trusted local Xiaomi repair center and get it fixed (they have authorized accounts) and also solve the charging issue. Again, Thanks to everyone and XDA.
P e a c e
Ok, so this is my first phone without a removable battery so very new in terms of fixing bootloops. I just have to deplete the battery because I can't turn off the phone in said bootloop, and also when I plug the charger it goes into loop again...
So anyways, it's very sketchy but 1 out of 20 power-ons I can get it into bootloader/fastboot? but I can't get adb or MiFlash tool to recognize the phone. So for now it's a brick. Is there any way to fix this? My phone has unlocked bootloader and had pixel experience 9, and it was years ago since I did all the romming so I don't have the old files nor the old drivers because of fresh Windows install.
Looking forward for your answers.
How did you get in bootloop in the first place? Did you try to boot to the recovery using volume up and power button?
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Fedegblack said:
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Click to expand...
Click to collapse
When the phone is turned off press first the volume up and while holding it press the power button. After phone vibrates release the power button but still keep the volume up button pressed and wait until twrp starts. If it gets stuck again tell where exactly.
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Fedegblack said:
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Click to expand...
Click to collapse
If USB debugging is working you can try to flash twrp or even fastboot rom with MiFlash.
Ok, tried to flash twrp but it says write protected, so I did "fastboot boot twrp.img" but freezes in the same place as my old twrp. Seems likely I have to flash stock now.
Edit: On second thought I might be able to do something else now, even if it freezes before the twrp menu it's showing with "adb devices" instead of "fastboot devices" so I will try dirty flashing what I think is the same rom as before.
Also, if it's likely this issue with twrp I will be sad. I have no idea when my internal memory got encrypted since it was one of the first things I didn't want when I first romed this.
Welp, after days of trying to enter fastboot again I find myself with this problem.
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried fastboot -w or flashing twrp and orangefox recoveries but same ol' same ol'. Write protection error, it's likely to be hardware issues, but I'm open to suggestions.
Your Odyssey might have an end!
Try to flash the factory rom instead, the one that came with the device, not the most recent one!
I'll guarantee it will work!
I also would try OrangeFox recovery if I was you... way better then twrp. Both my devices have OF as recovery.
Note 5 Pro and Note 8T. My willow have Carbon OS on it but I'm not using it since it only serves as a backup device, in worst case scenario...