Power button no longer turns the screen off. - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

I am running the stock MJ7, rooted with Kingo, and I have encountered the strangest thing. I had originally had MJ7, rooted, and I went into sytem/media and changed samsungboot.qmg and samsungbootloop.qmg to .bak files so I wouldn't have a boot animation at all. Everything went fine, and it was great. Then I installed Beans 2, and decided I didn't like it, did a full wipe, and installed the stock rom again. I did the same thing with the boot animation and my power button will no longer turn the screen off. I changed the files back to regular .qmg and my power button works just fine.
Does ANYONE know why this is happening? I really hate the boot logos, especially the Verizon one and I would really like to get rid of them.

Related

Help, phone doesn't boot (pure stock, not rooted phone)

I'm having a strange problem today on my Desire Z.
First of all, my phone isn't rooted or modified in any way, it's pure stock.
I rebooted the phone this morning and for some reason it doesn't want to boot anymore. All was working well before.
After I turn it on, it's stuck on a white screen with skateboarding Android (see attached file). I waited, and waited (over 15 mins) but nothing happens.
Since I can't turn it off, I pulled the battery and restarted the phone. Same thing happens over and over.
I tryed holding volume down + power to boot into bootloader: it doesn't work either.
Any help would be much appreciated
Thx in advance.

Multi-colored Screen

Hi Guys
When I turn my phone on, after the Galaxy S first screen, the screen is multi-colored for about 1 second before going to the boot animation. Once the boot animation appears the screen is fine.
That's not a problem. What is a problem is booting into recovery, the top of the screen has a few blue lines. It still operates as if it is in recovery, as if I press the power button it reboots - but if I press down once, then power, it's not rebooting. So it looks like it's just the screen can't display what's being sent to it. So I can't do anything in Recovery like installing the auto-phone record, screen capture service or extended power menu. It will also be a problem if I come to install another ROM.
Does anyone know why? It started happening after I flashed a new ROM - I flashed the new ROM because the phone was constantly freezing when running certain apps (and needed the battery removed to restart the phone) - it's no longer freezing.
thanks
I'm not sure but,i think it because you don't have the good bootloader.For example,if you flash a rom from Froyo to gingerbread,you need to choose a rom with the gingerbread sbl(bootloader) include.
So to avoid this problem,just re-flash the entire rom with boot loader included.
Just go there http://forum.xda-developers.com/showthread.php?t=1102881
thanks I'll try that

[Q] htc g2 tmobile no hard reboot

used gingerbreak on g2. Got superuser and everything was great. Now (don't know why) no splash screen, no recovery even holding down volume and power on boot, random screen blackout. tried to re-gingerbreak with no effect. tried hard reset with no effect. stuck in hell please help. phone is stock rom and has no modifications even has all bloat-ware.
p.s. initial problem upon booting screen black but have lights at bottom after stock boot sound hit power twice and phone is active like normal. now stuck like this after each boot and couldn't find anything about the problem after searching. I hope this hasn't been covered before. Any thoughts? I am at my wits end about to get out the light saber and take out my frustrations on the mutt
If your phone is this: http://www.htc.com/us/products/t-mobile-g2/ then you're in the wrong place.

[Q] Phone won't charge while turned off, just vibrates

I had an MK2 ATT Galaxy S4, which I believe has a locked bootloader?, that I rooted a long time ago. Keep in mind I don't know much at all about phones and only managed to do it by following a guide here. So I just switched to T-mobile and gave the phone to a guy in a store to allow it to work on T-mobile, which it does now. I noticed that the version is now 4.4.2 sgh-l337UCUFNB1. So I wanted to root it again. I finally rooted it using the towelroot.apk, after initially trying to root it with the Casual jar file and motochopper, which both didn't work for some reason.
After towelroot installed, I installed SuperSu and titanium backup. I then downloaded safestrap 3.75 and busy box and then installed a recovery. When I rebooted to recovery the phone didn't take me to safestrap custom rom slots, but instead just restarts the phone as normal, but with "Recovery Booting..." showing up in the left hand corner at the first splash screen in small blue text. I couldn't figure out why it wasn't working, so I repeatedly uninstalled recovery and tried the older versions/revisions of safestrap from 3.72 and up, but either the reboot from recovery option was grayed out or rebooting from recovery just restarted the phone like previously.
Now I just noticed that when the phone is off and plugged in with a USB cable, the phone doesn't light up and show a charging icon. Instead, it vibrates every two seconds while it's plugged in. Holding the power button does nothing until I unplug the cable, which will finally allow it to turn on.
I don't know what I've done that could have caused this. Is there any way to restore it? I would do a factory reset, but would it undo the T-mobile network transfer on the phone? I'm not exactly sure how it works when the person at the store switched it from AT&T to t-mobile. Is there any other solution for the vibrating? I'm scared that if I run out of battery, I won't be able to charge the phone again and will be left with a brick.
Thanks in advance. Help is very appreciated! :crying:

Nexus 10 powers off during boot screen

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

Categories

Resources