Related
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!
My friend purchased redmi note 5 pro.
He gets successfully unlock his bootloader but when he trying to boot twrp recovery his phone gets black screen. After facing so many problems he finally boot twrp but older one i think so but when he trying to flash custom rom like android pie aosp build or any other custom rom like pixel xperiance he successfully flashed but when he trying to boot his phone after mi logo his phone screen is totally blank and nothing comes up.
But when i check his phone i think so his phone is properly boot but display doesn't show, when i press power button screen lock sounds comes. I dont get this issue in my phone , i also have redmi note 5 pro.
If any one have solution for this please reply.
Need the version of TWRP
Phonexp007 said:
My friend purchased redmi note 5 pro.
He gets successfully unlock his bootloader but when he trying to boot twrp recovery his phone gets black screen. After facing so many problems he finally boot twrp but older one i think so but when he trying to flash custom rom like android pie aosp build or any other custom rom like pixel xperiance he successfully flashed but when he trying to boot his phone after mi logo his phone screen is totally blank and nothing comes up.
But when i check his phone i think so his phone is properly boot but display doesn't show, when i press power button screen lock sounds comes. I dont get this issue in my phone , i also have redmi note 5 pro.
If any one have solution for this please reply.
Click to expand...
Click to collapse
Please provide the full details with twrp version and also he flashed superuser or magisk root manager? if so then which version?
Check this
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-huaxing-displays-t3873266
heyyy .. iam facing too exact same pblm since 2 days .. does you have got the solution to this ?
anyone who knows the solution.. same problem to me and my phone is off since past 15 days.. when i switch it on, it is on but not able to see anything on screen... can someone pls help
could be new panel is beign used.?
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
anyone?
SallyTheDevil said:
anyone?
Click to expand...
Click to collapse
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
muhamet said:
What firmware you.flashed??Stock firmware??Stuck at samsung screen?
Click to expand...
Click to collapse
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
SallyTheDevil said:
yh I flashed the latest stock firmware,
n it's stuck there, like in th screenshot
Click to expand...
Click to collapse
Force restart,press volume up and power button same time
muhamet said:
Force restart,press volume up and power button same time
Click to expand...
Click to collapse
Volume up and power doesn't do anything
Volume down + power restarts the phone but it comes to the same samsung black screen
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
k3lcior said:
Are you sure you flashed correct firmware? Tried to factory reset in recovery? Full Wipe and then flash the firmware?
You can also try 'adb logcat' to see what the error is if adb is available..
Click to expand...
Click to collapse
I can't enter recovery mode
Volume down + power restarts but I did try to go to recovery by releasing volume down and pushing volume up the second screen goes black but it's not working
I can only enter download mode when it's connected to pc with odin running
Could it be a hard drive problem?
And I'm pretty sure i got the right firmware
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
k3lcior said:
Tbh not sure i got my A50 just recently, didn't even flash anything yet. Is you phone detected when you type "adb devices" in windows cmd?
Click to expand...
Click to collapse
tried it, it doesn't recognize the phone.
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
SallyTheDevil said:
is there anyway to figure out if it's a hardware issue?
cuz I've heard it's a somewhat common problem in the A50 for the hard drive/storage to go corrupt.
Click to expand...
Click to collapse
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
SallyTheDevil said:
here's what happened, the phone started freezing and restarting every 5 mins, I uninstalled some apps thinking that's what's causing it, I used it for around 10 minutes and it was fine, installed the latest security patch update, restarted and everything looked fine.
plugged it in, saw it had restarted again and it was stuck on the Samsung Galaxy A50 secured by Knox screen,
rn: I can't enter recovery mode, (the phone won't shut down and releasing the volume down and holding volume up thing doesn't work)
I can only enter download mode, Connected to Odin, flashed the latest firmware and it passed successfully, but still it gets stuck and won't boot.
any ideas?:crying:
Click to expand...
Click to collapse
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
muhamet said:
Connect the phone to pc,press same time volume up and down.You will boot on download mode.Then flash firmware
Click to expand...
Click to collapse
done that already, it flashes the firmware successfully but still won't boot, it just gets stuck at the same screen.
JulianaO said:
I am having a very similar problem to yours, so I will follow this thread. I was using my phone two days ago and it simply turned itself off and since then I am stuck in the logo screen. When the phone is loading I have no indication whatsoever of the battery percentage at all. I still can access option and factory reset and wipe cache (unlike you, apparently - but it does nothing for me). This simply does not help. I end up back at the logo Samsung Galaxy A50 screen. I have downloaded two different firmware... android 9 and 10 from Samsung mobile, and have used Odin to flash it. The process goes through ok and without errors. I get the pass message and the message that the phone is being updated. Then it is time for the logo screen again and form then on the phone simply does not start. I am lost. Can anyone help?
Click to expand...
Click to collapse
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
SallyTheDevil said:
hey there.
apart from the factory reset thing it seems like we have quite the same problem,
at this point I'm afraid it might be hardware thing
Click to expand...
Click to collapse
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
JulianaO said:
You know... I am not really sure. The only different thing I did was to accept to instal a new firmware one or two days prior. I am inclined to think that was it. Anyway... I tried to flash Android 10... Android 9 (both via Odin) and did not work. The support team instructed me to do the hard reset a couple of times ... and wipe cache and nothing. Today I sent my phone to Samsung assistance since it is still under the guarantee because that is what they thought I should do. I'll keep you posted. Hope you can get yours fixed soon.
Click to expand...
Click to collapse
yh I installed that update too and this happened later the same night.
unfortunately for me all the shops n services are currently shut down because of the Co-Vid situation so i have to wait for now.
thanks for sharing, lemme know what happens.
I've had these same problems before. When flashing with Odin, don't populate the last slot with anything (the HOME_CSC slot). Flash it to the device without auto reboot on, restart the device manually and hold vol up + down to get to blue scrern, then unlock bootloader. Let it restart, then reflash ROM.
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
OK, here is kernel log. I powered on the device, let it boot to the latest Lineage OS (lineage-17.1-20210201), then entered pin number and waited. Screen turned off, and a couple of second later device restarted (showing "Mi" and at the bottom "unlocked"). Then I imediately pressed "power + volume UP" to boot into recevery, where I copied log file).
I noticed multiple i2c errors, but couldn't find where exactly device initiated reboot.
klepec said:
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did you do clean flash? Wipe data, cache, system, on internal storage android directory must be deleted?
What's your firmware? I guess old oreo and not new one - pie, it should be 11.0.3 or newer!
Update Firmware first using MI FLASH TOOL NOT FROM RECOVERY!!!
Than clean flash Official LOS 17.1 again.
If your WiFi won't work after that your persist partition is corrupted.
For extra info search xda forums.
Good luck and stay safe!
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
klepec said:
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Yap all above 11.0.3 is ok..
Advice: don't rush! Read and take it slow. If you rush you'll probably mess it up... unlock your bootloader first, its easy to bring it back to life if you gonna mess up your phone.
For better overview watch how flash and what options to pick
Good luck and stay safe!
Hi to all, I just want to ask for some advice or tips. The thing is:
I have one old Redmi 5A Riva. It was lying in the drawer some time, so I decided to try to unlock the bootloader and flash some custom ROM.
So, I unlocked the bootloader - OK
Then I flashed TWRP - OK
Then I decided to make root on stock firmware - OK
Then I tried to flash Lineage OS 17 - after flash it stopped booting.
So I tried to flash Lineage OS 18 - it started booting again but I found out that phone doesn´t detect an USB cable, so I wanted to flash some other ROM instead.
But after few moments TWRP suddenly disappeared (volume up + power on stopped working, only vol. down and power on worked to fastboot) - kinda weird, I said to myself Now I am f**ked up because Lineage 18 was not rooted, I wanted to do it later, so I couldn´t use TWRP app to reflash it.
But after few moments there appeared stock recovery menu, so I thought okay, maybe its not dead, so I try to flash just stock rom. I tried MIUI 10, but again - not booting.
So I did wipe again and tried MIUI 9 - flashing via fastboot and used flash_all.bat attached to rom - it booted up and worked, so I enabled USB debugging again and tried OMNI ROM. I flashed it, after flash it boots up, but after few second screen goes black and nothing else happens.
I am kinda annoyed with this , I flashed many phones, but only Xiaomi makes these weird problems.
Can someone help me to fix this?