Currently a number of people are having issues with their Sprint versions and the OTA Sep update. I am just trying to start a new thread to help people coming from other places as to what their options may be.
Just to clarify I personally have a locked Sim and have not fixed the issue (I purchased the phone used from Amazon "Unlocked" but it was apparently a sprint version).
Currently can the phone (with the OTA) be rooted and flash an older version of the bootloader and modems? using Magisk (I believe this is still being discussed and worked on).
Can Sprint unlock the phone and it work? Either going down to a spring store, or doing the phone number deal?
I have been running through the same thought process. Had the phone for 6 months, now it doesn't work.
I was about to go to a Sprint store today to sign up for a monthly plan and port my number there (from Verizon). I am monthly on Verizon, so no real harm, except the rest of my family will remain on Verizon. After 50 days, apparently Sprint will unlock your phone, so I was going to do that in 2 months. Maybe Sprint will be better in the end??
But before I do that I may try the root and flash. Just that I use this phone for work, and I can't keep it rooted due to Blackberry restrictions. Which isn't that big of a deal to manage, but just a pain...
Anyone else thinking about just signing up for sprint for a few months to do this?
Teevan said:
I have been running through the same thought process. Had the phone for 6 months, now it doesn't work.
I was about to go to a Sprint store today to sign up for a monthly plan and port my number there (from Verizon). I am monthly on Verizon, so no real harm, except the rest of my family will remain on Verizon. After 50 days, apparently Sprint will unlock your phone, so I was going to do that in 2 months. Maybe Sprint will be better in the end??
But before I do that I may try the root and flash. Just that I use this phone for work, and I can't keep it rooted due to Blackberry restrictions. Which isn't that big of a deal to manage, but just a pain...
Anyone else thinking about just signing up for sprint for a few months to do this?
Click to expand...
Click to collapse
I'm doing sprint as a last ditch resort, but i've def thought about it.
I'm in same boat as you guys ..Mine worked for 8 months on TMobile before this crap..
Sent from my Moto Z3 Play using Tapatalk
---------- Post added at 11:48 AM ---------- Previous post was at 11:23 AM ----------
In the Sprint unlock sim thread is a guide that might work.Starts on reply 221..I'm at work and can't try right now
Sent from my Moto Z3 Play using Tapatalk
I figured i would check with sprint and they can't validate my IMEI number on their website or with a customer service rep. Although i still have 2 weeks left of my ATT account i guess i have to wait till i'm good and ready to move forward with this. What a hassle. I might try and explore these options of root once everything gets figured out with the touch issues (without having to use an "OTA mouse" which i don't even know what that is) so we will see.
https://www.reddit.com/r/essential/..._source=amp&utm_medium=top_post&utm_content=2
Sent from my Moto Z3 Play using Tapatalk
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
https://www.amazon.com/UGREEN-Adapt...1536167066&sprefix=c+ot&sr=8-3&ref=mp_s_a_1_3
Bthat is what u need with a USB mouse to plug in it..It simple and easy trust me ..
Sent from my Moto Z3 Play using Tapatalk
I bought mine secondhand & was pleased that it just worked after I inserted my T-Mobile SIM.
receiving the Invalid SIM message after the Sept Pie update really crushed me.
I've reached out to Essential Support who stated:
Thanks for reaching out. This error message indicates that this device was originally purchased from Sprint and never properly unlocked from their network. The recent update didn't lock the phone directly, but rather was just a trigger for the device to check its carrier-lock status.
I've reached out to the seller on eBay & am hoping I can have them perform a SIM unlock with Sprint. If not, I'll be requesting a full refund.
I'll update once more progress has been made, for anyone else in the same situation.
I downgraded to an earlier nouget build and then flash the unlocked modem files to get the phone to work with T-Mobile again. Of course this means I can't upgrade the phone past the August update since it will re-lock the phone. If you can get a refund, I would. I probably going to have to go to Lineage OS since I bought mines off Craigslist.
Unlocked for months......
In the bootloader, my phone states "Device State- unlocked" still getting invalid SIM. I left sprint months ago, with a fully purchased phone. They were not helpful, once stating that a device cannot be unlocked, and relocked, then telling me I'm not a customer, not their problem. I am going to try and install Oreo, and see if that helps.
ThermalFreeze said:
I downgraded to an earlier nouget build and then flash the unlocked modem files to get the phone to work with T-Mobile again. Of course this means I can't upgrade the phone past the August update since it will re-lock the phone. If you can get a refund, I would. I probably going to have to go to Lineage OS since I bought mines off Craigslist.
Click to expand...
Click to collapse
You can update to september build and it won't relock.
Stuck
I have been trying for hours to install an older ota, but i keep getting a prompt that downgrad not allowed. any help?
well, i'm happy to say, i'm on Sept 2018 (PPR1.180905.036) and i'm able to get my T-Mobile SIM to work again
below are the steps I performed
(DISCLAIMER: the below commands are from memory, you may need to confirm the correct verbiage if the commands do not take properly)
you'll need a few things:
- NMK24B (get fastboot version from https://www.essential.com/developer/current-builds)
- modem files (provided by ziddey - https://forum.xda-developers.com/showpost.php?p=77532356&postcount=20)
- PPR1.180905.036 (OTA version, from same Essential Developer Overview site listed above)
- ADB/fastboot files for your OS (I use Minimal ADB from https://forum.xda-developers.com/showthread.php?t=2317790)
- Android Debugging enabled
- a good quality USB3 cable that provides both data & power
steps:
- back up anything you feel is important & move off of your phone
- reboot to bootloader (either via ADB commands or via holding VolDown during power on)
- ensure your phone is recognized by running fastboot devices
- unpack the NMK24B zip file & place it in same folder as your ADB/fastboot files
- run flashall.bat (if on Windows, command varies for your desktop OS)
- wait
- place the modem files into your ADB/fastboot folder as well
- flash the modem files (fastboot flash modemst1 modemst1.img followed by fastboot flash modemst2 modemst2.img)
- if you receive a message stating unable to flash modem partitions, you may need to reflash NMK24B again. otherwise, the modem files will not take properly
- reboot to recovery
- to be safe, I performed a factory reset here, may not be necessary for your scenario
- place the OTA zip file into your ADB/fastboot directory
- select option to install via sideload
- install Sept 2018 Pie PPR1.180905.036 via adb sideload PH1-OTA-PPR1.180905.036.zip
- allow time to complete & boot
NOTE: during the entire process, I had removed my SIM & placed in a different device
after the long boot-up, I was greeted with the Android setup where I connected to my WiFi network
I chose to not copy any data & set up as new. I also let the phone sit charging & on wifi for ~30 mins
I powered off, inserted my SIM & found that it was no longer rejecting it. I also verified my APN settings were correct for T-Mobile. I received a few SMS messages during this period & felt confident service was working properly.
because I like a clean configuration, I went ahead & performed a factory reset from inside Android settings menu, rebooted & began setting up from a previous backup
thanks to everyone that was able to provide much needed help. I hope the rest of you are just as lucky with regaining service on your phone
Thanks Jon -
My mother in law just had the same experience after being on a non-sprint network for 3 months. Today she got the INVALID SIM alert. I noticed under the About phone tab that there was a new header called Brand and it had Sprint below it. I called Sprint and they confirmed the phone was fully unlocked and ready for domestic and international use. I emailed Essential and got a generic response:
Hi there,
Thanks for reaching out. This error message indicates that this device was originally purchased from Sprint and never properly unlocked from their network. The recent update didn't lock the phone directly, but rather was just a trigger for the device to check its carrier-lock status.
If you are the original purchaser, and you have fulfilled all of your contract obligations with Sprint, you should be able to contact them to have the device properly unlocked.
If you purchased second-hand, the seller did not have this device unlocked from Sprint before selling it to you. We recommend seeking a return / refund, as this device will not be able to function on a different carrier. Unfortunately, Essential has no ability to remove carrier locks on devices. This can only be done by Sprint by the original purchaser of the device. If you are unable to get a refund or exchange, we suggest filing a dispute with the marketplace (e.g. eBay), as this device was sold to you with a carrier lock.
Sincerely,
Essential
Essential Customer Experience Team
What a generic response. I even noted that I verified with Sprint that the phone was fully unlocked. Now she has no backup and we're in the midst of a storm that can potentially take out her landline. Essential team really dropped the ball on this.
JHXDA said:
Thanks Jon -
My mother in law just had the same experience after being on a non-sprint network for 3 months. Today she got the INVALID SIM alert. I noticed under the About phone tab that there was a new header called Brand and it had Sprint below it. I called Sprint and they confirmed the phone was fully unlocked and ready for domestic and international use. I emailed Essential and got a generic response:
Hi there,
Thanks for reaching out. This error message indicates that this device was originally purchased from Sprint and never properly unlocked from their network. The recent update didn't lock the phone directly, but rather was just a trigger for the device to check its carrier-lock status.
If you are the original purchaser, and you have fulfilled all of your contract obligations with Sprint, you should be able to contact them to have the device properly unlocked.
If you purchased second-hand, the seller did not have this device unlocked from Sprint before selling it to you. We recommend seeking a return / refund, as this device will not be able to function on a different carrier. Unfortunately, Essential has no ability to remove carrier locks on devices. This can only be done by Sprint by the original purchaser of the device. If you are unable to get a refund or exchange, we suggest filing a dispute with the marketplace (e.g. eBay), as this device was sold to you with a carrier lock.
Sincerely,
Essential
Essential Customer Experience Team
What a generic response. I even noted that I verified with Sprint that the phone was fully unlocked. Now she has no backup and we're in the midst of a storm that can potentially take out her landline. Essential team really dropped the ball on this.
Click to expand...
Click to collapse
that's the exact same response I received from Support when I reached out to them. I didn't want to wait for Sprint or my seller to confirm the unlock status so I decided to reattempt flashing again. thankfully, I wasn't too invested into the setup yet & was able to accept the resets that occur during flashing.
Sorry to hear about your current situation, I hope Essential is able to identify a fix for everyone that's affected
Downgrade
ThermalFreeze said:
I downgraded to an earlier nouget build and then flash the unlocked modem files to get the phone to work with T-Mobile again. Of course this means I can't upgrade the phone past the August update since it will re-lock the phone. If you can get a refund, I would. I probably going to have to go to Lineage OS since I bought mines off Craigslist.
Click to expand...
Click to collapse
I tried to downgrade to every single build below the most recent and my touchscreen is completely unresponsive for each build. any ideas?
jon_ybanez said:
well, i'm happy to say, i'm on Sept 2018 (PPR1.180905.036) and i'm able to get my T-Mobile SIM to work again
below are the steps I performed
(DISCLAIMER: the below commands are from memory, you may need to confirm the correct verbiage if the commands do not take properly)
you'll need a few things:
- NMK24B (get fastboot version from https://www.essential.com/developer/current-builds)
- modem files (provided by ziddey - https://forum.xda-developers.com/showpost.php?p=77532356&postcount=20)
- PPR1.180905.036 (OTA version, from same Essential Developer Overview site listed above)
- ADB/fastboot files for your OS (I use Minimal ADB from https://forum.xda-developers.com/showthread.php?t=2317790)
- Android Debugging enabled
- a good quality USB3 cable that provides both data & power
steps:
- back up anything you feel is important & move off of your phone
- reboot to bootloader (either via ADB commands or via holding VolDown during power on)
- ensure your phone is recognized by running fastboot devices
- unpack the NMK24B zip file & place it in same folder as your ADB/fastboot files
- run flashall.bat (if on Windows, command varies for your desktop OS)
- wait
- place the modem files into your ADB/fastboot folder as well
- flash the modem files (fastboot flash modemst1 modemst1.img followed by fastboot flash modemst2 modemst2.img)
- if you receive a message stating unable to flash modem partitions, you may need to reflash NMK24B again. otherwise, the modem files will not take properly
- reboot to recovery
- to be safe, I performed a factory reset here, may not be necessary for your scenario
- place the OTA zip file into your ADB/fastboot directory
- select option to install via sideload
- install Sept 2018 Pie PPR1.180905.036 via adb sideload PH1-OTA-PPR1.180905.036.zip
- allow time to complete & boot
NOTE: during the entire process, I had removed my SIM & placed in a different device
after the long boot-up, I was greeted with the Android setup where I connected to my WiFi network
I chose to not copy any data & set up as new. I also let the phone sit charging & on wifi for ~30 mins
I powered off, inserted my SIM & found that it was no longer rejecting it. I also verified my APN settings were correct for T-Mobile. I received a few SMS messages during this period & felt confident service was working properly.
because I like a clean configuration, I went ahead & performed a factory reset from inside Android settings menu, rebooted & began setting up from a previous backup
thanks to everyone that was able to provide much needed help. I hope the rest of you are just as lucky with regaining service on your phone
Click to expand...
Click to collapse
The NMK24B flashes OK up until the end and fails on certain partitions and still can't get the modems to flash
aaroncal said:
The NMK24B flashes OK up until the end and fails on certain partitions and still can't get the modems to flash
Click to expand...
Click to collapse
If you are unable to flash certain partitions, you may need to perform a flash critical_unlock. I'll share the actual command when i return to my PC but the command should also be listed in other threads here
commands:
fastboot flashing unlock_critical
fastboot flashing unlock
irish hammer said:
I tried to downgrade to every single build below the most recent and my touchscreen is completely unresponsive for each build. any ideas?
Click to expand...
Click to collapse
You need unlock_critical
So fellow essential owners -
If you complain to sprint about your problem (or just tell what it is, really) and then tell them you don't feel like you should be paying for anything - they will let you do the One free year of service bring your own device promotion! Doesn't matter what service it is - as long as your number is eligible to be ported you get one free year of sprint service. I chose to go to the sprint store to get my sim card (so i can use my essential today) and they waved the sim card fee and sprint called me back and set it up! Now I have my essential phone back! It's marvelous! I bought a temporary phone for a couple hundred and I immediately missed my essential thank goodness i can return the other phone. It works out! Just make sure your number is active so you can port it. Free service for A YEAR, legitimately, if you do it right. I have total equipment protection on for 13 a month but you can turn it off at any time. Just a heads up! It's worth switching to sprint for me to keep my essential working, i have my old number, and possibly a better carrier.
irish hammer said:
I have been trying for hours to install an older ota, but i keep getting a prompt that downgrad not allowed. any help?
Click to expand...
Click to collapse
Can't downgrade through OTA, you must install the fastboot files through adb
Related
Pre-requisites:
a) Rooted
b) CWM Installed
c) Sim Unlock Code
I could not find a straight forward way to get the ATT SGH-I727 Unlocked and working on T-mobile so I thought I'd make this short list of instructions for those going through the same trouble.
The first thing I had to do was unlock the phone. I contacted a local company that charged $35. Free options failed. Expect to pay. There were mentions of calling ATT for the unlock code which I did, however, the CSR looked up the IMEI and determined that the unlock code was not YET available. From what I gathered, because the original phone owner was still under the two year agreement, this unlock was on hold until that time period was up. Those that bought their phone outright without a contract are provided their code with a call to customer service.
With the phone unlocked, I still couldn't get the phone to connect to a T-mobile signal. With a tmob sim, either a no-signal icon appeared or the phone simply showed full ATT bars but wouldn't allow T-mobile use in options. Also, *#simunlock# would generate a com.android error.
Finally, the following formula allowed for an unlocked phone picking up T-mobile signal:
1. Install the STOCK ICS UCLF6 4.0.4 - UNTOUCHED - rom following the instructions on that page impeccably.
2. Install Busybox (may not be necessary)
3. Install UCLF6 modified boot Kernel
4. Install T-mobile compatible radio - Blaze_4G_LB7_ICS_Radio_MOD worked for me
Boot it and see if you have a signal. You may need to go to options and manually choose T-mobile.
After that, I was able to install a different ROM. I chose SKY-ICS 4.2F6-2.6.1
With any new rom, you will still need to flash a tmob supported radio.
My s.o. will be using this phone, so I won't be messing with other roms, unfortunately. Let me know if you have a fast and stable configuration.
I hope this helps.
Actually as the radio is deeper than the firmware we flash normally you should only need to flash a tmo radio once unless a rom has radio built in most all roms do not
Sent from my SGH-I727 using Tapatalk 2
Does it make a difference whether I install the stock ics and kernel you provided? All I did is update the phone to ics via kies, install a recovery, flash superuser, then installed the blaze 4g radio. Would it make a difference between doing what you said and what I did?
madmajd said:
Does it make a difference whether I install the stock ics and kernel you provided? All I did is update the phone to ics via kies, install a recovery, flash superuser, then installed the blaze 4g radio. Would it make a difference between doing what you said and what I did?
Click to expand...
Click to collapse
Any luck with that? I'm trying to get mine to work but had to flash a t989 rom on it instead
ziyaad89 said:
Any luck with that? I'm trying to get mine to work but had to flash a t989 rom on it instead
Click to expand...
Click to collapse
It works, but its very crappy, sometimes connects, sometimes doesn't, even followed this post's instructions, still has crappy connection
For those who have T mobile fine on the Skyrocket , how much DL and UP speeds are you getting (and compaired to true T mobile phones data speeds) ? I heard some say they never get more than ~1 or 2 mbps which sucks TBH
Heard this is the hot T-Mobile skyrocket radio.
TELUS_SGH-T989D_LE4_ICS_Radio_MOD.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Digelato said:
Pre-requisites:
a) Rooted
b) CWM Installed
c) Sim Unlock Code
I could not find a straight forward way to get the ATT SGH-I727 Unlocked and working on T-mobile so I thought I'd make this short list of instructions for those going through the same trouble.
The first thing I had to do was unlock the phone. I contacted a local company that charged $35. Free options failed. Expect to pay. There were mentions of calling ATT for the unlock code which I did, however, the CSR looked up the IMEI and determined that the unlock code was not YET available. From what I gathered, because the original phone owner was still under the two year agreement, this unlock was on hold until that time period was up. Those that bought their phone outright without a contract are provided their code with a call to customer service.
With the phone unlocked, I still couldn't get the phone to connect to a T-mobile signal. With a tmob sim, either a no-signal icon appeared or the phone simply showed full ATT bars but wouldn't allow T-mobile use in options. Also, *#simunlock# would generate a com.android error.
Finally, the following formula allowed for an unlocked phone picking up T-mobile signal:
1. Install the STOCK ICS UCLF6 4.0.4 - UNTOUCHED - rom following the instructions on that page impeccably.
2. Install Busybox (may not be necessary)
3. Install UCLF6 modified boot Kernel
4. Install T-mobile compatible radio - Blaze_4G_LB7_ICS_Radio_MOD worked for me
Boot it and see if you have a signal. You may need to go to options and manually choose T-mobile.
After that, I was able to install a different ROM. I chose SKY-ICS 4.2F6-2.6.1
With any new rom, you will still need to flash a tmob supported radio.
My s.o. will be using this phone, so I won't be messing with other roms, unfortunately. Let me know if you have a fast and stable configuration.
I hope this helps.
Click to expand...
Click to collapse
Are you trying to get Call/Text connection or 4G HSPA+ Connect?
Works on WIND too!
I spend a while trying to get this phone working on Wind (Canada's 1700 AWS carrier, similar to Mobilicity / TMo). I've finally succeeded by doing the following.
1: Install latest ICS STOCK
2: Use CWS to flash AT&T UCLF6
I have not been able to get nearfield working with this modem, but it's working great other than that (albeit somewhat slow UL/DL speeds, but that's likely a more wind's crappy network than the phone). Let me know if anyone has any ideas regarding the Nearfield issue.
Just wanted to share. I have been made so freaking happy by the fact that this worked
I bought my SR for full price (549.99) months ago and stupid att also saying my unlock code is not available yet !!
I just got my RAZR HD XT926, and I thought I would see f I can up it to Kitkat, or maybe even to Jellybean. No big deal, but it has been a while and I forgot the unlock thingie. There is currently no SIM inserted.
Current ROM: 9.1.41.xt926.verizon.en.us
Here is what I have done:
- Set the phone to USB debug
- Downloaded 4.4.2
- Downloaded RSDLite 6.1.x
RSD lite started fine, I already had my drivers installed, everything seems fine. However, I forgot to unlock it. The phone is in CMD mode, telling me the Device is Locked:status code: 0.
So I went to the Motorola unlocking service (I can google, I try to do a decent effort before posting for help) so I am in the process of doing just that, following the Moto instructions, but there is one thing I do not get with those. First it want to download a vast amount of updates, which I allow with default selection, then:
- Motorola tells me to place my CMD prompt at the SDK tools and type $ fastboot oem get_unlock_data . Where is that, in which folder of the SDK?
- Will it even work with phone in that mode?
Update. I managed to access the device ID and submit to Motorola. This device can not be unlocked by Motorola method.
So, can it be unlocked at all?
Update 2. Got out of boot mode by reversing the button controls while starting.
Might as well keep posting about my progress
I got the 4.4.2 Verizon (VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF) stock working with the help of www_phonearena.com/news/root-comes-to-the-motorola-droid-razr-hd-razr-m-and-atrix-hd_id35615 Motofail2go who emulated the root boot thingie that i failed to accomplish otherwise. In the phone it now says System version 183.46.10.xt926.Verizon.en.US, Android version 4.4.2.
After inserting a SIM card (Swedish 3, www_tre_se) calling works.
Upgrade to Kitkat, and calling outside of US = works. As described in this and above post.
It seems there is no need to unlock it at all. For my purposes as of yet.
Very werd, it seems to accept some SIM cards but not others, depending on provider.
As I posted above it worked with a 3 SIM card, but today testing with a Telia SIM card it claims that it is from an unrecognized source. After some googleing this could both be an issue, and not, depending on circumstances. The easiest check might be to make sure I have a 4G SIM card for the Telia subscription.
It found an update, an official one.
I just hit "Yes" and "Download" and "Install" so tight now its doing that. Could it be KitKat? :fingers-crossed:
/Edit: after update: 183.46.15.XT926.Verizon.en.us. It was not KitKat, still at 4.4.2
One would think it should detect it is not at home anymore...
XT925: www_gsmarena.com/motorola_razr_hd_xt925-4970.php
XT926 : www_gsmarena.com/motorola_droid_razr_hd-4971.php
Make note of the difference between LTE support. 925 is the one you want.
This explains part of my issues, I am returning the 926 and placed an order on 925.
(bloody URL blocker!)
Hello.
(backstory, boring) I have an SM-955F from Claro that I've been trying to unlock completely from the carrier. I've had lots of trouble with them and am pending a case with FCC to get out of their claws. In the meantime, I've been trying (without success, hence my posts) to get it working 100% with T-Mobile. I've had T-Mobile for years under a friend's name and couldn't get a device -so I took one from Claro when Puerto Rico was hit with the Hurricane (T-Mobile had no signal for months).
(Little-lot- of info) So, I had the phone updated to Sammobile's PCT 8.0 firmware -G955FXXU1CRC7_G955FOWA1CRC2_PCT-. But it didn't have the OEM unlock. At one point I remember installing TWRP but something happened to the phone and it wouldn't boot up. So, my act of magic (*coughs*, XDA) I found a way to get it back to official firmware (I think at first it was a Germany's 8.0 firmware*can't find the file name*). Anyways, I want to get the phone to have Wi-Fi calling, VoLTE, etc from T-Mobile and, for what I've interpreted, that comes from the CSC files.
Now, I found a thread that uses TWRP+AROMA to get a list of CSC files on the phone and I can just install the one I want. (I don't know if there's an easier way directly from ODIN but I've not found that compatible TMB CSC file for my phone to get the features working, if any).
In any case I still want my phone rooted (I think I triggered Knox, but the phone updated through the Samsung Updater just fine after installing a PCT 7.0 firmware -G955FXXU1AQCC_G955FOWA1AQCC_PCT-. Clearly I'm out of my depth)
(to the point) The phone doesn't want to install my TWRP file. Says "custom binary(RECOVERY) blocked due to remaining installment balance". Obviously it's Claro's side blocking it, I think?. But I can't get them to unlock it (since it's still "theirs", until I get my case resolved or pay their stupid balance. Long story short, Claro's service is **** and I regret not waiting to get my credit approved my T-Mobile)
So, how do I go about it? I read that its RMM blocked. But my state says normal. The OEM unlock only appears on the 7.0 -G955FXXU1AQCC_G955FOWA1AQCC_PCT- firmware (even then it won't let me install TWRP through ODIN). I honestly don't know. I'll appreciate all the help I can get to reach my goal of getting 100% on T-Mobile's features (mainly VoLTE, if possible-the feature is greyed out so I assume it can be activated). Can't even change the radio band on the thing. I read something about using Nova Launcher and having the widgets activate it through "Enhanced LTE" (I think) but that option doesn't appear on the list. I'd also like to delete all remnants from Claro on the phone, bloatware, booting logo and such. Since it's a 955F, I assume one can make it as if international?
Also, please check my previous post, I just realized I forgot to detail something. I did hit that "your phone has been modified, restart to undo process" and I forgot. Maybe that's the root of it all?
Any questions, please do ask. I'd like to get this moving. For now I'll use my Nexus 6 (God I love that phone a lot)
Maybe there's some compensation on this, maybe, if I get it done.
I've included the picture of the error and the info on Download mode, links for files I refer to also at the bottom.
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955F/PCT/download/G955FXXU1CRC7/216223/
https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955F/PCT/download/G955FXXU1AQCC/129048/
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Bump.
I have the same problem "custom binary (RECOVERY) blocked due to remaining installment balance", when trying to install TWRP, in my case I want to install Custom Rom and I could not, I have not found any solution to this problem, I do not have OEM on 8.0, and the RMM status is normal, I could unlock unlock SIM thanks to a friend with Z3X tool, do not charge for it but thankfully I made a donation for the hard work and also that the Z3X is not cheap at all, if you need to talk to him, you inform me to give you his contact.
SM-G955F Claro Puerto Rico.
I Present The Galaxy A71_5G Guide for Flashing Unlocked Firmware.
Here are some useful reminders:
All download links are at the bottom of this post.
Make sure you follow the "Prerequisites For Anything You decide To Do In This Guide" section.
Don't copy quotation marks, unless I tell you to in this guide.
You will need a Windows computer in order to utilize the software provided.
This is an A71_5G guide, not an A71_5GUW guide.
WARNING: Anything you do in this guide will erase your phone completely. It's recommended that you back up before you do anything and that you remove your google account from your phone (so you don't have to go through FRP).
Disclaimer:
I am NOT responsible for any damage done to your device if you decide to use this guide.
Prerequisites for anything you decide to do in this guide (Required):
Standard Odin
Samsung Drivers
Steps:
1) Uninstall Samsung Switch and/or Samsung Kies, if present on your computer. This helps removes any conflicts with Odin.
2) Extract the Samsung Driver zip and the Odin zip to somewhere safe on your computer.
3) Double click on the extracted "SAMSUNG_USB_Driver_for_Mobile_Phones" executable (SAMSUNG_USB_Driver_for_Mobile_Phones.exe) and complete the installation wizard.
3) Navigate to your extracted Odin folder and double click on the Odin3 v3.14.1_3B_PatcheD.exe.
All About Bootloaders (Required Reading):
As Wikipedia puts it, “A boot loader is a computer program that loads an operating system or some other system software for the computer after completion of the power-on self-tests.” In other words, a bootloader is what loads you operating system. In most Samsung phones (including the S8 and S8+), there’s an e-fuse that prevents downgrading of the bootloader. This means any firmware or firmware update containing a lower Bootloader version than the one you have, will FAIL to be applied. There is really no way to circumvent this.
I’ll be explaining how to properly identify your current Bootloader version.
How to identify Bootloader version:
Steps:
1) Open “Settings” on your phone.
2) Scroll down to “About Phone”.
3a) If you are on a standard, carrier firmware, under “Baseband version” you should see something similar to this: “G950UXXXXXXXX”.
3b) If you are on an unlocked firmware, under “Baseband version” you should see something similar to this: “G950U1XXXXXXXX”.
4) No matter which firmware you're on, the fourth “X” would be either a “1” or a “2”, which means you will have either Bootloader version 1 or Bootloader version 2, respectively.
Note: As stated in the last section attempting to flash firmware that contains Bootloader v1 onto a phone that already has Bootloader v2, will fail. You can update a phone on Bootloader v1 to a firmware that has Bootloader v2, however.
Flashing Unlocked Firmware:
NOTE: The unlocked firmware does NOT unlock your phone for use on other carriers, it only removes bloatware. Some carrier specific features, such as Wi-Fi Calling and VOLTE will not work with the Unlocked Firmware.
Prerequisites: What's listed in the "Prerequisites for anything you decide to do in this guide" section
Odin3 v3.14.1_3B_PatcheD.exe.zip
Unlocked Firmware from site listed below.
Steps:
1) Extract the Odin3 v3.14.1_3B_PatcheD.exe and the Unlocked Firmware you downloaded from below.
2) Turn off your A71_5G.
3) Once off, hold the Power button while holding the Volume Down button, and the Volume Up button until you feel a vibration then let go of the power button.
4) Press the Volume Up key to enter Download Mode.
5) On your PC, navigate to your extracted Odin3 v3.14.1_3B_PatcheD.exe folder.
6) Double click on the "Odin3 v3.14.1_3B_PatcheD.exe" executable.
7) Connect your phone to your PC with your USB cable.
8) You should see Odin3 v3.14.1_3B_PatcheD output "Added!!" in the "Log" tab and underneath the "ID:COM" section, you should see an empty box turn blue.
9) Now it's time to add your firmware files that were extracted earlier. Individually add an appropriate firmware file for each box on the right. The "BL" box will require a firmware file that starts with "BL", the "AP" box will require a firmware file that starts with "AP", the "CP" box will require a firmware file that starts with "CP", and the "CSC" box will require a firmware file that starts with "CSC" (DO NOT USE THE "HOME_CSC" file for the "CSC" box).
10) Go to the "Options" tab and make sure that only the "Auto Reboot" and "F. Reset Time" checkboxes are ticked.
11) Go back to the "Log" tab.
12) Click the "Start" button on bottom right.
13) Sit back and relax for a while. Odin will output what is being flashed in the "Log" and on a box in the top left.
14) The box in the top left will become green and in black letters say "PASS" once the flash was successful.
15) Once the flash finished, disconnect your phone from your computer.
16) Your phone will do an erase at this point, so don't mess with your phone until you reach the setup screen.
17) Continue with the setup on your phone and enjoy!
DOWNLOADS:
Standard Odin/Patched Odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Samsung Drivers: http://developer.samsung.com/galaxy/...er-for-windows
Google Platform-Tools (ADB): https://developer.android.com/studio/releases/platform-tools
Unlocked Firmware (Bootloader v1): https://samfw.com/firmware/SM-A716U1/XAA
CREDITS
Credit goes to each respective site/developer for the tools required to complete this.
If you would like to be added to the credits and are one of the developers or owners of the tools used please feel free to Private Messege Me!!!
This Will Be Updated To The Latest Firmware When The U1 Varient Gets Updates
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
cubano2031 said:
Do you know where i can find the carrier firmware ??? I'm looking for the AT&T one ..... Thank you
Click to expand...
Click to collapse
you should be able to find it using sammobile.com or frija https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
andrewNY said:
Does 5G still work for you? I had read somewhere that it wouldn't function if you didn't have the T-mobile firmware.
Click to expand...
Click to collapse
5G works just fine. pretty much everything works minus the chat features in samsung messages.
---------- Post added at 11:03 PM ---------- Previous post was at 10:49 PM ----------
SmileyMorgue said:
Original XAA user here...we're still on the June security patch which apparently does not support Chat in Samsung's message app (though does still work in Google's). Looks like TMobile is one of the carriers that actually cooperates with Samsung Messages which makes me think switching to the unlocked firmware (at least the current version) will break Chat. I actually considered flashing from XAA to TMB just to get this feature but I'm on Verizon and I figure the basebands won't match up.
I read (down a rabbit hole) somewhere that the July security patch enables support for Chat. The June update came out about a week before July, so here's hoping it won't be much longer till there's a July update for XAA
Click to expand...
Click to collapse
That's great to hear! I look forward to the patch. Yes, from the digging I did, chat features were not included in the XAA version, but they were working when I was using TMB before switching.
Update to ATH3 Available on phone still a U1 Bootloader.
For those that wish to download full firmware here is the link to it https://samfw.com/firmware/SM-A716U1/XAA/A716U1UEU1ATH3
allenjthomsen said:
Update to ATH3 Available on phone still a U1 Bootloader.
Click to expand...
Click to collapse
Wow, build date was only 2 weeks prior to release. Recently came from a Moto Z4 where we were lucky to have 6 month old security updates.
Unfortunately still can't get the chat feature working; maybe it'll take some time to register the update.
C.tig45 said:
Thanks for this guide!
Worked great for me. I was reluctant because your notes said wifi calling wouldn't work, but it is in fact working for me. No stupid pink t-mobile startup when i turn on/off my phone.
Only thing I noticed that isn't working is chat features in Samsung Messages. It works for Google messages so I switched to that for now, but it's a shame because like the ONEui interface.
Click to expand...
Click to collapse
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
If its like previous Samsung phones, you'll need to be on the carrier specific firmware to run the unlock. Once unlocked you can flash back to the unbranded/unlocked firmware.
Anyone tired these firmwares with AT&T
so there is no unlocked version firmware for bootloader V2 right now?
Is anyone else able to access the firmware file on the link? It mentions something about the download under construction.
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
No unlock needed
foamhead said:
If I unlock the bootloader, can I Edit the Access Points or APN Settings ?
Click to expand...
Click to collapse
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Rwmega said:
You don't need to unlock bootloader, you will not be able to delete the default but you can add another apn. I (on att) added nxtgen apn to get faster cell speeds.
Click to expand...
Click to collapse
Thanks for the reply. I added another APN. Your right cant delete the defaults ones. Im with sprint was trying to do the ,dun to get my hotspot to work. I have it on 3 other phones.
I have a Sprint version.
If I flash the T-Mobile software will it open up all of the T mobile bands?
It could already have them, but have not been able to find specific s on the bands on the sprint version of the phone to see.
Phone looks to be manufactured before the merger?
whatsitsnamenow said:
Can you still access "network unlock" (device sim unlock) with the "unlocked firmware"?
This is my only concern as I haven't sim unlock the phone yet and these T-Mobile phones requires that app to unlock the sim.
Click to expand...
Click to collapse
I haven't sim unlocked the phone yet since it's not paid off so couldn't tell u if I can still access that feature.
Disclaimer: So its not a stolen phone, prior owner was just being nasty. I bought the phone from a 2nd hand shop (Cash Crusaders, Kathu, South Africa), where they told me that a lady sold the phone to them, came back after 3 months and wanted to buy it back for the same price (they guarantee buybacks for 1 month), they refused to sell it back to her at selling price, so she went and had the phone blocked. They went through the process of unbricking it through the ISPs, but in the meantime also got repair shops to try and fix it... They changed the IMEI number... So I bought the phone, fully functional, did a factory reset, saw that it had OEM unlocked and figured it was the cause for the biometrics not working, turned that on and thats where my mission started. OEM locked, custom firmware detected... Used Odin to flash on stock firmware (from Frija), got the phone functional, but emergency calls only and no cellular. I have tried rooting and using console, I have tried changing it in the EFS file, I have tried changing it via ADB Fastboot, via dialer (does nothing even with Google Dialer Framework V5)) no dice, it keeps the incorrect IMEI. I have looked up the IMEI on IMEI.info and its clean, so I take it they managed to get it unblacklisted, which is why I want to get the original IMEI back.
What I would like help with is does anyone know how exactly I can change the IMEI number on my phone (Rooted with Magisk and TWRP, but eXposed framework is finnicky and doesnt register properly, even through I installed the RIRU (V23) and RIRU EdXposed (Canary, both Sandhook and YAHFA on seperate occasions) packages via Magisk (V21.1 and V8.0.3 for manager) as per instructions.
P.S. I am a student on a tight budget, so I would prefer to do it on the cheap/free and I live in Namibia, so sending it to Samsung isnt quite an option.
Also please let me know if there is any info, logs, etc. I can attach that might help.
Koonus said:
I suppose it was stolen
Click to expand...
Click to collapse
I have my receipt and they have theirs. So by all means verify the IMEI yourself 356630093456642.
There Are some leaks at "g-works..." To Get into a phone that is reported as lost.
Tekodrink said:
There Are some leaks at "g-works..." To Get into a phone that is reported as lost.
Click to expand...
Click to collapse
Thing is phone got cleared. Original IMEI is clean, which is why I wanna reset it back to it, only problem is they seem to have used a flash-kit to change it in the recovery partitions too (bricked the damn thing when I recovered it (accidentally turned OEM lock on...), I've tried everything down to loading the engineering combination file (interesting though, its android 8.1, which shouldn't actually be possible to do from Android 10) on it and trying through there, no dice. Also asked local repair shops if any of them have a flash kit, none have 1... So I'm stuck at this point, cant even do the normal 'pay a repair shop to fix it for you' method.