Related
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.
Dear All,
I write to inform you that i finally solved my GT-I9300 'Not Registered on Network' problem. I decided to make this official announcement so as to assure others, most especially those who have tried almost all the tricks and steps found on this and other forum on the subject that all hope is not lost.
May be if i shed more lights on the problem which i encountered, and i suppose many other people, you will understand me very well. First, i did the upgrade through Samsung Kies and after the phone rebooted, it lost link to network. I called Samsung and chatted online with the Customer Service, i was asked to send the phone to South Africa where i bought it. I called South Africa and also chatted but they could not understand let alone solve the problem. I headed to XDA and other forum to find solution, I tried all versions of ARIZA Patch, none work. I tried all modified ROM, yet no solution. At one point, the problem became complex. The phone moved from not registering on network to 'Factory Mode'. I followed many other steps, but could not get past restoring it back to User mode. I gave up after a month and bought another phone.
My son shocked me last Friday when he said that it will be his first time of seeing me accepting that some problems cannot be solved. I mused over it and told myself that i will rather destroyed the phone totally than giving him the impression that i cannot solve the problem.
I got out my two computers - Mac and PC and reformatted them all. Installed ODIN and downloaded a 4.3 Stock ROM. I then began searching everywhere for any clue as to what went wrong with the phone. My research is simple; the PHONE could not register simply because the IMEI and Serial Number were wrong. My IMEI and S/N moved from 0000 to unknown. After reinstalling through KIES, it came back from unknown to another wrong numbers.
I finally decided to go inside the phone by activating everything on ODIN and see if i can get the wrong EFS on the phone wiped away and left empty. I repartitioned, wipe EFS, etc. and the only thing the phone did was to move from unknown to another incorrect IMEI and Serial.
Finally, i read on a post that the problem is simply software, so i began searching if it is possible to repartitioned the phone completely and turn it into a toy. I recalled that about ten years ago, i successfully installed Nokia OS on Blackberry through a poorly concerted code designed by a friend. In so far i still have the code, I thought that i could do same with my GT-I9300. It won't work, sadly. But in the process of doing so, i realized that using SRS, i can do so comfortably. With this 20 USD software, i gained control of the internal organs of my phone and started out by wiping out the EFS first and with my EFS Backup, i re-wrote it back on the phone. That done, i expected the phone to work, but sadly it refused to register on network.
Not ready to give up, i went further to see what other options are available to me. I realized that i can actually re-wrote my IMEI and Serial number back to the phone. I tried it and after about an hour and almost three attempt, T-MOBILE surfaced on my phone and the GT-I9300 came back to life.
Altogether, i spent two unbroken days reading and reading and applying one step after another, one procedure after another till i finally got the phone back.
SRS can not only do this, but can take back your contract and locked phone from those shylock and give you your phone. It go inside your phone and show you all the codes that locked you to a particular network, etc. It can remove those useless codes that make your phone patented to a particular country and give you an international version. It can also turn your international version to a local one, if you so desire.
I do not know who designed this software, i however testify to its immense ability to safe you from Samsung's irresponsibility.
I am open to helping others and answering questions on GT-I9300.
I have since been enjoying my phone.
what's the short version of the story?
tmzbeme said:
what's the short version of the story?
Click to expand...
Click to collapse
Going by the last lines, it seems this is the tl;dr version
"SRS can not only do this, but can take back your contract and locked phone from those shylock and give you your phone. It go inside your phone and show you all the codes that locked you to a particular network, etc. It can remove those useless codes that make your phone patented to a particular country and give you an international version. It can also turn your international version to a local one, if you so desire."
Hi! As i understood i need to get SRS and after?
where is the SRS software ? can you post a link ?
I’m not sure if anyone will be able to help but I thought I’d ask. I had my phone replaced under warranty for the volume buttons sticking in and not being able to click them any more. Got the new device in and it wouldn’t activate. It registers the SIM card and goes to no service. I called Verizon and tried to get them to help me activate it and spent 2 hours on the phone with them and tried EVERYTHING they could think of. Entering IMEI numbers, SIM numbers, factory reset, and a new sim card.
In the end they told me that when I turn the phone on the IMEI number they entered changes to a different one from what the phone reports and is failing activation. They had me try a new sim card to make sure the sim wasn’t broken and that still didn’t work. Called Motorola spent a while on the phone with them trying the same things and they agreed it was a rare case and that I would need a second replacement phone.
I received the new (third) phone yesterday and it is having the same problem as the second phone. Won’t activate and when its powered on the IMEI number on the Verizon side is reports something different then what any of the other phones are showing. (so now between the 2 phones I have 4 different IMEIs reported (the assigned 2 the phone shows me and the 2 made up ones that the network switches to when I turn on the phone)
Now Motorola is suggesting another replacement and Verizon has stopped helping me and on my last call they transferred me to the Motorola support number. Has anyone seen anything like this?
Is there anything I can say to help try and get this resolved other than waiting for a fourth phone that may or may not work?
So I have a Samsung Galaxy S7 Edge, or rather my friend does but he brought it to me for some work. That being said he has about 20 different Gmail accounts with about 20 different passwords and he doesn't know which one belongs to which and I factory reset the phone part of discovering which one was the master account. In any case I try to use Chimera to do an FRP unlock but unfortunately because it is on Android 7.0 it did not let me do this. I also try to roll it back to 6.0 or 6.1 rather butt same.
I read a few different online guides and one of them was on how to do the network unlock by doing a bypass of the Wi-Fi to get around the initial settings and then from there you open up the terms and policies with the long press and allows you to open up the app manager in you go to settings there. The problem is is that unfortunately that seems be disabled on some security update to happen for 6.1 on one of the OTAs at some point in time
I saw there were few different tools out there but the one that I was able to read the guide on seem to not work at all because when I hit the button the response I got was green but the diamond ever popped up if that makes any sense. In any case it's 2017 about halfway through the year and it seems that every FRP unlock has changed modestly since 2015 near the end of the year.
Is there a current method on how to refresh that are peel off whether it is the change out Sims 2 loaded if in firmware to do something. But the phone is not even to root it yet but I intend to do so after we get into the phone directly. Please provide any assistance if you have it.
Thus, uh... Really sounds like your "friend" stole this phone ?
No. If we provide you any solutions even if what you said is true, other people with stolen phones can bypass the very measure that Samsung incorporated to disable stolen phones. If it is truly your 'friend's device, tell him ANY Google account he used with the phone will get rid of the frp lock. It doesn't have to be a specific one.
williamschromebook said:
So I have a Samsung Galaxy S7 Edge, or rather my friend does but he brought it to me for some work. That being said he has about 20 different Gmail accounts with about 20 different passwords and he doesn't know which one belongs to which and I factory reset the phone part of discovering which one was the master account. In any case I try to use Chimera to do an FRP unlock but unfortunately because it is on Android 7.0 it did not let me do this. I also try to roll it back to 6.0 or 6.1 rather butt same.
I read a few different online guides and one of them was on how to do the network unlock by doing a bypass of the Wi-Fi to get around the initial settings and then from there you open up the terms and policies with the long press and allows you to open up the app manager in you go to settings there. The problem is is that unfortunately that seems be disabled on some security update to happen for 6.1 on one of the OTAs at some point in time
I saw there were few different tools out there but the one that I was able to read the guide on seem to not work at all because when I hit the button the response I got was green but the diamond ever popped up if that makes any sense. In any case it's 2017 about halfway through the year and it seems that every FRP unlock has changed modestly since 2015 near the end of the year.
Is there a current method on how to refresh that are peel off whether it is the change out Sims 2 loaded if in firmware to do something. But the phone is not even to root it yet but I intend to do so after we get into the phone directly. Please provide any assistance if you have it.
Click to expand...
Click to collapse
If you're still in need of help see this post >>>> https://forum.xda-developers.com/tmobile-g6/how-to/frp-unlock-lg-g6-using-headphone-jack-t3616166
It's aimed at LG users but it may help. There's also a guide linked within post for samsung folks.
If it helps send a thanks.
I used realterm, but ill keep that post bookmarked Thanks
Sent from my HTC 0PJA2 using XDA Labs
My buddy gave me his phone to try to fix the same issue.
It is his 71 year old mother's phone and she can't remember her email address much less her password. I have tried everything I can think of to no avail.
Sent from my SM-G935U using XDA Premium HD app
Try blowfish unlocks in Google.
Sent from my SM-G935T using Tapatalk
Eric1084 said:
No. If we provide you any solutions even if what you said is true, other people with stolen phones can bypass the very measure that Samsung incorporated to disable stolen phones. If it is truly your 'friend's device, tell him ANY Google account he used with the phone will get rid of the frp lock. It doesn't have to be a specific one.
Click to expand...
Click to collapse
Not true at all.
It has to be the account that was logged into at the time of the reset. You can easily link your Google account to the phone and it still won't allow you to use your account to open it back up.
Not a troll either but in about same place this guy is just mine is legit
So basically this is what has got me messing around with flashing and trying to mess with the firmware also different settings on the android system. However so like the previous user which actually does sound like his "friend " did steal it. This one is a S7 I actually purchased in la. It is not a nightmare of a drive but for $200 it almost is. Im almost about to sell the phone on ebay. I immediately after purchase spoke with t-mobile and was told phone was good just it was sim locked. I would need to sign up with there service. The phone was supposedly frp free and sim unlocked for any carrier in the americas and europe. Very far from the case. I put my personal sim card in for att get the same network id message or the puk when i enter it wrong have tried even new att sim cards. Att is offering me the same deal but said to prepay for 90 days. I am not sure how this makes sense since how is unlocking the sim also going to unlock the google account from previous owner??? I keep trying different methods with odin and smart synch. Any other random apps basically and best I do is make a paper weight or can get to my imei on a legit dial pad however I try to go to even change to imei from previous phone which is still active just broken screen but still have the same issue. I am thinking at this point mabye t mobile and att are the hassle here and half the videos have helped me about 10% from youtube and different docs. I have been going on trial and error for about 2 weeks now. Called t mobile back last night same story just due to all the the theft but she again checked my imei on the device and said it was all good still to get back to them when ready to commit to service. yeah.... right. But Im trying to avoid just throwing the thing the next time I brick it or sell it on ebay. I am doing everything correctly and all is legit. Even trying to transfer my other phones info if needed. Obviously it is still sim locked and has frp through google. Please help any ideas. I am about to probably throw it before I ever get the chance to sell it is that frustrating. One thing I cannot get to work correctly is rooting. I even went loaded apps on sd card went into apply updates or data from sd card and reads folders but not the program im trying to use for rooting. I have done multiple times on many devices. I dont know if t mobile is just like jumping through hoops or am i just skipping some small detail somewhere in the process. IDK HELP PLEASE ANY FEEDBACK IS APPRECIATED. I AM USING THE NOUGHAT FIRMWARE, I TRIED ON MARSHMELLOW AND EVERYTHING GOES THROUGH THEN AT END GETS CAUGHT UP WHEN I GO BACK TO UPDATE BACK TO CURRENT FIRMWARE.
sapi3nt said:
So basically this is what has got me messing around with flashing and trying to mess with the firmware also different settings on the android system. However so like the previous user which actually does sound like his "friend " did steal it. This one is a S7 I actually purchased in la. It is not a nightmare of a drive but for $200 it almost is. Im almost about to sell the phone on ebay. I immediately after purchase spoke with t-mobile and was told phone was good just it was sim locked. I would need to sign up with there service. The phone was supposedly frp free and sim unlocked for any carrier in the americas and europe. Very far from the case. I put my personal sim card in for att get the same network id message or the puk when i enter it wrong have tried even new att sim cards. Att is offering me the same deal but said to prepay for 90 days. I am not sure how this makes sense since how is unlocking the sim also going to unlock the google account from previous owner??? I keep trying different methods with odin and smart synch. Any other random apps basically and best I do is make a paper weight or can get to my imei on a legit dial pad however I try to go to even change to imei from previous phone which is still active just broken screen but still have the same issue. I am thinking at this point mabye t mobile and att are the hassle here and half the videos have helped me about 10% from youtube and different docs. I have been going on trial and error for about 2 weeks now. Called t mobile back last night same story just due to all the the theft but she again checked my imei on the device and said it was all good still to get back to them when ready to commit to service. yeah.... right. But Im trying to avoid just throwing the thing the next time I brick it or sell it on ebay. I am doing everything correctly and all is legit. Even trying to transfer my other phones info if needed. Obviously it is still sim locked and has frp through google. Please help any ideas. I am about to probably throw it before I ever get the chance to sell it is that frustrating. One thing I cannot get to work correctly is rooting. I even went loaded apps on sd card went into apply updates or data from sd card and reads folders but not the program im trying to use for rooting. I have done multiple times on many devices. I dont know if t mobile is just like jumping through hoops or am i just skipping some small detail somewhere in the process. IDK HELP PLEASE ANY FEEDBACK IS APPRECIATED. I AM USING THE NOUGHAT FIRMWARE, I TRIED ON MARSHMELLOW AND EVERYTHING GOES THROUGH THEN AT END GETS CAUGHT UP WHEN I GO BACK TO UPDATE BACK TO CURRENT FIRMWARE.
Click to expand...
Click to collapse
Nothing I read stated that you have, or even know, what an FRP Locked device [is]. I'll skip badgering you with pointless questions & just jump straight to giving you solutions:
1) Flash & boot into TWRP Recovery > Wipe the IntrnlStrg/Cache/Dalvik/System (system is key > Flash stock firmware
2) Find my Galaxy S7 & S7e FRP Bypass post here on XDA (for advanced users)
3) Do more research
I'm not trying to sound like an asshole so I apologize if I come off strong - I'm [almost literally] sick of reading all these f*cking crybabieson XDA, or other sites, begging for somebody to solve their problem instead of doing their own research & trial error runs. I have successfully bypassed FRP on 30+ different devices from different carriers with different security patch updates on Lollipop-Nougat OS by using various different methods that are(n't) common (S7 included)
Bypassing FRP is Elementary school difficult. This sh¡t is checkers, not chess. My spiel is done with
Good luck.
I think I ended up with this guy's phone from Craigslist...
☆KØŁØЯΛĐØ☆ said:
Nothing I read stated that you have, or even know, what an FRP Locked device [is]. I'll skip badgering you with pointless questions & just jump straight to giving you solutions:
1) Flash & boot into TWRP Recovery > Wipe the IntrnlStrg/Cache/Dalvik/System (system is key > Flash stock firmware
2) Find my Galaxy S7 & S7e FRP Bypass post here on XDA (for advanced users)
3) Do more research
I'm not trying to sound like an asshole so I apologize if I come off strong - I'm [almost literally] sick of reading all these f*cking crybabieson XDA, or other sites, begging for somebody to solve their problem instead of doing their own research & trial error runs. I have successfully bypassed FRP on 30+ different devices from different carriers with different security patch updates on Lollipop-Nougat OS by using various different methods that are(n't) common (S7 included)
Bypassing FRP is Elementary school difficult. This sh¡t is checkers, not chess. My spiel is done with
Good luck.
Click to expand...
Click to collapse
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
U-TK said:
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
Click to expand...
Click to collapse
• A new cable would be ideal
• Try different versions of Odin
• Reinstall Device divers
What OS version is installed & are you able to boot completely?
☆KØŁØЯΛĐØ☆ said:
• A new cable would be ideal
• Try different versions of Odin
• Reinstall Device divers
What OS version is installed & are you able to boot completely?
Click to expand...
Click to collapse
Open to anything! A different came (not new) doesn't do anything when I plug it in. The cable that came with it charges it and is detected by phone, but not by PC.
I'll go buy a new cable and see it it does anything. Meanwhile I'll try all the previous versions of Odin. I also suspect the most recent version might not be doing the trick for some reason (having rooted and flashed about a dozen phones on prior versions).
It completely boots either Oreo 8.0 or 8.1 to the Welcome setup wizard every time. None of the soft tricks get me any further than the FRP.
Want me to post a picture or anything? Download bootloader or FRP screen? I've also ordered an OTG cable to try out the apk work around.
edit: also tried jodin on a mac mini and odin on a different laptop. I have an older laptop I may try too.
U-TK said:
I have a similar model that I got off of Craiglist:
- Samsung SM-G900T
- completely up to date
- freshly re-imaged and FRP locked
- no soft FRP bypass works (probably updated to the absolute most current version of Android)
- not detected by Odin/Octopus (appears USB connectivity is disabled - it won't even show up when plugged in, anywhere).
- doesn't appear that USB debugging was enabled before the reset
- ADB and download mode just sit on "downloading/looking for filename" - I assume both options are being blocked from the USB connection, so there's no activity on the PC/Odin/tools when I use these options
The only activity when plugging in is that on the phone it goes 'blip blip' and has a little graphic over the USB port.
I liked your suggestion of do more research but this is stumping me, mostly because the USB appears to have 0 life other than to charge the phone.
Only thing I have not tried it OTG cable apk but I'm not hopeful. Friend is giving me a cable when I see him in a few days.
Click to expand...
Click to collapse
U-TK said:
Open to anything! A different came (not new) doesn't do anything when I plug it in. The cable that came with it charges it and is detected by phone, but not by PC.
I'll go buy a new cable and see it it does anything. Meanwhile I'll try all the previous versions of Odin. I also suspect the most recent version might not be doing the trick for some reason (having rooted and flashed about a dozen phones on prior versions).
It completely boots either Oreo 8.0 or 8.1 to the Welcome setup wizard every time. None of the soft tricks get me any further than the FRP.
Want me to post a picture or anything? Download bootloader or FRP screen? I've also ordered an OTG cable to try out the apk work around.
edit: also tried jodin on a mac mini and odin on a different laptop. I have an older laptop I may try too.
Click to expand...
Click to collapse
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
T-Mobile S7 Galaxy - all drivers up to date on both systems. What did I say? Sorry I used an S5 for years and probably quoted the model wrong. It's an SM-G930T
---------- Post added at 11:07 PM ---------- Previous post was at 11:04 PM ----------
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
Site was being screwy - sorry for the PM man. Same as below:
Sorry - I used an S5 for years and miquoted you the model. It's an SM-G930T (T-Mobile S7) The drivers on both systems are all up to date as well. It's 0x0, qualcomm, k1 s3 if that helps.
Again, sorry for PM, just curious on your thoughts with this one. Also wondering if you know if Download Mode would supercede any FRP or security settings. I keep trying various versions of Odin while connected in Download Mode - no COM port getting assigned.
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
T-Mobile S7 SM-G930T running Nougat 7.x
☆KØŁØЯΛĐØ☆ said:
So you have a T-Mobile Galaxy S5 running Oreo 8.x?
I would make sure all your device drivers are up to date as well as your Windows/Mac OS updates
Click to expand...
Click to collapse
S7 Nougate, new cable worked like a charm. New firmware in 5min, thanks for the advice!
edit: new (old) firmware, but security patches still in place. Still need help with FRP lock!
U-TK said:
S7 Nougate, new cable worked like a charm. New firmware in 5min, thanks for the advice!
Click to expand...
Click to collapse
So are you through FRP or you still need assistance?
☆KØŁØЯΛĐØ☆ said:
So are you through FRP or you still need assistance?
Click to expand...
Click to collapse
I got ahead of myself and still need assistance.
I've managed to fix a few things (it would fail constantly in odin and result in a failed firmware screen upon restart).
Current situation:
- USB debugging was not enabled
- FRP is locked on Android 7.x
- I can upgrade/downgrade the firmware, but upon restart it pops up "Erasing" then "Installing updates" then "Erasing" so its basically undoing any security unpatching I'm try to do. Currently it's got G930TUVU4BQG5 July 2017 firmware, but the security patches to prevent RealTime, SideSync, Smart Switch and other dialer programs etc seem in place.
- I can put a COMBINATION firmware which gets me into a factory binary, but I don't see anything in here and have to reflash back to G930TUVU4BQG5
- Spamming RealTime to repeat dial a number shows me the traditional "calling" screen, but bluetooth, end call, etc are all greyed out.
- I have no SIM installed.
This guy did an FRP unlock (most up to date security patch) in 10 minutes. EXCELLENT service.
https://simunlockremote.com/contact/
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.