someone please help me, i did the full GPE conversion in september and all of a sudden for the past few days my phone screen wont turn on after i take it out of my pocket and sometimes restarts on its own. i reset the phone and still nothing. i want to know how can i turn my phone back to stock with s-on and the rest? i think i have to return my phone. as of right now its a gamble whether i can turn my phone on. i have the stock 531.11 downloaded but not sure how to go about it since my phone can shut off on me suddenly. i really don't know what to do. phone was great until it got the 4.4.2 ota, after that it started to act weird and got worse. weird thing is when i do root check it says the phone is not rooted. s-off though and i tried to change "unlocked" and get s-on so i can get it fixed under warranty but only thing i was able to do was to change it to "relocked" since the phone shuts itself down.
when the phone screen is off, i dont hear any phone rings if i call that phone from a different number, but my pc recognizes it when i connect it with the usb cable with the screen off.
ayk07 said:
someone please help me, i did the full GPE conversion in september and all of a sudden for the past few days my phone screen wont turn on after i take it out of my pocket and sometimes restarts on its own. i reset the phone and still nothing. i want to know how can i turn my phone back to stock with s-on and the rest? i think i have to return my phone. as of right now its a gamble whether i can turn my phone on. i have the stock 531.11 downloaded but not sure how to go about it since my phone can shut off on me suddenly. i really don't know what to do. phone was great until it got the 4.4.2 ota, after that it started to act weird and got worse. weird thing is when i do root check it says the phone is not rooted. s-off though and i tried to change "unlocked" and get s-on so i can get it fixed under warranty but only thing i was able to do was to change it to "relocked" since the phone shuts itself down.
when the phone screen is off, i dont hear any phone rings if i call that phone from a different number, but my pc recognizes it when i connect it with the usb cable with the screen off.
Click to expand...
Click to collapse
so last night i got the phone to work again and i woke up everything was good until i was transferring files to the phone from my pc and one file did not transfer and a message popped up on my pc to try again or cancel, i hit cancel and my phone screen turned off and would not power on until i had a flash light on it and pressed the power button. i really dont know what to do. in the off screen state, if i disconnected it from the usb it and connect it back my pc recognizes it and the folder opens up like it would normally.
Related
I picked up a used Vibrant last week and it initially worked fine. However, it still had 2.1 installed so I decided to update to 2.2 with Kies Mini. After 4 hours of screwing around and with it and much searching of forums, I finally got it upgraded, but something seems to have happened to the phone in the process.
The phone acts like the USB is permanently on, even if no cable is attached. The USB plugged in notification stays on even when the cable is unplugged. After I charge the phone and unplug it, the battery indicator continues to show that it is charging. The main problem is that the phone gets stuck in some kind of loop when the phone is turned off and never truly turns off. Initially, what would happen was that the little loading circle indicator would appear then the battery charging icon would pop up for a moment. However, since there was no cable plugged in, it would disappear. After several seconds of a black screen, the loading circle would come back up. This loop would simply continue over and over. Pulling the battery and putting it back in did nothing; the loop would just start over again the moment the battery was inserted. The phone would not respond to the power button while this loop was going.
At this point, I was still able to get the phone to boot by plugging in the USB cable, waiting until it started to charge (with the green battery icon) and then hitting the power button. This went on for several days. Today, I decided to take the battery out for several hours to see if anything would reset. However, things only got worse. The loading icon still pops up but now the charging icon doesn't come up, even if the USB is plugged in. I just get a loop where the loading circle pops up, disappears, comes back, and so on. I am now also not able to power on the phone with the power button.
I am still able to get into download mode (but not recovery mode) so I flashed everything back to stock using Odin and the instructions on this forum. This does get the phone booted back up, but as soon as I turn it off again everything starts all over.
So now I have a phone that, if it is ever turned off or loses power, has to be reset, wiping everything in the process. Does anyone have any idea how to fix this? Is it some kind of bootloader issue?
Odin, put 2.1 stock rom back.
Like the post before me mentioned, Odin back to stock 2.1
And personally, I'd much rather install stock froyo with ODIN rather than KIES.
Or just use a Custom ROM altogether.
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
mordrid52 said:
As I mentioned in the original post, I've already restored the phone with Odin several times and it has absolutely no effect. It allows the phone to boot once but as soon as it is turned off again the loop starts over.
Click to expand...
Click to collapse
I have heard of KIES updates screwing phones before! I would contact T-mobile and tell them the situation....letting them know its used and had stock T-mo 2.1 and after using KIES to upgrade to 2.2 it screwed your phone.
Eventhough its used and You didnt buy it from them, they would probably fix it for you for free since their update program caused the issue...If it was a stock phone then they will probably fix it.
edit: in your story to them, leave out the part about you using ODIN...i am sure they will call that a void of the warranty.
So I hopped on a plane today, turned off my phone as required. Landed, and tried to turn it back on, but nothing happened. Thought perhaps I'd not successfully turned it off before and the battery died during the flight, but I got back to my hotel room, connected the charger, and still nothing. Waited for a while to let it REALLY charge, and nothing. Phone is completely unresponsive, will not turn on at all.
I'm going to try to run it by a repair center in the morning since this seems to be a hardware issue, but I thought I'd ask here to see if anyone had any wisdom. Phone is completely stock, unrooted, by the way.
TIA for any insight.
Were you running a custom ROM? Did you flash anything recently? If you plug it into a pc does it try to install a driver for qhusb_dload?
BTW, you don't need to turn it
off completely They just don't want to put in the time, effort or money to figure out what (if anything) interferes with cockpit equipment. I fly a couple of times a month and always just put mine in airplane mode...pretty sure my phone has no effect on anything going on up there from back in row 19.
Sent from my EVO LTE
So ive been using JMT since the v8 and ive never had a problem before. One night i decided to get the X1 and everything seemed to well..the next day i was chargin my phone and i noticed that the phone was off, the chargitng icon was not showing.
I turned to phone on and it would go halfway the splash screen and then it would go black.. then it would start vibrating the way it vibrates when u turn the phone on and it just does that. I tried doing a battery pull but everything that i put in the battery the phone turns on automaticly.
Ive tried going to recovery but it just wont go in. PC doesnt detect the phone and it looks like theres a 5 second gap before the phone does the same hthing over and over.
I dont know what to do because the phone doesnt let me do anything.No recovery,no nothing.
could somebody help me please?
what can i do!? any other ways to totally erase the whole phone! even if i have to fry the motherboard so i could get a replacement lol! but i dont want to do that tho that would be my last solution
it looks like you may need a jtag to fix the phone, it seems that the X1 may have bricked your phone.
Today I just wanted to uninstall Temple Run from my Moto E. I followed the standard procedure and suddenly as I dropped the icon in the uninstall menu, the Motorola boot icon appeared and the phone switched off. I tried to boot it into fast bootloader but nothing happened. I dont really know what has happened with my phone since the notification LED is blinking randomly even though the screen and everything else is not working. When I tried calling my phone number it says phone switched off. What has happened with my phone? What can I do so that my can start again
Try holding Power+vol up+vol down together for 10+ seconds.
If it doesn't boot up, connect it to the charger for a few hours and try again.
That too is not working I guess it is hard bricked and I will have to take it to the service center. I failed to understand though how an unrooted phone with stock rom could possibly get so damaged just with normal usage. Although the possibility of a virus is very less could it be the reason?
-SKV- said:
That too is not working I guess it is hard bricked and I will have to take it to the service center. I failed to understand though how an unrooted phone with stock rom could possibly get so damaged just with normal usage. Although the possibility of a virus is very less could it be the reason?
Click to expand...
Click to collapse
What was the battery% when you uninstalled the game?
my mobile is suddenly switched off and then i have to switch on the mobile.that is not clearly restart.it will come blue colour moto symbol.how to solve my problem.please replay me.
That too is not working I guess it is hard bricked. I failed to understand though how an unrooted phone with stock rom could possibly get so damaged just with normal usage. Although the possibility of a virus is very less could it be the reason? It will be happened 40% of battery
My Galaxy Alpha was completely stock and I only had a few 3rd party Play store apps installed. I had not done anything to the phone, no rooting (was unlocked from factory), no odin, no recovery mode, nothing.
I charged my phone overnight and used it when I got up. I left it on top of my bed and left the room.
I came back to get my phone and my wife said she found it under the blanket and that is was warm.
I looked at my phone and I saw the blue notification light was on. I hit the power button to turn the screen on but the screen did not respond. I reseated the battery but my phone is a brick.
Wifi was on and the phone was set to only update firmware on wifi but my phone was also setup to kill wifi if the screen was locked.
I will get a new phone but I would like to get my stuff off of my old phone.
Thanks!
svtfast said:
My Galaxy Alpha was completely stock and I only had a few 3rd party Play store apps installed. I had not done anything to the phone, no rooting (was unlocked from factory), no odin, no recovery mode, nothing.
I charged my phone overnight and used it when I got up. I left it on top of my bed and left the room.
I came back to get my phone and my wife said she found it under the blanket and that is was warm.
I looked at my phone and I saw the blue notification light was on. I hit the power button to turn the screen on but the screen did not respond. I reseated the battery but my phone is a brick.
Wifi was on and the phone was set to only update firmware on wifi but my phone was also setup to kill wifi if the screen was locked.
I will get a new phone but I would like to get my stuff off of my old phone.
Thanks!
Click to expand...
Click to collapse
Looks Like A Hardware Damage :/ Probably problem in display (Completely Turned Off) Due to short circuit or may be another reason but i am sure it is not a software side problem