I've realised I've got no Vibrate on the nexus now. It doesn't buzz at start (can't recall if it ever did ) and stuff like haptic feedback does nothing
I want to know if flashing back to a stock ROM will reset it, or if its a hardware thing that can'r be solved with a flashing or something I can do myself.
I have MCR 1.3 and a theme on, and its unlocked and rooted.
Any ideas? its livable with, but I'm narked as its only three days old.
Dayzee
Just bumping this - any ideas? Thankyou all
Disclaimer: I have the Sprint Hero.
I had this problem on my Hero. After some research, I found that others were having problems with their vibrate functions not working, and that a factory reset fixed their issues. This didn't work with my handset, and I had to exchange it. The vibrate stopped working after a week or so of using the phone.
YMMV, but good luck.
I'm sure its hardware really, just hoped something else as I've unlocked and rooted Gonna try to exchange as its nothing to do with rooting obviously. If there are any kind souls on here who are HTC support connected and can help I'd appreciate it greatly xxx
Dayz - gutted
Try preforming a nandroid backup, then wiping and see if it's fixed then restore the nandroid back up if you want.
Hmm looks like you are not alone
http://forum.xda-developers.com/showthread.php?t=615637
I called HTC and spoke to a support guy who rightly said that since the Vibrate or Haptic feature has not worked since I recieved the fone on Monday (which it hasn't, I just didn't register it straight away as I don't usuall have it turned on on my Hero) then it will be replaced like for like with a new one. I've been given a ticket number for a full return, UPS are picking up my handset on Monday morning and HTC have sent a printable returns label for it.
At no time during the call and all the questions he asked, was I spoken to about warranty or Bootloader Unlock, so at the end of the call, so before I rang off I asked him - will it make a difference if my bootloader has been unlocked? He said he wasn't sure what I meant so I explained I had unlocked the bootloader. He then said it wouldn't matter as its a hardware fault, as long as there is no 3rd party software on the fone.
I'll have to wait and see what happens but he obviously hadn't been briefed to check for voided warranty by unlocking the bootloader. My fone has now been returned to stock everything (ROM Recovery etc) using this thread here http://forum.xda-developers.com/showthread.php?t=614850
and I'm using my hero in the meantime.
Dayzee xx
Dayzee said:
I called HTC and spoke to a support guy who rightly said that since the Vibrate or Haptic feature has not worked since I recieved the fone on Monday (which it hasn't, I just didn't register it straight away as I don't usuall have it turned on on my Hero) then it will be replaced like for like with a new one. I've been given a ticket number for a full return, UPS are picking up my handset on Monday morning and HTC have sent a printable returns label for it.
At no time during the call and all the questions he asked, was I spoken to about warranty or Bootloader Unlock, so at the end of the call, so before I rang off I asked him - will it make a difference if my bootloader has been unlocked? He said he wasn't sure what I meant so I explained I had unlocked the bootloader. He then said it wouldn't matter as its a hardware fault, as long as there is no 3rd party software on the fone.
I'll have to wait and see what happens but he obviously hadn't been briefed to check for voided warranty by unlocking the bootloader. My fone has now been returned to stock everything (ROM Recovery etc) using this thread here http://forum.xda-developers.com/showthread.php?t=614850
and I'm using my hero in the meantime.
Dayzee xx
Click to expand...
Click to collapse
could you update us on this?
i feel like my vibrate is going out and thinking of doing an exchange as well
Related
Just wondering, since mine has never worked out the box.
Does the nexus vibrate slightly for these things whether you set vibrate or not? :
Long press to move things around the screens
When a call connects
When you start up the phone after turning off completely
Just going off my Hero, these things all have a "buzz" and to be honest I don't know if the Nexus does that. My Vibrate is still obviously broken, because it doesn't vibrate on anything whether I have it set to vibrate or not. I just wondered about the above vibrate stuff that isn't set by the user.
Dayzee
I think all new HTC phones vibrate when you turn them on, Mine does as well.
Also it vibrate when i hold an icon to move it. If your doesn't work? what you waiting for mate give a phone call to HTC for replacement.
Thanks Hassan - HTC are collecting it today - rang them on Friday. I just realised I wasn't sure if it did that the same as my hero - Ta for the info
Dayz xx
Its part of their Haptic User Feedback system
yes, mine does vibrate on boot.
Dayzee said:
Thanks Hassan - HTC are collecting it today - rang them on Friday. I just realised I wasn't sure if it did that the same as my hero - Ta for the info
Dayz xx
Click to expand...
Click to collapse
Are you getting a repair or replacement?
I noticed you've rooted that's all and I thought the warranty was void?
Mine just does it on boot...I have Haptic turned off.
I have sent it with an unlocked bootloader, as there's nothing I can do about that, but it's not rooted anymore and is totally stock apart from that. I did mention it was unlocked bootloader, but the support guy seemed not really clear on that - he DID say that as long as it doesn't have third party software on it won't be an issue. But that's just a support guy. So I'm waiting to see. The issue is obviously hardware, was present out the box and not related to software. I'm hoping they still sort me out as the device was only days old.
Ok, so the vibrate feature no longer works on my device. Whether it be the vibrate profile (phone stays silent but no vibrate), Haptic feedback is no longer working in keyboard and neither is the haptic feedback in HTC Sense and inc bootup.
I sent detailed info on my fault, phone was sent last friday. Vodafone sent me a txt saying they had received my device on Monday morning and then sent me another txt at 19:50 saying that the device is on it's way back to me fixed and would be with me tomorrow by Royal Mail and make sure someone would be in.
I then took the day off unpaid and the device never arrived until this morning. I was so excited to get it back but already annoyed due to losing pay yesterday. Opened box and there was my baby. I popped in my battery and no vibrate during boot?? No haptic feedback in keyboard (checked settings)??? Then tried vibrate profile and rang my phone, surprise "No Worky" phone silent and no vibrate. ??? Checked accompanying documents. One is a check list from engineer. As Follows:
"Reported fault Resolved Tick (No it's not)
Data Content Cleared Tick
Latest Version Software Same as sent
Established Live Call Tick
Incoming Audio (speaker) Test Tick
Display Test Tick
Keypad Test Tick
Imei: *********************
Date Test Completed 25/01/10"
Then letter says:
"hank you for sending your phone to us for repair, we are pleased to say that the fault has been fixed.
What we've done
One of our engineers has throughly tested your phone. The fault on your device has been corrected by upgrading the software to the latest manufacturer approved version. If you mentioned any other faults when you booked the repair, these will have also been fixed.
As part of the repair process, we have given your phone a full internal service including upgrading the software inside the phone, as this is how many faults are fixed. The software is responsible for many aspects of how the phone actually works and though you may not expect it, upgrading the software can increase battery life and memory capacity, and provide you with a more up to date phone.
If you need us again
You can pop into the shop or call customer services, blah blah blah."
Well what BULL. The software is the same as previous (before sending) Phone has not been fixed. I lost a days pays (although my choice I surpose for doing as they asked) And I'm now worse off.
I popped into vodafone store and they said they could do nothing as they dont sell that phone instore and were not even aware of the model. See said call 191 from phone. And all they would do is send it off again. I'm reluctant to do this as I'd be without a phone for further number of days. working virtually non-stop over next couple of weeks so being in to recieve the phone may be a prob. I just feel like taking they phone and both signed documents to a solicitor.. They clearly state it's been repaired but it's not. Exactly the same as was sent. Well as soon as contract is up with vodafone I'm going back with O2. First time with Vodafone and also my last!!
Sorry for the rant. Any Idea's? What would you do? Should I send it off for repair again or demand a replacement or just shut up and take it like a *****???? Thanks for listening... Anyone a Solicitor?? lol
Just for reference, the shops, the internet shop, and the phone shop are 3 different branches of the same company. They do not share deals, devices, staff, or even knowledge. This is quite common, and normal for most (if not all) of the major providers.
Anyway, I'd ring back and just explain to them what you've explained to us. Try and stay calm with them but be very persistent. Don't end the call till they've acknowledged what the fault is by telling you what they've recorded on your notes, and they've agreed to once again collect the phone.
If you do need a phone while it's away (do you? You already received text messages from them last time it was away), they may be able to arrange one of the shops to do you a loaner for a while, but it will be a piece of crap that will make you blush when you have to pull it out in public.
My best advice would be to not get angry on the phone with them. It's done, and the person at the other end of the phone isn't responsible for the problem. Too many people start these conversations aggresively, and that won't get you any further. If I was CS staff and someone rang up and started ranting at me immediately, I'd be disinclined to be as helpful as I could.
I know it's crap, but it is what it is, and the phone simply needs fixing or replacing.
Good luck, and let us know how you get on.
Thanks for your quick reply. The only reason I popped in store was because the letter said I could and I was going into town anyway so took my chance. I was very pleasant on the phone (couldn't have been anything else as I have a really sore throat and a blocked nose, lol) In fact i'd say that the Welsh guy from customer services is about the only thing Vodafone currently have going for them. He was great and very polite. Just waiting on his supervisor calling me for a chat but said it could take up to 48hrs.
Will keep you informed, Just cant believe they say that the problem is fixed. Well gonna keep smiling and looks like i'll have to use my mates pink flip up phone again for a while. uughhh, I'm not gonna hear the end of that I can tell you.
I turned on my phone last night, pressed the camera icon in the list of programs and it disappeared and hasn't come back since?????
Then went to the picture and movie tab and pressed the camera tab (both for taking picture and movie) and nothing happens, no camera launches.
I've had the phone sitting in the cupboard for days and it's cold where I live so I wonder if it's possible that the camera hardware has frozen and the icon disappears because the system cannot detect working hardware?
I don't know but my phone is out of warranty and I am worried.
Would flashing a new ROM help do you think?
normally your phone should not be out of warranty yet, since htc offers a 24 months warranty.
and if the camera worked with your rom before, changing the rom should not be necessary, but maybe a radio/rilphone upgrade would help or a hard reset.
Thanks for the reply
I've emailed the local distributor of my phone (bad reputation for replies) who paralell import it from singapore so I might be out of luck.
Done several hard resets and also warmed the phone up to see if the camera hardware was maybe stuck from the cold but no luck.
Tried to burn a new rom (The EnergyRom looked good) and the software keeps complaining that it lost communication with the phone so I can't even do that. Tried 10 times already.
So, I guess I have to wait for the supplier but they said the warranty is only one year.
afaik htc generally offers a 2 year warranty, so they are probably the ones, you'd want to contact about that issue, but before actually sending it to them, make sure to flash back the stock rom, radio and spl.
As I said above, I tried burning a new rom but the software keeps complaining that it loses communication with the phone so I've given up.
Thanks for the suggestions though.
I absolutely agree with Chef_Tony.
You've tried enough to exclude everything. It must be a hardware issue.
I think you can check the production date via the sn below the batt. I would just go ahead with HTC and call them, and NOT your local dealer.
You can also open a ticket online but from my experience that is a waste of time since they will start asking stuff to do and email them again.
HTC provides 24 months of warranty in most areas and the sn will be enough for them to decide if it is warranty or not.
Also do not mention the custom roms as that will void your warranty, even if the issue was there on the stock rom!
So go back to everything stock, everything that you need is in the sticky on the rom page, and give HTC a call.
The ROM is a stock one. I mentioned in my above post that when I tried to burn a new one that the phone lost comms so I never could get a new rom on to test if the camera would come back so I am still stock.
HTC mentioned all the same things you guys did.
Spoke to my supplier, looks like I have to send this back. Damnation!!!!!
Okay, made a few mistakes about trying a new rom but under severe pressure since my father died so I can't comprehend much at the moment.
Will try all the steps later when I am less distressed.
Sellers have gone, phone is worse.
Just to update people, this post can be locked now.
Blue Fly Mobile are gone, nobody can find them. They told me to send the phone back for repairs and when I was just about to, they turned up missing.
Web site is gone, no contact anywhere and I read in many forums about their bad rep.
Camera still gone. Battery may last a day if that. Phone randomly cuts of calls when I make them or when people make them to me.
Looks like I will be waiting for the new Samsung Galaxy Tab 10.1 when it hits OZ as it's better for my eyes.
Now, how to convince my wife that I absolutely need it???
Hi everyone,
So about five days ago I was in the middle of using my Galaxy S4 (I think I was playing a game or something) and all of the sudden my cellular signal dropped out completely—from 4 bars to zero with a little X in it. There it's remained ever since.
My first thought was that I ought to reboot the thing and see if that would solve anything. The answer was no.
My second thought was that maybe my contract was up (as that was due to happen this month), and rather than auto-renewing, they kicked me off. Weird, but possible. But that's not it: I phoned up my provider and they said that all systems are go, there are no outages, your account is active for a week still, and even past that contract expiry I'll just get bumped to month-to-month and never experience a blip in service. So that's not it.
So then I put my SIM in another unlocked phone, and lo-and-behold, it connects just fine. So clearly the problem is with my phone.
My i337M is running Liquid Smooth 2.9 and KToonSez' kernel. I decided to make a nandroid and flash back to stock ROM/kernel. Still I could not connect to the network.
I can only think of two potential problems. First, I unlocked the phone myself via FastGSM.com's tethered USB method. It was a Bell-locked phone, and I'm on Rogers. This was accomplished back in July, and since then, there haven't been any issues to speak of (i.e., the unlock worked flawlessly). I tried to see if those unlocks ever expire, and couldn't find any reason why they ought to. I personally don't think it's that, but I mention it out of interest in being thorough.
Second, I messed around with my phones NVData a few weeks back to enable the AWS network via this method. I didn't experience any signal problems after doing so. Again I mention this out of interests of being thorough. Could that have had something to do with it? I suppose I could try flashing back my original NVData, but honestly I don't see why that would suddenly kick in now since I did it weeks ago originally.
Any thoughts? This is really bizarre, and it sucks being without connection.
I was also thinking of flashing back to stock and going to a Bell shop to see what happens when I put a tester SIM in.
It sounds to me like it's hardware related. Don't see anything you've done that would have caused it. I'd flash back to stock and if it still persists I'd file a warranty claim.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi, thanks for your reply.
An additional thought's occurred to me: I lost signal at or about the same day I setup Android Device Manager to allow for remote lock/wipe directly from Google. That couldn't possibly be responsible for signal loss, could it...?
Currently flashing back to stock, and I'll unroot/restore kernel/restore NVData and make it look factory, and see what the store says about it. Hopefully I don't have to pay for another unlock at some point.
Okay, this is very messed up. Nobody has any idea why my phone isn't getting signal. I can scan for networks and everything shows up, but in any case with any SIM it says "unable to connect to network". It doesn't matter what ROM I'm on. I flashed back to stock and updated to latest using KIES of all things, which found a firmware/modem/baseband update, and still no dice. I don't know what to do with this thing except take it to an unlocking store that might be able to figure something out for me, but it'll cost me. This is messed, I've never had to get someone else to look at my tech for me.
Okay, so the situation is that it most probably is a hardware failure related to the radio.
I am a Rogers customer who bought the phone from a guy from CraigsList who apparently got it from Bell. I went into Bell and explained the situation, and they scanned the IMEI and printed me out a proof of purchase of the guy's name and told me I should take that to the Bell service centre, and it doesn't matter if I'm not the guy. I also had them check to see if he reported the phone stolen; it turns out he did not—though it should be known that if he had done so, then that could have very well been the reason I wasn't getting signal from anyone, as all providers across Canada apparently share their blacklists with one another now (including the little guys like Wind/Mobilicity).
So now I am in the process of making it look like it's never ever been hacked before: I shall restore my NVData, unroot, and update everything using KIES, and then perform a factory data reset. I'm also on the hunt to figure out what the heck the "flash counter" is and whether or not I need to reset that, but perhaps since mine is the i337M Canadian variant, I don't need to worry about that. (Any advice on restoring my phone to factory condition would be welcome, thanks.)
Edit: Figured out TriangleAway and everything associated. I'm all stock now and ready to bring it back to the factory.
MAJOR UPDATE: PROBLEM IDENTIFIED
So I got my phone back from the factory today. They reported that everything is 100% a-ok on the hardware/software side of things. The radio IC is NOT blown as was suspected.
You know what they said? The problem is on the network. I have a story to tell that I think people should hear, as I've learned something very valuable today and people need to learn this lest they get conned themselves.
Today I phoned in Rogers again, armed with new information, to ask what's up. They ran the IMEI number, and this time... it's come up on the blacklist.
It wasn't there last week. In fact, it wasn't even there an hour ago. It actually only appeared there as the clock ticked past midnight Eastern time... as that is EXACTLY 90 days from when the phone was reported missing. It took them a long time to track down this information.
To reiterate, I did not steal the phone. I bought it from a guy on Craigslist who had it brand new in box with the screen-protector sticker still on the front of it. I checked it out, tried it, and unlocked it myself and have been using it since July without issue, until a week ago.
There is the trouble of, why now? Why only now does the IMEI come up blocked? What the senior rep at Rogers thinks happened was that the guy had it delivered to his house, didn't sign for it, kept it in box, reported it as "undelivered", and flipped it to me for cash. Insurance has meanwhile hooked him up with a new phone, and the factory kept my phone in the "we're looking for it" pile for the requisite 90 days, after which they officially publish its IMEI as "blacklisted". That would explain why it worked for a while but doesn't now; and this 90-day TO THE DAY period is the same for Rogers as it is for AT&T apparently (which is where the rep used to work for 10+ years).
I am in possession of stolen property. I've little hope of recuperating my losses. I've been advised to file a police report, and I think I will actually, given that I've got a receipt with the "anonymous" guy from Craigslist's name on it which I had printed out from Bell after they scanned the IMEI number for my factory warranty receipt. This phone will officially never work in Canada, as there is no way for it to be removed from the blacklist. I've been very unfortunate in this case, and it's a real shame.
People should take note: If buying a phone, ALWAYS do it in-store and have the IMEI number run first to check and see if it's on the blacklist. Next, have the phone transferred into your name so that the IMEI and you are officially linked, and the guy can't report his gear stolen or lost. That should suffice in most cases... except in the case of insurance fraud, which is my case, where there is a 90-day delay period in the IMEI number being added to the blacklist (which is why it didn't come up on the blacklist last week when I had the Bell rep run it in-store for me). Another point of interest is that in my case, I found it was possible to lose service BEFORE the number is on the blacklist—assuming the Bell guy didn't run the number wrong last week.
So f**k me. All I can do is try to hack the number, I guess, or find a way to spoof the IMEI.
Edit: Unf***ing believeable—I somehow reenabled data and texting by messing around with QPST. Calls still not happening, though.
Figured I share my repair experience here as OnePlus has set a new low in my book for customer service. Started when I sent my device (unlocked by T-Mobile) for repair last month. I was given the option of repair or replacement but chose repair so I wouldn't have to unlock again. I received it back about a week later but with no documentation as what the repair was (found out through my calles it was a motherboard replacement. I did notice the SN was the same but the IMEI was different. Used it for 3 days and called T-Mobile to have it unlocked but their system now sees my device as a non-T-Mobile phone and they can't unlock it (and they have tried 4 times since Sept 25th). Over the past few weeks I have conferenced on T-Mobile support with OnePlus support in an attempt to get it unlocked and every time I call it's like starting from scratch with OnePlus. Four times now I've been told to wait 24-48 hours so they can hear back from there repair facility, I've made 14 total calls to check status (they have never called me back once). T-Mobile has been absolutely great and were on the phone with OnePlus with me for over an hour. So for know unless a miracle happens I'm stuck with a phone that can't be network unlocked by any carrier. Looks like the repair facility perhaps used a standard motherboard and flashed the T-Mobile firmware on it from what I can determine. If you need service for a T-Mobile device ALWAYS choose a replacement if you have the option)
Rule #1: Never ever choose repair when replace is an option. XDA is rife with people complaining about repair issues with every phone manufacturer. But I think you know that now. Also, I would hardly fault OnePlus in this situation. Its a simple issue of the IMEI not being in the T-Mobile database. Thats not OnePlus' fault. Thats a T-Mobile issue. IT can be added to there database. Verizon does this but for a completely different reason. But ultimately fault is in the eye of the beholder.
Also, to further support my claim think of it this way... T-Mobile (and Verizon) request the bootloader / SIM lock. If you buy the non carrier version from One Plus this would be a mute point. Again, a T-Mobile issue, not OnePlus. If you really want to get technical fault the US Congress for allowing them to lock in the first place. Ok Ok... Way off on a tangent...
Now... Some questions for you...
Have you ran the IMEI against an IMEI check database to see what kind of device it returns as? I would be curious to see. Another way to find out if its a T-Mobile device is to check the IMEI against your last phone. If the first few digits are the same or different will support your claim of the device being different.
Have you tried to tried to toggle the bootloader unlock switch or is it gray'ed out?
Have you tried popping in another carriers SIM just for giggles?
Lastly, have you tried to unlock it yourself by using the built in unlock program in network settings?
If that fails you may want to consider sending it back to OnePlus again for replacement. I can only assume that you do not have insurance? If you do then you may want to check with them about replacement faulting the IMEI as the issue. Might be a hard sell but I'm sure it could be done.
Scott said:
Rule #1: Never ever choose repair when replace is an option. XDA is rife with people complaining about repair issues with every phone manufacturer. But I think you know that now. Also, I would hardly fault OnePlus in this situation. Its a simple issue of the IMEI not being in the T-Mobile database. Thats not OnePlus' fault. Thats a T-Mobile issue. IT can be added to there database. Verizon does this but for a completely different reason. But ultimately fault is in the eye of the beholder.
Also, to further support my claim think of it this way... T-Mobile (and Verizon) request the bootloader / SIM lock. If you buy the non carrier version from One Plus this would be a mute point. Again, a T-Mobile issue, not OnePlus. If you really want to get technical fault the US Congress for allowing them to lock in the first place. Ok Ok... Way off on a tangent...
Now... Some questions for you...
Have you ran the IMEI against an IMEI check database to see what kind of device it returns as? I would be curious to see. Another way to find out if its a T-Mobile device is to check the IMEI against your last phone. If the first few digits are the same or different will support your claim of the device being different.
Have you tried to tried to toggle the bootloader unlock switch or is it gray'ed out?
Have you tried popping in another carriers SIM just for giggles?
Lastly, have you tried to unlock it yourself by using the built in unlock program in network settings?
If that fails you may want to consider sending it back to OnePlus again for replacement. I can only assume that you do not have insurance? If you do then you may want to check with them about replacement faulting the IMEI as the issue. Might be a hard sell but I'm sure it could be done.
Click to expand...
Click to collapse
Same situation here, mine was unlocked did a replacement and it was locked and T-Mobile has no record of it. It took me 17 days to get the replacement and every day I checked the status I get told wait 24-48 hours. Now after I got it I'm told every day to wait 3-5 days for an update. Really one plus?
One plus sucks at anything customer service. Can you not do a warranty through tmobile?
Hi, i have the same problem. I was able to unlock my OP8 the moment I bought it. But after sending my OP8 for repair, it was locked when sent back. I got the error "server 255" when I tried to do a permanent unlock.
I contacted Tmobile and they said I need a valid tmobile account, which I don't:
"One of our mobile device unlock requirements is an active T-Mobile account. Since you don't have one you're going to need the get the unlock via a 3rd party company. Our apologies for this."
I have contacted OP 4 times now. They say they'll escalate my problem to the relevant team.
So how did u ppl solve it? Anyone tried the mtd below:
https://www.reddit.com/r/oneplus/comments/qn8dez
Thanks.
zonexo said:
Hi, i have the same problem. I was able to unlock my OP8 the moment I bought it. But after sending my OP8 for repair, it was locked when sent back. I got the error "server 255" when I tried to do a permanent unlock.
I contacted Tmobile and they said I need a valid tmobile account, which I don't:
"One of our mobile device unlock requirements is an active T-Mobile account. Since you don't have one you're going to need the get the unlock via a 3rd party company. Our apologies for this."
I have contacted OP 4 times now. They say they'll escalate my problem to the relevant team.
So how did u ppl solve it? Anyone tried the mtd below:
https://www.reddit.com/r/oneplus/comments/qn8dez
Thanks.
Click to expand...
Click to collapse
I hate oneplus with a passion I'm 8 months and still going with an issue they keep BS'n me on
Hi, I would like to post an update. After contacting OP support a few times thru chat, they agree to help me talk to Tmobile directly. I told them I can't use the phone, I'm overseas (really, no joke), and I contacted Tmobile but they refused to help.
After waiting for a few days, my IMEI is whitelisted and I was able to unlock the phone. So I guess if you are persistent enough and tell them tt you've exhausted your options, they will help. So I guess they're still nice ppl (kudos to Sophia!)
Hope someone with similar problem can try what I did.
Just wanted to fan the flames that OnePlus is still up to their BS. I sent my phone to repair the back glass after I recovered from unbricking my phone rooting after the Android 13 OTA. When I get it back, after all these warnings signs something was off I realized when I tried to put my unlock_code.bin and it kept failing that they gave me a new motherboard. Luckily I AM a Tmobile customer, but holy heck, what if I was not? Luckily somehow I was able to get in to get the info to request another code to unlock my bootloader even though I'm still carrier locked.
fgjruiz said:
Just wanted to fan the flames that OnePlus is still up to their BS. I sent my phone to repair the back glass after I recovered from unbricking my phone rooting after the Android 13 OTA. When I get it back, after all these warnings signs something was off I realized when I tried to put my unlock_code.bin and it kept failing that they gave me a new motherboard. Luckily I AM a Tmobile customer, but holy heck, what if I was not? Luckily somehow I was able to get in to get the info to request another code to unlock my bootloader even though I'm still carrier locked.
Click to expand...
Click to collapse
I just had my op8 repaired back with a motherboard replacement so that it can't unlock the sim as I am not a T mobile customer. I used online chat several times and complained about sim-unlock. Finally, after I gave them both old and new imei and strong complain, they unlocked my sim card. Not a good experience, but the result turned out to be good.