Hey guys,
I have a Tegra Note 7 tablet from advent in 4.4.2 version. After I (mistakenly) modified some files my tablet didn't wanted to boot anymore. I decided to send it on fastboot and flash an old backup I had.
This backup was a 4.3 version. Everything went fine but now after the boot screen I have the welcoming message and on top of that the Shutting down pop-up window (the one that pops-up when you press the button to turn the tablet off). It then shuts off and I can't do anything to sop it.
Did anyone ever experienced the same problem? Do you have any idea that could fix the problem?
Thanks,
BTW, the tablet is rooted and BL unlocked.
EDIT: Fixed by flashing back on 4.4.2
Related
Im running the stock ROM, rooted, wanted to back it up before I install Paranoid Android, restarted to bootloader, chose Recovery Mode (mine is CWM, flashed with mskip's toolkit), and suddenly it froze on the unlocked bootloader's screen ("Google" and the opened lock underneath). Hardware buttons don't work, the computer doesn't see the tablet. Is there a way to restart it and fix the problem? Thanks for your help.
Edit: Solved it, long pressing the power button for about 10 secs restarted it...
Hi There,
Shortly after updating my Nexus 4 to 4.2.2 OTA today the screen went blank and I've been unable to get it to function correctly again.
The phone is still showing some signs of life, I am getting notification LEDs and I am unable to unlock the phone with facial recognition even though the screen remains blank - I can tell from the vibration and the LED stopping that it has unlocked. Pressing the power button to lock it starts the notification LED again.
I have tried a hard boot (Volume Down + Power) and the screen did come on to display the google logo followed by the X but as soon as they had been shown it returned to a blank screen.
Does anybody have any ideas of what this could be or how to solve it or should I contact Google in regards to this issue?
Thanks in advance for any help
seems like the OTA update has corrupted somewhere. You should reboot into bootloader and use fastboot to flash the stock 4.2.2
Is there anything else worth trying before doing that? I wouldn't have a clue where to start as this is my first android device
Ok so I got it working but did lose all my data. If anyone else comes across this issue I had to boot into recovery mode and do a full wipe/factory reset. The first time i did this the phone started up with no problems but during configuration when I entered my Google account the blank screen strangely returned so I again did a full wipe in recovery mode, skipped the 'set-up google account' step and then entered it manually later in settings once the device had started up.
No idea what caused this and if its a bug in 4.2.2 or an issue with some settings in my google account that are being backed up and restored to the phone but either way I had no problems until 4.2.2 update installed and the issue occuring even after first data wipe rules out any third party apps being the cause.
I had a similar problem after updaing that the screen stay blank and it wo'nt unlock
As soon as i disable the bluetooth the problem solved.
It's happened when i paired it with my pc
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
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
PIT files
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
Is the battery original? If so, it's possible the battery could be reaching its end.
Reddog090 said:
Hey all,
Just some details before the background.
I was running a stock with a unlocked bootloader for a while now. I basically only use my nexus now to watch netflixs and HBOgo. Got the tablet over four years ago.
This morning after it's nightly charge I went to unlock it and it froze up. I rebooted it, noticed the date was off (Jan 1st) and froze after I unlocked it. Reboot again, it made it to the screen where it was optimizing my apps but the screen starting flickering and having artifacts, and powered off. Now it will power itself off 5 or so seconds into the boot animation.
I've tried going into recovery via the bootloader but when I select it and hit the power button it just turns it self off. I then used the nexus toolbox to reflash a stock rom (along with a factory reset), and TWRP. I tried booting up again and same thing. I then went into TWRP and start troubleshooting, but the screen is starting to flicker and have artifacts, then powers off.
Is the hardware dead on this?
Sorry for the jumbled mess of details, i've been bouncing around trying to troubleshoot/fix this.
Click to expand...
Click to collapse
I have been having a problem with my note 4. When ever the phone is powered down and powered back up it reboots normally. I see my lock screen and everything is fine. The problem is when the phone locks either by the power button or just by screen time out. It stays a black screen even though i can swipe my my finger and hear it being unlocked. They only way to fix it is to take the battery out and reboot it then everything is good until i lock it again. Any help would be appreciated thank you.
Sorry me again just wanted to ask another question. I rooted my note 4 after this problem started happening. I used cf-auto root so from what information i have seen im still running stock recovery justed rooted. I was wondering can i flash a Samsung software upgrade without any problems. My problem with the black screen started after an software update so i wondering if i could flash and reinstall the update to see if that fixes my problem. Once again thanks in advance for your help im just trying to save my phone and hoping its not a hardware issue.