Hello all, I've done weeks of researching online how to fix this issue but have not found a solution.
I'm on a TMobile pixel 6 pro, which is sim locked and OEM locked (trying to see if tmo will sim unlock for me).
I decided to try the android 12L beta as one of the "bug fixes" were Bluetooth fixes, long story short it didn't fix the problems I was having, i opted out of beta, downloaded the "update" installed, rebooted to a prompt of no operating system found and reinstalled the beta, I tried Google's flash tool, it stated in OEM locked (can't unlock even through fastboot). I then decided to try the 13dp2 and see if I can roll back afterwards, unfortunately I get a timestamp error..
Anyone have any ideas on what I can try or if they have had a similar issue that was resolved?
Start clearing caches.
Go to settings/apps/see all.
Without your bootloader unlocked, it is impossible to roll back.
This is weird. I opted out and got an update about 5 minutes later. Twas about 15mb iirc. It wiped the phone but it's been fine for me otherwise.
Also, this problem is not uncommon. Sadly. I guess some opt out updates were almost 500mb. From what I've read, these are the ones that are causing problems.
Larzzzz82 said:
This is weird. I opted out and got an update about 5 minutes later. Twas about 15mb iirc. It wiped the phone but it's been fine for me otherwise.
Also, this problem is not uncommon. Sadly. I guess some opt out updates were almost 500mb. From what I've read, these are the ones that are causing problems.
Click to expand...
Click to collapse
There is nothing weird. People fail to read, and then reap their mistakes. It clearly states on google flash tool website NOT TO use it if you bootloader is NOT unlocked. The only thing causing issues are users not reading, and expecting others to clean their mistakes. Rules of modifying software: 1. Read. 2. Read again. 3. Read it once more. If fails, go to step 1 again. 9 out of 10 times you are not the first user experiencing an issue, and it has already been replicated and a solution provided, but people once again.... FAIL TO READ.
teegraves58 said:
There is nothing weird. People fail to read, and then reap their mistakes...it has already been replicated and a solution provided, but people once again.... FAIL TO READ.
Click to expand...
Click to collapse
Just had to respond to this as I have noticed this becoming more of an issue in society that began to swell and expand in occurrence over the last ten years. Ironically enough, I just saw an article in my Google news feed that mentioned reading a lot on the cellphone lowers comprehension by causing overactivity in the prefrontal cortex.
Now, of course, I don't mean this as an insult to the OP. But everyone needs to make a few mistakes here and there so that they can learn from them and prevent the same thing from occuring again (and in this case the primary mistake would be a lack of reading).
Oh... And yeah... I tend to do a lot of reading on my phone and so my prefrontal cortex has probably been reduced to water lol.
My stance is clear: If your bootloader is locked, you don't belong in the beta program, you shouldn't be flashing developer previews, and your rescue options are limited or not timely. You are owed zero support for something you've been explicitly warned against.
Go to T-Mobile support on Twitter. You can chat with them and they will answer you pretty fast. Then ask them if you can have your device unlocked, that you are going to Europe for 3 weeks. And they will do it right away. No questions ask. They permanently unlocked my device. And I have not even paid for it.
Related
Hi everyone, I've scoured the forums for my problem, but my search has been fruitless.
I'll be brief: Bought the girlfriend a Galaxy Nexus, unopened from a guy who didn't want the "upgrade" over his iPhone.
It was locked to Vodafone, but the box included a link to Vodafone's website, where you could get the code.
The code didn't work at first, but after lots of searching I found out that a factory reset fixed this problem, and voila! It did.
I'd love to include this link but apparently I need 8 posts.
The link also has people with the exact same problem, but all of them were "contacted by a vodafone moderator" and it ended with that.
The phone worked perfectly for several weeks, but all of a sudden it decided to ask for the network unlock code once again.
We tried it, but to no avail, and had to do a factory reset before the phone would accept the code.
It's since happened twice more, is this phone just a dud? This is totally unacceptable.
Can I fix this with a custom rom?
Thanks.
I've seen several threads from people in other countries all complaining that their sim unlock had to be redone - for many it was after each boot.
It was a while ago - I gave up reading all new threads a coupla months back and when I stopped no solution had been found.
Sorry I can't be more helpful but if you go back far enough you should find other threads on this problem.
eta: a thread with some instructions on how to make the unlock permanent popped up in general discussions, it looks pretty heavy:
http://forum.xda-developers.com/showthread.php?t=1606982
Hi Techie folks!
All right, hopefully everyone would excuse any blunders made by a noob but this is my dilemma.
This is my first, and most assuredly not my last, post on this quite interesting platform.
I had recently purchased a device (Google Samsung Galaxy Nexus I9250 Android Smartphone 16Gb) which was supposedly 'unlocked' from an online store (Expansys USA) out here in the US.
I bought it outright for $409.99
Link: http://www.expansys-usa.com/google-nexus-prime-android-smartphone-unlocked-16gb-224148/
I had received that device without any issues and had been using it for over three weeks.
I have the StraightTalk (USA) GSM SIM on it and like I mentioned, no issues whatsoever was faced during daily day-to-day use.
However, yesterday for the first time, I noticed that the network was not connecting and so I rebooted the phone thinking it was some network error.
Now when I did that I received a message after the boot-up which stated 'SIM Network Unlock Pin' and the options were to enter the PIN or dismiss that.
When I dismissed the message notification, I found out that the network was not available.
But the other features of the phone was not affected, as in navigating through the phone and applications (non-internet based) was without an problems.
Just that the network was not connecting although I observed that I could make emergency calls.
So I tried rebooting it again, by taking out the battery and SIM card as well, the issue still persisted.
So I started to troubleshoot the issue, by inserting in another GSM SIM card into the phone, but found the issue to persisting.
To double-check, I took out my StraightTalk SIM card and put in another phone, the SIM card was working fine! :good:
Just to be on the safe side, I called StraightTalk Customer Support and had asked them for some clarification as to why this SIM Network Unlock PIN was shown.
They suggested that this was the phone issue and needed to be sorted out by the place of purchase/manufacturer.
I even tried entering the SIM card's PUK code but did not reach far in that regard.
On searching the net (which is why I had come here for proper support and answers), I had found quite a lot issues with regard to this problem.
I was under the assumption that this phone was the GSM Unlocked International Version, but after this incident, it so happens that this is not the case.
The solution given online and out here is to root the phone using the Wugfresh method and after rooting, run the device with the application (http://forum.xda-developers.com/showthread.php?t=1548210) which would take care of this issue.
However, I am not too keen on voiding my warranty on this account, and also the steps are quite complicated with respect to rooting the device.
Yes I am noob! So please don't roll your eyes!
This is the issue, and now to what I would appreciate this forum's assistance.
Being an expensive product, I dont want to buy another one just because of this issue.
I do not know where this phone is purchased from, which means, I have no idea which network provider this is locked to.
I can only provide the IMEI number.
Question 1: Is it possible to find out to which network this phone is locked to?
I have to add that the phone does not have any network branding on it, nor does it show any during the boot-up process.
Question 2: Can the phone be unlocked with online unlocking sites?
Question 3: If so, can someone provide me any good sites that can unlock the device.
Is this site any good? Link: http://www.unlockallcellular.com/samsung-galaxy-nexus-unlock-code-p-196144.html
Like I said, worse case scenario, I would indeed have to root my phone and proceed to install that software which will help me get rid of this issue once and for all.
As you all can see, I'm desperately looking for some solutions/answers and would appreciate it if someone would shed any light to this issue.
PS: I do know that there are threads on this issue, but mine is more or less around finding the invisible network provider that this phone is locked to.
Best Regards,
Reena Johnson
Your device was not factory SIM-unlocked. The vendor probably unlocked it using a code. That said, you should call Expansys and ask them for the code.
Otherwise, you can take a look at the following two threads. The first one is easy, but temporary -- in other words, you will need to do unlock every time you flash a new ROM. The second is permanent, but not as straight-forward to accomplish.
1) http://forum.xda-developers.com/showthread.php?t=1548210
2) http://forum.xda-developers.com/showthread.php?t=1606982
Further queries now arise ....
efrant said:
Your device was not factory SIM-unlocked. The vendor probably unlocked it using a code. That said, you should call Expansys and ask them for the code.
Otherwise, you can take a look at the following two threads. The first one is easy, but temporary -- in other words, you will need to do unlock every time you flash a new ROM. The second is permanent, but not as straight-forward to accomplish.
1) http://forum.xda-developers.com/showthread.php?t=1548210
2) http://forum.xda-developers.com/showthread.php?t=1606982
Click to expand...
Click to collapse
Thanks a lot for the quick reply.
Wow! You guys are fast!
Much appreciated.
Now I have a query. The option 1 which you have stated, is the one which I have looked at.
Even that requires me to root my phone.
Isn't it so?
Cause the OP in that thread specifically mentions the need to root the phone.
I have asked Expansys USA for that code, and since Saturday/Sunday is off for them, I am hoping to get a reply from them on Monday.
Like I said, my main concern is that I would like this process to be hassle free.
You guys (no-offence intended for the male demographic) are quite capable of rooting the phone.
Unfortunately, I wish not to choose that route, unless no options are left available at my disposal.
Which is why I am bending towards the easy unlocking method.
So my next question really is since its (read: the phone) not a factory SIM-unlockedissue, can I find the original network provider to which this phone was locked to?
As in, is there any where on this device which can tell me that information?
Once again, I sincerely thank you for your support and assistance in my life a lot easier! :victory:
Regards,
Reena J
djjohnson said:
Thanks a lot for the quick reply.
Wow! You guys are fast!
Much appreciated.
Now I have a query. The option 1 which you have stated, is the one which I have looked at.
Even that requires me to root my phone.
Isn't it so?
Cause the OP in that thread specifically mentions the need to root the phone.
Click to expand...
Click to collapse
Yes, you are right it does require root. (I didn't realize that it was the link you had looked at and mentioned in your post.)
djjohnson said:
I have asked Expansys USA for that code, and since Saturday/Sunday is off for them, I am hoping to get a reply from them on Monday.
Like I said, my main concern is that I would like this process to be hassle free.
Click to expand...
Click to collapse
Probably best to wait until Monday then, as that would certainly be the most hassle-free option.
djjohnson said:
You guys (no-offence intended for the male demographic) are quite capable of rooting the phone.
Unfortunately, I wish not to choose that route, unless no options are left available at my disposal.
Which is why I am bending towards the easy unlocking method.
Click to expand...
Click to collapse
Believe it or not, "rooting" a Nexus device is extremely easy, and should not take more than 5 minutes. The part the takes the most time is to make sure the drivers are set up properly on your PC... Once that is done, no more than a few minutes is all it takes.
djjohnson said:
So my next question really is since its (read: the phone) not a factory SIM-unlockedissue, can I find the original network provider to which this phone was locked to?
As in, is there any where on this device which can tell me that information?
Click to expand...
Click to collapse
Yes, there is a way, although I believe you need root, although I could be wrong here. You need to post this file from your device: /factory/mps_code.dat and someone will be able to tell you. Or you can look in that file and compare the code in there to this list.
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
djjohnson said:
[snip]
Question 2: Can the phone be unlocked with online unlocking sites?
Question 3: If so, can someone provide me any good sites that can unlock the device.
Is this site any good? Link: http://www.unlockallcellular.com/samsung-galaxy-nexus-unlock-code-p-196144.html
Click to expand...
Click to collapse
And yeah, you should be able to get it unlocked by one of those site, even the one you mentioned. But I can't vouch for it, nor can I recommend any site, as I have never used any.
Hey djjohnson
I've got the exact same problem, but bought my phone from a different seller.
Did you manage to get any information (or PIN) from expansys??
Thymine said:
Hey djjohnson
I've got the exact same problem, but bought my phone from a different seller.
Did you manage to get any information (or PIN) from expansys??
Click to expand...
Click to collapse
It looks like OP disappeared after getting his issue solved. Expansys has great customer service and would have exchanged the phone with no problems. Which retailer did you get it from? There are unlocking sites out there but you have to know which network its locked to. Or root it and try the methods listed in this thread. GL
Cheers mate,
I bought mine from an ebay seller and have already sent them a message asking for either the PIN or the name of the original service provider.
If that falls through, I'll have no other option but to root....or just be the first of my friends to not have a phone number and live exclusively on the internet...
I'll probably root.
A delayed update ...
Techies folks!
This is just to update you guys on this issue and if in future any one else faces such similar issue just do this and get back your peace of mind.
First you need to root your phone as mentioned by Efrant and it is indeed a simple process once you have set up the required drivers.
Once again thanks a lot Efrant for your support and time in helping me out with this.
:good:
First you need to root your phone, period.
I tried all methods before diving into this method.
Rooting isn't complicated and all it takes is patience and the exact details to get this done.
What I am about to suggest is to be taken at the reader's risk and I am not responsible for any damage done to your phone.
That being said, I highly doubt that anything will go wrong unless you arent used to following instructions!
My Nexus was magically locked to an invisible network and you guys can find that out by going into fastboot mode.
What that means is to turn your device off and then press the buttons together (volume Up + volume Down + Power), you will get that info under the "baseband version" and "carrier info".
I could not resort to the online unlocking sites because ALL of them require the original network to unlock the phone.
I suggest that you root the phone and it is quite simple not taking you longer than 10-20 minutes.
1) First you will need to install the drivers onto your phone from your computer which you will need during the rooting process.
You can get that from here
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
It is called the Universal Naked Driver 0.7.
The download instructions are given in this link http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
The OP was quite comprehensive in providing the exact details in what needed to be done. So once you have installed the necessary drivers proceed to the next step.
2) Download Wugfresh Toolkit which is the main tool needed to root your phone.
First you will need to unlock your phone and then root it.
The beauty of this software is that everything is on it. Just click on the Unlock button first and then you just have to sit back and wait for the magic to happen.
The instructions on the screen will tell you what its doing.
I would suggest reading through the entire process before going through with this.
http://www.wugfresh.com/dev/nexus-root-toolkit/
Extra material on this http://wugfresh.com/Help/
3) Once you have rooted your phone, the hardest bit is over. Then all you need to do is install this application on your device. And run it.
Simple.
You have yourself an unlocked phone!! :victory:
http://forum.xda-developers.com/showthread.php?t=1548210
There will be questions as to if this will work in CDMA or GSM versions.
I got mine from Expansys and it was supposed to be an unlocked GSM model.
I hope that will help as it did with mine.
Actually I got my bf to do this for me as it is a tad bit complicated and it was a birthday gift from him.
mendezj666 said:
It looks like OP disappeared after getting his issue solved. Expansys has great customer service and would have exchanged the phone with no problems.
Click to expand...
Click to collapse
Wow!
I seriously didn't realize that I had a personal assistant or the CIA to track my moves!
I apologize if my bf didnt get back to you guys on this issue. I, on the other hand, have work which consumes 12hrs of my day.
So I really do not have the time to post a reply.
But hey! a simple 'I dont know where SHE is, but here's what I can do to help you out' would have sufficed.
I'm just saying. No offense intended mate.
By the way, I'm a girl, and in my opinion Expansys came highly recommended to me by all my co-workers.
But I had the most horrible customer support ever!
My personal opinion would be to NOT buy from there!
Get from Negri's or some place better.
God knows how many times I had tried calling them. Even tried sending them tons of emails and not even one peek into my issue.
Goes to show how "great" of a customer service they have!
Thymine said:
Hey djjohnson
I've got the exact same problem, but bought my phone from a different seller.
Did you manage to get any information (or PIN) from expansys??
Click to expand...
Click to collapse
I hope my post will help you also to resolve your issue.
Best way is to root your phone. But like I said earlier, do read everything, and download the drivers and the Wugfresh Toolkit before proceeding.
All the best.
Soon you'll be like me enjoying what can only be said as a beauty of a device.
A big thanks to Efrant for helping a gal out!
Cheers!
Regards,
Reena J
[Q] Same problem, solved, but now how can I network lock it again...
Hi All,
In short, same problem here, I used another unlock code(bought it) and now i want to network lock it again? How can I lock it?
I had very same problem of this thread, I bought phone as factory unlocked but was code unlocked(Vodafone Spain), later after updating to 4.0.4 and then to 4.1.1, it asked for the code again.
I raged with the problem and I rushed to buy a unlock code (8$), a bit shady, but it works fine.
Now I want to confront the shop who sold the phone lying about its lock state, and it would be convincing if i can send them the phone network locked as it was.
How can I network lock the phone again?
I have tryed inputing the code *7465625*638*# or *7465625# and similar combinations with no lock, I don't get a popup asking me for the carrier data to lock it.
I also tryed to downgrade the phone to 4.0.4, with no result and later to 4.1.1 and the same it is not asking for the unlock code...
Just an obvious clarification, I am talking about carrier network locking, not lock/unlock the bootloader.
Thanxs a lot in advance
djjohnson said:
Techies folks!
This is just to update you guys on this issue and if in future any one else faces such similar issue just do this and get back your peace of mind.
First you need to root your phone as mentioned by Efrant and it is indeed a simple process once you have set up the required drivers.
Once again thanks a lot Efrant for your support and time in helping me out with this.
:good:
First you need to root your phone, period.
I tried all methods before diving into this method.
Rooting isn't complicated and all it takes is patience and the exact details to get this done.
What I am about to suggest is to be taken at the reader's risk and I am not responsible for any damage done to your phone.
That being said, I highly doubt that anything will go wrong unless you arent used to following instructions!
My Nexus was magically locked to an invisible network and you guys can find that out by going into fastboot mode.
What that means is to turn your device off and then press the buttons together (volume Up + volume Down + Power), you will get that info under the "baseband version" and "carrier info".
I could not resort to the online unlocking sites because ALL of them require the original network to unlock the phone.
I suggest that you root the phone and it is quite simple not taking you longer than 10-20 minutes.
1) First you will need to install the drivers onto your phone from your computer which you will need during the rooting process.
You can get that from here
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
It is called the Universal Naked Driver 0.7.
The download instructions are given in this link http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
The OP was quite comprehensive in providing the exact details in what needed to be done. So once you have installed the necessary drivers proceed to the next step.
2) Download Wugfresh Toolkit which is the main tool needed to root your phone.
First you will need to unlock your phone and then root it.
The beauty of this software is that everything is on it. Just click on the Unlock button first and then you just have to sit back and wait for the magic to happen.
The instructions on the screen will tell you what its doing.
I would suggest reading through the entire process before going through with this.
http://www.wugfresh.com/dev/nexus-root-toolkit/
Extra material on this http://wugfresh.com/Help/
3) Once you have rooted your phone, the hardest bit is over. Then all you need to do is install this application on your device. And run it.
Simple.
You have yourself an unlocked phone!! :victory:
http://forum.xda-developers.com/showthread.php?t=1548210
There will be questions as to if this will work in CDMA or GSM versions.
I got mine from Expansys and it was supposed to be an unlocked GSM model.
I hope that will help as it did with mine.
Actually I got my bf to do this for me as it is a tad bit complicated and it was a birthday gift from him.
Wow!
I seriously didn't realize that I had a personal assistant or the CIA to track my moves!
I apologize if my bf didnt get back to you guys on this issue. I, on the other hand, have work which consumes 12hrs of my day.
So I really do not have the time to post a reply.
But hey! a simple 'I dont know where SHE is, but here's what I can do to help you out' would have sufficed.
I'm just saying. No offense intended mate.
By the way, I'm a girl, and in my opinion Expansys came highly recommended to me by all my co-workers.
But I had the most horrible customer support ever!
My personal opinion would be to NOT buy from there!
Get from Negri's or some place better.
God knows how many times I had tried calling them. Even tried sending them tons of emails and not even one peek into my issue.
Goes to show how "great" of a customer service they have!
I hope my post will help you also to resolve your issue.
Best way is to root your phone. But like I said earlier, do read everything, and download the drivers and the Wugfresh Toolkit before proceeding.
All the best.
Soon you'll be like me enjoying what can only be said as a beauty of a device.
A big thanks to Efrant for helping a gal out!
Cheers!
Regards,
Reena J
Click to expand...
Click to collapse
Google is selling these phones for $350 ? Why would you pay more and not get it from the source, just curious. Not trying to be argumentative.
jawmail said:
Google is selling these phones for $350 ? Why would you pay more and not get it from the source, just curious. Not trying to be argumentative.
Click to expand...
Click to collapse
Maybe they're not in the US or purchased them more than 2-3 months ago.
The point is that google does not sell them worldwide, they don't sell them in my country (Spain), or at least not 3 months ago when I bought mine. And if they would sell them it would be more like 400€ minimum (equivalent to 500$ moreless)
But lets not lose the focus, of the question, any idea of how to network lock the phone again?
jawmail said:
Google is selling these phones for $350 ? Why would you pay more and not get it from the source, just curious. Not trying to be argumentative.
Click to expand...
Click to collapse
I had let my nexus update to 4.1.1 before realising I had a sim unlock problem here, the guide above was spot on, if you are on 4.0.4. I just couldnt get the last bit done on JellyBean, so went back to google image 4.0.4 and it work flawlessly
Phone updated to JB an hour ago, and its still working sweet
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
Hello all,
So, I'm in US and have Google Fi. Bought a G710ULM from ebay and when I get it, check IMEI and it comes back as an g710PM, not ULM. I specifically did research here on xda (lurker for many yrs ) so knew I wanted an ULM. I see many threads about this is common practice of cross flashing the PM's to ULM, and get conflicting info with what works and what doesn't: things like Google Pay, no OTA updates (flashing thru LGUP is only option). The only issue I have is wifi calling does not work, it gets ER081, which is not a deal killer, but is still a handy feature to have. Have found posts from others with the wifi issues, and it seems to be on an issue on older Oreo ROMS, which mine has (pic below). So I could potentially just flash to the latest ULM Fi Pie ROM and it might/probably resolve this, but I'd still not have Google Pay (possibly might work, conflicting info) and no OTA updates still (not sure if Fi pushes OTA honestly). I've emailed the seller, laying all this out, and saying I could flash an update but not before he said that he would not blame me for anything not working. Still waiting on his reply. But sleeping on it overnight, I think I just want to return the friggin thing and try to find a REAL ULM. I'm not trying to be a d*ckhead about this, but I wanted an actual ULM, not a cross-flashed phone, as I did my research here about what best to buy. Apologies, was a bit of a rant. So am I worrying about nothing here and a flash will getting it good or do I have valid concerns here? Thanks all for this awesome community.
What did you do? Irritated that I didn't discover the problem for 9 months on my phone.
I just got one on eBay & this post got me up to the current ULM 20e: https://forum.xda-developers.com/showpost.php?p=81131579&postcount=247
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.