[Q] Xperia Z2 Tablet SGP512 Won't Boot - Xperia Z2 Tablet General

I unlocked the boot loader through the official Sony Developer site to upgrade to Android 4.4.4. Emma wouldn't let me in so I figured I should boot into recovery to do all the wiping. I held volume down and power and then my tablet stays off. Nothing to display, no LED lights, my PC won't recognize it, and just nothing. I think my tablet is bricked. Can anyone fix this?

Related

[Q] Black screen after downgrade

I was running Cyanogen 6.1 on my HTC Dream fine, after that i decided for full downgrade. So i searched google for it and found the cyanogen wiki for doing it. I followed each step and after flashing DREAIMG.NBH to my phone, it restarted. And so it entered a boot loop. I took off the batery and then tried to enter recovery or the bootloader.When powering the phone normally, i see the T-Mobile logo, and after that, the screen turns black. Whenever i try Camera + Power, after the logo it goes to black screen. Home + Power points the same thing and so does back + power. Fastboot doesn't seem to work even though i have all drivers properly installed and the Android ADB Device shows under Device Manager.
I know i messed up because i didn't wipe before the downgrade. If there is any possibility to repair it? If so..what is to be done?
Thank you in advance!

[Q] Need help - HK MX 030 won't boot

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

Stuck in logo after flashing stock. Can't boot into recovery. PC doesn't recognize.

So, I rooted and tried flashing the stock ROM (from Sammobile, same country, same exact model [SM-G950F], I already had the stock ROM and had never flashed anything else to the phone other than root, June security update, my phone had July's) to see if I could fix a problem that couldn't be fixed with any other method I had tried.
Everything in Odin seemed to go well, I got the PASS green box at the end. But then the phone couldn't go pass the Samsung logo when booting up. I left it quite a few minutes, before trying to boot into recovery mode and wiping data. Only to realize that I couldn't boot into recovery mode. In fact, I can't even turn the phone off. No combination of hardware keys works other than power button + bixby + vol down, to get into download mode. But that's of no use, because when I plug my phone into my PC (with the same cable and port I used before to root and flash the firmware into it) it is not recognized by Odin or the PC.
It just has the Samsung logo flashing slowly over and over because I can't turn the device off. By the time the battery dies out I'll most likely have the logo burnt into the display.
I also haven't been able to find any help online. Everyone's suggestion is “boot into recovery and wipe data”, but I can't do that.
Is my phone gone for good?

Bricked L1 G3312

Hello,
I used TWRP to upload custom rom and it was ok.
Unfortunately (can't remember what anymore) it suddenly stopped on sony logo and it is like that till now.
I used the correct TWRP (HERE v5-twrp-l1.img)
I can enter fastboot and flash boot mode. I have uploaded various ROMs, locked the bootloader via flash tool to use Xperia Companion. It uploads the software and unfortunately it continues to loop on the logo.
Flash tool uploads correctly, but no change.
When it is connected to the charger it vibrates 1 time, turns on the logo and again
I used this topic https://forum.xda-developers.com/t/guide-recover-2012-and-newer-xperias-from-soft-brick.1849170/
Is there anyone who can help me?
facing same issue. started while back when i did factory reset while in lineage os 14.1. nothing i've tried helped. flashtool upload correctly. same with Sony Emma. after locking bootloader, even Sony Companion does everything like it should. but still loops with white Sony logo.
Using Xperia L1 G3311

Lenovo Yoga Tab 3 Plus YT-X703L Bootloop.

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?

Categories

Resources