Hello. Please. I have a damaged Lenovo k920 at home. The system will not boot showing only the reboot menu. Nova Rom did not help via OTG cable. He doesn't have a PC. Neither does the Lenovo downloader. Do you think the phone is completely dead? I will only get into Lenovo recovery but reboot will not change anything. The update will not take place in the form of OTG - usb. For a quality screen and good performance, I want to use it as an offline screen on a drone. Can you please advise me? The only menu that loads when turned on is the test menu - board, sensor, etc. Format, update, reboot. But nothing starts the system.
Related
Hello everyone!
My brother sent me is MX 030. It is the original Meizu MX HK version with the unlocked bootloader. Two weeks ago, he found his phone had crashed. The screen was black and he powering it off and then back on would not do anything (black screen - only vibrates on power on).
I got it today and first thing I did (after charging it-the charging mode works and displays a battery logo) was boot into recovery mode (or update mode on Meizu phones) and I was able to reach the menu. It let me mount the drive onto my PC. I downloaded the latest firmware and put it on the drive. I pressed upgrade and cleared data. The software seemed to install fine, but then the phone rebooted to a black screen - again.
Then I tried installing older versions which I found on the meizu website. They all install and I can see the recovery mode is different, but they all boot into black unresponsive mode (which drains the battery).
Having had other android devices before, I feel the phone is stuck in reboot loop.. I don't know what else to try or attempt. I feel am running out of options. The fact that the phone still responds to some commands and allows me to flash firmware should indicate that the phone isn't brain dead quite yet, right? Anyone else experienced a similar situation?
Thank you,
Oli
hi dude, can you help me ? my asus zenfone 5 always freeze and reboot, i know how to fix it, but when i read it all thread needed droidboot/bootloader. my phone cant enter droidboot. but i can enter recovery mode, can you fix it ? any tutorial ? help me pls
Make a backup, then reflash stock rom
Random reboot, freeze then stuck at charging mode
Anyone have this problem ?, my phone always like this. It always hang then reboot to charging mode, phone only can be started when charger are detected, then press power button. Phone start normally (without charger), any solution for this ?
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Pwoper said:
Tried to install a custom ROM on my old N4 via Toolkit but got a bootloop on the Nitrogen logo. Right after the screen the phone would turn off. So, i rolled back to stock rom, unrooted and everything but now it seems the problem its even worse: the boot doesnt go past the Google logo. When the phone is charging i can access the recovery and even boot into Android. Off the charge it looks like i cant do nothing other than go to fastboot. If i choose the recovery option the phone turn itself off. I tried to install other ROM via TWRP when charging, but right after 2 seconds after the process begins, the phone turns off.
I think it may be a battery problem, but i wanna make sure it is so i dont waste money.
Thanks
Click to expand...
Click to collapse
hi buddy, problem is also happend to me, unfortunatly its not a software issue , its a battery problem, and its only fix with changing battery or you could turn on airplane mode (to turn off radio and only in custom rom) and keep using the phone offline.
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Angel Hyerald said:
Hello friends, I have a similar problem with my nexus 4.
I can use the device well if it is connected to a USB or plug. (If the device isn't connected, this turns off). But I can use TWRP without problems (works without connect to a USB or plug), I can install ROMS until finish, but when I want to start the system, only stuck on Google Logo and the device turns off (I tried to start the device but just stuck in Google Logo and turns off again) But if it is connected to a USB or plug works well without problems.
I tried to install all STOCK roms too but only work well when the device is connected. I think that isn't a battery problem because I can use TWRP (without connect to a usb or plug) and install every rom.:crying:
Someone would like to help me. Thanks a lot.
Click to expand...
Click to collapse
i told just above your post,that is a battery problem and only fixes with changing battery, the reason you can use twrp is that the voltage needed for boot phone in recovery mode is less than for booting the whole system with apps and radio functions
Hi guys!
I need your help with my Moto E4 Woods. I left it charging overnight. In the morning, it had a black screen. I tried pushing the power button with no result. I removed the battery and tried to boot again with no result. I thought that maybe an intervention in the TWRP recovery is needed (yes, it is rooted). When I try to access recovery, I have the screen working in the fastboot screen (or whatever you call the screen where you select to launch recovery, factory reset, start, etc...).
Whenever I choose recovery or start, nothing, black screen!!!
It was working on stock ROM, so I flashed it again using SP flashtool. Still the same issue. It works when I push Vol- and power, just to let me choose recovery or start then dive in darkness again.
Could it be a software issue? or hardware? what makes the screen work in fastboot mode then refuses to work when I select start or recovery or even push the power button normally? I might have thought the screen needs replacement, but it works just fine in fastboot. It is really annoying me and would really appreciate your help in the matter.
Thank you in advance!
Up
Hi
I'm facing a problem with my tablet. It shut down after official update and gets a bootloop. I'm not able to get into recovery mode beacuse when I press power+vol up it gets stuck on Lenovo logo. I was able to enter a fastboot mode so I decided to flash ROM. I tried official Lenovo assistant and Qfil + Many roms (stock, dumps from other users) but I always gets a bootloop. I can't turn off a tablet, because it turn on by itself and gets into bootloop until battery dead. What is a cause? How to fix it?
Update: I leave it plugged in to PC via USB cable and after many bootloops my PC shows tablet as a hard drive (I was shocked). Then tablet shows animated Lenovo screen, then Lenovo screen with Snapdragon and finally on screen I saw menu with language selection. My joy was short, because right after choosing language I get a information: Battery temperature is to low. Charging has been stoped" Then tablet shut down again and goes to many bootloops until it will turn on again with the same information. Is this a battery problem?