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 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!)
I'm about ready to throw this phone out the window, and hoping someone here can help me out...
My wife ordered a never used g955u off of ebay. It came with Oreo installed. It had the CRE9 firmware installed. We are on Page Plus (Verizon reseller). We put in her SIM card, went through setup, but we are not able to make phone calls. The SIM card works fine on her old phone. I reset the network settings to no avail.
I did a network search and selected Verizon Wireless, but it times out and gives the error :
No Service
Selected network (Verizon Wireless) not available
I talked to Page Plus, and everything looks fine on their end, they say it's something in the phone.
I suspect it's something in the radio settings, but I'm locked out of the service menu. I factory reset the phone, and that didn't fix it either.
I've been down several rabbit holes since then.
I tried to follow the steps in this thread: https://forum.xda-developers.com/galaxy-s8+/how-to/carrier-switch-snapdragon-t3615680 hoping that if they can make non-verizon phones work on verizon, then it can make a verizon phone work on verizon. I also tried to root the phone using this thread: https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 hoping to get access to the service menu.
But evertime I tried to flash any of the necessary binaries, I got Fail! (auth) and the phone gave the error:
sw rev check fail : [boot]Fused 3 > Binary 1
or
sw rev check fail : [boot]Fused 2 > Binary 1
Turns out, you can't downgrade. And all the binaries in the tutorials are now downgrades.
Somehow in all this, I managed to flash the phone to CRD4. I tried flashing back to CRE9, but regular Odin fails without telling me what the error is, and Comsy Odin gives a model dismatch fail.
I tried connecting the phone to Kies, but it gives me the error "only the device owner can connect to kies" even though I'm running Kies as administrator.
I've ordered a new SIM card from PP, just in case that fixes it, but I'm losing hope here. If anyone can help me out here, I'd really appreciate it. If there's anymore information you need, let me know and I'll post it.
garlicfiend said:
I'm about ready to throw this phone out the window, and hoping someone here can help me out...
My wife ordered a never used g955u off of ebay. It came with Oreo installed. It had the CRE9 firmware installed. We are on Page Plus (Verizon reseller). We put in her SIM card, went through setup, but we are not able to make phone calls. The SIM card works fine on her old phone. I reset the network settings to no avail.
I did a network search and selected Verizon Wireless, but it times out and gives the error :
No Service
Selected network (Verizon Wireless) not available
I talked to Page Plus, and everything looks fine on their end, they say it's something in the phone.
I suspect it's something in the radio settings, but I'm locked out of the service menu. I factory reset the phone, and that didn't fix it either.
I've been down several rabbit holes since then.
I tried to follow the steps in this thread: https://forum.xda-developers.com/galaxy-s8+/how-to/carrier-switch-snapdragon-t3615680 hoping that if they can make non-verizon phones work on verizon, then it can make a verizon phone work on verizon. I also tried to root the phone using this thread: https://forum.xda-developers.com/ga...root-g955u-g955u1-snapdragon-sampwnd-t3658911 hoping to get access to the service menu.
But evertime I tried to flash any of the necessary binaries, I got Fail! (auth) and the phone gave the error:
sw rev check fail : [boot]Fused 3 > Binary 1
or
sw rev check fail : [boot]Fused 2 > Binary 1
Turns out, you can't downgrade. And all the binaries in the tutorials are now downgrades.
Somehow in all this, I managed to flash the phone to CRD4. I tried flashing back to CRE9, but regular Odin fails without telling me what the error is, and Comsy Odin gives a model dismatch fail.
I tried connecting the phone to Kies, but it gives me the error "only the device owner can connect to kies" even though I'm running Kies as administrator.
I've ordered a new SIM card from PP, just in case that fixes it, but I'm losing hope here. If anyone can help me out here, I'd really appreciate it. If there's anymore information you need, let me know and I'll post it.
Click to expand...
Click to collapse
fused binarys usually mean you are flashing older firmware than whats on device,Anti rollback
TheMadScientist said:
fused binarys usually mean you are flashing older firmware than whats on device,Anti rollback
Click to expand...
Click to collapse
Yeah, that's what I had figured out. I'm still not sure what direction I need to go in to find a fix for this.
garlicfiend said:
Yeah, that's what I had figured out. I'm still not sure what direction I need to go in to find a fix for this.
Click to expand...
Click to collapse
So I know Odin 3.13 at least. But other than that with Oreo I don't know
I wanted to stop by and mention I am having nearly the identical issues. I bought a used Verizon Galaxy S8 from somebody today, and even ensured that the IMEI was supported by Page Plus beforehand. I tried using an existing, working SIM card of mine from Page Plus but found that it did not work automatically as it should have. After going through four customer service representatives, I was told that my phone is somehow not compatible. Still, I think I may have a slightly different situation going on... I was told it would not work because there is no "LTE/CDMA" option in the "Network Mode" setting. Instead, upon inserting the existing SIM into the new phone, my Network Mode setting only has access to "LTE/3G/2G (auto connect)", "3G/2G (auto connect)", "3g Only", "2G Only" options.
When I put the SIM back into my working phone, it gives me the correct network options. For some reason, this new phone is not allowing me to connect to the Verizon network at all.
You've taken a lot more steps than I have... I figured it could be an issue with Android Oreo, but I am really not looking to delve into the degrading process. I will also order a new SIM and see if that magically fixes things, but it's starting to look like a lost cause.
Let me know if you figure something out - you are the ONLY person online I have found with my identical (or near identical) issues. If you happen to know any way around the exact issue I'm having with the Network Mode, that would be insanely cool.
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