[Q] Phone doesn't boot up - T-Mobile myTouch 4G Slide

Hi everyone.
I have a problem with my phone, I've used it over 6 month without any problem, firmware was custom. Several days ago I found, that icon for FFC disappered, then sometimes the phone was freezing. But it happened not so often. Today the phone was freezed, i've removed the battery and restarted it, but it's showing only first logo and then it's restaring again. I've tried to enter to Clockwork Mod Recovery, I've entered to it without problem, but then the problem freezed and it doesn't react at any key.
Also I've tried to flash boot.img from my present firmware, but it didn't give me success.
Please advice, what else can I do and what's the problem. Tx

Related

[Q] Galaxy S - MIUI ICS problem

Hey xda.
Recently I flashed my GS with this rom (http://forum.xda-developers.com/showthread.php?t=1449156&page=), but just in a older version(pre-alpha) and after probably a month of use I began to experienced at lot og bugs and suddenly crashes in apps and programs. I decided to do a reboot,battery pull or wipe cache to see if that clould do it, but nothing help. On the contrary, my phone would not start. The Galaxy S logo showed u, but when the miui xiaomi.com logo showed it bootlooped. Several reboots did not work, so i decided to mount usb from recovery and download the newest version of the rom and then try to flash. I did not wipe, but i worked just fine and i thought i had my phone back, but after little over a day of use the screen began to flicker and blink, and no programs nor apps worked, just crashed. I flashed again again but nothing worked, and now i'm stuck with the same problem as before. bootloop..
So have anyone experienced the same or does anyone have a solution for this problem?

[Q] Need Help! Boot Problem.

Can someone help me. I am current facing a difficulty on booting my device. When I turn it off, I cant boot it without first removing the battery for let say 10-15 seconds and then replacing it and boot it on. Sometimes I can boot it using that procedure once but sometimes it only boots after several attempts. I already flashed different roms and even restored to stock but to no avail. I dont know if it is software related or hardware failure. Funny thing is, once the phone booted, I am not having any problem using the power button to lock, unlock or turn off the phone. Somebody help me please.

Galaxy s6 G920v stuck in bootloop, have tried everything

Hi guys, so recently I bought a Galaxy S6 Verizon off of eBay. I got it for fairly cheap because it was stuck in a boot loop. I usually have no problem fixing stuff like this, but this time is different. So the first thing I tried when I got the phone was to do a reset and cache wipe from recovery. I rebooted the phone and it showed a screen that said "Android is starting, optimizing app 9 out of 31." when it got to 21 the phone rebooted and went back to 9. It did this several times before I attempted to wipe/reset again. I then downloaded the tar file G920VVRU4CPH1 and flashed it in Odin. I did a manual reset before the phone booted, and it is doing the same thing again. reboots to a green screen where it tries to optimize apps, stays there for about 20 seconds, and reboots over and over again in the same cycle. I have tried all other stock marshmallow roms that i can find, Odin won't flash older ones, (assuming its not letting me downgrade). Also another weird thing, every time I flash, the blue update screen goes to 32%, stops, erases, and reboots. Phone is on 6.0.1 version MMB29K.G920VVRU4CPH1 as seen in recovery. Any help would be gladly appreciated. Thank you!
I am having a similar problem with loading new rom. The farthest it gets is 32%. Sometimes it doesn't get even that far.
I ended up just buying a trashed s6 and swapping the motherboards. Only way I could fix it

UMI Iron Pro - Can't boot or access recovery

Hey guys,
I have an issue with my Iron Pro, basically I turned off the phone one day, went to turn it back on and the UMI logo showed for 2 or so seconds and the device turned off again. I can access the bootloader but the same issue occurs when selecting recovery. I have tried reflashing the device several times with different roms (custom and stock) using SPFT with no success. However, after leaving the battery unplugged for a long period (3 or 4 days?) of time the device booted so I thought it was all fixed, went to restart and... guess what happened. I can't use fastboot to reflash because I don't have a custom recovery nor when I do flash one it still doesn't work. I believe it may be a hardware fault at this point. Any help or advice would be appreciated. Cheers

Random crashes

Hi everyone,
Someone asked me to fix his phone and i'm stuck. The S7 is crashing randomly (black screen) and after a crash, it cannot be booted until the battery is dead (even by pressing power +home or power + vol-) and charged again. I don't know how to fix it and i'm stuck at this point.
Here is the story behind it :
The phone wrote the famous "moisture" message and then won't boot up. He never put it in water. So he put it in rice but it didn't work. The owner of the phone took it to a fixing store in Thailand where they changed the battery. After a day, the phone crashed and we send it to Samsung Thailand who told us a high cost without explanations so they didn't fix it and we got it back.
Hopping someone can help me about this problem :angel:
Update :
A deep-clean flash () got me stuck into "no command" and pushing vol+/vol-/home didn't change anything, it just bootlooped.
So then i tried installing TWRP 3.1.1, it's a success but after installing LineageOS 14.1 and booting the phone crashed at bootlogo and won't boot up again...
Another Update :
I finally managed to get it working saturday, but it crashed just today and it's the same. It crashed in a lightweight app with no app running in the background. I'm thinking of a material problem :/
New update, still hoping someone know how to fix this:
I tried to flash stock firmware over and over but it keeps crashing at the end of the boot animation... I'll try an oreo firmware, hope it'll fix it

Categories

Resources