Hi
I begun experiencing some random freezings at homescreen. When that happenned I rebooted and resumed working. I thought it was some app or OS problem and ignored that.
Until phone didn't boot anymore and now I'm stuck at boot screen. It does not pass through it
I cannot do anything at recovery. I can see the menu, but when I release any of the keys I used to access recovery, everything dissapear and turns off.
Is there any way to debug which could be the problem? Or any tools I could use to repair it
PS: I did not try to unlock bootloader, flash any other recovery, kernel, rom, etc. Its stock as I took it off its package since bought it.
Thanks a lot for any tip you could give me :good:
Related
Hello,
In the last few months i have had some minor issues with my phone. In May or in June I have tried to root my phone. It was my first device I wanted to root, so I decided to use Kingo Android root. It didn't work. I installed HTC universal toolkit ( or how was it called ) from XDA forums to my computer. With its help I unlocked the bootloader, installed the TWRP and rooted the phone with Kingo. Everything worked OK, the only problem was that TWRP didn't respond to touch input. I didn't solve it at the time because it wasn't urgent. A month ago I installed few root apps from Google Play, but I didnt experience any issues. Today I was browsing the internet and suddenly I saw a HTC logo and the screen came grey. I waited for a minute and then force turned the phone off. It didn't want to start again. I booted into bootloader. It showed few errors, but was successful to boot. I wanted to open recovery, but it opened the bootloader menu again. Factory reset option didn't work too. I turned the phone off and then turned it on again, but it was stuck in infinite startup loop. Also the HTC logo was broken, there were strange colourful squares around it.
How can I repair my phone? I know that it isn't totally bricked, but this looks really bad. At least I would like to save my data and I will buy a new phone.
Thank You very much for Your help.
Dominik
P. S.: Sorry if I made any mistakes, but I am not a native speaker.
So today it doesn't even turn on!!!! I have tried everything, I was holding power and volume down button for almost two minutes, did the same with my mobile connected to the charger and to the computer, but nothing :crying: .
CAN ANYBODY HELP ME?????
So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Well, this guy managed to fix it
. Not sure if its the best way to fix it but it's still something
Effected said:
So guys
I was on twrp and tried to flash a new rom but when it rebooted after the install, my Zuk z2 died.
It does nothing now. If I press the powerbutton for a long time it shortly vibrates for one second and the notification light also lights up for 1 second, but does not boot up. I tried volume combinations, don't work either.
What can I do guys?
Click to expand...
Click to collapse
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ follow the steps
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146
Use this if you didnt success from other methods.
tlxxxsracer said:
My video. The brick occurs when you usually backup a room with one version of twrp, flash another variant of twrp and then restore the nandroid from before.
Happened to me. Flashed MIUI, and then tried to restore a nandroid (not realising the TWRP changed).
Hope the video helps. Plus then you have a cable premade in case it happens again
Click to expand...
Click to collapse
Hello. Maybe you can give me some advice. I am stuck in engineering/diagnostics mode after I accidentally selected that option when I was in the bootloader trying to flash TWRP.
Basically, I had installed TWRP and Mokee 7.1.1. I wanted to check out the original chinese ROM so I relocked, flashed with QFIL, etc. I had first flashed MM, then I flashed latest chinese Nougat official.
I didn't like it, so I was trying to unlock the bootloader again, and in the process I ended up selecting the diagnostics/engineering mode. The phone was stuck there and I had no way of accessing the bootloader to reflash with QFIL or MiFlash
TO try to fix, I used the deep flash method you describe in the video, only I found it in zukfans. I was able to open the 9008 port, flash with QFIL/MiFlash. Even though both tools describe the flash as successful, on boot, it goes back to engineering mode.
How to I get out of there? Is my phone done?
Thanks!
Hello there
After my phone randomly rebooted while watching a video it ran into a bootloop.
I had been running LineageOS for the past couple of months and everything was fine up until yesterday.
I have tried restarting, and everything and only managed to reflash twrp via adb and force it to boot into twrp, but now it's stuck booting into that.
when I try to boot into lineage I only see the boot animation of lineage that never stops, and when I boot into twrp I see the boot screen of that, which never stops.
I've let the phone do its thing for so long that it has run out of power, so it's not something that just takes a long time. I feel like this thing is completely bricked now.
Anyone maybe got a solution? Any help would be appreciated.
Hi,
Think I might have the same issue, except I didn't flash or modify anything on the phone. I'm running all stock ROM and all the rest.
Stuck in a bootloop in recovery mode. Mini partition does not recognise the phone. Same with QPST. QComDloader does, but only for a few seconds, so whatever I try it's not fast enough before the next reboot...
Whats are the options? I don't want to have to send it back to China
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
That's probably some random issue, the BLOD happens like this:
You do your stuff on the N5X,
everything freezes for several seconds,
phone restarts itself and doesn't get past google logo,
can't access recovery, however you can access bootloader, which is very laggy,
starting up again is nearly impossible, you can hold the button for an hour and the phone won't even get to the google logo.
ZLevente said:
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
Click to expand...
Click to collapse
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Thanks, i'll try bhz31a thanks
(I'll write in some days if it worked or not)
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Which bootloader is bhz31a? I tried the bootloop fixes, none worked. Only have access to bootloader, no recovery.
edit: i see bullhead-opm1.171019.011-factory-3be6fd1 has the bhz31a bootloader. I tried this, with no luck on my end. Even with the 4core modified recovery/boot. I must have one of the unfixable BLOD.
I tried that bootloader too, same
My phone can boot, just sometimes it's stucks at google logo, but i can access recovery every time, even if it's stucked at google logo.
Usually every 2. reboot stucks.
Hi,
I have a Brazilian stock mMoto Z2 Force, XT1789-05, never unlocked the bootloader or root or whatever in this phone, just did the normal Motorola updates as they arrived.
2 months ago I had some battery issues, changed it and was working just fine until this morning. Today the phone restarted after I closed the alarm, and got stuck in boot loop.
I read some threads about this problem for people messing with Roms and baseband, but they don't really apply for me.
The phone reaches the Motorola logo and after a few seconds it restarts.
I can go into fastboot and select recovery mode, but then there's just a black screen with "No commands" written.
Tried Factory Mode with no success.
LMSAA don't recognize the phone, and don't let me select the correct one.
Is there anything else I could try? Maybe force LMSA to do it's magick? manually selecting my phone model for example?