Related
So my HTC VZ6900 (Vogue) was acting up two days ago and I could tell it was a software issue and has not done any real research on the device till yesterday! Here is my story...
HTC started acting up while at school on Monday and was not doing great. I tried a soft reset but nothing worked... Booo. I tried removing the battery and waiting a few minutes and it took an entire 90 minutes + to get past the WM 6.0 screen! Once it got to the today screen the touch feature was none responsive so I could not really access anything. Soft keys worked. Couldn't get anything and the phone would not connect to the network.
Tuesday morning I took it to the Verizon store before I went to work. I had brought my old phone because I was not sure what was wrong. I personally thought it was a software problem, and figured that if that was the case Verizon would hard reset the phone or at least give me a replacement. Wrong. The clown at the desk took my phone and word for word quotes here: "Ah, yeah this thing is dead you’re going to have to get a new phone. Oh! Wait you have insurance you can pay $50 and they will give you a replacement."
I am a studying to get a PHD in electrical engineering and my gut told me this was not the case... So I said no thank you to the insurance and ask him to switch my phone to my old phone that being my old envy which still works perfect. When I went to leave they tried to take my HTC touch to which I protested and they complied. To work I go...
Well it was a quiet day so I had lots of free time and decided to Google VZ6900 problems, after about 10 minutes of searching I came across XDA-Developers! Did a little searching and saw that some people had similar problems. Figured out how to hard reset my phone (This was not a problem all of my contacts were saved to windows live!). Phone resets and it’s like brand new. I had seen these ideas of Custom ROM's and decided to do a little reading. After about 20 minutes I decided that it would not be hard to upgrade my ROM, loaded coke loader and followed the Verizon directions, 20 minutes later BAM running WM6.5 custom ROM. Hm I began to wonder, will Verizon be so nice as to activate this for me? I know they love to lock everything down so that they will get paid. I walk back to the store at 430 and proceed to wait 25 minutes to talk to a different person. I was explaining that their Tech earlier had told me the phone was broken beyond repair and that in fact he had just been lazy and refused to even attempt to fix the phone. They did not like this one bit. They told me I would have reset to the original Verizon settings. Though what he intended was that I needed to run the Verizon ROM with its own customization. So I asked the guy if he could get the other Tech who had helped me earlier to come into the conversation and he was somewhat upset at this time, but complied.
"Hey your back, oh wow this is the new Windows Mobile Cool!"
"Yeah I spent the better part of the day fixing my phone, now switch my phone back"
"Um... I do not know if I am supposed to do that. Um."
"Remember this morning when you told me to file an insurance claim for a broken phone?"
"Yeah, don’t have to do that anymore but I cannot activate an unlocked phone"
"Yes but telling me to file an insurance claim for a broken phone when it was not actually broken is insurance fraud"
"Oh... well we are not supposed to do this but I'll make an exception"
Two minutes later that had it all up and running and I was out the door without any problems.
Thanks to everyone who has contributed to the information I used, it saved me a great deal of time!
My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en
Are you using a custom recovery/ROM? That icon you posted isn't the stock image
Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?
just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet
Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!
Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.
I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...
I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?
I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.
Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.
Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !
No, but this problem is not ROM related.
discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.
I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.
welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.
Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.
Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks
I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary
Hello all, i am having a couple of problems with my sensation,firstly its a refurb supplied by an insurance company and they only gave it a 30 day returns policy which expire over a month ago,i had already sent one back where the microphone didn't work.
The first problem is that i have a green flickering that appears on just over half of the screen (see attached video) it comes and goes but is there most of the time now,if it gets really bad in the area where the screen flickers the graphics within that area goes corrupt almost as if someone has brushed the graphics down the screen with a paint brush.
It is worse than the video shows but only have an old phone to take the video with.
Could this be hardware malfunction? It was there before i upgraded to 4.0.4 and there afterwards.
The second problem is since upgrading to 4.0.4 i have terrible battery life 8-9hrs max the phone keeps turning it self off, on nearly every re-boot "upgrading applications 0-32" comes up runs through the upgrading and then turns off again. these re-boots also suck the life out of the battery.
I haven't yet tried flashing a new custom rom to it as it has not been rooted etc yet.
Any ideas/suggestions?
Thanks in advance.
I am 99% sure the screen flickering is hardware related. For battery life, firstly check for battery draining apps running in the background. The android is upgrading message happens when android is building the dalvik cache and seems to happen only when dalvik cache and cache are wiped on deodexed systems, however it seems to happen on every boot on odexed systems but either way, its normal and nothing to worry about
oh well time to phone the insurance company AGAIN then,just as you get all your progs/games on your phone you want on there, somethings screws it up.
was gonna flash a custom rom to see if that worked out the screen probs but, i shall wait until i know what the insurance people say.
Thanks for the response
Now what to do for the best????
Ok so i contacted my insurance company and they agreed to take the phone and fix it for free,they have dispatched a special delivery envelope to me.
I have wiped my phone and got a little annoyed because i have got 29gb worth of programs installed and its such a pain in the arse to reinstall everything!
So the phone is now reset to factory settings and guess what......Thats right the fault has gone!
What to do still send it off with no visible fault?
Or keep it?
I cant see it being a program thats did it as i hadnt s-offed the phone or rooted it so there shouldnt be any software that can interfer with the phones screen can there?
I have had a few "huh humm" trial versions of games and apps on it,could there be mal or spyware that has done it or possibly where something may or may not have been [email protected]?
What to do.....
back a little bit...Damn phone
Well after the factory reset the battery life is a lot better.
The screen flicker has come back but very very intermittently so hoping that the tech guys at either the insurance company or more likely HTC as the insurance people quoted this "you should within 17 days you will get your phone back" will be able to see it.
All this trouble aside this is definitely one of the best phones i have ever owned and i love it,never did i think back in the days when i owned a titan II and a jade did i think i would ever see graphics like i do today,the game, application programmers/designers and the phone makers just keep on astounding me with what they produce.
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Never dropped it or got water in it. Never tried to change the OS or anything like that either.
It started freezing and a soft reset would get it back up. Started happening more often and eventually none of the suggested resets would work and even when charging with the phone off it would freeze. I eventually managed to get it into the recovery boot (just the once) and it said E:/ failed to mount over and over. When i pressed a button it froze again and since then i haven't been able to get any response. Not even the little battery symbol or red light when it's on charge. It seems completely messed up and essentially a brick right now.
Any ideas? I can get it repaired via my UK network provider (O2) which would take a couple of weeks but would really like to back up and factory reset my stuff if possible as i have lots of personal data on my phone including passwords to peoples websites (i'm a web developer). As well as the ordinary things your girlfriend wouldn't want ending up on the net. My online banking and everything is on there. There's pictures with some famous people at Glastonbury and also some brilliant sporting events i was at that i'd never be able to get the vids/pics back.
With the failed to mount error, would that mean they'd have to factory reset it regardless of what happens and i'd have no chance to back it up either? I'd really rather not lose my files but i also don't want some random guy snooping through my stuff.
Thanks in advance for any replies guys!
Have you tried a different charging method?
From PC with a different USB lead for example
Leave it connected overnight and see how it is the next day
Thanks for the reply.
My girlfriend uses my charger to charge her blackberry as she lost hers and it works fine. I also tried leaving it for a few hours connected to the laptop using the USB connection from the original charger with no response whatsoever. My mother has as Samsung too... given the points i just told you, is it worth trying to borrow another charger still?
I'd reluctantly be happy even if i have to factory reset to save me having to wait for ages to get it back.
No, sounds like you can rule out the charger being the problem
Sounds like something inside the phone has fried, possibly the charging port if you can't even get an LED on, but considering the errors leading up to the fault it sounds more like the motherboard has died, which, unless you saved anything to external SD (MicroSD), contains the Internal storage where all your files are
More than likely, Samsung will just replace the board rather than fiddling around trying to repair that one, so unless it is something else at fault you can probably relax about them snooping, it'll end up in the recycling bin to be melted down for it's gold contacts never to be powered up again
I can't think of anything else you can try to get life out of it tbh other than opening it and charging the battery another way / replacing the battery with a charged one, but warranty is gone after that and not even sure how you would go about switching batteries tbh, if you can
If it is already out of warranty, you could find where the battery terminals connect to the motherboard, and put an alternate power source to them matching the battery voltage etc (Removing the battery first), might give you time to remove / erase / copy
Thanks again for the reply.
So you think the motherboard just progressively died? I hadn't mentioned this but a while ago i accidently left the phone on the radiator for a short while whilst working. It worked fine afterwards and when i asked on another forum they said if any damage was going on it would have restarted or gave an overheat message (which it didn't).
I guess i'll be sending it off to my network provider (O2 UK) then, it's still in warranty (just) so they should fix it or send me a new one. I've seen so much stuff on amateur porn sites of videos or pictures that probably weren't meant to be "released", leads me to having a fear about my girlfriend ending up on them. And like i said, passwords are stored on there to some websites i create for people so its not just my personal data but theirs. I don't really know how these businesses are run, i'd imagine they'd want to get as many phones done as possible... but knowing me if i was doing that job i'd probably have a snoop where i could lol.
powlesy6 said:
Thanks again for the reply.
So you think the motherboard just progressively died? I hadn't mentioned this but a while ago i accidently left the phone on the radiator for a short while whilst working. It worked fine afterwards and when i asked on another forum they said if any damage was going on it would have restarted or gave an overheat message (which it didn't).
I guess i'll be sending it off to my network provider (O2 UK) then, it's still in warranty (just) so they should fix it or send me a new one. I've seen so much stuff on amateur porn sites of videos or pictures that probably weren't meant to be "released", leads me to having a fear about my girlfriend ending up on them. And like i said, passwords are stored on there to some websites i create for people so its not just my personal data but theirs. I don't really know how these businesses are run, i'd imagine they'd want to get as many phones done as possible... but knowing me if i was doing that job i'd probably have a snoop where i could lol.
Click to expand...
Click to collapse
If the phone powered on when you sent it in then no doubt somene would have a snoop, but if it is DOA they won't waste their time, they'll be getting thousands of phones a day to go through, yours will just be another number: Press power > Nothing > test with some USB device > Nothing > open > replace motherboard > test > working > job done
Something like that I would imagine
For future reference, get a MicroSD card for your replacement and save all media to that, then you don't have this problem if it dies