Touch screen not respond ? - Xiaomi Mi 8 Questions & Answers

Code:
Help!
I‘ve restarted my Mi 8 and wanted to enter TWRP.
Unfortunately the phone doesn‘t enter TWRP and went into a bootlloop.
I couldn’t shut down the phone completely.
The only thing I could was to enter fastboot mode.
After a few other tries I‘ve reflashed the stable global ROM from Xiaomi homepage.
The phone now reboots correctly and I can see the start screen.
But now the phone doesn’t respond to input.
I can see everything, but I can‘t write anything.
I‘m also not able to shutdown the phone completely.
What should I do now??
Envoyé de mon SM-A510F en utilisant Tapatalk

founy75 said:
Code:
Help!
I‘ve restarted my Mi 8 and wanted to enter TWRP.
Unfortunately the phone doesn‘t enter TWRP and went into a bootlloop.
I couldn’t shut down the phone completely.
The only thing I could was to enter fastboot mode.
After a few other tries I‘ve reflashed the stable global ROM from Xiaomi homepage.
The phone now reboots correctly and I can see the start screen.
But now the phone doesn’t respond to input.
I can see everything, but I can‘t write anything.
I‘m also not able to shutdown the phone completely.
What should I do now??
Envoyé de mon SM-A510F en utilisant Tapatalk
Click to expand...
Click to collapse
I have the same problem, I was on the last xiaomi.eu. I re-lock my bootloader and flash the latest official stable version but it still does not work.
Envoyé de mon SM-A510F en utilisant Tapatalk

Related

Huawei p8 lite 2017 pra-lx1

Hi
I have problem with my phone cant access to fastbootmode
Phone start on error mode not rescue mode
I have installed twrp on phone but now he dont work and all procedure with update via sdcard with dload folder with update.app dont work
I need help
Thks
Envoyé de mon SM-G935F en utilisant Tapatalk
I forget same with volume down and usb cable
Only error mode screen at start with error recovery image
I have update phone with twrp recovery
I think its the problem
Envoyé de mon SM-G935F en utilisant Tapatalk
jmush303 said:
I forget same with volume down and usb cable
Only error mode screen at start with error recovery image
I have update phone with twrp recovery
I think its the problem
Envoyé de mon SM-G935F en utilisant Tapatalk
Click to expand...
Click to collapse
To access bootloader connect your phone to usb and hold the three buttons until the phone vibrates then quickly hold only volume down.
Sent from my PRA-LA1 using Tapatalk
Dont work
I have only error mode screen with this errors:
Funct NO : 11 (recovery image)
Error NO : 2 (load fail)
Some times after many reboot with buttom recovery image change to boot image
Thats all
Thks for help im stuck in error mode
Envoyé de mon SM-G935F en utilisant Tapatalk
jmush303 said:
Dont work
I have only error mode screen with this errors:
Funct NO : 11 (recovery image)
Error NO : 2 (load fail)
Some times after many reboot with buttom recovery image change to boot image
Thats all
Thks for help im stuck in error mode
Envoyé de mon SM-G935F en utilisant Tapatalk
Click to expand...
Click to collapse
Try to make the battery drain and then hold the volume down button and connect it to usb
Sent from my PRA-LA1 using Tapatalk
I already try with battery drain
But read somewhere must be wait for red light when press power buttom
If not i think its dead
Envoyé de mon SM-G935F en utilisant Tapatalk
For red light not lighting
Sorry
Envoyé de mon SM-G935F en utilisant Tapatalk
Flash the boot.img. This goes in the Errormode and then try to reboot.
https://mega.nz/#!dl1mRJqJ!FnCX7hocErMTw32rRhO8EO16Rug6fITQmmyNkh59DwU

Your device has failed verification

Hello, I can't install any updates anymore.
I also get this when I boot the phone (VTR-l29)
"Your device has failed verification and may not work properly"
Hold volume up for 3 secounds for erecovery.
Push power to boot.
Note: The device won't boot if you do not select an option.
Is there any way to fix this? The bootloader is locked now, but unlocked it with fastboot, to recover.
I have this issue as well but for a specific app. Tried changing the date and time which were correct anyway. Contacted the app and they are saying its my phone blocking it but as far as ive checked all the settings that need to be on are on .. so confused. Any help with this would be gratefully appreciated!
I've got the same problem. I tried Firmware Finder and tried to install version 172 (but not the full one).Installation failed and I got this message since.
I tried to download full version but It always says my connection is too instable.
If somebody has a solution, it's welcome !
Envoyé de mon VTR-L29 en utilisant Tapatalk
mega180 said:
I've got the same problem. I tried Firmware Finder and tried to install version 172 (but not the full one).Installation failed and I got this message since.
I tried to download full version but It always says my connection is too instable.
If somebody has a solution, it's welcome !
Envoyé de mon VTR-L29 en utilisant Tapatalk
Click to expand...
Click to collapse
I solved my problem :
It was impossible to download full version so i tried change DNS option on Firmware Finder. I was able to download and install version VTR-L29C185B172 !
Envoyé de mon VTR-L29 en utilisant Tapatalk
3D Fred said:
Hello, I can't install any updates anymore.
I also get this when I boot the phone (VTR-l29)
"Your device has failed verification and may not work properly"
Hold volume up for 3 secounds for erecovery.
Push power to boot.
Note: The device won't boot if you do not select an option.
Is there any way to fix this? The bootloader is locked now, but unlocked it with fastboot, to recover.
Click to expand...
Click to collapse
i have phone RELOCKED and frp LOCK. Bootloader is unlock in fastboot.
cant do anything.
skiswim said:
i have phone RELOCKED and frp LOCK. Bootloader is unlock in fastboot.
cant do anything.
Click to expand...
Click to collapse
Have you tried downloading full firmware of your phone, extracted update.zip and placed the UPDATE.app in a new folder in the sd card named 'dload'.
And then power off, and power on whith holding (power, volume down and up) until force update? that worked for me
if it fails, you can try funkyhuawi's unbrick (last solution)
3D Fred said:
Have you tried downloading full firmware of your phone, extracted update.zip and placed the UPDATE.app in a new folder in the sd card named 'dload'.
And then power off, and power on whith holding (power, volume down and up) until force update? that worked for me
if it fails, you can try funkyhuawi's unbrick (last solution)
Click to expand...
Click to collapse
cant copy firmware at sdcard because is biger than 4gb . FAT32 doesnt supports bigger files than 4gb.
skiswim said:
cant copy firmware at sdcard because is biger than 4gb . FAT32 doesnt supports bigger files than 4gb.
Click to expand...
Click to collapse
try formating to exfat
tryed, but doesnt work.
skiswim said:
tryed, but doesnt work.
Click to expand...
Click to collapse
Did you try with Firmware Finder like I did ?
Envoyé de mon VTR-L29 en utilisant Tapatalk
mega180 said:
Did you try with Firmware Finder like I did ?
Envoyé de mon VTR-L29 en utilisant Tapatalk
Click to expand...
Click to collapse
how you instal firmware, by sd card ?
in what format was sd card- fat32 ? how big was UPDATE.APP ?
skiswim said:
how you instal firmware, by sd card ?
in what format was sd card- fat32 ? how big was UPDATE.APP ?
Click to expand...
Click to collapse
No I installed with Firmware Finder from playstore, and then you go go to your parameters to update system. The update is more than 2GB, and my sd was formatted by the phone.
Envoyé de mon VTR-L29 en utilisant Tapatalk

NEM-L51 blocked in erecovery mode

Hi everyone after rooting my Honor 5c then unroot it each time I power on the phone I enter on Huawei erecovery mode screen. But trying to download and install OTA update I get the error message "Getting package info failed".
In fastboot mode I have noticed that bootloader is relocked and FRP is locked.
Can anyone give me a solution ?
Thanks.
Try dload method.
Envoyé de mon NEM-L22 en utilisant Tapatalk

Mi A2 Hard Bricked (Anti-Rollback on October update?)

Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
tomgv said:
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
As I've said, I can't enter fastboot mode.
My device is bricked
Lurensu said:
As I've said, I can't enter fastboot mode.
My device is bricked
Click to expand...
Click to collapse
Open your phone and flash through EDL mode by shorting test points...
Yep, your last hope is attempt to flash through edl mode by shorting those pins, that's why I always re-install stock rom using Mi flash through edl mode booted from fastboot
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Lurensu said:
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Click to expand...
Click to collapse
When phone is recognized as qualcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Nebrassy said:
When phone is recognized as quallcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Click to expand...
Click to collapse
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Lurensu said:
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Click to expand...
Click to collapse
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there's no ARB yet
Nebrassy said:
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there;s no ARB yet
Click to expand...
Click to collapse
Thank you so much, I'll try to flash the september update then, let's hope everything goes right!
EDIT:
well, everything went smoothly and I'm now on the october update
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
kevin2546 said:
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Click to expand...
Click to collapse
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
yisao said:
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
Click to expand...
Click to collapse
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
gian789 said:
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
Click to expand...
Click to collapse
Con la herramienta Mi Flash de Xiaomi lo puedes recuperar fácilmente, todo está en Google. En parte es tener el programa MiFlash y que te bajes una ROM OEM de este sitio, lo flashees y queda como nuevo; todo esto suponiendo que no tenga un daño peor, pero eso es raro
Lurensu said:
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
Click to expand...
Click to collapse
09

Bricked Phone need Help

Hey guys after doing stupid this i ended up with an locked bootloader and and boot loop with (The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it. ).
now i can only access to the phone in edl mode
atm im searching for ways to flash a rom in that edl mode but its difficult
so i need ur help guys
whyphyrl said:
Hey guys after doing stupid this i ended up with an locked bootloader and and boot loop with (The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it. ).
now i can only access to the phone in edl mode
atm im searching for ways to flash a rom in that edl mode but its difficult
so i need ur help guys
Click to expand...
Click to collapse
it is simple to put the mode in bootloader, then flash the recovery of mauronfrio and from there you install the rom that you are going to put, then start and the mobile will go to you
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
it is simple to put the mode in bootloader, then flash the recovery of mauronfrio and from there you install the rom that you are going to put, then start and the mobile will go to you
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
no i cant get into any bootloader or fastboot or recovery only thing that works is pressing vol+ and power for some sec then its blackscreen and its shows me connected as Qualcomm HS- USB QDLoader 9008(COM3)
whyphyrl said:
no i cant get into any bootloader or fastboot or recovery only thing that works is pressing vol+ and power for some sec then its blackscreen and its shows me connected as Qualcomm HS- USB QDLoader 9008(COM3)
Click to expand...
Click to collapse
ok that happens you have to leave it about 4 hours without doing anything and then it will work for you alone, it happened to me and looking for I saw that it is like a mistake they have to protect themselves and they are deactivated for a few hours, do not connect it or try to turn it on or anything, set it aside for about four hours and then try
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
ok that happens you have to leave it about 4 hours without doing anything and then it will work for you alone, it happened to me and looking for I saw that it is like a mistake they have to protect themselves and they are deactivated for a few hours, do not connect it or try to turn it on or anything, set it aside for about four hours and then try
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
Hi
I'm in the same problem, you also blocked the BL and the same thing happened to you? Then leave it for approx. 4 hours and can I enter the FB?
Sergiocubano1 said:
ok that happens you have to leave it about 4 hours without doing anything and then it will work for you alone, it happened to me and looking for I saw that it is like a mistake they have to protect themselves and they are deactivated for a few hours, do not connect it or try to turn it on or anything, set it aside for about four hours and then try
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
sounds very weird to me but ill give it a try
it didn't work for me
Isavar said:
it didn't work for me
Click to expand...
Click to collapse
You have left it almost four hours and then you have tried to turn on and arrange the charging cable, connect it and then press and hold on + vol + to see if it turns you on that way, I already tell you I had scared for almost 5 hours until without anything else property and look for information and it happens in all are blocked and you have to wait a good while, although the computer recognizes you as a device, he doesn't give an image
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
You have left it almost four hours and then you have tried to turn on and arrange the charging cable, connect it and then press and hold on + vol + to see if it turns you on that way, I already tell you I had scared for almost 5 hours until without anything else property and look for information and it happens in all are blocked and you have to wait a good while, although the computer recognizes you as a device, he doesn't give an image
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
didnt worked for me to
whyphyrl said:
didnt worked for me to
Click to expand...
Click to collapse
Connect the cable and try to light it by pressing the volu + and turning on
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
Connect the cable and try to light it by pressing the volu + and turning on
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
yeah then im in edl mode or whats it called
whyphyrl said:
yeah then im in edl mode or whats it called
Click to expand...
Click to collapse
Normally it is to enter the recovery, but they say that this is revived
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
Connect the cable and try to light it by pressing the volu + and turning on
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
not working, do you block BL after remplace original recovery for twrp?
I comment to see if you are in the same case as us
cheers
Isavar said:
not working, do you block BL after remplace original recovery for twrp?
I comment to see if you are in the same case as us
cheers
Click to expand...
Click to collapse
I had the bootloader unlocked but the phone was dead and when I connected it to the computer I recognized it but did not give image or anything
Enviado desde mi RMX1931 mediante Tapatalk
Sergiocubano1 said:
I had the bootloader unlocked but the phone was dead and when I connected it to the computer I recognized it but did not give image or anything
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
yur case its diferent, you should enter in fast mode an re flash room and ready. your case it is not a brick!
Isavar said:
yur case its diferent, you should enter in fast mode an re flash room and ready. your case it is not a brick!
Click to expand...
Click to collapse
Lol I was not allowed to enter anything the phone was dead, or do not understand, the phone was dead for 4 hours without turning on and without anything, although it will connect to the PC appeared on it but the Phone did not turn on or anything
Enviado desde mi RMX1931 mediante Tapatalk
Anyone find a way to unbrick this phone yet?
Hi all It seems that offline charging is broken in Evolution X n others GSI...I had to wait like 8 hours to revive ??
---------- Post added at 11:51 AM ---------- Previous post was at 11:33 AM ----------
Sergiocubano1 said:
Lol I was not allowed to enter anything the phone was dead, or do not understand, the phone was dead for 4 hours without turning on and without anything, although it will connect to the PC appeared on it but the Phone did not turn on or anything
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
Ty bro n u r Cubano from Clan GSM ??
Hi! Did you found any working solution @whyphyrl?
I'm having the same issue, the bootloop on the first screen.
Manage to enter edl mode for a quick time, before it starts to charge again, but I can't find a flash tool.
Hope to hear from someone soon. Thanks! : )
---------- Post added at 09:35 AM ---------- Previous post was at 09:35 AM ----------
Hi! Have you found any working solution @whyphyrl?
I'm having the same issue, the bootloop on the first screen.
Manage to enter edl mode for a quick time, before it starts to charge again, but I can't find a flash tool.
Hope to hear from someone soon. Thanks! : )
I send it to an service center thex fixed it for free now its working

Categories

Resources