Hello! I'm new here. I've been browsing the forums for a couple of months now so i finally decided to make an account and this is my first post .
OK. now my question.
so around probably around 15 minutes ago i picked up my phone and it was working fine.
like 5 minutes ago, i picked up my phone and it was turned off. i figured the battery might have died or something. I go to turn it on, and it won't turn on. i took the battery out twice, and still no luck. After about 5 minutes, my phone decided to turn on by itself.
It works fine and everything, but still, can someone possibly explain to me what just happened? lol. i figured it would be hardware related, but if the information is needed...
My phone is rooted
The rom it currently runs is RoyalThunder 2.1. i flashed it yesterday.
So thanks to anyone that can explain this. like i said, my phone works. but i want to know if this has happened to anyone else.
honestly, i've never heard anything like this before. i have a galaxy s i9000 rooted and it has similar problems, the screen would turn off and i can't turn it on until i pull the battery and reboot.
so, not sure, but glad it still works fine
and by the way, welcome to the XDA forums
saranhai said:
honestly, i've never heard anything like this before. i have a galaxy s i9000 rooted and it has similar problems, the screen would turn off and i can't turn it on until i pull the battery and reboot.
so, not sure, but glad it still works fine
and by the way, welcome to the XDA forums
Click to expand...
Click to collapse
I've never heard of this either lol. i've been rooted since around mid june and i've had the phone since around november? whenever it first came out. i thought it was bricked at first but then it turned back on. kinda weird.
and thanks
Related
Anyone else been bricked by the HTC update?
If so what kind of response did you get from Sprint? Any suggestions for dealing with them?
The current state of my phone... completely dead, it will not turn on.. connecting it to a pc doesnt show a device is connected..
Try taking out the battery for a little bit. If that doesn't work, just take it back to Sprint. They'll give you a replacement Evo or a loaner for the time being until a new shipment comes in.
They might think you bricked it through rooting.
Not sure on there policies.. Let us know
sorry about ur issue but i have to hand it to u bro.. congratulations on using the word "bricked" correctly regarding the status of ur phone.. for god knows how long ppl have been calling their phone bricked if their volume button stopped working.. im gonna go celebrate with a cheesecake!
Engadget confirmed 10 minutes ago that the OTA has been halted, its happening to lots of people I guess
Sent from my PC36100 using XDA App
http://www.phonenews.com/sprint-aborts-evo-4g-update-amid-concerns-of-failed-updates-11567/
Mine went as smooth as butter. Phone is much better as well.
Mine went good as well. No issues, and phone is much more responsive. I guess it pays to not root.
My stock EVO update was scary. It took between 10 and 15 minutes. It seemed to be in an endless boot loop. It rebooted about 4 times and it finally worked on the 5th. At some point I thought, "if it boots again, I'm pulling the battery." At the end, the voicemail icon was replaced by an error message. I trashed it and reinserted the original icon. There was no indication or hour glass or something letting me know the process was normal. It really seemed like something was wrong.
I can understand if some customers aborted the process pulling the battery, thus bricking their phones. I don't think it would be their fault.
I think a lot of phones were bricked because of user error. A lot of people probably pulled their batteries. I do agree that there should be some kind of indication that the update was still in progress. I'm rooted and I haven't updated yet since I already get amazing battery life.
Uh oh.
Sprint pulled the update.
My condolences to those that have been bricked.
FYI - my update went very smooth. Stock EVO, unrooted. Did not make the mistake of accepting yesterday's update twice though ;-)
What did Sprint said about your phone, will they exchange it?
bricked mine yesterday.
Made the mistake of running the patch twice. Being used to windows I like to patch first and ask questions later.
Learned my lesson.
1st patch went through smoothly. Everything was great except a few widgets need to be reloaded. Got prompted for a new patch in the afternoon and ran that without checking xda first. And that was all it wrote.
Called Sprint last night and tech on the phone knew exactly what happened to the phone and made an appointment for me this morning to get it exchanged. He said a lot of people are calling in about the same issue. Since it's within the 30 day period he informed me that I will be getting a brand new replacement.
Went to the store this morning and confirmed my phone is DOA. and *suprise* no phone in stock. They indicated they will be order me a new phone. The MOD also told me there are five people showed up last night with bricked evo's.
Called Sprint again after the visit. They are looking for another phone I can use in the mean time.
Not impressed with HTC at this point.
if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.
kthejoker20 said:
if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.
Click to expand...
Click to collapse
don't know who you're talking to but my phone is completely stock. (unrooted)
kthejoker20:
The reason it bricked was because of double updating, not because of rooting it.
kennyc1:
With that said, sorry for your trouble. Hope you get a new one soon!
AssassinsLament said:
kthejoker20:
The reason it bricked was because of double updating, not because of rooting it.
kennyc1:
With that said, sorry for your trouble. Hope you get a new one soon!
Click to expand...
Click to collapse
Thanks, the only saving grace of this whole fubar is that having heard some horror stories about Sprint's CS before. I was treated very well by everyone I spoke with so far.
Fingers crossed.
kthejoker20 said:
if you rooted your phone, then tried to apply this update, your screwed.
It will brick.
Good luck returning it. Not covered by insurance when you tinker with it.
If you do get a new phone, don't be surprised to see a big bill once they look at what you reprogrammed later on.
Click to expand...
Click to collapse
I was rooted with unrevoked. Ran Update everything went smooth just lost root. Did not update twice. baseband 2.05.00.06.10 software 1.47.651.1
My phone was not rooted... I havent really seen a point to do it yet... (i did root when I had a hero)
I went to the sprint store, it took about 30-40 min to get a new phone..
But now I want to update it... just a bit concerned about updating it (for good reason lol)
First phone has never been rooted, it is stock latest sprint rom.
Starting 2 weeks ago the phone has been acting odd, keeps losing my custom ringers, turning itself up and down, no software installed to do that. I have also had to re-enter all my logins over the last 2 weeks. Now the weirdest one, I left it on my charger last night as a slept and this morning when I took it off the battery fully charged Icon stayed on and would not go away.
I turned the phone off and on and it still came up. I turned the phone off again but this time the phone would not even boot. I tried to remove battery and put it back still no boot. I finally got it to boot but only if it was plugged into the Samsung wall charger.
I don't think it is any type of malware, spyware or virus, I get all my apps off of the marketplace and I run the norton security beta.
As anyone heard of anything like this before?
Thats weird..... I would either get it replaced or ROOT THE DANG THING lol
EDIT: First ^_^ .....
I remember having strange issues when I first rooted the stock EC05, but that vanished when I installed a custom rom. Nothing like this though.
I had 2 Epics do this exact same thing. Took them back got brand new ones from the store. The latest one I have started not sending texts a few days ago, which it would receive them fine and everything else worked it just stop sending texts. Hard reset wouldn't fix it so after a call to sprint and them "refreshing" my phone it worked. Then 2 days ago after taking it off the charger it went on roam and stayed that way all day. Wouldn't go off roam after battery pulls or restarts, so I odined fresh EC05 and it still was stuck in roam. I am running EC05 stock rooted, and wife's phone is completely stock and it does weird stuff too. Now I am waiting I guess for a refurb since I am past my 30 days. My Epic does weird stuff too and I tried to get them to let me get something else but they won't yet which is really disappointing since I just started service with Sprint 6 weeks ago. I am not really impressed with the service or phone so far and definately thinking I should have never came to Sprint.
Well the phone is back to normal today. It did it yesterday as well though. I can't wait until Sprint gets a good Windows Phone 7 device, 200 for the Arrive without 4g and a small screen still is ridiculous. I only got this phone as a stop gap and I really dislike Android the more I use it. Thank you for your help.
Sent from my SPH-D700 using XDA App
c-had2001 said:
I had 2 Epics do this exact same thing. Took them back got brand new ones from the store. The latest one I have started not sending texts a few days ago, which it would receive them fine and everything else worked it just stop sending texts. Hard reset wouldn't fix it so after a call to sprint and them "refreshing" my phone it worked. Then 2 days ago after taking it off the charger it went on roam and stayed that way all day. Wouldn't go off roam after battery pulls or restarts, so I odined fresh EC05 and it still was stuck in roam. I am running EC05 stock rooted, and wife's phone is completely stock and it does weird stuff too. Now I am waiting I guess for a refurb since I am past my 30 days. My Epic does weird stuff too and I tried to get them to let me get something else but they won't yet which is really disappointing since I just started service with Sprint 6 weeks ago. I am not really impressed with the service or phone so far and definately thinking I should have never came to Sprint.
Click to expand...
Click to collapse
The official Twitter app causes a lot of problems in the Epic. I couldn't send text, watch videos, or listen to music. After finding a post here mentioning it I uninstalled Twitter and now I have no problems. The official twitter app could be the problem. I wouldn't out right blame android or sprint for the problems of one phone that may potentially be caused by one app.
Sent from my not rooted Samsun Epic 4G using free XDA Official App
R3537L1F3 said:
The official Twitter app causes a lot of problems in the Epic. I couldn't send text, watch videos, or listen to music. After finding a post here mentioning it I uninstalled Twitter and now I have no problems. The official twitter app could be the problem. I wouldn't out right blame android or sprint for the problems of one phone that may potentially be caused by one app.
Sent from my not rooted Samsun Epic 4G using free XDA Official App
Click to expand...
Click to collapse
I thought of that too, but after using Oden to get back to EC05 and having done mutiple hard resets that rules out the twitter app or any other app. Plus that don't explain why it went on roam and even using oden and doing mutiple hard resets wouldn't fix that either. Today it quit sending texts again and would not keep a data connection until I did 2 factory resets and all I have is stock apps nothing more. I haven't had this phone rooted for over a week now because of all the problems. Thanks for suggesting but its not the twitter app its definately my phone and possibly sprints network.
My first epic also had an issue similar to this, it wouldn't charge and the few tims it would whenever id unplug it , it would still say it was charging and have radom reboots. Also when it died the only way to turn it on was to take out the battery and plug it in , then put he battery in.
Long story short try ad get it replaced.
Sent from my SPH-D700
I got another 1 that they sent to the repair store and I am guessing its gonna be a refurb, so after work I gotta swing by and switch them out and see how long its gonna last.
Just for the hell of it I guess I will take it to the local Western Talk store, they don't ask any questions and just replace the phone. I am just pissed that I will have to pay 35 damn dollars because of Sprint's new rules.
Hey guys, i just got a replacement Atrix because my girlfriend dropped my original Atrix in the toilet, and the new Atrix keeps dieing/shutting down after the screen has been off for more than 10 minutes. Any clues or hints as to what i can do to stop this or perhaps this is just a faulty device?
More info needed on your setup, i.e. ROM, bootloader unlocked, etc.
Not sure if this was the case before i got the phone, but i did notice that the screen wouldn't turn on after it timed out the first time i turned it on.
As for my setup, i unlocked the bootloader as soon as i got it, and i rooted it also. After rooting it i put The DarkSide v3.1.0 on it.
Oh ya, one more thing, the only way to keep the phone from dieing by timing out is to set the screen to never time out... Don't know if that bit of info would be helpful.
if the issue is not resolved by a factory reset, it sounds like you were sent a faulty replacement device.
since it was unlocked and all, re flash a different ROM and see if the issue persists.
Kk, i'll put a new rom on it in a bit and re-update with the progress.
Ehhh... No luck, slapped on Alien by Kenn and still no luck... I'll wait and see if anyone else has any other helpful hints meanwhile i search other forums. Guess my best bet would be to get another replacement again?
TfzSCVang said:
Hey guys, i just got a replacement Atrix because my girlfriend dropped my original Atrix in the toilet, and the new Atrix keeps dieing/shutting down after the screen has been off for more than 10 minutes. Any clues or hints as to what i can do to stop this or perhaps this is just a faulty device?
Click to expand...
Click to collapse
Try flashing different kernels and also try to fix permissions on recovery. If these don't help, I am afraid you have a faulty Atrix my friend.
Sent from my MB860 using XDA App
boot phone, screen is on, hit power button or just let screen go off and then it won't come back on with the power button, phone is working, everything is working but screen won't come back on, on froyo it works fine, on gingerbread, won't work, this is wifes phone completely stock.
I odined to stock froyo, works fine, did the update on the phone, then it doesn't work, tried the rooted ei22 on here, odined it and screen won't come back on. has anyone else had this problem?
i put her back to froyo for the time being, but really need to fix this for her.
Did u try changing the cpu settings to were it won't go into 100
Sent from my SPH-D700 using XDA App
its the wifes phone, its completely stock, no root, nothing. was working fine for the past month or so with the gingerbread update from samsung/sprint, now won't work with ei22. i'd like to just take it back to sprint and say fix it. but i don't know if its hardware or software, can't understand how it would be hardware if its working with froyo, but doesn't make sense that it could be software since it works on everyone elses phone.
Its more than likely a bad update id say take to sprint after you odin back to stock and install the update in front of them and show them the screen won't come on they will more than likely help you and if they can't fix it they'll give you a new phone free since its their fault.
Sent from my OG Epic
Even with phone out of warranty? And do I tell them I odined back after it happened the first time?
I wouldn't tell them that you've odined back.. When I went in to get my phone fixed I just acted dumb. Tell them you just updated it, and the screen won't turn back on..
Not sure about the out of warranty bit though. I have insurance on mine
But all phones were updated a month ago or so, so i'm not sure playing dumb would work
Just take it in on gb and tell them you decided to update that day and that's what happend
Sent from my SPH-D700 using XDA App
i know, but my point is, since the update went out like a month ago, doesnt it force you at some point to update? wouldn't she have had to update already? We got the phones right when they came out and mine has been rooted since day 2, so I really don't know. just don't want to go look like a moron.
robl45 said:
i know, but my point is, since the update went out like a month ago, doesnt it force you at some point to update? wouldn't she have had to update already? We got the phones right when they came out and mine has been rooted since day 2, so I really don't know. just don't want to go look like a moron.
Click to expand...
Click to collapse
No they'll believe you if you just recently "decided" to update. Its an error on their part and are forced to fix it or replace it.
Sent from my OG Epic
took it back today, they wanted to charge me 37.10 to warranty the phone. I asked if we could get sprint to waive it as it was their software update that botched the phone. The guy said he would do it since he is in a good mood. but really I left feeling that sprint might as well close up shop, everything is all about the insurance, insurance insurance. why would I need insurance to cover them bricking my wifes phone??
funny thing is, it was working on gingerbread just fine for a month or so until it didn't. now I just odined the phone back to stock froyo and its working fine again until she gets the new phone.
Hello All,
I've lurked for a fairly long time, however I have come forward from the darkness to share some problems brought to light from the KK OTA update.
It Sucks.
There is no way around this. It's laggy in every menu. When im typing anything out, whether its a text, or an email or even into a search bar Its always chopping and lagging behind a couple seconds. Its a pain to hit the home button to back out of apps or just go get out of something that stopped responding for no apparent reason.
Also, as a small business owner, It is imperative that i stay in communication with my employees and family at all time should anything arise.
The KK OTA has failed miserably in this function. I have had it happen almost everyday for the last month since i downloaded it and installed it on my device that there are periods of time in between me receiving messages and sync data(email, push notifications, etc) that can be quite long. I have noticed that sometimes i just plain don't get my text messages for hours at a time. I'm a hard-working, geeky, IT guy 100% of the time, but Im a father first. Its not okay for me to not hear back from people regardless of what the situation is, and then I step out for air at night and go for a cruise, and then all of my texts and push data suddenly hit my phone all at once, sometimes anywhere from 3-6 Hours later!!!!
Its not my reception. I have a full 5 bars at my residence and at least 4 everywhere else in town, and average speeds of 45 Down and 30Up. My brother and girlfriend also have Note 3s and experience the same and even some different issues. My girlfriend's note 3 cant stay charged longer than 6 hours. even with the phone having all the apps closed and RAM cleared and the phone in complete Airplane mode. Its gotten to the point where she always has her charger with her! We feel like iPhone users! We've gone as far as to buy 3 extended batteries and everybody gets to keep one as a spare. Often times i have 2 spares in my backpack and I swap batteries once a day. My brother has had issues with his keyboard failing to work at all and requiring an actual reboot of the device and yesterday he called me to tell me that his speaker stopped working and after 3 reboots the speaker was functioning normally again. What causes this?
To sum it up, I knew there was only one way to remedy this situation and I was dreading it. I had to call Verizon. I had to tell them that the OTA update had made my phone worthless and unusable. It was an even further long shot, but i had to request and demand a replacement Note 3 with Jellybean on it and NOT KIT KAT.
The phone was overnighted yesterday and it arrived this morning. It came with Jellybean. Flicking through the menus and settings I had forgotten what the speed had felt like. Crisp, concise and without the slightest hesitation. The main purpose of this replacement on JB was so that it could be rooted and the stock apps could be frozen through TiBu and a nice aftermarket ROM could be installed. And that's just what I'll do. I've kept my Sim in my old phone and made sure WiFi stays off on the new one until the old one is backed up and Im ready to root the new one. I cant take anymore chances with these stupid OTAs
Briefly after i had taken the OTA, I had attempted to use Kingo and vRoot(I had been out of the phone mod/root scene for a while) To my surprise it didnt work. Then i realized the boot loaders had changed and were blacklisted and there was no going back.
I've been stalking all of the similar "4.4.2 root method? threads for the last few weeks and all of the responses led me to this obvious conclusion.
Lesson Learned. READ XDA BEFORE TAKING OTAs.
Note 3 junk now.
My Note 3 after OTA:
1 in 30 chance of not seeing "mobile network not available"- and actually making a phone call.
Random reboots
Short battery life
Hot
Crappy visual voicemail trial hard to disable
Overall, my Note 3 which ran perfectly before the update, is junk now.
VZW only has one answer- refurb.
How's about a fix!
I with you. Was so excited about the update until i got it. Phone havent been the same since. I have to hit airplane mode about 10 times a day to get 4g back. The phone button just hangs and take forever to respone. The whole phone now is very slow. I calling verizon when i get a day off. Really thinking about ditching samsung altogether. Their not what they use to be
Sent from my SM-N900V using XDA Free mobile app
droidfreak02 said:
I with you. Was so excited about the update until i got it. Phone havent been the same since. I have to hit airplane mode about 10 times a day to get 4g back. The phone button just hangs and take forever to respone. The whole phone now is very slow. I calling verizon when i get a day off. Really thinking about ditching samsung altogether. Their not what they use to be
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
I know Samsung can do better than what they're doing right now. But the simple fact that Verizon was 2 months late to the KitKat party with a ****ty OTA to boot makes my blood boil. Currently running Hyperdrive Rom and I have not regrets.
:laugh:
So any suggestions? Really don't want a refurb if possible for their screw up but i need a phone that works. The guy at the vzw store did tell me a fix was in the works Just wait?
charge1 said:
So any suggestions? Really don't want a refurb if possible for their screw up but i need a phone that works. The guy at the vzw store did tell me a fix was in the works Just wait?
Click to expand...
Click to collapse
Hey guys, I experienced many of these issues as well but have since resolved them.
First, any auto killers that you are running will lag the system big time! I dont know the technicals of why this happens but I experimented on my phone and it happens. SO AVOID AUTO KILLER APPS.
Second, this is in addition to the above suggestion. If you still have problems, a clean re-install might solve it. You can simply use kies or the verizon upgrade app which you can download with a little google search. Repair the installation or install clean (even better) to clear these issues up.
Again, I don't know the technicals but this worked for me after a good amount of experimentation and it's working fine until a root is available.
Best of luck!