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?
Related
It's an AT&T S5. I messed with the build.prop to try to spoof another phone, and wound up having the Android UI appear tiny and crash whenever I booted to the home screen. I tried to fix this problem by flashing earlier stock firmware with Odin, but now my phone freezes every time it boots up. It will load until the Samsung logo animation, then freeze mid-animation, and the screen will go black with my led light in the corner blue. I have to pull the battery out.
Every soft brick solution I see is to flash stock firmware, but it doesn't seem to be working. I flash G900AUGU1ANCE 4.4.2, the AP, CP and CSC files, but the phone still boots up with the the CUSTOM appearing at initial boot with the unlocked padlock graphic. Usually that goes away after flashing older firmware. SO despite flashing older firmware, it still boots and freezes. I can boot into Recovery mode and Download mode, so the phone is not all the way gone. I try wiping data and cache in Recovery, but that doesn't fix anything. I am at my wit's end. Can anyone help fix this?
QUOTE=RageKage14;59207198]It's an AT&T S5. I messed with the build.prop to try to spoof another phone, and wound up having the Android UI appear tiny and crash whenever I booted to the home screen. I tried to fix this problem by flashing earlier stock firmware with Odin, but now my phone freezes every time it boots up. It will load until the Samsung logo animation, then freeze mid-animation, and the screen will go black with my led light in the corner blue. I have to pull the battery out.
Every soft brick solution I see is to flash stock firmware, but it doesn't seem to be working. I flash G900AUGU1ANCE 4.4.2, the AP, CP and CSC files, but the phone still boots up with the the CUSTOM appearing at initial boot with the unlocked padlock graphic. Usually that goes away after flashing older firmware. SO despite flashing older firmware, it still boots and freezes. I can boot into Recovery mode and Download mode, so the phone is not all the way gone. I try wiping data and cache in Recovery, but that doesn't fix anything. I am at my wit's end. Can anyone help fix this?[/QUOTE]
I'm having the same problem after installing and using the TWRP app on my ATT S5. I tried reflashing the stock rom using odin and it says successful but the phone never boots. It only makes it to the Samsung logo then the screen goes black. I've heard that if the phone is on lollipop which mine is you have to downgrade to kitkat first then flash the stock files.
If your fone boot in recovery perform a full vipe and format system and after go in download mode end use odin for flash all file bootloader, modem ,PIT file for partition find the pit file for ur device modell in xda
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
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.
Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.
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?