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
Related
After a year of playing with Galaxy S3 I got bored with constant flashing and well, I never got used to onscreen keyboard.
I wanted a phone that will just work and decided to go for a Droid Pro+. Device was form Germany as there is no official distribution in Poland. It worked like a charm for two weeks till just now.
While playing with it (changing ringtones and stuff) I got several messages about services failing - com.service.usb, com.service.google, etc.) As it happened before (but only com.service.usb) I restarted it - in a normal way - power button and then Reboot. It rebooted and after that got stuck on M logo.
The firmware was as stock as it could be. No modifications were made. What's strange, the device can't be hard resetted. I can hold the power button for several minutes and it won't turn off.
Recovery mode works, but wiping does not help. Fastboot also works, but RSD Lite shows N/A in every column of Device info. I flashed GB 2.3.6 (5.5.1Q-110_ELW-TA-36-65-release-keys-signed.Retail-en-GB.tar) found on XDA. The rom itself should be OK, as no functionality was lost (recovery and fastboot), but the device still hangs on the boot logo. Device info is still N/A.
Could it be a hardware malfunction or is there something else I could try? Warranty is probably not an option since as i mentioned there is no official distribution in Poland. Any help would be appreciated since I'm out of ideas by now... Also, does anyone know if the battery is charged when in Recovery or fastboot mode? Connecting to a charger ends up on the M logo. And because very few people in Poland have Moto devices I have no other way to recharge the battery.
Hi,
I have a N4 that was new but the screen cracked on it and eventually the battery died as well (wouldent hold a charge). I got the battery and screen replaced but as soon as this happened I could not boot into any rom. I had twrp installed but everytime I tried to install a rom such as CM it would install but would stay stuck in the boot loader. I then used NRT to try and kick it out of bootloader and I tried several different stock firmwares, 5.01, 4.4.4, and 4.2. The only rom that was able to get past the boot animation was 4.2 it went to the welcome screen to choose a language but I could not select anything via touch screen. In that screen I could lower and raise the volume via the rockers and turn the screen on and off. I had twrp installed and the touchscreen worked fine in twrp. I also tried this: http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060 and it also let me get into the developer firmware but of course it is encrypted so I could do nothing. The phone has not had contact with water etc. Do I have any other options? Can I get some type of diagnostic such as logcat or something?
Thanks!
Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
Hi guys,
hopefully you can help me or link me to a thread with some help.
After 5 years my g2 broke down last week. I had the official Android 4.4.2 and have never flashed anything. Don't know if it has anything to do with it but i didn't have any free storage left of my 16gb (european version, so i gueass D802). The days and weeks before it warned me that i used all the storage and some apps won't work properly ( I didn't care because I ran without problems for month)
My phone broke down and now I am stuck in the boot loop. When I disconnect the battery on the back and then connect it again and plug it in my laptop the LG Logo will appear and the phone will charge. No Problem there, I still have battery left. When I try to turn it on the LG Logo will appear and then the display turns black, you know how this goes.
I can not enter the recovery mode nor the download mode. My Laptop wont recognize my phone on the device manager or somewhere else. What my laptop does, is that the typical windows sound comes when I plug the G2 in and then after some seconds the sound comes again when the phone turns black.
Then I got a error message:
Kernel Crash! DemiGod Crash Handler : Kernel Crash!
From there I did not reboot successfully. How can I get a Kernel Crash with the normal Android Software? weird.
All I care about are my pictures left on the phone. I was dumb enough to not make a backup. Do you know a way to save my pictures? Can I somehow exchange the storage chip?
Please help me.