I have a rogers dream running Open Éclair 1.3.0 (32A patch, Apps2sd ext4, 256mb swap). Yesterday, I received a call, and the phone vibrated as per normal. However, it would not stop vibrating after the call went to voice mail. I rebooted the phone, and it kept vibrating. I then pulled the battery and let it sit for a while. As soon as the splash screen appeared on boot, it started vibrating.
I then did a full wipe and reinstall of the OS, and it still vibrates. It kept vibrating even when I had it on the recovery screen. After finishing the reinstall, I used the terminal emulator to run "fix_permissions". Interestingly, the phone remains completely functional in-spite of its constant vibration. Also, the vibration stops when the screen goes dark.
As a last resort, I'm tempted to put it back to the OEM state with the standard issue Rogers ROM, however, that would be an absolute last resort, as the Rogers ROM is practically unrootable. Does anyone have any ideas as to what would be the cause of this? The phone is still under warranty.
you can root the phone if you know how to use a goldcard. It just got solved I believe (99% sure its solved lol)
Most likely a hardware issue
hmmm... more than likely a hardware issue. Not software.
Just my opinion though.
KAwAtA said:
you can root the phone if you know how to use a goldcard. It just got solved I believe (99% sure its solved lol)
Most likely a hardware issue
Click to expand...
Click to collapse
I was thinking hardware issue as well, but that doesn't explain why it stops vibrating when I turn the screen off with the "end" button. (Of course, it starts vibrating again as soon as the screen lights).
Give it to some girl as a gift?
@gmupps
yup sound hardware if your still under warranty then OEm it and send it i..... then gold card i guess
if you are not there is probably a terminal command to disable the vibrate completely (or you can remove it manually)
Kazan22 said:
Give it to some girl as a gift?
Click to expand...
Click to collapse
I'm sure my significant other would be thrilled, but then I'd be stuck using my old LG Shine "dumb phone". I guess it's time to send it in for warranty, and in the meantime, start reading up on goldcards.
Kazan22 said:
Give it to some girl as a gift?
Click to expand...
Click to collapse
lol oh man, consider exorcism?
Now I'm really confused. I was backing stuff up in preparation for return to stock, and I fired up a terminal emulator so I could reboot into recovery for taking a nandroid (because I'm too lazy to just shut it down and hold down home when booting), and when it rebooted, it stopped vibrating. I rebooted out of recovery, and it seems to have fixed itself.
I don't see the problem here.
boldfilter said:
lol oh man, consider exorcism?
Click to expand...
Click to collapse
I second this
hahaha
And it randomly started doing it again, seemingly as a result of being placed on a desk. Warranty time.
try removing the vibrator at the back if it bothers you that much...
its at the back accesible when you remove the battery cover
The phone is being replaced under warranty. Now to get my root back :-/
gmupps said:
The phone is being replaced under warranty. Now to get my root back :-/
Click to expand...
Click to collapse
you still have warranty
good to hear
Related
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
We are going to need some more information to better assist you.
1) What Build are you using
2) Are you running Apps2SD
3) How much space do you have left on your internal storage?
Sure, thanks
Jf 1.5
Radio: 26I
No A2SD
31MB free
Nothing crazy.
I wipe every time I flash.
I've tried factory resetting too.
I try to keep the system clean.
he3 said:
Hola,
Dont know if Im over (ab)using my phone or if anyone else has the same issues.
My phone loves to reboot
-When I answer a call once in a while.
-When I turn off StreamFurious once in a while.
-When I disconnect the usb every once in a while.
-For no apparent reason every once in a while (ex. Ill find it turned off in my pocket or on my desk, but I never turned it off)
This happens about 3-5 times per day.
Also, on some of the StreamFurious reboots, it turns off and I have to pull the battery or it gets stuck on the G1 screen and never finishes.
Do you think I need a replacement or is this just a version 1 hardware thing?
Thanks in advance for your input!
Click to expand...
Click to collapse
Something like this happened to me about a month or more ago. It was everytime I try and use my phone when I was charging it, it would reboot. After a few days it would just do it at random. I just called tmobile and they just sent me a new one out.
the same thing is happening to me. my phone randomly crashes/reboots and i was starting to think it is the Haykuro build im using. is there any way to test the hardware? is there something like that in an app?
help
Are you using ahome or someting like that cause those programs cause problem with 1.5 uninstall all your theme apps if you have any
No, no themes.
Called t-mob, since I've had the device (sans insurance) less than a year, they are sending new hardware without a battery to replace mine. I decided to add insurance to the new hardware just incase. Thanks for the input! Glad I called!
Now to virginize the phone... heh
I have the same problem. There's a lot of this going around. It sure seems like a coincidence that it started with Cupcake for most all of us.
This has been something that has been happening since the RC33 load it...
Now I got the stupid random reboot problem. This is a warranty replacement and my first one never did this. I guess I gotta get another warranty replacement. Anyone find a definitive cause for this yet?
almost 100% sure you have a hardware problem
savethechicken said:
This has been something that has been happening since the RC33 load it...
Click to expand...
Click to collapse
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
rikupw said:
I used to have the same issues WAAAY back after I recieved an OTA update from tmobile for rc33 or whichever one it was in march... back when I had still no idea what "cupcake" was...
always seemed to happen when I was:
answering a call, recieving a text while in a call that I started, etc.
but after I found out about the linux bit of my phone, I immediately cracked it... and... cupcake... and then? there weren't any reboots.... I wonder whats up with that? maybe something to do with OTA spls? I don't remember lol
Click to expand...
Click to collapse
RC33 was the OTA was in March I believe maybe Feb. This didn't happen as much on RC30 and then RC33 came out and this started to happened more often. Obviously it is not the ROM doing it as not everyone has the problem but something seemed to trigger it on some devices.
alapapa said:
almost 100% sure you have a hardware problem
Click to expand...
Click to collapse
Going to have to agree. This is starting to seem like a Hardware problem, considering all the feedback we are being given.
I have the same exact problem.
It's definitely a hardware issue.
I was thinking it was because my extended battery pack is a little loose or some loose wiring. It happens when the phone is bumped a little. Like putting it on a table too roughly or flipping the screen up too quickly or it shaking in my pocket. Probably going to replace it.
I have this same problem...i had it originally with RC33 then it went away with the cupcake update and I recently root and install cynogen's build and its back to screw up my day
i don't think its a hardware thing ...at least in my case doesn't make sense to be gone for a month and then come right back after rooting
I also experience random reboot issue. Usually when the phone hang first then next thing you know, it is rebooting. Sometimes the phone will be just sitting there and it will reboot by itself. I always thought it is the ROM issue, never suspect hardware. I am running an old version of Dudes v1.3a build.
For me too
I am getting too many reboots too, just got a replacement phones(previous one did this too), same with this phone, first i thought it was Hardware but now it think its the roms. On hero it rebooted 3 times while booting the first time, on cyanogen it rebooted in a couple of hours, just dont know what the problem is, maybe abusing the phone
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
charnsingh_online said:
I got a replacement phone and still have reboots issue on it when booting, playing music etc.
Click to expand...
Click to collapse
Makes me wonder on the apps your using in the background or settings you have up, or even the ROM. Do you have any extra info whats up before it reboots? Does it choke out due to low memory maybe?
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
So my Galaxy S seems to have **** the bed 7 days to the minute.
Working all fine today, restarted the phone as it seemed a little slower than usual.
Upon restart doesn't go any further than the animated splash screen, problem is my phone is one that doesn't have the 3 button combo. Awesome.
Only things I have done to it is the one click root and one click lag fix, no other flashing.
I've tried taking the battery out for about 10 minutes, starting with no sim, with sim, with charger, withough charger all to the same effect.
Am I SOL and have to send this back or are there any other tricks to try?
I think I'll be sticking with vanilla if I can get it replaced.
E: I should say, after about 10 minutes from sitting at the samsung splash screen, the screen turns off and the two touch sensative buttons light up and don't turn off.
Do you have an external memory card installed? If so remove that and try again.
Hey.
Sorry for your phone dying. I am able to get my phone into recovery and download mode by letting it charge up. The goal is to make it warm to touch. This is the only way I can get it going. I've also used a hairdryer with success. Might as well try everything right?
you can still take it back to the store and claim warranty on it
Tehpriest said:
Do you have an external memory card installed? If so remove that and try again.
Click to expand...
Click to collapse
No memory card installed
MomijiTMO said:
Hey.
Sorry for your phone dying. I am able to get my phone into recovery and download mode by letting it charge up. The goal is to make it warm to touch. This is the only way I can get it going. I've also used a hairdryer with success. Might as well try everything right?
Click to expand...
Click to collapse
Will give this a go tonight.
AllGamer said:
you can still take it back to the store and claim warranty on it
Click to expand...
Click to collapse
Yeah I called my carrier last night. It's only 7 days old, as I upgraded online they are sending out a satchel for me to send it back in.
Back to the old iPhone 3G for the time being. Such a step back.
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
sinajei said:
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
Click to expand...
Click to collapse
seems like infamous bootloop... harware issue. send it to tmobile or LG.
raptorddd said:
seems like infamous bootloop... harware issue. send it to tmobile or LG.
Click to expand...
Click to collapse
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
sinajei said:
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
Click to expand...
Click to collapse
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
raptorddd said:
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
Click to expand...
Click to collapse
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
sinajei said:
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
Click to expand...
Click to collapse
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
raptorddd said:
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
Click to expand...
Click to collapse
This one (603) is a HW Version 1.0 ...
sinajei said:
This one (603) is a HW Version 1.0 ...
Click to expand...
Click to collapse
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
raptorddd said:
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
Click to expand...
Click to collapse
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
sinajei said:
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
Click to expand...
Click to collapse
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
raptorddd said:
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
Click to expand...
Click to collapse
Good to know it's not just me then. Guess it's a common screen glitch then.
Thank you for the info!
Well another 505 g4 bites the dust. Playing a game, backed out of it, phone froze, pulled battery, turned on to endless bootloop, pulled battery again, now nothing and I mean nothing, no boot loop, no nothing
Definitely a brick. Computer doesn't recognize or even try to charge it. Hopefully still under warranty.
Sent from my LG-VS980 using Tapatalk