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?).
Related
Hi
can someone direct me to some stock/close-to stock roms for lg g2x? i sold the phone. do you think i need to revert it to unroot and put back 2.3.3 stock rom before sending it out? what would you do?
Thanks,
sold it to a private party? no reason you "have" to do anything to it. the stock rom can be found in the dev section though.
yes i am selling to people on ebay. thats private i guess. i search through the development section but it not easy to spot it.
Second page in the Dev section...
Stock Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0
Yeah, you WANT to set anything you sell on eBay back to stock....
Why? Because they might take it for tech support after they buy it.
I learned that lesson the hard way 2 or 3 years ago...
When I got my G1, I sold my old HTC Touch Vogue on eBay. It was unlocked and running a Rom from the forums here on xda (NFSFan's I believe)... It stated so *VERY CLEARLY* in the description.
Well, the buyer took it to the Sprint store to activate it. Now, I knew it could be activated because I'd activated it on another line just to make sure. However, the guy at the Sprint store took ONE LOOK at it and refused to activate it since it wasn't running Sprint firmware.
The buyer emailed me back asking for help, and I assured him that it could be activated, and gave him a link to instructions on how to do so, and even gave him my phone# in case he had any questions.
Next thing I know, a chargeback hit my Paypal account for the full purchase price of the phone... apparently the guy took it back to the Sprint Store who again refused to activate it - and this time called his credit card company from the Sprint Store and the rep told them the device was broken.. So they charged back my account...
Thing is, nothing was wrong with the device, and the buyer knew what he was buying. Not only did it get charged back, but Sprint confiscated the device claiming the reason it couldn't be activated this time was that it was stolen (which it certainly wasn't)... so I was out the full sale price PLUS did not get the device returned...
I learned my lesson - NEVER EVER SELL A ROOTED/CUSTOM FIRMWARE DEVICE. Ever. Period. Sell it in FACTORY CONDITION because you never know what kind of idiot is going to get it on the other end.
sorry to hear your unfortunate story. i guess i will unroot it and do a factory rom install
lotherius said:
Yeah, you WANT to set anything you sell on eBay back to stock....
Why? Because they might take it for tech support after they buy it.
I learned that lesson the hard way 2 or 3 years ago...
When I got my G1, I sold my old HTC Touch Vogue on eBay. It was unlocked and running a Rom from the forums here on xda (NFSFan's I believe)... It stated so *VERY CLEARLY* in the description.
Well, the buyer took it to the Sprint store to activate it. Now, I knew it could be activated because I'd activated it on another line just to make sure. However, the guy at the Sprint store took ONE LOOK at it and refused to activate it since it wasn't running Sprint firmware.
The buyer emailed me back asking for help, and I assured him that it could be activated, and gave him a link to instructions on how to do so, and even gave him my phone# in case he had any questions.
Next thing I know, a chargeback hit my Paypal account for the full purchase price of the phone... apparently the guy took it back to the Sprint Store who again refused to activate it - and this time called his credit card company from the Sprint Store and the rep told them the device was broken.. So they charged back my account...
Thing is, nothing was wrong with the device, and the buyer knew what he was buying. Not only did it get charged back, but Sprint confiscated the device claiming the reason it couldn't be activated this time was that it was stolen (which it certainly wasn't)... so I was out the full sale price PLUS did not get the device returned...
I learned my lesson - NEVER EVER SELL A ROOTED/CUSTOM FIRMWARE DEVICE. Ever. Period. Sell it in FACTORY CONDITION because you never know what kind of idiot is going to get it on the other end.
Click to expand...
Click to collapse
Precisely why I deal locally and accept cash only for anything I sell.
Sent from my Nexus S 4G using XDA App
I am at the last step of unrooting the phone. Im using superoneclick v2.3.3. do i power on the phone and plug in usb and click "unroot"? superoneclick (not responding) at Installing BusyBox, adb command type ChangeMode.
the program not responding, did i do something wrong? anyway i can remove the superuser icon in the drawer, it is still there.
I use a different version and it work
tainle said:
I am at the last step of unrooting the phone. Im using superoneclick v2.3.3. do i power on the phone and plug in usb and click "unroot"? superoneclick (not responding) at Installing BusyBox, adb command type ChangeMode.
the program not responding, did i do something wrong? anyway i can remove the superuser icon in the drawer, it is still there.
Click to expand...
Click to collapse
Try what was done at this link.
http://forum.xda-developers.com/showthread.php?t=1441929
First one was hacked almost immediately. Ended up perma-roaming with an IMEI of 0.
They replaced that with a new one. Of course they wanted to re-up my contract and steal my unlimited data. I looked the guy dead in the eye and said "No, that's unacceptable." He said "but unlimited data isn't in the system." I said "There's no 'system' to it. I take my old SIM, put in in a new phone, and walk out." Then he wanted to tell me that wouldn't work, until I grabbed my old phone, SIM, and threw it in the new phone. Then the manager walked up and said I could go.
That phone lasted until yesterday. Capacitive touchscreen starts acting up. Reboot, nothing. Turn it off for a while (CM10 was running hot), and it started working for just a couple of minutes. Restored to stock and it stopped working all together.
Took that to the store, and they were nice once they figured out that this one didn't come from online, but another store. Then they realized it was out of 14 days so it had to be a refurb. Wanted to ship it with free 5 day, but I paid $15 for it to get here by 10am this morning. Not a bad deal, over all.
Refurb arrives this morning, pull the SIM, battery, etc from the old one, and boot it up. Capacitive layer works properly, so that's good. Skip all the My Verizon and Google stuff, because I want to get everything tested. Open a few apps, good. Press physical home button....
NOTHING. Press it again. Nothing. Third time (really pressing hard this time), it pauses for a few seconds then slowly crawls back to the homescreen.
Freaking refurb. I call up verizon and they were super nice. Explained this was my 3rd phone, and they are overnighting another GS3 for free. Let's hope this lasts a little longer.
Edit: just realized this was my first actual post! I've been a member here since I got my first smart phone: an HTC Touch with WM 6!
I'll bet those VZW reps are loving to see you come through the door :laugh:
It's amazing how easy it is to get into the refurb vortex and not be able to get out. As you've seen, device after device has some inconspicuous issue that requires a return. These forums are loaded with these stories.
Hopefully the next one will be the one that keeps you happy, out of the VZW stores, and out of that vortex.
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
con247 said:
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
Click to expand...
Click to collapse
Yeah, I was in IRC while switching to CM10. invisibleK tried to help me out, but this was before the EFS or QPST fixes.
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
no wonder verizon doesnt like people rooting their phones. op's fault
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
luke1333 said:
no wonder verizon doesnt like people rooting their phones. op's fault
Click to expand...
Click to collapse
Yeah, I'd like to say it's vzw's fault for locking things down, but it happens on other networks as well. Looks like a Samsung issue.
Jothen2002 said:
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
Click to expand...
Click to collapse
Hah, I tried to switch to a gnex and they talked me out of it.
tgom222 said:
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
Click to expand...
Click to collapse
Yeah, they should replace it, just play dumb and make sure you're on stock. But you'll end up with a return if it's been more than 14 days, and you really don't want that. Instead, just use QPST to write your IMEI to your phone. You don't need a backup, just the number on the back of the phone.
Neverendingxsin said:
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
Click to expand...
Click to collapse
How is a faulty capacitive layer on a touchscreen my fault? A ROM doesn't make a touchscreen go bad.
Anyone able to make purchases with google wallet or softcard after updating their firmware to 4.4.3?
nomisunrider said:
Anyone able to make purchases with google wallet or softcard after updating their firmware to 4.4.3?
Click to expand...
Click to collapse
I'm on the latest firmware and running NuSenseSIXv2.0 (4.4.3 based). Softcard works as expected after setting up the Rootcloak Xposed module.
shortstuff_mt said:
I'm on the latest firmware and running NuSenseSIXv2.0 (4.4.3 based). Softcard works as expected after setting up the Rootcloak Xposed module.
Click to expand...
Click to collapse
Same here with rootcloak
Sent from my HTC6525LVW using Tapatalk
nomisunrider said:
Anyone able to make purchases with google wallet or softcard after updating their firmware to 4.4.3?
Click to expand...
Click to collapse
Same here. I used to use Google Wallet before the update on CVS once in a while. However after the update I'm not able to use it anymore.
Not rooted, running stock Android 4.4.3. OTA Verizon Updated.
I am resetting my phone now and will try soon when I get another chance. Anyway, how did it go for you? is yours working now? I do not have insurance, just ran out two days ago when I did a plan change. Sucks big time now that I have to get to know that it doesn't work. Also, just to be sure I tried ISIS/Softcard Wallet as well to see if it is the Google Wallet itself is blocked or handicapped for some reason. But to my surprise, ISIS/Softcard does not work as well. I am doubting the hardware now. Or this is a solid 4.4.3 Update bug that is causing our device to not function as normal. Question is, is Verizon aware of this? How do we report this to Verizon?
According to what I see here, only few have been affected it seems? or is it so?
I am left with many more questions than answers ever since the update.
P.S - After the update my phone isn't as smooth as it was before either. Feels like the I am experiencing choppy frame rates often times. But not to the level that I will fault the phone.
Please help. Let me know what worked for you and what didn't.
Deepak Sanje said:
Same here. I used to use Google Wallet before the update on CVS once in a while. However after the update I'm not able to use it anymore.
Not rooted, running stock Android 4.4.3. OTA Verizon Updated.
I am resetting my phone now and will try soon when I get another chance. Anyway, how did it go for you? is yours working now? I do not have insurance, just ran out two days ago when I did a plan change. Sucks big time now that I have to get to know that it doesn't work. Also, just to be sure I tried ISIS/Softcard Wallet as well to see if it is the Google Wallet itself is blocked or handicapped for some reason. But to my surprise, ISIS/Softcard does not work as well. I am doubting the hardware now. Or this is a solid 4.4.3 Update bug that is causing our device to not function as normal. Question is, is Verizon aware of this? How do we report this to Verizon?
According to what I see here, only few have been affected it seems? or is it so?
I am left with many more questions than answers ever since the update.
P.S - After the update my phone isn't as smooth as it was before either. Feels like the I am experiencing choppy frame rates often times. But not to the level that I will fault the phone.
Please help. Let me know what worked for you and what didn't.
Click to expand...
Click to collapse
Sorry this probably doesn't help you much but I am totally stock 4.4.3 - no s-off no root and Softcard ( used to be Isis ) works fine for me. Just used it this morning.
Hope you get your issue figured out.
Thanks for your response,
DangerousDave said:
Sorry this probably doesn't help you much but I am totally stock 4.4.3 - no s-off no root and Softcard ( used to be Isis ) works fine for me. Just used it this morning.
Hope you get your issue figured out.
Click to expand...
Click to collapse
Thanks for the response, Honestly, anything and everything helps. Since you have a Verizon M8, assuming from your signature, I guess I am in the minority or rare bunch who's device is affected. I am glad to know that your device is functioning as normal.
I do not have insurance at the moment. And I am sad to learn that I have to send my device to HTC for repairs. Which takes about 10-14 days without phone.
Does Verizon do loaner phones?
Deepak Sanje said:
Thanks for the response, Honestly, anything and everything helps. Since you have a Verizon M8, assuming from your signature, I guess I am in the minority or rare bunch who's device is affected. I am glad to know that your device is functioning as normal.
I do not have insurance at the moment. And I am sad to learn that I have to send my device to HTC for repairs. Which takes about 10-14 days without phone.
Does Verizon do loaner phones?
Click to expand...
Click to collapse
You should be covered under verizons one year manufacturer warranty go in to a verizon corporate store they will probably overnight you another m8, and from what most assume usually they seem to always send a new m8 because they are really hard to disassemble so many thing they replace with new. I know many people that got an m8 replaced through asuron the verizon and at&t insurance and everyone says they got a new one because you can go into the settings and they dont show reconditioned and usually show a build date within a couple months of when they receive them.
I say take it to a verizon owned corporate store steer clear of verizon dealers a corporate store can do more for you like overnight you a replacement.
Bit the bullet and called HTC.
Roefastford said:
You should be covered under verizons one year manufacturer warranty go in to a verizon corporate store they will probably overnight you another m8, and from what most assume usually they seem to always send a new m8 because they are really hard to disassemble so many thing they replace with new. I know many people that got an m8 replaced through asuron the verizon and at&t insurance and everyone says they got a new one because you can go into the settings and they dont show reconditioned and usually show a build date within a couple months of when they receive them.
I say take it to a verizon owned corporate store steer clear of verizon dealers a corporate store can do more for you like overnight you a replacement.
Click to expand...
Click to collapse
Bit the bullet and called HTC. Found out there is another program that they send out a device in advance, overnight that is along with a mailer envelope to return our old unit. But it seems they put a hold on your card for 599 and also a 29 one time fee for this to happen. I am thinking if it is worth going this route. At least this will solve my problem of being without a phone.
But before I do that, I have made sure the HTC Rep to record our coversation and give me time to call back, so that I can test it out one more time.
( Did I tell you some HTC reps are dumb? The first one I talked to, the girl was so stupid that she did not know what is NFC and asked me to explain what it is, and how to use it. Asked me to pause, stopped me numerous times and made me repeat what was not working. After all that, she still did not get it. Hung up the phone on me and left, and did not bother to call me on my backup callback number. Lol. )
---------- Post added at 02:24 PM ---------- Previous post was at 01:40 PM ----------
Just went to CVS and tried my Google Wallet. Wholla, it worked. So the second reset seemed to have fixed the problem. Or did it? I am not sure, only time will tell. I will keep on trying once in a while to be sure that it is not just a fluke.
Here is what I did.
The HTC rep (the second one that is, first one was dumb and rude due to her limited understanding) asked me to reset the phone once more, and when the phone booted up, I unchecked the Settings > Power > Fastboot option. Disabled Softcard/ISIS Wallet in App settings, Installed Google Wallet again. And all seems to be in order now. Not sure what caused the initial trouble.
I will be on the look and report if the trouble comes back again.
Thanks for the suggestions and feedback guys.
Deepak Sanje said:
Bit the bullet and called HTC. Found out there is another program that they send out a device in advance, overnight that is along with a mailer envelope to return our old unit. But it seems they put a hold on your card for 599 and also a 29 one time fee for this to happen. I am thinking if it is worth going this route. At least this will solve my problem of being without a phone.
But before I do that, I have made sure the HTC Rep to record our coversation and give me time to call back, so that I can test it out one more time.
( Did I tell you some HTC reps are dumb? The first one I talked to, the girl was so stupid that she did not know what is NFC and asked me to explain what it is, and how to use it. Asked me to pause, stopped me numerous times and made me repeat what was not working. After all that, she still did not get it. Hung up the phone on me and left, and did not bother to call me on my backup callback number. Lol. )
---------- Post added at 02:24 PM ---------- Previous post was at 01:40 PM ----------
Just went to CVS and tried my Google Wallet. Wholla, it worked. So the second reset seemed to have fixed the problem. Or did it? I am not sure, only time will tell. I will keep on trying once in a while to be sure that it is not just a fluke.
Here is what I did.
The HTC rep (the second one that is, first one was dumb and rude due to her limited understanding) asked me to reset the phone once more, and when the phone booted up, I unchecked the Settings > Power > Fastboot option. Disabled Softcard/ISIS Wallet in App settings, Installed Google Wallet again. And all seems to be in order now. Not sure what caused the initial trouble.
I will be on the look and report if the trouble comes back again.
Thanks for the suggestions and feedback guys.
Click to expand...
Click to collapse
Glad you got it working and I can empathize some of the reps can be infuriating !
i could be able to make purchases using google wallet and im on MIUI digital high v4.9.21
before that i used digital high's GPE rom and it did NFC purchases just fine
No Longer Working - Again
DangerousDave said:
Glad you got it working and I can empathize some of the reps can be infuriating !
Click to expand...
Click to collapse
So as my previous post suggested, after a hard reset and disabling the Softcard/ISIS app, and having Google Wallet as the exclusive app, the tap and pay worked at the CVS. However, when I tried again last night, it is no longer working and not registering the tap anymore at the terminal.
I am confused. Is it the hardware? Should I go ahead with the replacement device from HTC? or Should I just blame the software and keep the phone as is. Although my contacts and account is backed up in Google accounts, I still think its a hassle reinstalling 50+ apps, and restoring the phone to its fully functional day to day state that suited me. I just do not like the hassle of swapping phones.
Any last suggestions guys? Or hardware swap is my only way?
Switched Phones, gave up on HTC One m8.
Deepak Sanje said:
So as my previous post suggested, after a hard reset and disabling the Softcard/ISIS app, and having Google Wallet as the exclusive app, the tap and pay worked at the CVS. However, when I tried again last night, it is no longer working and not registering the tap anymore at the terminal.
I am confused. Is it the hardware? Should I go ahead with the replacement device from HTC? or Should I just blame the software and keep the phone as is. Although my contacts and account is backed up in Google accounts, I still think its a hassle reinstalling 50+ apps, and restoring the phone to its fully functional day to day state that suited me. I just do not like the hassle of swapping phones.
Any last suggestions guys? Or hardware swap is my only way?
Click to expand...
Click to collapse
Update - Got rid of the HTC One M8, swapped for a Galaxy S5 on craigslist and guess what, Google wallet works fine there. Yes, although that is a Verizon phone as well, grass is definitely greener on that side. I do not like the menu system and UI, color etc, but what it supposed to do, it does without any issues. Yes I miss the aluminum body and the build, also the sense 6, but the ease of use with fingerprint sensor and the vibrancy of amoled screen picks up the slack. Wish HTC can use Amoled screens as well.
I was able to use google wallet no problem after the 4.4.3 update at CVS this is however before CVS disabled their NFC payment system.
Stock Rooted.
I was able to use it just fine at Walgreens this morning.
Never had a problem with it 4.4.3 or 4.4.4
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Thanks for the heads up! With JUMP it shouldn't matter, but a device exchange may flag.
Sent from my LG-H901 using Tapatalk
I rooted my Note 4 and 5 with twrp aswell.... Did jump from both with no problem! My last jump was Nov. 15th for the V10 and the promo and had no problem, must be a new policy!!! But yes, always go back to stock before upgrade lol
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
YrrchSebor said:
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
Click to expand...
Click to collapse
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
daveeckert said:
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
Click to expand...
Click to collapse
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
That's weird. I called a store and asked them this exact question before turning in my G3. She said it didn't matter and they were gonna wipe the phone. It's possible she didn't understand the question, but I turned it in with no issues and haven't received any calls over the few days I've had the V10. I'm on the basis Jump plan too.
No issues trading in my Knox-tripped Note 4 a couples months ago. Maybe just that one store is getting a little wacky with the checking lol
Unheard said:
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
Click to expand...
Click to collapse
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
I can't tell the number of rooted phones I've sent back to Verizon and T-mobile, never a word.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
Click to expand...
Click to collapse
Okay you could also block it with root cloak...
Sent from my LG-H901 using Tapatalk
Been on Verizon, Alltel, Sprint, and Ma'Bell. always rooted, never had e Problem. Just make shure you return to stock. I even exchanged a couple of Samsungs with Knox trip, Lucky I guess. I've heard Stories but never met anyone that has been returned or charged a device.
spg900ny said:
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
Click to expand...
Click to collapse
Currently have the Note 5. I wouldn't say there is a lot of dev activity. Then again, I came from a Nexus 6. [emoji2]
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Cool, so no more Jump for me. Looks like a steady stream of Priv's, 950XL's, Moto's, or Nexuses.
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
I just got the V10 and traded in my rooted and ROM'd Galaxy S6 for it. She did the code thing, didn't bat an eye.
Sent from my LG-H901 using Tapatalk
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
What ## code do you enter?
I would imagine that code is more of a quick IMEI/"is the phone stolen" verification rather than checking for root.
daveeckert said:
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Click to expand...
Click to collapse
No, he was pulling your leg. I turned in my note 4 with twrp and a custom rom in October and I had to do the same check, it's just a service code check to make sure it's the same one you bought from tmo, if it checked for root I would never be able to get a phone again because I flashed that phone so much. I talk to the guys at the store and told them I rooted do they.
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.