So as the title says i currently have MIUI 1.6.10 demonSPEED v1.1 ROM and it is not booting, just completely unresponsive to everything i could think of. Im just throwing this out there to see if this has happened to anyone before or if there is a way of fixing this issue. I don't believe it has anything to do with thederekjay's rom just some unfortunate event. Anyway i fear it is possibly bricked and that i am gonna have to shell out the $150 to get a new mt4g from the insurance. Details follow...
So have had this rom for about a week now and has been working great. However this morning i was on the browser reading the news and it became unresponsive. After i let its display turn off (i just left it alone) i used the track pad to wake it. It was slow but it did show me the lock screen. When i attempted to unlock with a swipe down i felt the vibrations but the slide lock didn't budge. I then tapped the power button to turn the display off and tapped the power button once again to turn it on but nothing, just stayed black. I tried a soft reset by removing the battery, placing it back in, and powering back up. When i did so the t-mobile mytouch 4g boot image w/ the white background came on then went to an android image (lighting up a through d, looping) but then it just remained at the android image for five minutes! So i tried a soft reset again but the same thing would happen, act like it was gonna boot up completely but then gets stuck at the android image. So then i tried removing the battery and booting into recovery (via power, vol down, trackpad) that time the t-mobile mytouch 4g image would appear but after that the screen went black and after that every attempt with either the soft reset or boot into recovery wouldn't do anything at all, just a black screen as if the battery wasn't in at all. Its been like that all day and i can't figure it out so if anyone knows some info i would greatly appreciate it thanx
I've had my tablet going on 3 years with never a problem...last night I was using it at work, went to text on it with the Swype keyboard and it totally froze. I waited for about 2 minutes to see if it would just release the freeze but it didn't. I held the power button to just do a reboot and it stuck on the Acer screen. After playing around with it a few minutes I got the android screen up, but it froze there. I've done the hard factory reboot, then tried the Power>Vol - > and rotate toggle...now my screen is stuck on "Bootloader v0.0312-ICS: Starting Fastboot USB download protocol"
What now...I miss my tablet :crying:
thanx
I have the strangest damn problem on my phone. Sometimes, when I press the power button to turn the screen off, the phone just shuts down completely and then when I try to reboot won't get past my splash screen. When this first happened I couldn't get the phone restarted at all, even by taking the battery out and waiting for over 10 minutes. Everytime I tried booting it would go to the splash screen and then blank back off. It would do this once and then I had to remove and replace the battery just to get it to boot to the splash screen again. I thought this might have something to do with having a custom rom installed (sacs custom), so I played around with the phone and managed to get it in Odin mode. I then brought the phone back to stock. Everything worked so I figured I had fixed it, but then after pressing the power button one time I got back the same problem. It shutdown and would not restart past the splash screen. In retrospect, I think when I pressed the power button the screen did not immediately go off and so I clicked it a couple times in a row before it crashed, that may be what triggers it, b/c sometimes i press the power/screen button and it goes off without incident.
So, now I had the phone back to stock and had the same problem. It turned off and would not boot past the splash screen. By a stroke of good fortune I figured out how to get the phone booting again past the splash screen. When the splash screen came up, I started repeatedly touching and swiping at the phone; drawing little circles tapping at it, etc... When I did this the phone continued to load and boot up normally.
I installed AVG antivirus, to see if maybe there was malware on my phone. Scans showed nothing. I updated all of the software as well. I now have an app installed for turning off the phone instead of using the power button. This of course is not an ideal situtation, why should pressing the power button crash my phone like this??
I only use my S4 to listen to Spotify and Podcast, no other apps are present. I use it until I the replacement Headphone thingy comes for my Nexus 5x.
It's my old phone and it worked great until yesterday when my screen went completely pink and then my phone restarted. Now it's stuck on the first logo screen.
Not the Samsung animated logo screen, but the very first completely white text Samsung Galaxy S4 logo, I can't post pictures.
I am using a Cyanogenmod Rom because of the memory leak bug on stock rom.
I can't boot to recovery because it just boots for few seconds, then shuts off, vibrates 2 times and goes back into the boot screen where it's stuck.
The vibration thing happens everytime I try to boot the phone. The logo comes up, it shuts down, vibrates twice and then it gets stuck on the logo indefinitely.
I can boot to Download Mode and I can't boot to Safe Mode.
Any ideas what I could do? I really want to listen to stuff again.
Could be a power button issue. Open the phone, clean the power button contacts with a bit of pure alcohol, quickly press and release the power button several times in a row using a bit more pressure than usual, reassemble the phone, and see if it works.
audit13 said:
Could be a power button issue. Open the phone, clean the power button contacts with a bit of pure alcohol, quickly press and release the power button several times in a row using a bit more pressure than usual, reassemble the phone, and see if it works.
Click to expand...
Click to collapse
It's still stuck the same way.
When I got to the Recovery Screen once, the screen turned yellow and phone restarted.
The power button may need to be replaced. Do you have a multimeter to test the connections?
@audit13: I've got a feeling the power button isn't his issue. On a properly working S4 the screen wouldn't flash a particular color before rebooting. Given that this happened to him suddenly, I think he has an issue with the SoC itself.
audit13 said:
The power button may need to be replaced. Do you have a multimeter to test the connections?
Click to expand...
Click to collapse
I have a almost dead S4 i9515 model here, it stopped working.
Here at home I plugged it in and it vibrated continue and nothing more.
Tried a couple of times to go to recovery (unrooted, so the standard recovery) and one time I got a Samsung logo with something blue in the top left side of the screen and nothing else.
Cleaned the power button and started the phone and got the Samsung boot logo, but it got stuck in the logo loop.
How can I check the power button with a multimeter? Is there a trick to get to the connectors?
You need to remove the back frame to access the power button connectors. There should be there of them. Without the power button pressed, touch the probe across the outer two and see if there is any current being passed.
https://m.youtube.com/watch?v=2l_6fwzuIwA
Will try it this weekend, if it is the button I will just take it out, and try it that way till I get a new button.
Thanks for the tip!
Well, the button was not the problem, see next post
While starting it won't pass the Samsung logo boot,
while starting via recovery (power, home vol-up) I still won't pass the Samsung logo screen, but now with the message in the top left screen 'Recovery Booting...'
It's dead I believe, the power button is okay, but after a few difficult boots, it wouldn't pass the Samsung logo.
But now it doesn't respond at all anymore.
Is there a way to access this phone?
Via adb or Odin? I don't think so, if the phone doesn't startup I can't do anything...?
It is bye S4 I guess...
I am blocked here too with a GT-I9506, and can't fin anything, so yeah, i guess it's dead, mine too
Time for something new...
Anyone managed to revive his I9506? I have similar problem, if you can guys look into it and tell me that you have tried this already:
https://forum.xda-developers.com/galaxy-s4/help/i9506-stuck-gt-i9506-logo-recovery-t3659795
Can't help you there ?
But I am looking for a new motherboard...
HaroldNL said:
Can't help you there
But I am looking for a new motherboard...
Click to expand...
Click to collapse
I think it will be the best way. It's third day of flashing stock firmware from 4.3 to 5.0.1 NEE an TPL. There ware two times that phone actually booted to recovery and green android appeared. But then phone rebooted and still can't get up.
Hello, so I have a J7 2017 (SM-J730GM/DS) 32 GB Unlocked Dual SIM which has served me well for a while. I ended up dropping the phone at some point in a sliver of time without a case and the screen cracked. After replacing the screen I noticed if the screen was pressed in a certain area it would go crazy and reboot the phone (crazy as in the pixels would do weird things like dimming, going grainy, like the display shorted in some area, then the phone would reboot itself), probably some error on my installation of the screen and the ribbon cables (I can see an area where it looks creased, it never sat flush with the body of the phone as the OEM screen did). I was able to just be careful and not trigger the reboot for some good time until it happened again and the phone would continuously reboot, allowing me to only get back to the OS through the boot menu, selecting "reboot now". That worked for a while until it would never boot into the OS, just looping at the screen where it says the phone name, where it would vibrate, go black, and go back to the phone name screen. I gave up trying to fix it, as I had a backup phone, and just now had some ideas. I figure the OS is corrupted in some way, I am no master in knowing the details on how phone boots up and such, so I did some research and successfully flashed the most recent ROM onto the phone using Odin 3.14. It still doesn't stop the looping, unfortunately.
Any ideas? I hear people talking about using TWRP or something to do things boot related, but I don't want to possibly mess anything up further nor do I know what they were talking about.
Thanks,
Stella