The screen stays black, I think system is booting because I can hear unlock click if I press the power button. Also notification led indicates charging when connected.
-in fastboot mode the screen is black too, but fastboot sees the device, though the name is different than before the brick.
-In recovery all I can see is black screen.
Now, here's how this happened:
-I got the phone, updated firmware to 323
-Unlocked successfuly with unofficial unlock
-Tried installing TWRP to no avail - The process seemed to go through fine, but no TWRP, just stock Asus recovery. Tried multiple times, tried rebooting straight to recovery from fastboot, tried on different computers. Weird thing I noticed was that write time in fastboot during the process was like 0.001s, which led me to believe it thought it was writing TWRP, but really wasn't for some reason.
The screen stays black i flash fastboot rom by adb , stock recovery by adv but the mobile is still same
Related
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.
Hello, i have a big issue with my friend's old phone, i really did not want to open a new topic, but i'm desesperate.. Here's the cause of my headaches below.
I don't know what happened to it (neither does he know) but it is in bootloop since years ago, as i can tell by the current android version(Lollipop).
When the phone turns on, the asus static logo appears for a few seconds, then a blue screen blink quickly and reboot.
Sometimes the asus logo animation starts for milliseconds and reboot.
I already tried to flash the stock firmware (almost all WW versions), but the problem persists.
The phone doesn't accept any marshmallow firmware, only lollipop.
I already tried all tutorials that i found, flashing .bat files with phone .imgs, flashing full firmware throgh adb sideload, apply update from sdcard, nothing works..
If i flash twrp, when boot recovery, the phone reboot instantly in fastboot mode.
The bootloader is locked.
Any ideas?
Hello!
I just repaired the display of my OP2 and when turning it back on it went straight into bootloop. Only showed the OP Logo and android on the bottom. ADB obviously doesnt work and tried to all partitions via fastboot to get fresh start. After completely resetting I unlocked the bootloader again just to be sure. Then I tried to flash twrp 3.2.1-0. it say dtb not found error. I tried a twrp 3.0.0-0 and it said succesfully flashed but after automatically rebooting the screen just turns black. I can the into fastboot mode or into bootloop can't do anything else. I also tried the MSM8994DownloadTool.exe but it just returns into bootloop again or turns black.
Help pls
Hi all,
I unlocked bootloader and tried several custom ROMs. Then I came back to ColorOs 5 version A.15 by converting ozip to zip and flashing from TWRP (twrp-3.4.0-20200610-RMX1801.img) but then I made a great mistake. Without upgrading the stock ROM, I directly wiped 5 and flashed PixelExperience android 10. Upon reboot after a momentary "Realme" splash screen the phone turned off. It can't boot or bootloop, it can't boot to recovery or even bootloader. The only time the screen ever shows a momentary splash screen of Realme is when I long press and release power, thereafter pressing power+volume up. Otherwise it looks dead. The PC can't detect any adb or fastboot interface, only the interface as in attached picture is detected. I think it is EDL mode. At this pandemic situation it's very difficult to access service center, and even if I can, they'll probably flash Realme UI, thereby making bootloader unlock impossible. The most pathetic situation is that I have the ofp file version A.17 for EDL flashing but no virus-free and authentication-free tool to do so. After searching for hours I am asking for your help, if there is any.
EDIT: Nevermind, problem solved by trying different key combinations.
Please HELP
I am writing here the whole story.
I unlocked the bootloader of my Asus zenfone max m1 (3/32GB) using the unlock tool which I downloaded from Asus's website.
Then, I went to fastboot mode and flashed TWRP recovery and then tried booting into it through the cmd screen using fastboot boot twrp.img command and it worked.
Then I followed a really good tutorial and flashed the pie firmware, Pixel Experience and magisk and ZIPs in order.
And it showed no error, everything was fine and then I clicked on the reboot system button, it rebooted the system but the phone was stuck at the google logo with a loading bar and didn't go beyond that even when left for 30 mins and I tried rebooting the phone multiple times and that did not help. the phone was stuck at the google logo every time.
Then I turned off the phone and tried going to TWRP to flash the pixel rom again but the phone only went into fastboot mode, it never booted into recovery even though I tried multiple times(I was trying to boot into the recovery through the volume and power buttons, not through fastboot mode).
I flashed the phone's recovery multiple times and also the boot image (I even tried flashing the stock recovery) but the problem is that everything goes fine in the terminal, it shows that it flashed the img file successfully and it is finished but the commands like fastboot reboot recovery don't work at all, they all just reboot the phone normally and the phone just shows the ASUS logo for few secs and then turns off.
Note: I used fastboot erase commands to remove the pixel experience rom and now I'm only left with a phone which boots only into fastboot with no rom and I don't know about the recovery because it shows that it flashed but it never opens.
Hi
I am having a similar problem in that I can oly get into recovery mode with adb reboot recovery. I researched and tried all possibilities with the phone key but I can only go into bootloader mode.
After flashing recovery successfully (?) I can only boot the phone normally and that seems to reinstall the default recovery manager.
While researching I found that there are some discrepancies with the ID out there. While my phone is a Zenfone Max (M1) with the ID X00PD some places (TWRP) confirm that but others refer to Z555KL.
Did you get any further?