Hello all -
New to Android platform. Hope someone from this great forum can assist ... I'll try to be brief. First, my device:
Razr HD LTE xt925
FIDO
Android v.4.1.2
Had attempted a little while ago to unroot my phone, as I was curious about better customization options. For various reasons, I tried to 're-root' and go back to factory. Did that, upgraded from ICS Jellybean 4.1.2 (which is what my phone was on when purchased).
Now, when I boot the phone, I still get the message 'Bootloader is unlocked'. After upgrading from ICS to Jellybean, I saw a large number of Verizon specific apps. When booting the phone, instead of the Motorolla 'M' icon/splash, I get a 'Droid' icon, with sound-effects. Also, System Version shows as 9.16.XT926.Verizone.en.US (even though my phone is an XT925 on FIDO). I obviously fudged something up... !
Most importantly, ever since, my GPS is very spotty, and I cannot get on the FIDO LTE network. In Mobile Networks setting, I have to always have 'Global' selected as network. If I choose LTE/CDMA or GSM/UMTS, it can never find an available network.
I'm really just trying to get my phone back to the state is was when I purchased it.
Any ideas would be GREATLY appreciated!
Canlin said:
Hello all -
New to Android platform. Hope someone from this great forum can assist ... I'll try to be brief. First, my device:
Razr HD LTE xt925
FIDO
Android v.4.1.2
Had attempted a little while ago to unroot my phone, as I was curious about better customization options. For various reasons, I tried to 're-root' and go back to factory. Did that, upgraded from ICS Jellybean 4.1.2 (which is what my phone was on when purchased).
Now, when I boot the phone, I still get the message 'Bootloader is unlocked'. After upgrading from ICS to Jellybean, I saw a large number of Verizon specific apps. When booting the phone, instead of the Motorolla 'M' icon/splash, I get a 'Droid' icon, with sound-effects. Also, System Version shows as 9.16.XT926.Verizone.en.US (even though my phone is an XT925 on FIDO). I obviously fudged something up... !
Most importantly, ever since, my GPS is very spotty, and I cannot get on the FIDO LTE network. In Mobile Networks setting, I have to always have 'Global' selected as network. If I choose LTE/CDMA or GSM/UMTS, it can never find an available network.
I'm really just trying to get my phone back to the state is was when I purchased it.
Any ideas would be GREATLY appreciated!
Click to expand...
Click to collapse
Here's the JB file for Fido/Rogers:
http://sbf.droid-developers.org/van...12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
Thanks very much for your reply. I did try flashing with the FIDO file you quoted, and my phone didn't take it. I booted to fastboot, current drivers, and the RSD Lite message I got was:
Failed flashing process. 1/21 flash partition "partition_signed" -> Phone returned FAIL
The corresponding message on my phone was: Failed flashing process. 1/21 flash partition "partition_signed" -> Phone returned FAIL
Hope someone has an idea on how to successfully get back to the FIDO Android v.4.1.2.
Thank you all!
Have you removed the Getvar lines? You can also try the Telcel rom with Fido modem/fsg files placed into it. (That's what I had before custom roms because Fido was slow with JB).
Yes, I did try when removing getvar line in the xml.
I stated erroneously the error on my phone after trying the intitial FIDO flash - the phone error in fact was:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I appreciate the input. Any other thoughts on this? I regret trying to unroot the damned thing in the first place... !
Canlin said:
Yes, I did try when removing getvar line in the xml.
I stated erroneously the error on my phone after trying the intitial FIDO flash - the phone error in fact was:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I appreciate the input. Any other thoughts on this? I regret trying to unroot the damned thing in the first place... !
Click to expand...
Click to collapse
From what I can see, those errors come when trying to downgrade to ICS through RSD but you are trying to install JB so that makes no sense. Since you are bootloader unlocked you can probably flash the files through fastboot?
no worries man...calm down...you'll be fine...i had the same issue..i'm actually using an xt925 as well; had the same issue a couple of days back...see the issue is the ROMs that you see for xt925/926 is actually the ROM for verizon, so when you flashed a custom ROM, it actually flashed your GSM radio to the version radio, which is CDMA; These are the steps you need to follow, and you're good to go, trust me:
1). After deleting the getvar line, delete 2 lines below it as well, so lines 12 and 13, then try flashing with this new xml file. really imp, this will take about 5-10 mins, then the phone will reboot, dont unplug the cable yet, it's gonna reboot, and ask to sync phone with SIM, do that....and you're good to go.
2). Root.
3). Install TWRP, preferably 2.5, then backup your stockROM.
4). I would recommend using Matt's utility for xt926, and you can perform all the steps in sequence.
note: Since you unlocked your bootloader, you will always get that warning message, it's normal.
lemme know if it works!
eomahos I am in your debt. Worked like a charm!
In step 4 you indicated using 'Matt's utility for xt926' ... I'm not familiar with the utility. Do I use this to install TWRP?
Thanks again man!
Good Afternoon everyone
I'm of average knowledge and have had an issue that im hoping you kind people can assist with. I will happily add more details if necessary but I'll try and keep it simple and clear for now for my current sitation and what I'm looking to do.
I've been happily using AOKP on my XT925 for a few months now and updating it every now and again. After an infinite bootloop issue last night, I was kind of buggered but after toing and froing I got into Fastboot. After not much and desperate to attempt was working I used Mr Parkinsons 2.0 tool, and with it listing flashing to stock XT925 / XT926 as its option 1, I clicked that. Successfully it flashed it with the package it uses and booted fine. I have functionality, on the phone settings strangely its now listing as XT926 but again it works HOWEVER unbeknowst (probably stupidly) to me its a VZW American default and naturally won't recognise my SIM and I can't make calls.
I'm currently trying to flash it again through Fastboot with RSD Lite 6.15 to a Stock Xt925 Firmware, ones I acquired through the thread in the XDA Dev. I'm based in the UK and my SIM / Network provider is O2. The nearest fit Firmware wise seems to be the Orange UK package or the Vodafone France ones.
The Orange UK package won't decompress in RSD as it's saying 'the filename may be too long'. The Vodafone France one will decompress - however originally it said 'unknown flashboot command - flash failed' (getvar). Having done some reading I deleted the sole line 'Getvar' string in the XML through notepad, saved it and tried again. This time is said something along the lines of 'Flash failed 2/22 - phone returned'. I've tried Googling this error and all the forums that mention it seem to be in Spanish or French.
I'm tired and it's been a long day for family issues - however I could do with having my phone back on an even keel. Please can someone help or at least point me in the right direction? I'd be very VERY grateful for any dialogue.
SHORT VERSION OF PROBLEM: Currently running the Stock Recovery Package included in Mr Parkinsons 2.0 utility. Phone is functional bar not recognising my SIM and Im in the UK on O2 and it's US centric. Concerned that in phone settings it says XT926. Recovery and fastboot options available. RSD Lite is returning primarily saying 'flash failed 2/22'
Are there any other utilities to recommend that would get me where I want to be other than RSD?
Please go easy on me! If I've not explained myself very well then and someone may know the answer then I'm happy to be more descriptive in terms of details
Additional details:
- On startup its saying 'SIM is from unrecognised source
- My current system version is 9.16.6.XT926.Verizon.en.US / Baseband: VANQUISH_BP_100730.081.64.09P
After some playing I resolved this.
In terms of anyone who should be faced with this issue, the answer lies in deleting more of the .xml file in your zip that your flashing via RSD
I browse this forum every now and again so reply if you need assitance and need me to be more specific, otherwise mods can lock this as closed.
I had to switch phones this week and have an old Razr HD Maxx - XT926.
I bought from ebay and never really used it before - it has bootloader unlocked, rooted and running Pacman 4.4 ROM.
Anyway I live in Ireland can can't get my SIM recognised.
It get the error No signal!! your sim does not allow a connection to this network or unfortunately the process com.android.phone has stopped
Reading through the forum i see there are know issues with the XT926 users that are outside the US, use SIM cards and Custom ROMS.
What is the quickest way to get my phone actually to work as a phone
I think i can flash back to Stock?
Can i flash a XT925 ROM without bricking?
Is there a Custom ROM i can use that does not have this GSM issue -Currently have teh JB Bootloader so ideally a ROM compatible with that?
Build.prop attached.
I tried this patch http://forum.xda-developers.com/showthread.php?t=2394689
But get the message This not seem to be a Verizon Phone
Any help is much appreciated.
The quickest way to get your phone working would probably be to download "DROID RAZR HD XT926 Utility 1.4 KK" found in this thread: http://forum.xda-developers.com/showthread.php?t=2474393
Make sure to read the instruction while you charge your phone's battery to 100% before flashing. I assume that you've already done something like this?: http://firstandgeek.com/solved-unfortunately-process-com-android-phone-stopped/
And yup, this is stock firmware.
I am using XT926 in Europe as well, and there's a few thing you should do with the stock Verizon firmware:
1) Get root
2) Disable the annoying "Sim card is from an unknown source" ("VzwPhoneService.apk")
3) Download Titanium Backup and freeze all VZW apps and unnecessary services.
4) Wireless Hotspot hack
OR.........
You could download CM12 Lollipop, but this will probably take more time than the previous option.
@sd_shadow
Went to the Verizon store to get my droid unlocked only to have the tech people there input different codes that did not work and the security feature unexplained. I went to try the sim and within a few tries it was locked.
Tech support has given me the sim network code that goes with the phone now that it is subsidy locked. I have looked at the steps on Sd Shadow's site about flashing and rooting the phone and have gone so far as to download and install the motorola drivers (signed by microsoft?). The device now shows in device manager as an ADA interface.
I have tried flashing with rsd lite, only to hear several sounds as if the device is reconnecting and see flash failure at 6/18 partition.
Am I using an incomplete .Xml?
The Fast boot version is 0A.53 and the xml downloaded from http...........://......................motofirmware.center/files/ was
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
Haven't seen anyone trying to unblock for use with Pure Talkusa. I don't know if it makes any difference what third-party carrier i decide to go with.
I have used three different cords for the flashing, one of them does not "wiggle" in the ports like the others, but it is an older cord.
I am using Windows 7
Shakbazian said:
Went to the Verizon store to get my droid unlocked only to have the tech people there input different codes that did not work and the security feature unexplained. I went to try the sim and within a few tries it was locked.
Tech support has given me the sim network code that goes with the phone now that it is subsidy locked. I have looked at the steps on Sd Shadow's site about flashing and rooting the phone and have gone so far as to download and install the motorola drivers (signed by microsoft?). The device now shows in device manager as an ADA interface.
I have tried flashing with rsd lite, only to hear several sounds as if the device is reconnecting and see flash failure at 6/18 partition.
Am I using an incomplete .Xml?
The Fast boot version is 0A.53 and the xml downloaded from http...........://......................motofirmware.center/files/ was
VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml.zip
Haven't seen anyone trying to unblock for use with Pure Talkusa. I don't know if it makes any difference what third-party carrier i decide to go with.
I have used three different cords for the flashing, one of them does not "wiggle" in the ports like the others, but it is an older cord.
I am using Windows 7
Click to expand...
Click to collapse
The member you mentioned (sd_shadow) has replied to you in his thread
http://forum.xda-developers.com/showpost.php?p=64183133&postcount=2
Post further questions and discussions in that thread to get further help (that is the correct section to post)
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