So what would you do? - LG G Flex

Well i never rooted but i want more. I want to customize the vol up/ vol down buttons on the back so a long press will work to control tracks. Also I want better themes and the ability to tether via bluetooth. I bought the Sprint LG flex on release day... Got pissed and threw and kicked the phone in a fit of rage. Well insurance claim later. I have my new Flex.
I turned it on and put it in airplane mode. It shipped with JB . My question is this. I have 10 days to return my old phone to assurion . Surprisingly beside the screen being cracked to hell n back. The KK flex still works. Can I try my first root on the one slated for return? Can I root it and return it back to stock? I dont want assurion denying my claim? What to do?
Ill post up some pics when i get time.
Sent from my MZ601 using xda app-developers app

Veno8mm said:
Well i never rooted but i want more. I want to customize the vol up/ vol down buttons on the back so a long press will work to control tracks. Also I want better themes and the ability to tether via bluetooth. I bought the Sprint LG flex on release day... Got pissed and threw and kicked the phone in a fit of rage. Well insurance claim later. I have my new Flex.
I turned it on and put it in airplane mode. It shipped with JB . My question is this. I have 10 days to return my old phone to assurion . Surprisingly beside the screen being cracked to hell n back. The KK flex still works. Can I try my first root on the one slated for return? Can I root it and return it back to stock? I dont want assurion denying my claim? What to do?
Ill post up some pics when i get time.
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
First I would go and see a psychiatrist j/k. As long as the phone can boot properly then rooting/unrooting won't be a problem. Use this to root if you're on KK http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869If you paid the deductible then they(Asurion) really shouldn't care either way though. You can probably use the SU app to to unroot itself(easiest method). The safest way would be to return to stock http://forum.xda-developers.com/showthread.php?t=2644083

Has anyone remapped the physical buttons on the g2 or flex?
Sent from my MZ601 using XDA Free mobile app

Related

Warning Nexus 7 Owners.. JellyBean 4.2 Update Can Brick Your Device.

Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
mr23 said:
Hi
I bought my first ever tablet on 24/11/2012. I was aware that the 4.2 updates was causing problems for many including myself. I updated device as soon as I started up device, as I did not know what the tablet was like before hand when running I could not be sure for definite if it was update that caused it or the tablet was just like that before update. My tablet was not great after the update. I woke up and restarted my tablet to find it would not boot back up and wold not turn on, could not enter boot recovery either. tablet was fully charged and I was using it for 30 minutes beforehand, whilst using it, it kept saying force closure on chrome clock, that's when I decided to restart the device as it kept popping up force closure every 20 seconds roughly, the device seemed bricked even thou I have never rooted it or anything. I got the device replaced immediately today and am not bothering with the 4.2 update until Goole releases a stable update. Because I have not updated the new tablet works like a charm thank god.
Tip: if this happens to your device within 28 days of purchase take it back to store for a refund not replacement. You are entitled to a refund under sales of goods act. Then once you got a refund buy the device again if you want another. reason I say to get refund first is if you just get a replacement your 28 days start from when you bought the first tablet, and won't start from the date you got tablet replaced. Buy getting a refund first then re buy it this way your 28 days start from the date you rebought it from. That way if tablet buggers up again you got 28 days all over again to get a replacement or refund. I did this today so now instead of just 25 days remaining to get refund if I just got a replacement and got a refund then rebought it and now have 28 days to get a refund or replacement. That way of mine does happen again even thou I'm not installing update it still gives me a new 28 day period.
Sent from my Nexxs 7 using xda app-developers app
Click to expand...
Click to collapse
I also bought my device about a week ago but im still on 4.1. i think i will wait before i apply any update, to make sure things getting stablized with a new version
Edit.. Nevermind.. I'm in a jumping to conclusions bad mood.. Away from the keyboard I go.
4.2 update won't brick your device. It is a Nexus - just about impossible to brick. You had a problem - but it was not the update.
Sent from my Nexus 7 using xda app-developers app
There are many running 4.2 Builds (Eclipse being one of them) and are having no issues.
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
Well maybe it wasn't but its possible and wanted to warn others. Whether people update is there choice obviously.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I concede with approximately three million people updated by now, you could have been the one to find the error in the update.
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Jellybean 4.2 Ruined my Asus nexus 7.
X_Fact0r said:
Mine is on 4.2 and I haven't had any problem you described. It could have been just that one tablet.
Click to expand...
Click to collapse
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Kpennett said:
Seriously, just the "one" tablet, get a clue....
Bluetooth, ruined, no stereo anymore. Battery life/charging time, ruined. Lag, lag, lag...
Stupid one sided "fat clock" December missing in contacts event option. some strange keyboard swipe came & went away!
Complete rubbish in this update...
Click to expand...
Click to collapse
The guy you were replying to was talking about the OP's issue which was supposedly a bricked Nexus as a result of upgrading to 4.2. It has nothing to do with the items you mentioned, so I would suggest that he is not the one who needs to "get a clue".
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed. you could have cleared the data for the chrome clock in manage apps(probably would have fixed your issue), you also could have factory reset and manually reupdated the official 4.2 release(without needing root).
Click to expand...
Click to collapse
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
mr23 said:
as I stated the device would not turn on at all, no sign of life plugging in charger and unable to boot into recovery to do a factory reset, you obviously did not bother to read my post properly.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
simms22 said:
your issue could have been fixed by you, easily. besides that, you didnt have a brick. a brick is when your device either wont power on or wont pass the google screen(and wont do anything else), and cant be fixed.
Click to expand...
Click to collapse
THANK YOU. The term brick started with the Linksys routers and a brick was just that, a brick, a paperweight, doorstop, and was a very real possibility (though rare).
Before that PCs would be called anchors or door-stops but those terms were also used for PCs that were beyond any possible usefulness rather than just being beyond repair.
At least say soft-brick.
Sent from my Nexus 7 using xda premium
---------- Post added at 02:07 PM ---------- Previous post was at 01:51 PM ----------
dilldoe said:
well there is no indicator when you plug in the charger. if you hold the power button down for 15 sec, you should be able to reboot. there were many times that I thought my n7 was bricked, but holding down the power button for awhile got it to reboot
Click to expand...
Click to collapse
If you can pull or remove the battery you can leave the battery out for 15 minutes. That can revive a device that has become non responsive.
I dunno is the battery on the N7 soldered in or use a ribbon connector?
Sent from my Nexus 7 using xda premium
OP, your device probably wasn't bricked, you need to press the power button for 5>7 seconds and it would of powered on, if for you get the count wrong the Nexus 7 wouldn't power up, this is why you thought it was bricked, in any case, all you needed to do is press and hold the power button for 20>30 seconds and i would of powered on.
fernando sor said:
When did we get a 24th month?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
In some parts of the world the day comes before the month, the UK > 24/11/2012, US > 11/24/2012.
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
mr23 said:
I held the power button down multiple times for 10, 20 and 30 seconds and it still never came on. Oh well each to there own opinion.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I only mentioned the above because you didn't say in any of your posts that you had tried this.
Just what this forum needed, more *****ing.
May be a defect device most likely due to hardware. Other than the some performance issues and some minor ones here and there, I don't think anyone got their device bricked. I hope the new one will be a better experience. Also it'll be informative if you could have mentioned the first four alpha numeric serial number.
Sent from my Nexus 7 using xda premium

[Q] Can someone kindly explain to me what just happened?

I got into the house today, after a long day at work. Decided I'll put my phone on charge. I'm that type of guy that likes his phone to always be towardsthe 90% when it comes battery, barely happens though . So I left it on charge whilst I went into the shower. I came out, and I tried entering my password, which was the "pattern lock." I would press the power button to do so, and a few times, the screen turned around. So I tried entering it, and it wouldn't take no feedback. So, I locked it again, by the use of the silver power button, and this time it came up the right way round, thankfully. When I entered my pin again, it took the feedback but didn't progress. I recently got this phone, and it's been a few weeks since I've made the purchase. As it clearly seems, it wouldn't unlock, so I decided to switch my phone on and off. Guess what?
The phone was fricking on the "Please wait, Shutting Down" notification. So I waited and waited till I got fed up. It lasted around an hour. I was really furious, and was about to call my carrier service (Orange/EE) when it was pointed out to me they'll end up giving you a refurbished model rather than a brand new one. I looked up on the internet, and it wasn't anywhere. At this point I tried the solutions of PRESSING THE RED BUTTON NEXT TO THE SIM CARD TRAY or PRESSING THE VOLUME DOWN AND POWER BUTTON TOGETHER. Those simply didn;'t work. I couldn't even boot into safe mode on my phone. So I went on the PC in order to Restore my phone. Maybe that was the last hope. As soon as I plugged the phone into the PC, via the cable, the phone finally reboots and works.
Right now, I'm worried, that this may occur in the future. I hope it doesn't because maybe next time this fix may not work. That's the worry. So, could someone kindly explain to me what exactly happened? Please?
-Haleem.
I honestly have no idea what exactly happend to your phone, and I doubt anyone does. From my experience the current Z1 firmware isn't the most stable though. I've had a few times where my phone would randomly freeze while I was using the phone. What always worked for me was get a paperclip out and press & HOLD the red button next to the sim tray until you feel a few vibrations. (3 iirc) Then I turn the phone on and everything is fine again.
It's no workaround but if I were you I wouldn't worry too much. Just wait until Sony brings out the 4.3 or 4.4 update and hope they fixed the problems. Until then, keep a paperclip in your pocket.
Always press the red button, i call it emergency button or redboot, whatever...when it comes to that matter.haha! B1nny is right maybe it's about the firmware...firmware mulfunction sometimes..
sent from future!
Volume up and power does the same thing without the need for a paperclip to be on hand
Sent from my C6903 using XDA Premium 4 mobile app
Haleem98 said:
... I was really furious, and was about to call my carrier service (Orange/EE) when it was pointed out to me they'll end up giving you a refurbished model rather than a brand new one...
Click to expand...
Click to collapse
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
bogdan wst said:
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
B1nny said:
I honestly have no idea what exactly happend to your phone, and I doubt anyone does. From my experience the current Z1 firmware isn't the most stable though. I've had a few times where my phone would randomly freeze while I was using the phone. What always worked for me was get a paperclip out and press & HOLD the red button next to the sim tray until you feel a few vibrations. (3 iirc) Then I turn the phone on and everything is fine again.
It's no workaround but if I were you I wouldn't worry too much. Just wait until Sony brings out the 4.3 or 4.4 update and hope they fixed the problems. Until then, keep a paperclip in your pocket.
Click to expand...
Click to collapse
Thanks for the advice. And thanks to everyone else too. 4.3 should bre released this month, if everything goes well, for the Z, Z ULTRA and Z1. Not sure about other devices, however in January we should see the release of KitKat, which I'm looking forward to seeing.#
PS. With the Red Button, I pressed it but nothing happened. I probably didn't push it all the way, or didn't hold it down long enough. I just pressed it once, and then left it.
bogdan wst said:
I know Sony's international policy states that they could replace your phone under warranty with a refurbished one or that they could use second hand materials to repair your phone, but in my country that kind of policy is forbidden. The law in my country says that all the repairs must be done using new materials or the device must be replaced with a brand new one.
p.s. - also, the legal warranty term in my country is 2 years, though Sony's policy states 1 year warranty.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's good to know! Here, I'm not sure what materials they use to fix the phone, however I do know for sure they don't give you a brand new phone. That sucks. Where you from btw?
What makes you say January for kit kat, Sony have said no such thing, just that kit kat had been promised with no eta
Sent from my C6903 using XDA Premium 4 mobile app
Yeah, it wouldn't make much sense at all to release kitkat in January and 4.3 in December. It's just 4 weeks in between and if everybody knew that 4.4 is coming so soon, hardly anyone would go through the hassle of updating and then again. At least I wouldn't and wait until 4.4.
Therefore, Sony will either release 4.4. straight away or later and skip 4.3 or release 4.3 in December and 4.4. in March or something. I assume the latter will be the case.
Haleem98 said:
That's good to know! Here, I'm not sure what materials they use to fix the phone, however I do know for sure they don't give you a brand new phone. That sucks. Where you from btw?
Click to expand...
Click to collapse
I live in Romania (Eastern Europe).
Sent from my C6903 using XDA Premium 4 mobile app

[Q] Root or no if I plan to sell

Hey all,
Just upgraded to the One this last week from the HTC Mytouch 4g Slide, and so far I love everything about the phone except the camera. Which is alright because the HTC M8 is supposed to have a (much) better camera (obviously we've only got a little to go on right now).
I had rooted and installed a custom ROM on my MT4GS, which I loved, but I'm thinking I'm going to keep stock ROM on this one. The only thing I'd want to root it for would be to have more control over the phone and a wider array of available apps.
But I plan on selling the phone once the M8 comes out in May-June.
What is your advice? Is it worth rooting for the couple of months? Is there a risk associated with decreasing the sell price of the phone? Other thoughts?
GiftigDegen said:
Hey all,
Just upgraded to the One this last week from the HTC Mytouch 4g Slide, and so far I love everything about the phone except the camera. Which is alright because the HTC M8 is supposed to have a (much) better camera (obviously we've only got a little to go on right now).
I had rooted and installed a custom ROM on my MT4GS, which I loved, but I'm thinking I'm going to keep stock ROM on this one. The only thing I'd want to root it for would be to have more control over the phone and a wider array of available apps.
But I plan on selling the phone once the M8 comes out in May-June.
What is your advice? Is it worth rooting for the couple of months? Is there a risk associated with decreasing the sell price of the phone? Other thoughts?
Click to expand...
Click to collapse
No one has any input?
GiftigDegen said:
Hey all,
Just upgraded to the One this last week from the HTC Mytouch 4g Slide, and so far I love everything about the phone except the camera. Which is alright because the HTC M8 is supposed to have a (much) better camera (obviously we've only got a little to go on right now).
I had rooted and installed a custom ROM on my MT4GS, which I loved, but I'm thinking I'm going to keep stock ROM on this one. The only thing I'd want to root it for would be to have more control over the phone and a wider array of available apps.
But I plan on selling the phone once the M8 comes out in May-June.
What is your advice? Is it worth rooting for the couple of months? Is there a risk associated with decreasing the sell price of the phone? Other thoughts?
Click to expand...
Click to collapse
Only if you are running something that requires root
I would like to use an app that allows me to restart or power off without using the power button at the top of the phone. Also ES File Explorer is nice when it has root privileges.
I'm just worried about it affecting the potential selling price.
Sent from my HTC One using xda app-developers app
GiftigDegen said:
I would like to use an app that allows me to restart or power off without using the power button at the top of the phone. Also ES File Explorer is nice when it has root privileges.
I'm just worried about it affecting the potential selling price.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well, if u restore the phone correctly 2 its unrooted state, nobody will even come 2 know that it was ever rooted. I unrooted my rooted phone and sent it for warranty repair. The phone was THAT STOCK. completely untraceable if restored correctly. So, no, it wont affect selling price
BTW, throw it ur warranty card. It will fetch u a higher price
If you want to use something that needs root, just do it
When you will sell the phone, just back stock and you will not have problems
BartLuke94 said:
If you want to use something that needs root, just do it
When you will sell the phone, just back stock and you will not have problems
Click to expand...
Click to collapse
Same answer, no doubt, everything well provided here
I didn't know I could relock the boot loader once it was unlocked?
Sent from my HTC One using xda app-developers app
GiftigDegen said:
I didn't know I could relock the boot loader once it was unlocked?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It will say relocked
Doesn't that just tell the purchaser that e fiddled with it and the warranty is voided?
Sent from my HTC One using xda app-developers app

Verizon LG G2 will not turn on. Just vibrates

My Verizon LG G2 was rooted and was trying to install CWM. Was booting into recovery through CWM App and now phone will not turn on at all. Just vibrates when I hit the power button. Any help please?
The Loki patch is not a bootloader unlock you cannot install cwm through ROM manager you have to use an app called freegee once the screen is not turning on I don't think its fixable I may be wrong but it sounds like its really bricked
Sent from my LG-VS980 using Tapatalk
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Crap spell checker added once
Sent from my LG-VS980 using Tapatalk
I used Freegee to install. Was trying to boot into recovery using CWM.
Same problem
there has to be some sort of a fix... I downloaded freegee, then installed TWRP, rebooted it, and now it wont turn on, is NOT recognized by my computer, and wont even load the logo after i hold the power + Vol. Down. if I hold them for a while, red LED will show until I let go of them.
Same thing happened to me today. Cant get it to come on at all.
hopk1719 said:
My Verizon LG G2 was rooted and was trying to install CWM. Was booting into recovery through CWM App and now phone will not turn on at all. Just vibrates when I hit the power button. Any help please?
Click to expand...
Click to collapse
Has happened to a few of us. I wish I would have seen this post before I tried to flash recovery
The dev of freegee has removed twrp from the app until he finds out what happened plug your phone in maybe 30 minutes and try to turn it on the dev of freegee says your g2s should be fixable don't know how but he knows this phone a lot better than me if it still won't turn on wait a few days and hopefully someone will come up with a fix I feel bad for you guys hope you can get your g2s fixed
Sent from my LG-VS980 using Tapatalk
---------- Post added at 12:34 AM ---------- Previous post was at 12:18 AM ----------
Correction he has removed 12b support entirely
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
The dev of freegee has removed twrp from the app until he finds out what happened plug your phone in maybe 30 minutes and try to turn it on the dev of freegee says your g2s should be fixable don't know how but he knows this phone a lot better than me if it still won't turn on wait a few days and hopefully someone will come up with a fix I feel bad for you guys hope you can get your g2s fixed
Sent from my LG-VS980 using Tapatalk
---------- Post added at 12:34 AM ---------- Previous post was at 12:18 AM ----------
Correction he has removed 12b support entirely
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yah, this sucks. Just curious if the manual way is working fine with the ota 12b?
I wouldn't try it its not freegee the app I wonder if Verizon/lg patched the bootloader to deny our current Recovery's this seems to be happening to people who just bought there g2s they must have just patched the bootloader but no ota update this has Verizon's name written all over it
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
I wouldn't try it its not freegee the app I wonder if Verizon/lg patched the bootloader to deny our current Recovery's this seems to be happening to people who just bought there g2s they must have just patched the bootloader but no ota update this has Verizon's name written all over it
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
I bought a used one and used the app and my phone is bricked. I'm talking about manually using adb. That method works still?
It is not the app it is the recovery shellnut thinks verizin /lg did something we are all very confused if I were you just to be safe I wouldn't try it
Sent from my LG-VS980 using Tapatalk
Is there any news on this? I have tried everything to get the g2 to fire back up but no luck. When charging the led blinks red. When attempting to turn it on the phone vibrates every 2 seconds. I think I am just going to get a replacement. Anyone have any advice?
On a separate note, I have no idea why this happened. I clean wiped, installed a rom, rebooted all from recovery and the phone never booted into anything. I wasn't even a slight bit worried because I know I did this correctly.
I appreciate it, thanks.
mattandroidmatt said:
Is there any news on this? I have tried everything to get the g2 to fire back up but no luck. When charging the led blinks red. When attempting to turn it on the phone vibrates every 2 seconds. I think I am just going to get a replacement. Anyone have any advice?
On a separate note, I have no idea why this happened. I clean wiped, installed a rom, rebooted all from recovery and the phone never booted into anything. I wasn't even a slight bit worried because I know I did this correctly.
I appreciate it, thanks.
Click to expand...
Click to collapse
Just get a replacement. tell them that it wont turn on. DO NOT tell them that you rooted it. hahaha
Just had this happen to me.
It's probably dead.
Plug it in and give it some time to charge.
I finally got into recovery mode and was able to restore a ROM (bad flash and was stuck at the LG logo)
Freegee has been bricking devices since its conception. I'm surprised people are still trying to use it.
If anyone reads this before trying to use it, I would suggest not to.
I've used flashify once and it worked fine, but it's really best to push it via adb. Don't know how? Google is your friend. Or the search function on these forums. There's full guides on how to push a recovery on the g2.
Taking the easy way is normally never the best way.
Sent from my VS980 4G
So does this mean the phone is fried? I received mine like this and have no idea what to do. I am not a Verizon customer so I have no way to return the phone. I took it in a trade for my phone thinking it must be fixable and now I am without a device. I know it is my own fault for not doing my research first but this really just sucks :/
nickkeslar said:
So does this mean the phone is fried? I received mine like this and have no idea what to do. I am not a Verizon customer so I have no way to return the phone. I took it in a trade for my phone thinking it must be fixable and now I am without a device. I know it is my own fault for not doing my research first but this really just sucks :/
Click to expand...
Click to collapse
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Lawlrus said:
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Click to expand...
Click to collapse
No download mode, no recovery. The stupid LED wouldn't even light up. Luckily, I was fortunate enough to get my old phone back. A guy found me on craigslist and texted me asking me to unlock his model LS980 for T-Mobile, and in turn he would trade me the VS980 for a Droid Ultra. And like I said, I obliged and thought I could fix it, without doing my research first. Well like I said, I was fortunate enough that he traded me back today. Now I have another swap set up with a guy tomorrow, to trade my Ultra for his LS980. But this one has issues too. For some reason it has no sound at all, unless you use a Bluetooth. I'm sure that will be annoying really really fast, so anyone have any ideas where I can find the info to fix this? Lol
nickkeslar said:
No download mode, no recovery. The stupid LED wouldn't even light up. Luckily, I was fortunate enough to get my old phone back. A guy found me on craigslist and texted me asking me to unlock his model LS980 for T-Mobile, and in turn he would trade me the VS980 for a Droid Ultra. And like I said, I obliged and thought I could fix it, without doing my research first. Well like I said, I was fortunate enough that he traded me back today. Now I have another swap set up with a guy tomorrow, to trade my Ultra for his LS980. But this one has issues too. For some reason it has no sound at all, unless you use a Bluetooth. I'm sure that will be annoying really really fast, so anyone have any ideas where I can find the info to fix this? Lol
Click to expand...
Click to collapse
I am pretty sure that LG has a 1 year warranty and they would've replaced it for you for free. I went to Verizon and they sent me a new one right away but a while back I had upgraded my old droid 1 before the 1 year period ended and I bricked it just messing around. Motorola replaced it with a refurb and I never even went to Verizon. I just had to pay shipping. Maybe you should try the same thing. Just send a couple emails back and forth with LG customer support and see what happens. Good luck.
Add me to the brick list
Lawlrus said:
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Click to expand...
Click to collapse
Mine did the same thing this morning, although it has been fine for 2 months since root+xposed+freegee (for TWRP).
But if I send it back for warranty replacement, will they be able to see it has been rooted if it won't turn on? I love the phone, but really don't want to be billed full price for a new one.

Custom button mappings using custom firmware

Hi all,
I have an original pebble that has a non functioning back button. Unfortunately it is an earlier version without a screwed on back meaning there is no way to open it up and fix any loose connections without completely destroying the watch.
I was wondering if it would be possible to create a custom firmware with the back button remapped to something like long press up. If not then it'll be a sad end for my faithful watch.
Cheers
Andrew
contact pebble support and ask how do you get it fixed you may get lucky you and get the option of RMA or a way to get it fixed cheaply
Sent from my SM-G920F using XDA-Developers mobile app
randomhkkid said:
Hi all,
I have an original pebble that has a non functioning back button. Unfortunately it is an earlier version without a screwed on back meaning there is no way to open it up and fix any loose connections without completely destroying the watch.
I was wondering if it would be possible to create a custom firmware with the back button remapped to something like long press up. If not then it'll be a sad end for my faithful watch.
Cheers
Andrew
Click to expand...
Click to collapse
you can buy a time steel for under $100 and a non steel for less than that. just upgrade and experience a massive upgrade!
Sent from my Moto G (4) using Tapatalk
kmaximax said:
contact pebble support and ask how do you get it fixed you may get lucky you and get the option of RMA or a way to get it fixed cheaply
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
Way out of warranty haha I purchased it the first week it was available.
somnambulator said:
you can buy a time steel for under $100 and a non steel for less than that. just upgrade and experience a massive upgrade!
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
I just found it collecting dust, I've actually been on android wear for a while now.
I'm sorry to hear that
Sent from my Moto G (4) using Tapatalk

Categories

Resources