Related
Recently I noticed that out of nowhere my audio for me phones speaker stopped working. I know its not something to do with the phones overall sound because plugging in headphones or some other audio cable gives me sound when playing music etc. I don't get any sound when playing music through my phones speaker.
Last known thing I did to my phone was try and reflash leedroid's gb 3.3.3 and then the dhd to inspire + audio fix combo in the op of the Dev thread for the leedroid Rom. Now even after nandroid restoring there is still no sound. Fully wiping doesn't give me sound either.
Did my speaker just decide to take a poop (not the best way to describe the speaker) ?
Let me know if you can help me out. Thanks.
Sent from my Inspire 4G using XDA App
Try flashing back to stock. If still an issue, then you are at stock already and can use warranty on it.
Sent from my Inspire 4G using Tapatalk
Downloading the RUU that recently came out to go back to stock. Ill see how that goes. Hopefully I don't have to go all the way back to 2.2 froyo stock and unrooted to fix this.
If nothing works as far as flashing then my speakerphone blew some how. I never increased the volume for long periods of time.
Sent from my Inspire 4G using XDA App
shugga101 said:
Downloading the RUU that recently came out to go back to stock. Ill see how that goes. Hopefully I don't have to go all the way back to 2.2 froyo stock and unrooted to fix this.
If nothing works as far as flashing then my speakerphone blew some how. I never increased the volume for long periods of time.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Well it's no big deal to back to stock. Just do a nandroid and if you need to flash back to rooted everything is saved. It's probably a connection messed up in the phone, not a blown speaker.
Sent from my Inspire 4G using Tapatalk
So I flashed the stock RUU rom for gingerbread 2.3.3. I'm still rooted because that should mess up the speaker phone.
All in all nothing worked. I called ATT and HTC. ATT wants me to pay $125 for a new phone, yet I paid $99 for the phone when I got it. I have the insurance plan and it's under warranty.
Or see if i can fix it by flashing something.
HTC said, just send in the phone once they get it they will try and fix it as long as they don't detect i'm rooted. I don't know if I should go back to no root for the time being send my phone in get it fixed for free hopefully and wait the 6-10 business days for the phone.
HTC said if they can't fix due to some other issue (most likely warranty being voided) then I would have to pay $35 for labor and shipping. And they won't fix my phone.
So those are my options.
I'd choose the HTC option over $125 from ATT.
Let me hear your opinions.
Thanks
shugga101 said:
So I flashed the stock RUU rom for gingerbread 2.3.3. I'm still rooted because that should mess up the speaker phone.
All in all nothing worked. I called ATT and HTC. ATT wants me to pay $125 for a new phone, yet I paid $99 for the phone when I got it. I have the insurance plan and it's under warranty.
Or see if i can fix it by flashing something.
HTC said, just send in the phone once they get it they will try and fix it as long as they don't detect i'm rooted. I don't know if I should go back to no root for the time being send my phone in get it fixed for free hopefully and wait the 6-10 business days for the phone.
HTC said if they can't fix due to some other issue (most likely warranty being voided) then I would have to pay $35 for labor and shipping. And they won't fix my phone.
So those are my options.
I'd choose the HTC option over $125 from ATT.
Let me hear your opinions.
Thanks
Click to expand...
Click to collapse
Dude just unroot your phone... HTC is great to deal with they repaired my rooted n1 no questions asked.
Sent from my Inspire 4G using Tapatalk
shugga101 said:
So I flashed the stock RUU rom for gingerbread 2.3.3. I'm still rooted because that should mess up the speaker phone.
All in all nothing worked. I called ATT and HTC. ATT wants me to pay $125 for a new phone, yet I paid $99 for the phone when I got it. I have the insurance plan and it's under warranty.
Or see if i can fix it by flashing something.
HTC said, just send in the phone once they get it they will try and fix it as long as they don't detect i'm rooted. I don't know if I should go back to no root for the time being send my phone in get it fixed for free hopefully and wait the 6-10 business days for the phone.
HTC said if they can't fix due to some other issue (most likely warranty being voided) then I would have to pay $35 for labor and shipping. And they won't fix my phone.
So those are my options.
I'd choose the HTC option over $125 from ATT.
Let me hear your opinions.
Thanks
Click to expand...
Click to collapse
LOL...HTC actually said to you, unprompted, "as long as we don't detect you're rooted"? Or did you subtly and hypothetically bring up the rooting issue? I'm surprised they said that, given the rooting community is so small compared to the general user base. It would be like your local car dealer saying, "Yes, we will fix your new car under warranty as long as you haven't put a new engine in it". Kind of a rare situation that doesn't warrant even mentioning IMO.
I had the same issue for my phone few months back. It's the speaker popping.
Sent from my Desire HD using XDA Premium App
henrybravo said:
LOL...HTC actually said to you, unprompted, "as long as we don't detect you're rooted"? Or did you subtly and hypothetically bring up the rooting issue? I'm surprised they said that, given the rooting community is so small compared to the general user base. It would be like your local car dealer saying, "Yes, we will fix your new car under warranty as long as you haven't put a new engine in it". Kind of a rare situation that doesn't warrant even mentioning IMO.
Click to expand...
Click to collapse
Yes only a small number roots, but out of that small number most of their repairs come from rooted phones.
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
MyronJ906 said:
Alright guys, after seeing 2.20 being rootable I decided to dive back into the One X. I traded my S3 for it + $50. Flawless S3, seriously. The guy I traded with seemed perfectly cool and legitimate but now an issue has arisen.
I didn't think to check it when we made the trade (though I checked other things like mobile data, etc.) but when I made a call later, the person on the other end couldn't hear me.
Here's what I've found:
Microphone works for recording video
Microphone works *on speaker phone*
Microphone works with an external source (bluetooth headset or earbuds with mic)
but the regular handset microphone does not appear to work.
Does anyone have ANY idea what might cause this? Unfortunately, I've already rooted. Literally the only thing I've done. I tried AOKP nightly, I've tried Nocturnal Limited edition. Next I'm going to attempt a RUU.
I've talked to the guy. He swears it was working, I'd like to believe him but neither of us tested it. He didn't test calls on the S3 either so it's not like he wasn't taking the same gamble.
He says that if I can get it working, he'll trade back but since he gave it to me working (as far as he knows) he won't trade back
I'm at a loss here. Can I (legally) mark the S3 as stolen? In that as far as I know, he made me a bad trade and will not simply give me my device back in return for his and his money
HAAAAALLLLLLPPPPP!
Thanks
Click to expand...
Click to collapse
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
adulel08 said:
tell him you fixed it and when u meet up, switch phones and RUN off. thank me if I helped :good:
Click to expand...
Click to collapse
lol you helped with a good laugh. That's genius, dude
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
---------- Post added at 08:37 PM ---------- Previous post was at 08:29 PM ----------
Can't seem to edit my post. I didn't realize you were using the other microphone. You should run the ruu regardless to at least try and sort out any sort of software issue.
Sent from my HTC One XL
ECEXCURSION said:
Run the ruu. If the microphone works in other situations you're fine. Run the ruu.
And no you can't legally say it was stolen.
Sent from my HTC One XL
Click to expand...
Click to collapse
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
MyronJ906 said:
That's about what I thought actually. I'll run the RUU but can you explain what might have happened? If it's not actually broken hardware I don't have a problem keeping the phone but need to know how to avoid it
Click to expand...
Click to collapse
The microphone volume is a perennial problem with this phone. No one seems to know for sure what causes it. Reseting and ruu'ing ought to fix it.
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
MyronJ906 said:
Thanks guys, downloading the 2.20 RUU now. It does have to be the 2.20 RUU since I'm already on 2.20 right? No downgrading, is that correct?
I really hope this fixes it, because I love the One X. Haha, don't know how I dodged this problem the first time I had it.
Now I must ask and re-verify.
While booted into Nocturnal Lite
Run RUU
Reboot into stock and make sure everything's working
Reinstall recovery via fastboot
Install ROM of choice
Fastboot boot.img for ROM of choice
Boot up
Love One X
That's it right?
Click to expand...
Click to collapse
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
iElvis said:
Correct, you cannot downgrade. But to RUU, you have to relock or it will fail. Also, once you relock, you have to RUU then and there because your phone won't boot up. You'll need to go through the whole unlock/root process again. Remember this will wipe your phone.
Click to expand...
Click to collapse
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
MyronJ906 said:
Cool, so I'm not as much of an idiot as I thought. having a new problem though. All my RUUs keep failing. USB error? I feel like a noob.
I was perfectly fine with my first One X and this one is giving me hell now. That's what I get for dancing with the devil lol
By the way, thanks a lot guys. I usually don't need half this much assistance, but you know ish happens.
Click to expand...
Click to collapse
Did you relock? An RUU will fail otherwise.
iElvis said:
Did you relock? An RUU will fail otherwise.
Click to expand...
Click to collapse
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
MyronJ906 said:
Yeah man, relocked. I'm running the AT&T RUU found here. Fastboot OEM readCID still shows SuperCID, I'm reinstalling HTC Drivers and then I'll restart the computer. Maybe that's all it is.
Click to expand...
Click to collapse
Unplug your phone, turn it off, and restart it. Sometimes that helps. It won't boot, but you can get it back into the bootloader.
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
MyronJ906 said:
Does it need to be in Fastboot or Bootloader? I'm close to giving up on the laptop (which worked fine for the other 90%) and trying my ancient desktop
Click to expand...
Click to collapse
Bootloader.
Pretty sure my drivers have just fubarred. I'm not showing up on adb devices either. GRRRRRR this is driving me mad
EDIT: Finally got the RUU to run. Had to replace the standalone HTC drivers with fullblown HTC sync but it's whatever lol. Now to see if the RUU actually fixes the problem
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
MyronJ906 said:
Ran the RUU. Didn't fix it. I'll run it again, but any more ideas?
Click to expand...
Click to collapse
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
iElvis said:
"It" meaning the microphone? The phone is working okay otherwise? If so, I'm out of ideas. Might try flashing different roms to see if there's any change.
Click to expand...
Click to collapse
Yeah, I meant the microphone still isn't working. I've been on the stock RUU, AOKP, and Nocturnal. All of them have the same issue so I'm expecting that it's hardware.
I just don't know what to do guys. I guess I'll e-mail HTC, swing by the AT&T store in hopes of something, and call it done. I find it ****ty that the guy won't cooperate so far because truthfully I *would* at least cooperate but it's tough when he says it was working when he had it and I say it wasn't working when I had it.
BUT he says that he didn't make any calls that day. However, he "knows it was working when he gave it to me"
Guys, I just don't even know what to do. If I can't get it replaced, he completely won out on the trade. I was originally asking for + $100 and lowered it to + $50 for him. Yet he doesn't want to do anything for me.
I want to handle all of this responsibly, but I also want a completely functional phone
MyronJ906 said:
Can I (legally) mark the S3 as stolen?
Click to expand...
Click to collapse
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
redpoint73 said:
For what purpose, a homeowners/renters insurance claim, or something else? Don't want to sound preachy, but insurance fraud is serious business, and a federal crime. Not worth it for a phone. Homeowners insurance claims for theft also require a police report, which is also something you obviously do not want to falsify.
If the microphone was malfunctioning before you did any mods to the phone, it would seem to me that the guy scammed you. Its highly improbable it was working for him, then just "coincidentally" broke around the time he traded it.
Try unlocking again, and flashing a new ROM. Combination of RUU, then fresh ROM may make a difference. Otherwise, I don't think HTC can do a warranty repair without proof of purchase. But they can probably fix it for a fee. True, the other guy will have made out on the deal, but at least you'll have a working phone.
Click to expand...
Click to collapse
I did mean for the insurance claim. I didn't want to do it fraudulently which is why I asked. I wasn't sure what the exact definition of stolen (or even lost) in this regard is. But this doesn't count so that's no longer an option. Haha I now see that the AT&T warranty plan doesn't cover user idiocy, just drops and spillage.
I'll RUU again then install an AOSP ROM. I'm pretty sure it's the hardware mic that's busted though. Does speakerphone use a secondary microphone? I imagine videorecording does. If so, do the camcorder and speakerphone use the same mic?
Maybe the noisecanceling mic is screwing things up and that could be software but I think the microphone is just physically broken.
Idiot me, being the hardcore modder made changes to the phone *before* testing for the microphone. In my defense, I've owned the One X before so I knew what the hardware was capable of. I knew the current state of ROMs, so why not pick up where I left off?
I'll send HTC a pity e-mail and see where that gets me. Better to try and fail than to never have tried at all.
EDIT: I wanted to ask as well, does anyone think ROM flashing/BL unlocking etc. Really could have caused this? I mean, if it did there's no reason different software shouldn't fix it. But if it's hardware, that establishes that it's more likely that it wasn't my fault, right?
So I noticed when I take video the audio that is recorded is all garbled and static. Any one have this problem? Running 4.2.2 on a DE
Sent from my XT1080 using Tapatalk
No. But I did notice yesterday I had no audio at all. A reboot fixed it.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
jfriend33 said:
No. But I did notice yesterday I had no audio at all. A reboot fixed it.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
Click to expand...
Click to collapse
Nope, thats not it for me. I tried FXZing, and that did not work. I then updated to 4.4. Still didnt work. I am about done with this phone. Now after updating, touchless control isnt working. The old bugs of double home button is back, and when you FXZ it wipes your whole SD Card partition, not just the data partition, so I lost a bunch of stuff.
Anyway, once motox 2 comes out I think I am jumping ship.
coronanlime said:
Nope, thats not it for me. I tried FXZing, and that did not work. I then updated to 4.4. Still didnt work. I am about done with this phone. Now after updating, touchless control isnt working. The old bugs of double home button is back, and when you FXZ it wipes your whole SD Card partition, not just the data partition, so I lost a bunch of stuff.
Anyway, once motox 2 comes out I think I am jumping ship.
Click to expand...
Click to collapse
Surely you could consider letting verizon exchange it? Or FDR and sell it as is? I assume you're unlocked. If so that's gonna suck to lose that. Have you tried any other roms? I mean if you've already lost everything why not try.
I had weird problems on a Galaxy nexus. Switching computers helped somewhat.
Does this phone use different microphones for speakerphone / audio /video recording?
Sent from my Nexus 7 using Tapatalk
jfriend33 said:
Surely you could consider letting verizon exchange it? Or FDR and sell it as is? I assume you're unlocked. If so that's gonna suck to lose that. Have you tried any other roms? I mean if you've already lost everything why not try.
I had weird problems on a Galaxy nexus. Switching computers helped somewhat.
Does this phone use different microphones for speakerphone / audio /video recording?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Well I bought it off Swappa so doubt verizon will do anything. It is a DE edition so I am going to call motorola and see if they will do anything about it.
I probably will try some new roms, just hate losing touchless control, active display, and the gestures to go straight to camera.
I have tried different apps, like instagram, to record video and still no luck with it recording sound.
coronanlime said:
Well I bought it off Swappa so doubt verizon will do anything. It is a DE edition so I am going to call motorola and see if they will do anything about it.
I probably will try some new roms, just hate losing touchless control, active display, and the gestures to go straight to camera.
I have tried different apps, like instagram, to record video and still no luck with it recording sound.
Click to expand...
Click to collapse
Well found out the microphone alltogether does not work. Was working fine two days ago. Anyone have an issue like this? I cant even make calls. Anyone return a DE to motorola and was it easy?
coronanlime said:
Anyone return a DE to motorola and was it easy?
Click to expand...
Click to collapse
If you return it you need to keep pestering them for status or they'll let it sit.
I had to return mine after it dropped dead. I was able to get a replacement, but it was kind of an odd procedure - apparently the folks who do Moto's repairs don't have a way to get new phones, and/or there aren't enough DE's cycling through to have refurbished ones on hand. They eventually told me to buy a new one from Moto's web store and cut me a check to reimburse me. I'm guessing their service is done by a subcontractor.
Ultimately I did end up with a new unit, and wasn't any poorer (they turned around the check about a week after I sent them the receipt).
I'm hoping for your case they can simply swap out the mike assembly, if I recall from one of the teardowns on the web it's a small plugin unit so they should not need to replace the motherboard.
I see no reason they shouldn't support it though, the DE's haven't been out long enough for any of them to be out of warranty.
kenryan said:
If you return it you need to keep pestering them for status or they'll let it sit.
I had to return mine after it dropped dead. I was able to get a replacement, but it was kind of an odd procedure - apparently the folks who do Moto's repairs don't have a way to get new phones, and/or there aren't enough DE's cycling through to have refurbished ones on hand. They eventually told me to buy a new one from Moto's web store and cut me a check to reimburse me. I'm guessing their service is done by a subcontractor.
Ultimately I did end up with a new unit, and wasn't any poorer (they turned around the check about a week after I sent them the receipt).
I'm hoping for your case they can simply swap out the mike assembly, if I recall from one of the teardowns on the web it's a small plugin unit so they should not need to replace the motherboard.
I see no reason they shouldn't support it though, the DE's haven't been out long enough for any of them to be out of warranty.
Click to expand...
Click to collapse
Yeah so moto got back to me quickly. They offered a maxx DE or motox DE with power pack. I went with the motox. More development. Just getting annoyed with all the bugs on the maxx 4.4 and waiting for updates that the x will continue to get on time. I will miss this battery life. Definitely got spoiled.
As for the return they are doing it how Verizon does it. Sending phone with label to send maxx back. Think I need to lock the bootloader prior to sending it back?
Sent from my XT1080 using Tapatalk
coronanlime said:
Think I need to lock the bootloader prior to sending it back?
Click to expand...
Click to collapse
Nah. It's a developer edition, so mucking with the software is perfectly expected.
You might want to do a factory wipe though, just for safety's sake (practice Safe Hex!).
kenryan said:
Nah. It's a developer edition, so mucking with the software is perfectly expected.
You might want to do a factory wipe though, just for safety's sake (practice Safe Hex!).
Click to expand...
Click to collapse
Ha will do. What's funny is the recorder magically started working today. Not perfectly but seems to pick up sound now. I think it's from the sulfer smoke at Yellowstone. That's when it began. Anyway, the upgrade still brought the bugs of double tap home button which annoys the hell out of me so I think I'll go with the X anyway. Seems much more stable and working the way it should.
Sent from my XT1080 using Tapatalk
So I have been loving my pixel and I baby it. However this morning out of nowhere when the phone vibrates it sounds like it is buzzing and probably something is loose inside causing this. Seems others have had this. Long story short looks like I need a replacement. I came from an iphone so it took me a while to set up this phone as ideally as I want. I have rooted it and have TWRP flashed.
Is the best way to set up my new phone when it comes in to back up this one with TWRP, root the new one, flash TWRP on and restore a back up? Will this remember all my settings? Will it back up my apps and info, photos?, notes?.
I'm looking for the fastest way to get set up again
Thanks in advance.
dejanspa said:
So I have been loving my pixel and I baby it. However this morning out of nowhere when the phone vibrates it sounds like it is buzzing and probably something is loose inside causing this. Seems others have had this. Long story short looks like I need a replacement. I came from an iphone so it took me a while to set up this phone as ideally as I want. I have rooted it and have TWRP flashed.
Is the best way to set up my new phone when it comes in to back up this one with TWRP, root the new one, flash TWRP on and restore a back up? Will this remember all my settings? Will it back up my apps and info, photos?, notes?.
I'm looking for the fastest way to get set up again
Thanks in advance.
Click to expand...
Click to collapse
You should use Titanium Backup to back up all user apps+data. Copy that backup to your PC. When you get the new phone, root, install TB and restore. Done!
Do you have a Verizon Pixel? If you do, and the replacement device has the latest security patch, the previous advice is moot since you can't root it any more (locked bootloader).
quangtran1 said:
You should use Titanium Backup to back up all user apps+data. Copy that backup to your PC. When you get the new phone, root, install TB and restore. Done!
Do you have a Verizon Pixel? If you do, and the replacement device has the latest security patch, the previous advice is moot since you can't root it any more (locked bootloader).
Click to expand...
Click to collapse
Okay perfect thanks i'll do that instead. And no verizon pixel, whew!
dejanspa said:
Okay perfect thanks i'll do that instead. And no verizon pixel, whew!
Click to expand...
Click to collapse
Is the replacement on the way already? When you get a new Pixel there is a way to transfer all your programs and settings to your new device at the initial setup even without root yet. But you will want to unlock the bootloader first which will cause a factory reset and then do the transfer. I did it from my n5x and it worked great. I wasn't even unlocked or rooted and I'm still not. I haven't used Titanium backup obviously and don't feel the need to any longer. But if you want root then you might as well backup everything and restore what the transfer misses. Best part of the transfer is that all your settings get ported over to the new device, i.e. sounds, preferences, security settings etc. Titanium will not do that.
Alternately, you can set it all up again which is sometimes fun. It lets you change a bunch of stuff and make it like a new device all over again. But as you said, that does take time. Anyway, good luck with the new one.
bobby janow said:
Is the replacement on the way already? When you get a new Pixel there is a way to transfer all your programs and settings to your new device at the initial setup even without root yet. But you will want to unlock the bootloader first which will cause a factory reset and then do the transfer. I did it from my n5x and it worked great. I wasn't even unlocked or rooted and I'm still not. I haven't used Titanium backup obviously and don't feel the need to any longer. But if you want root then you might as well backup everything and restore what the transfer misses. Best part of the transfer is that all your settings get ported over to the new device, i.e. sounds, preferences, security settings etc. Titanium will not do that.
Alternately, you can set it all up again which is sometimes fun. It lets you change a bunch of stuff and make it like a new device all over again. But as you said, that does take time. Anyway, good luck with the new one.
Click to expand...
Click to collapse
Well currently arguing with google. Since I didn't buy it from google store but a carrier they want me to send the phone in first before they ship the new one. If you buy it from google then they send you a new one first and put a charge on hold on your CC until old one is received. I asked them to do the same for me but they said it's policy. I'm having the issue escalated.
The steps you mentioned is exactly why I want google to send me one first, through my carrier I would probably have to swap it right away and never have both in my hand.
If I get google to send me one, i'll do both things. Root then transfer via google's method and then use titanium as well for the rest of the stuff.
dejanspa said:
Well currently arguing with google. Since I didn't buy it from google store but a carrier they want me to send the phone in first before they ship the new one. If you buy it from google then they send you a new one first and put a charge on hold on your CC until old one is received. I asked them to do the same for me but they said it's policy. I'm having the issue escalated.
The steps you mentioned is exactly why I want google to send me one first, through my carrier I would probably have to swap it right away and never have both in my hand.
If I get google to send me one, i'll do both things. Root then transfer via google's method and then use titanium as well for the rest of the stuff.
Click to expand...
Click to collapse
I have been dealing with the same problem!! I started a thread right below yours called RMA for new Verizon pixel! They want me to be out a phone for some 14 days while I send them my defective device and then they send my new one!
zaksimmermon said:
I have been dealing with the same problem!! I started a thread right below yours called RMA for new Verizon pixel! They want me to be out a phone for some 14 days while I send them my defective device and then they send my new one!
Click to expand...
Click to collapse
I don't remember seeing your response on this on your thread. Why wouldn't you guys return at Verizon? You bought these at Verizon, right? Something doesn't add up. Just curious now. I've never had a Verizon exchange not show up at my door the next day, if ordered before 4pm.
quangtran1 said:
I don't remember seeing your response on this on your thread. Why wouldn't you guys return at Verizon? You bought these at Verizon, right? Something doesn't add up. Just curious now. I've never had a Verizon exchange not show up at my door the next day, if ordered before 4pm.
Click to expand...
Click to collapse
I haven't been back on XDA until now and I haven't checked my thread until just now actually lol. But I bought mine from a different retail store called Nebraska Furniture Mart they have a store in Kansas city Mo where I live and they sell the Verizon variant. I called Verizon first and they told me to contact google. Maybe there was just a misunderstanding with the rep I spoke to? I have tried lots of different options but all are pointing to sending the phone in first because I'm past the 14 day remorse period?
quangtran1 said:
I don't remember seeing your response on this on your thread. Why wouldn't you guys return at Verizon? You bought these at Verizon, right? Something doesn't add up. Just curious now. I've never had a Verizon exchange not show up at my door the next day, if ordered before 4pm.
Click to expand...
Click to collapse
Mine is not from verizon, i'm in Canada. With it being christmas my carrier currently has this phone online only. They have a $300 off activation credit going on right now so have had a huge amount of order and it's couple of weeks back log.
Just to back up the fact that Verizon requires you to go through the manufacturer if it's still on the OEM's warranty, the same happened with my LG G Pad 8.3 LTE (VK810). I was paying for the absolute best Verizon warranty on all three lines, and less than six months after I got this device I had a problem with the screen on the LTE (not dropped or cracked, just not working right), and Verizon wouldn't lift a finger to help me and said I had to go through LG.
Totally off topic but luckily LG gave me the absolute best warranty service I ever received. They had me take my device to a FedEx, LG paid for FedEx to box it up and have it shipped to them. I dropped it off on a Monday evening about 5 PM and the tablet was back in my hands fully repaired (not replaced with a refurb) on Friday of the same week around the same time. Sorry for the OT part. Too bad LG bootloader unlockable devices are rare except maybe through some other carriers (T-Mobile?).
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.