Related
I encourage anyone concerned about the availability of the 3 button download mode, or other issues, to comment on the Samsung Facebook page. I already posted a comment and got a response I find somewhat disturbing... maybe there is strength in numbers.
http://www.facebook.com/samsungmobi...omment#!/samsungmobilecanada?v=wall&ref=notif
Make sure he doesn't duck the question. 3 button means that experienced end users can actually fix a bad flash (lol @ Kies) without having to lose their phone for a month (Allgamer is at the 3 week mark now after sending his phone in).
Hopefully they will provide an answer. I have since returned mine back to Future Shop. I've tried 4 other phones hoping to be able to do an exchange, but all of them had 3 button recovery disabled. If they release a fix for this I will buy the phone in an instant.
I saw your post over there...
Exactly what I figured their response would be... I for one am not holding my breath for an update through Samsung to enable 3 button recovery.
They messed though by inexplicably letting some through with it enabled...Makes it hard to justify why some have it and some don't... If anything, expect an update to disable it on the ones that have it enabled!
I hope otherwise, but in all seriousness, the majority of users will likely never have to use recovery and the average user out there is not an xda-developpers member. Yes, Samsung will have to deal with bricks but probably in their mind, they are making it slightly harder to do 'unauthorized' stuff.
Added a comment
I am also not holding my breath...
n0th1ng said:
Hopefully they will provide an answer. I have since returned mine back to Future Shop. I've tried 4 other phones hoping to be able to do an exchange, but all of them had 3 button recovery disabled. If they release a fix for this I will buy the phone in an instant.
Click to expand...
Click to collapse
I'm pretty much in the same boat. No recovery mode, no sale.
xtoad said:
I saw your post over there...
Exactly what I figured their response would be... I for one am not holding my breath for an update through Samsung to enable 3 button recovery.
Click to expand...
Click to collapse
Please add a comment, the more the better!
DarthV said:
I'm pretty much in the same boat. No recovery mode, no sale.
Click to expand...
Click to collapse
Meh, I am not going that far. Recovery mode is a nice to have but it is not going to deprive me of the best phone on the market by miles (there is not a phone that is going to be better than the 3GS for at least 6 months or more, nothing is in the pipeline that comes close)
brunes said:
Please add a comment, the more the better!
Meh, I am not going that far. Recovery mode is a nice to have but it is not going to deprive me of the best phone on the market by miles (there is not a phone that is going to be better than the 3GS for at least 6 months or more, nothing is in the pipeline that comes close)
Click to expand...
Click to collapse
Until you accidentally brick it, then you are paying $60 a month while it goes off to get fixed. Yes, it's awesome hardware, but without 3 button, it's not worth it to me. I'm also stubborn enough to demand a resolution to this issue before forking out the money a 2nd time
I've left a comment of the Facebook page. Let's hope someone hears something. Going back to using my iPhone has killed me.
wow samsung come on your slacking
Samsung Mobile Canada Hi Jason. 3 button download mode is for internal firmware functions and is not recommended to end-users. It’s typically used by technicians to service malfunctioning phones. Modifying the internal firmware on a mobile phone device may void the warranty. What function you are trying to do? Maybe we can help find another way. Feel free to reach out to us at 1-800-SAMSUNG and we'll see how we can help. Thank
sounds like they could fix it but might not if your dumb enough to flash your bell sgs and have the 3 button combo disabled best of luck to you
haha sumsung cant ignore facebook
ive taken back 6 phones 600x6 is 3600 worth of phones lol and they all didnt have recovery so i took them back best buys 100% satisfaction guarantee gotta love it
Smash them boys!
I strongly recommend that you start new fresh posts each time instead of replying into a long one. Multiple posts on the wall are much more visible and potentially effective.
Come one guys, hit them hard (while staying polite obviously)
Posted on the wall.
Good idea will post to wall
Sent from my GT-I9000M using XDA App
done my part
they will hate it, i hope they don't remove it
just for reference the correct link to the wall is
http://www.facebook.com/samsungmobilecanada#!/samsungmobilecanada
DarthV said:
Until you accidentally brick it, then you are paying $60 a month while it goes off to get fixed. Yes, it's awesome hardware, but without 3 button, it's not worth it to me. I'm also stubborn enough to demand a resolution to this issue before forking out the money a 2nd time
Click to expand...
Click to collapse
If I am unlucky enough to brick it (which, despite my rants, is pretty hard to actually do in practice.... as long as you are flashing with a stable laptop it is not going to brick), then I'll get it replaced under warranty. The odds of me flashing it again after Froyo is out are near zero.
See, unlike WinMo, you don't have to re-flash Android to customize it, nearly everything on the phone can be customized in-line. All the stuff Cyogen etc. are doing can be done without flashing the phone, so you don't have to worry about bricking it
I learned from my years with my HTC dev. that re-flashing every few weeks is a huge pain in the butt, and I don't plan on doing that again with this phone.
astralmind said:
I strongly recommend that you start new fresh posts each time instead of replying into a long one. Multiple posts on the wall are much more visible and potentially effective.
Come one guys, hit them hard (while staying polite obviously)
Click to expand...
Click to collapse
Be careful, if you post too many things on the wall, they will just get frustrated and get Facebook to remove all the posts. You can do that with paid Facebook pages like this.
they removed one of my messages
It's an article that I came across.
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
If this article has been posted, sorry, Mods could delete this.
Sent from my SPH-D710 using Tapatalk 2
Its a non issue in my opinion. If you flash leaks, you know the chances. I flash the leaks and know o could end up with an epic doorstop. Long as its fixed when the official ota comes, it's cool
Sent from my SPH-D710 using Tapatalk 2
Nice article. Very informative. I personally never flash anything while on ICS. But based on that article that might not even be enough. It also gives us an idea that until Samsung/Google has fixed the issue we won'tbe sseeing an OTA updates. At least I would hope they wouldn't OTA an update that is going to brick a **** ton if devices.
I was victim of the superbrick towards the beginning. Whatever it did it really messed that thing up. If JTag can't repair it then it's hosed. Thanks for sharing.
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
blackroseMD1 said:
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
Click to expand...
Click to collapse
Yep Sbrissen and entropy got this fixed. Ive used his 3.0 Kernel and flashed about a billion times to test it lol. Its awesome and brick proof :] I just hope people wait for sbrissens 3.0 to be finished before they starting "borrowing" from it and calling it their own -_-.
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
garwynn said:
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
Click to expand...
Click to collapse
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
HaiKaiDo said:
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
Click to expand...
Click to collapse
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
garwynn said:
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Ahh yeah I got ya. I agree, I would much much rather see a fix and the knowledge that comes with it than seeing people get upset. I for one am happy to see things progressing and have no wish to blame anyone for anything. Even though it was a serious issue, we all take the risk of flashing things that are unknown upon ourselves.
blackroseMD1 said:
The fault here lies on both the person that flashed and on Sammy for their crappy code.
Click to expand...
Click to collapse
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Yeah. Anything other then official released software is on our heads. If I flash a leak and I brick my phone, which I did, then its my fault. I flashed Sbrissens CM9 back when he first released it. He sent me a test build. I flashed it. I bricked it. It was completely my fault. Wasn't Samsung or Sbrissens. Now if Samsung had officially released that file to the public and said oh yeah this is 100% safe to flash. Then maybe it would have been on them.
LudoGris said:
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Click to expand...
Click to collapse
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
blackroseMD1 said:
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
Click to expand...
Click to collapse
How are any of these leaks anything but internal testing? It is absurd to think that these bricks are of any fault to Samsung, they obviously aren't releasing these to us and then saying "Hey, flash this."
Granted, not all of us on here are adults, but for a second, let's be mature and take some ownership for our actions.
The part about it being Samsung's fault, is in regard to the Note. Not our device. They did release software that had the bug, and bricked devices.
But, that's so overblown. Replacing the device is more than enough, in my eyes, for taking responsibility. They are just required to provide a working device.
Any expectation above that, just shows impatience and naivete of the software development cycle.
Sent from my SPH-D710 using Tapatalk 2
I just bought a new (used) Note 4. It is fresh, stock, BOB7.
If I root, install recovery, and install a new rom, I figure it will trip Knox and turn it "custom".
My question - is it possible after that to return to out-of-the-box-stock? Do I have to take an image of the current config or something?
Thanks!
Mike
resarfekim said:
I just bought a new (used) Note 4. It is fresh, stock, BOB7.
If I root, install recovery, and install a new rom, I figure it will trip Knox and turn it "custom".
My question - is it possible after that to return to out-of-the-box-stock? Do I have to take an image of the current config or something?
Thanks!
Mike
Click to expand...
Click to collapse
Yes. You can odin the stock ob7 tar and the phone will be as out of the box but of course Knox will still be tripped.
Get the stock tar here in the OP :
http://forum.xda-developers.com/showthread.php?t=2944867
Full instructions are there also.
jhill110 said:
Yes. You can odin the stock ob7 tar and the phone will be as out of the box but of course Knox will still be tripped.
Get the stock tar here in the OP :
http://forum.xda-developers.com/showthread.php?t=2944867
Full instructions are there also.
Click to expand...
Click to collapse
Wow, you Note 4 guys are quick. Thanks for the reply!
So, not that it matters too much, but there is no way to retain/restore the Knox counter then? On my Note 2, there was a flashable back-to-stock image.
resarfekim said:
Wow, you Note 4 guys are quick. Thanks for the reply!
So, not that it matters too much, but there is no way to retain/restore the Knox counter then? On my Note 2, there was a flashable back-to-stock image.
Click to expand...
Click to collapse
Not at this time and unlikely in the future.
jhill110 said:
Not at this time and unlikely in the future.
Click to expand...
Click to collapse
Wasnt there talk in the past, forgot who or what thread it was in/about and it was stated that after the repair center gave them their phone back the knox-counter was reset to 0x0 ?
Ive seen many mentions of xda users in this forum(N910P) of working at sprint stores, if not that, working in the repair center. With the FUSE counter itself being an issue and the Signature also being an issue, i wonder the validity of that claim(counter reset), let alone if anyone who claims to work at sprint, could provide feedback on that claim, which at the time, there was none and yet to be.
And the surprising jump in members alone from the last year and a half to current date(wasnt it like 5.5 mil and now its sitting at a cool 6.5 mil) no telling how many Samsung employees probably just sit and search to counter hurdles that have been leaped, only to have updates, like OE1, magically and inconveniently push out updates thwarting what devs have accomplished.
xxSTARBUCKSxx said:
Wasnt there talk in the past, forgot who or what thread it was in/about and it was stated that after the repair center gave them their phone back the knox-counter was reset to 0x0 ?
Ive seen many mentions of xda users in this forum(N910P) of working at sprint stores, if not that, working in the repair center. With the FUSE counter itself being an issue and the Signature also being an issue, i wonder the validity of that claim(counter reset), let alone if anyone who claims to work at sprint, could provide feedback on that claim, which at the time, there was none and yet to be.
And the surprising jump in members alone from the last year and a half to current date(wasnt it like 5.5 mil and now its sitting at a cool 6.5 mil) no telling how many Samsung employees probably just sit and search to counter hurdles that have been leaped, only to have updates, like OE1, magically and inconveniently push out updates thwarting what devs have accomplished.
Click to expand...
Click to collapse
Well. I had run across a tmo thread that had posts stating phones had been returned with the Knox bit reset. There was a guy posting in that thread saying he worked out front at a Samsung authorized repair joint and had techs tell him the bit can be restored. Others elsewhere thought it would take replacing the mother board to achieve that. Bottom line I took from all that was samsung will repair a clearly bad hardware issue even with the bit tripped. Of course a lot of legend in their own mind types put the pupu on that but it has happened.
And yes, Samsung has been engaged in a we'll show you thing. Now I'm probably going to catch a lot of flack for saying this but I'm going to.
Most of the development for Android devices comes from the US... I think it's very likely the Koreans (samsung) hate that and take it as a challenge to show how much better/smarter they are than we.
Just my non insider opinion...
jhill110 said:
Well. I had run across a tmo thread that had posts stating phones had been returned with the Knox bit reset. There was a guy posting in that thread saying he worked out front at a Samsung authorized repair joint and had techs tell him the bit can be restored. Others elsewhere thought it would take replacing the mother board to achieve that. Bottom line I took from all that was samsung will repair a clearly bad hardware issue even with the bit tripped. Of course a lot of legend in their own mind types put the pupu on that but it has happened.
And yes, Samsung has been engaged in a we'll show you thing. Now I'm probably going to catch a lot of flack for saying this but I'm going to.
Most of the development for Android devices comes from the US... I think it's very likely the Koreans (samsung) hate that and take it as a challenge to show how much better/smarter they are than we.
Just my non insider opinion...
Click to expand...
Click to collapse
Yep, TW, Tizen, Knox, KnoxII, menu/recents button. Need I say more: Samsung/Galaxy app store, Milk, Chrome plug-in, security updates. Google has a rocky relationship with Samsung. One minute they're slapping then on the wrist, the next minute they're defending them in court against Apple.
All the while Samsung is copying Google to be their own standalone mobile platform. They may succeed eventually.
Competition is good. Truth is Samsung needs Google right now with its dwindling sales.
When the S5 came out with the menu switch from recents back to menu as an option, I was with Samsung on that but the Note 4 seemed to be a wink at Google like Samsung was more willing to do things Google's way. That gave us the silly white background menus and removed the menu/recents option in settings. What a cave in! Wrong move giving us KnoxII with non-user trip reset and this ugly UI. I hear they messed with the S5 on updates too. Yuck Samsung!
Sent from my SM-N910P using Tapatalk
Yes... The awful "material" white background, so retro low tech, so dos ansi... I was one very happy user when @tx_dbs_tx came with the dark mod... It wasn't perfect but it was what I preferred.
Hello.
11.11.2015 i recived a notification on phone that Elephone had released a new update to improve system functioning ect.
Keep in mind this is a stock p8000. nothing done with it.
I downloaded update, installed and it said phone will reboot.
After that phone is stuck in bootloader and simply wont boot.
Ive tried wiping cache and factory reset but PHONE WONT turn on.
So question is. What the hell do i do now?
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms. ?
This thread should be merged with other ones.
Have anyone found a solution?
pitrus- said:
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms.
This thread should be merged with other ones.
Click to expand...
Click to collapse
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
The Boards are full of Threads and solutions about this problem !
Why aren't you looking around a bit ?
How about the first post in Q&A section ???
http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203
StormiZMo said:
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
Click to expand...
Click to collapse
manually flash the stock rom .. i faced the same ****.. i followed the below steps and my elephone working fine
http://bbs.elephone.hk/thread-9229-1-1.html
hope this will work...
Fixed
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
StormiZMo said:
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
Click to expand...
Click to collapse
LOL, fired for what? it worked on most devices.
you get what you pay for! how are elephone selling a phone with decent specification for that price? they cut corners everywhere.
quality being 1 and skilled staff is the other.
with the given resources, their staff did they best they could with the test hardware they had.
StormiZMo said:
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
Click to expand...
Click to collapse
Also, most China phones don't even get updates, or even more exclusive, source code releases like this one. My guess is that there's likely only a one man show in charge of software development for this model, so give them some slack will you. [emoji1]
mine went off to after the OTA so i had to flash manually and like my friend said there trying, unlike most china phone company's so even though mine failed my father's and my friend's p8000 got there OTA np
It seems like the first 5000 batch delivered had no notification led,they seem to put in different hardware thats available.So end up with a hotch podge of slightly different devices.
So fingers crossed that a update works.Thankfully Elephone allows ,enables development.
It also looks like OTA update fails on rooted phones, which is not so different than what happens to most Android phones. When I used a Samsung phone long ago, OTA update notifications wouldn't even show up if you had rooted your phone, and on other phones I remember having a similar issue after I applied an OTA update with the phone rooted
Hey guys,
I issued a complaint about my 6 Pro (purchased from the Google Store in November) some weeks ago due to it having connection loss, GPS never pointing me in the direct direction (and some other things), got an replacement device, that randomly rebooted like 5 times in the first 2 days, so I sent back the replacement and hoped for the updates to resolve my issues with the original one. Well they didnt and I just got out of a chat with a service agent, who said, they can only offer repair options now.
As a Google buyer since the nexus days, having the ability to get a good service has always been a strong case for my choice for Google. This is very disappointing. Since when did things change, and why? Or are there people who got more than one replacement?
The dude i had in the chat today said he checked with the specific deparment and they will only offer repair for my device.
Thanks guys!
In the future return the device in the available return window if defective.
Make it their problem not yours (I have 2 open box specials to my name so far with Samsung).
You can try contacting your bank if you used a MC to see if you can return the device and get the bank to do a charge back.
You need to be effectively assertive or people will walk all over you.
I be all over Google like a cheap suit...
xflowy said:
Hey guys,
I issued a complaint about my 6 Pro (purchased from the Google Store in November) some weeks ago due to it having connection loss, GPS never pointing me in the direct direction (and some other things), got an replacement device, that randomly rebooted like 5 times in the first 2 days, so I sent back the replacement and hoped for the updates to resolve my issues with the original one. Well they didnt and I just got out of a chat with a service agent, who said, they can only offer repair options.
As a Google buyer since the nexus days, having the ability to get a good service has always been a strong case for my choice for Google. This is very disappointing. Since when did things change, and why? Or are there people who got more than one replacement?
The dude said he checked with the specific deparment and they will only offer repair for my device.
Thanks guys!
Click to expand...
Click to collapse
Connectivity problems seem to be mainly software related, many people were able to fix their problems by flashing the november radio file. What other problems do you have?
Have you set up your device "fresh" or with a backup? Google cloud or cable?
Some people had problems with backups, if Google doesn't offer you another replacement, I'd suggest to set up your device without any previous backup stuff, to see if that solves your issue.
That's a weird turn of events with that agent
What you are describing is a complete change from how Google handled warranty claims in the past. I would call back and see if the answer changes, this feels like a support agent that was confused.
That said, Google is currently in a very bad spot with support, it is a disaster.
TonikJDK said:
What you are describing is a complete change from how Google handled warranty claims in the past. I would call back and see if the answer changes, this feels like a support agent that was confused.
That said, Google is currently in a very bad spot with support, it is a disaster.
Click to expand...
Click to collapse
This is a good idea to call back. Can't tell you how many times I've received different answers depending on who I talk to from various company's support services.
Lughnasadh said:
This is a good idea to call back. Can't tell you how many times I've received different answers depending on who I talk to from various company's support services.
Click to expand...
Click to collapse
TonikJDK said:
What you are describing is a complete change from how Google handled warranty claims in the past. I would call back and see if the answer changes, this feels like a support agent that was confused.
That said, Google is currently in a very bad spot with support, it is a disaster.
Click to expand...
Click to collapse
I know right. I buying from Google since the nexus days. And getting a replacement has never been an issue. But there seems to be a change in poilicies.
Thats why I'm asking, if someone got a second replacement device, cause I think that is were the cutoff is now.
xflowy said:
Thats why I'm asking, if someone got a second replacement device, cause I think that is were the cutoff is now.
Click to expand...
Click to collapse
If it is, this is the last Pixel I will buy.
Are you on Twitter? Send a message to MadeByGoogle. They might provide clarity.
TonikJDK said:
Are you on Twitter? Send a message to MadeByGoogle. They might provide clarity.
Click to expand...
Click to collapse
Sadly i am not on twitter :/ perhaps someone can take over here?
blackhawk said:
In the future return the device in the available return window if defective.
Make it their problem not yours (I have 2 open box specials to my name so far with Samsung).
You can try contacting your bank if you used a MC to see if you can return the device and get the bank to do a charge back.
You need to be effectively assertive or people will walk all over you.
I be all over Google like a cheap suit...
Click to expand...
Click to collapse
If you do a chargeback they'll freeze your Google account. Lots of reports of this happening on Reddit and they never reverse course and let you keep the account.
EtherealRemnant said:
If you do a chargeback they'll freeze your Google account. Lots of reports of this happening on Reddit and they never reverse course and let you keep the account.
Click to expand...
Click to collapse
All the more reason to never do business with this company it true. I'd return it anyway. Then start filing complaints if they froze the account.
The FTC will take action if they get enough complaints of inappropriate behavior like this.
As it is I would never give Google a dime outright anyway.
blackhawk said:
All the more reason to never do business with this company it true. I'd return it anyway. Then start filing complaints if they froze the account.
The FTC will take action if they get enough complaints of inappropriate behavior like this.
As it is I would never give Google a dime outright anyway.
Click to expand...
Click to collapse
Yeah after hearing about the chargeback situation I decided I'll order from Amazon when it's time. Too many reports of FedEx stealing the phones and Google support not being helpful with requesting refunds.
I agree with OP that it's a shame if Google has now decided they'll only replace a device once. A defective device is a defective device, not anyone but Google's fault that their QA sucks.
EtherealRemnant said:
Yeah after hearing about the chargeback situation I decided I'll order from Amazon when it's time. Too many reports of FedEx stealing the phones and Google support not being helpful with requesting refunds.
I agree with OP that it's a shame if Google has now decided they'll only replace a device once. A defective device is a defective device, not anyone but Google's fault that their QA sucks.
Click to expand...
Click to collapse
As Lughnasadh pointed out calling Google back is a good idea. I've literally called some companies over 2 dozen times over the course of a week or two, escalating the case, ask to talk to supervisors, managers, even a VP at Sony.
Trying to get them to do the right thing.
Hammer them until they blink first... it's like playing the slots.
I'm successful almost always but it can take some doing. Once I get started I go to town...*
It's all good though because it's another free course in assertive training. Unfortunately for them I'm already well trained and worse I enjoy it
*attitude adjustment theme music courtesy the Kinks
I think maybe too many scams going on....
Morgrain said:
Connectivity problems seem to be mainly software related, many people were able to fix their problems by flashing the november radio file. What other problems do you have?
Have you set up your device "fresh" or with a backup? Google cloud or cable?
Some people had problems with backups, if Google doesn't offer you another replacement, I'd suggest to set up your device without any previous backup stuff, to see if that solves your issue.
Click to expand...
Click to collapse
actually, from what I heard it was mainly adaptive connect that caused the problem. (Least it was for me and I was on December update, but November did it to). Now I am on January update.
edmondt said:
I think maybe too many scams going on....
Click to expand...
Click to collapse
I agree. People bl unlock flash the wrong image, can't recover, and say my phone won't respond. Not that it happened here but you can search the threads and see what I mean.
bobby janow said:
I agree. People bl unlock flash the wrong image, can't recover, and say my phone won't respond. Not that it happened here but you can search the threads and see what I mean.
Click to expand...
Click to collapse
No doubt that may be true, but not all devices are equal (even the same model).
It's a dirty little secret but a common practice for phone manufacturers to substitute smaller chipsets and components during a production run due to parts availability. If it's a chipset it may not be compatible with the original firmware instruction set.
Eventually the manufacturer will modify the firmware to incorporate these off spec components, hopefully. Once they realize there's a problem. Almost always they need to physically examine the device to know if/what was substituted. So yeah they like you to send it in for repair. Fking beta hardware
Samsung is known to do this.
So when others are having issues you never experienced or easily fixed and they can't, don't be so sure it's the user's fault. Especially if there are wide spread reports.
so no one here who got a second replacement device?
xflowy said:
so no one here who got a second replacement device?
Click to expand...
Click to collapse
I'm very sure I remember reading some other members in this section reporting having received second replacement devices. No idea who they were or in which threads you might find their posts, though.