I bought one of these phones from Gearbest, and it's running the "modded" RETCN firmware and it's the XT1635-3 hardware. It came with the bootloader unlocked, but I'd like to restore my phone to RETCA firmware, 6.0.1 and then unlock my own bootloader, root, etc...
The RETCA firmware I'd be using is from the XT1635-2 release, specifically:
XT1635-02_ADDISON_RETCA_MPN24.104-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I'm wondering, if I flash the bootloader.img from the RETCA package will I run into any troubles? Is this going to brick my phone (assuming the usual risk that flashing brings to bricking ones phone)?
akaleshnikov said:
I bought one of these phones from Gearbest, and it's running the "modded" RETCN firmware and it's the XT1635-3 hardware. It came with the bootloader unlocked, but I'd like to restore my phone to RETCA firmware, 6.0.1 and then unlock my own bootloader, root, etc...
The RETCA firmware I'd be using is from the XT1635-2 release, specifically:
XT1635-02_ADDISON_RETCA_MPN24.104-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I'm wondering, if I flash the bootloader.img from the RETCA package will I run into any troubles? Is this going to brick my phone (assuming the usual risk that flashing brings to bricking ones phone)?
Click to expand...
Click to collapse
It shouldn't, just don't flash -02 modem files.
catsruul said:
It shouldn't, just don't flash -02 modem files.
Click to expand...
Click to collapse
Why not? I've already done it and it seems to be working fine.
akaleshnikov said:
Why not? I've already done it and it seems to be working fine.
Click to expand...
Click to collapse
Great. I'm just going off what I've read from other users' experiences here. I would have gotten a GearBest MZP had I not snagged an Open Box -02 for $260 off of eBay.
catsruul said:
Great. I'm just going off what I've read from other users' experiences here. I would have gotten a GearBest MZP had I not snagged an Open Box -02 for $260 off of eBay.
Click to expand...
Click to collapse
I couldn't ignore the Gearbest price, $245 for a brand new white 64GB? Sign me up.
I don't like the white, but the discount swayed me.
akaleshnikov said:
I couldn't ignore the Gearbest price, $245 for a brand new white 64GB? Sign me up.
I don't like the white, but the discount swayed me.
Click to expand...
Click to collapse
Yeah it looked like a great deal. Didn't know about this otherwise I might have jumped ship.
Problem is, whether that actually works is iffy, and given that I'm in the US with T-Mo a single 800MHz LTE band isn't going to cut it- the XT1635-03 is missing a ton of bands needed for most US carriers.
akaleshnikov said:
I bought one of these phones from Gearbest, and it's running the "modded" RETCN firmware and it's the XT1635-3 hardware. It came with the bootloader unlocked, but I'd like to restore my phone to RETCA firmware, 6.0.1 and then unlock my own bootloader, root, etc...
The RETCA firmware I'd be using is from the XT1635-2 release, specifically:
XT1635-02_ADDISON_RETCA_MPN24.104-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I'm wondering, if I flash the bootloader.img from the RETCA package will I run into any troubles? Is this going to brick my phone (assuming the usual risk that flashing brings to bricking ones phone)?
Click to expand...
Click to collapse
If you install the Verizon version your device will update automatically
Related
I though that H815 was the european open version (able to unlock bootloader and such) and that the other versions had other names, but I've seen people about talking about H815 versions with the same name and with or without LTE-A, or even specific H815 versions for Asia, France or even non-carrier USA, and on all of them the bootloader is locked as ****.
Is this true? in this case, if you were buying this phone online, how to determine you're buying the european open version? what's the model name exactly for that?
Thanks!
I got mine from handtec.com. I made sure before purchasing that it was the H815 EU. That is what you are looking for. And as a note, I unlocked my boot loader 3 days ago so I know what they sell is the true EU version.
pre4speed said:
I got mine from handtec.com. I made sure before purchasing that it was the H815 EU. That is what you are looking for. And as a note, I unlocked my boot loader 3 days ago so I know what they sell is the true EU version.
Click to expand...
Click to collapse
I got my H815EU from handtec as well. Unlocked the bootloader the same day.
Only way I know of is to check settings under software version. For example mine shows V10C-TWN-XX.
scottjal said:
Only way I know of is to check settings under software version. For example mine shows V10C-TWN-XX.
Click to expand...
Click to collapse
So when do you think we will be able to unlock the bootloader?
Sent from my LG-H815 using Tapatalk
hermeez said:
So when do you think we will be able to unlock the bootloader?
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I'm also thinking the same thing here. ?
I have managed to root. But I need custom recovery just in case I need to back up etc
to see whether your model is unlockable - please see my post entitled [UNLOCK] list of LG G4 models that you can unlock
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
tuxdreamerx said:
Well this was a display model I guess, no specifics on what kind of store but its listed as being a Verizon model. So I may be SOL. As far as working on T-Mobile if that is the case are there any downsides to using the Verizon model aside from flashing?
Click to expand...
Click to collapse
Verizon model is fine for what the phone is.
You shouldn't have any issues using it on T-Mobile USA . Verizon phones are sim unlocked . The only thing with the Verizon version is that if it had the update where they don't let the bootloader unlock then you can't unlock it and root. Besides that you can use it on TMobile as a regular Google phone.
Sent from my Pixel XL using Tapatalk
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
This is partially false, I'm using a Verizon pixel XL on TMO and when I dropped out of beta, Google rolled out the TMO branch to my phone.
If you can depixl8 it and unlock the bootloader, you can flash custom Roms or the factory images to your heart's desire with no issues. Just never relock the bootloader, since it won't be able to be unlocked again(if it truly is a Verizon pixel XL)
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
You can sideload updates to a locked device so OP could sideload a current ota from tmobile. It can in fact beneficial to run the tmobile software on tmo because of optimizations for network connectivity
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
STraver said:
I have a BL unlocked, Verizon rooted Pixel XL. Can I put an ATT sim card in it and use it on the ATT network? Would I need to flash a different rom?
Click to expand...
Click to collapse
Should be able to just pop in the ATT sim
JimSmith94 said:
If you haven't updated it yet and its version is older than last November, you should be able to unlock the bootloader. Once it's been updated to a newer version, it can't be unlocked.
Click to expand...
Click to collapse
I guess that'll be the big question. If the phone was only a display model since it was released. I wonder if the display models get the updates pushed automatically... I will find out tomorrow.
Well the phone came with 7.1.2 so no fun for me. Thanks for the info from everyone.
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Grubling said:
I'm curious, have you tried unlocking the BL now that you can toggle OEM unlocking?
Click to expand...
Click to collapse
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
tuxdreamerx said:
I have not I will this evening or tomorrow though. I was just under the impression that all Verizon Editions had that switch disabled no matter what SIM card went it. As I stated before this was a display model, I got it for next to nothing due to very minor screen burn from the demo mode, I can barely see it so i'm good with what I paid. So I wonder if display models weren't Verizon models? Or maybe this was a third party Verizon store and not corporate. Either way is there anyway to tell which one it is? The SKU on the back is G-2PW2100-021-B and it has build number N2G47E on it, which is not the verizon build I don't think.
Click to expand...
Click to collapse
Google points to that being a Verizon SKU. But with the build number being non-Verizon, you might be able to unlock it.
There may be some relevant information here: https://forum.xda-developers.com/pixel/help/bootloader-unlock-verizon-pixels-t3616101
tuxdreamerx said:
Very interesting, I stuck a T-mobile SIM in it and I can now switch on OEM unlocking. It was greyed out before I put the SIM in.
Click to expand...
Click to collapse
Count your blessings, most of us with Verizon models are still locked on other carriers.
parakleet said:
Only thing that matters is if the origin of the phone is Verizon or Google.
If the origin is Google you can install the Google factory image and use it on anywhere, unlock the bootloader, root and have a grand old time.
If the origin is Verizon you are relegated to the Verizon image regardless of where you use the phone, no flashing for you.
Compare the build code of your phone to the build codes on google factory image website and you will know what you have.
good luck
Click to expand...
Click to collapse
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
zfk110 said:
Hi, I was about to buy Google Pixel XL off the eBay how can I tell if its Verizon phone or Google phone? I asked two sellers, they didn't know if it was Verizon on Google phone, they are just selling as Unlocked GSM , I never bought Google phone so I'm very new to it, per my understanding Verizon phones wont able to have unlock bootloaders? and Google phones will do? also Google phones can work with Verizon and GSM phones without any issues or they are only good with GSM?
you were saying something about build id to check
https://developers.google.com/android/images
I went to this webpage but I dont see any differences in model # for both ver?
Click to expand...
Click to collapse
You can unlock the bootloader on Verizon.
tuxdreamerx said:
So I just bought a Verizon Pixel XL off ebay with the intention of using it on T-Mobile because I was under the impression that taking it to T-Mobile was no issue and would be no different than using a google store one on T-Mobile. Although I am reading some concerning threads about the bootloader issue. If this phone happens to have 7.11 will I be unable to flash the T-Mobile factory image onto it? Or is there really no benefit in doing this anyway? Do I and will I be able to flash at least the T-Mobile radio over to it?
Then if it is before 7.11 and I unlock the bootloader right away can I keep it unlocked even if I play around with images and stuff such as trying out the O beta? or do I have to avoid Factory images once its unlocked and only use custom roms?
Thanks in advanced!
Click to expand...
Click to collapse
I literally just did this 2 months ago. Got a pixel xl and it was a verizon phone but I have Tmobile. The phone can be unlocked, it can be rooted, it can be rommed, yes it can! Mine came with 711 or 712 cant remember but whatever doesnt matter. Just follow the guide in the other thread by @Homeboy76, it's a GREAT read and tutorial. It will put you from stock nougat to stock pie, but afterwards you can go to nougat, oreo, or pie. I know because after I did it, i went to an custom rom, then to a custom oreo rom, back to stock pie, back to custom pie lol. I would put a link up to the thread but idk how to do hyperlinks lmao, i skipped that day of school.
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
No, bootloaders are different, with the S7 there was an unbranded U firmware that was compatible with most of them, unlocked firmware will be that one for the S9, but no you cannot just flash different device firmwares to the wrong model
I was able to flash the ATT rom onto my Verizon S9. I got a VZ s9 from work but I'm on ATT. For the most part it's worked great, I had done the same thing previously with a Galaxy S7. I say for the most part b/c I am on here tonight to post a question myself about the fact that I'm getting a delay with MMS messages. I imagine it has something to do with the APNs I have setup, but I can't seem to figure it out.
toronado13 said:
I was able to flash the ATT rom onto my Verizon S9. I got a VZ s9 from work but I'm on ATT. For the most part it's worked great, I had done the same thing previously with a Galaxy S7. I say for the most part b/c I am on here tonight to post a question myself about the fact that I'm getting a delay with MMS messages. I imagine it has something to do with the APNs I have setup, but I can't seem to figure it out.
Click to expand...
Click to collapse
Did you have to flash to the U1 software first?
I do think that is what I ended up doing... tried to go directly first and it kept failing. Got fed up and decided to just try and put the bone stock rom on it, and that went on really easily.... so after using it like that a few days I tried to drop the ATT rom on it and it worked without issue.
SEALBoy said:
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
Click to expand...
Click to collapse
Yes, but you need to go to the u1 firmware 1st then to the other carrier firmware. Also make sure you avoid the newer firmwares with the new bootloader, as the unlocked model and certain carrier models don't have the new bootloader.
*Detection* said:
No, bootloaders are different, with the S7 there was an unbranded U firmware that was compatible with most of them, unlocked firmware will be that one for the S9, but no you cannot just flash different device firmwares to the wrong model
Click to expand...
Click to collapse
lolol
yes u can.. u can flash between U and U1 firmwares no problem..
normally ud b correct tho but since s8/s8+ it has been ok.. just cant flash 9600 or 9650 to a U or U1 device
elliwigy said:
lolol
yes u can.. u can flash between U and U1 firmwares no problem..
normally ud b correct tho but since s8/s8+ it has been ok.. just cant flash 9600 or 9650 to a U or U1 device
Click to expand...
Click to collapse
That'll be why I still thought that then, coming straight from the S7 > S9
Had many members flashing the wrong firmwares thinking they could do that and bricking their S7s / wondering why ODIN failed
*Detection* said:
That'll be why I still thought that then, coming straight from the S7 > S9
Had many members flashing the wrong firmwares thinking they could do that and bricking their S7s / wondering why ODIN failed
Click to expand...
Click to collapse
I tried downloading vzw firmware G960USQS3ARI6 to my unlocked sprint s9 and still not vzw flashed. want to do this so can have voice over LTE. Any other steps im missing? flash went through but still sprint
As soon as Firmware ver. 3 came out for the G960U1, I was able to flash it to my Sprint G960U and finally have VoLTE, WiFi calling and stable LTE for MetroPCS. Used samkey to unlock it from Sprint. My phone is actually performing much faster without all of Sprint's bloatware hogging my RAM and storage space. I can confirm that OTA updates still work the same...I received September's security patch (current) with no problems. Device is still official status and Knox hasn't been tripped.
A lot of people think you can just flash the carrier firmware of your choice and boom, it works...I had the same thought process....that's not the case. You have to make sure that there is a matching firmware version for the carrier you want to flash to, as well as make sure the G960U1 firmware version (the unlocked version of the S9's software you have to flash first before even carrier flashing) is the same version of what is installed on your phone now. It's easy ya'll......just READ lol.
I'm in love with my phone again thanks to XDA. ?
HAPPY FLASHING!
nickosarus2008 said:
As soon as Firmware ver. 3 came out for the G960U1, I was able to flash it to my Sprint G960U and finally have VoLTE, WiFi calling and stable LTE for MetroPCS. Used samkey to unlock it from Sprint. My phone is actually performing much faster without all of Sprint's bloatware hogging my RAM and storage space. I can confirm that OTA updates still work the same...I received September's security patch (current) with no problems. Device is still official status and Knox hasn't been tripped.
A lot of people think you can just flash the carrier firmware of your choice and boom, it works...I had the same thought process....that's not the case. You have to make sure that there is a matching firmware version for the carrier you want to flash to, as well as make sure the G960U1 firmware version (the unlocked version of the S9's software you have to flash first before even carrier flashing) is the same version of what is installed on your phone now. It's easy ya'll......just READ lol.
I'm in love with my phone again thanks to XDA.
HAPPY FLASHING!
Click to expand...
Click to collapse
Hi, I got one unlocked G960U1(G960U1UES3ARI1) and downloaded new fireware(G960U1UES3ARI1-SPR) from sammobile, but after flashed SPR ROM successfully, the info on the phone still shows XAA, anything I missed here? Thanks!
Curtis2018 said:
Hi, I got one unlocked G960U1(G960U1UES3ARI1) and downloaded new fireware(G960U1UES3ARI1-SPR) from sammobile, but after flashed SPR ROM successfully, the info on the phone still shows XAA, anything I missed here? Thanks!
Click to expand...
Click to collapse
Well first off, you have the unlocked phone. I don't. My G960U is originally from Sprint, so I'm not sure about carrier flashing regarding the G960U1. I thought it was supposed to provision itself after you put the sim in, and the associated carrier apps will download since it's the unlocked model...but I may be wrong...
SEALBoy said:
I've read that the Galaxy S9 hardware is identical for all carriers in the USA.
If I bought a factory unlocked Galaxy S9 can I flash it to the carrier I am using (Verizon, Sprint, T-Mobile, AT&T) to enable carrier specific software and features? Can I flash it back to the unlocked firmware?
I already see a thread about flashing the unlocked firmware to carrier models so I am assuming there are no issues there.
Can one carrier model be flashed to another carrier model?
Click to expand...
Click to collapse
I know so many people have already answered your question from some saying No to others saying Yes but you need to Install U1 first and Bla Bla Bla.
I want to give you one specific answer: With S9 you can any Carriers firmware you wish or even Unlocked phone's firmware. You will never have any issue. And you don't ever need to flash U1 or something else before changing carrier firmware you can Flash from ATT S9 firmware to VZW S9 firmware without any issue. You can also flash from U to U1 which is from Carrier specific to Unbranded/Unlocked but only hiccup is original Odin will give you SHA-256 error, which is normal because you are flashing U1 firm to U device or vice versa. This error can easily be resolved by used Patched odin that disabled SHA-256 check. And trust me you will never have any issue.
You will never want to do this but I have gone as far as mix-matching U and U1 firmware together as well. Like flashing AP, BL and CP of U device but flashing CSC of U1 device. and it still works.
hey there, a little late to the party, having trouble with going from a Verizon to a Sprint, even by way of U1. I can't get any of them to work. And I've been told I have to go from VZW to U1 before I went to Sprint. Is that not the case? I'm having a hell of a time getting anything to flash, everything fails.
---------- Post added at 03:08 AM ---------- Previous post was at 02:57 AM ----------
ret4425 said:
hey there, a little late to the party, having trouble with going from a Verizon to a Sprint, even by way of U1. I can't get any of them to work. And I've been told I have to go from VZW to U1 before I went to Sprint. Is that not the case? I'm having a hell of a time getting anything to flash, everything fails.
Click to expand...
Click to collapse
well, I tried to load the Sprint image from the VZW, no dice. It said it passed, but upon reboot loaded up the old Big Red (even with the Sprint SIM in it).
Anyone have any ideas? This is driving me insane....
I have AT&T Pixel 6 Pro which is SIM unlocked and I have already unlocked the bootloader. Can I flash unlocked Pixel 6 pro firmware (factory image) on it instead of AT&T factory images?
There are different carrier specific firmwares released for a reason
miravision said:
There are different carrier specific firmwares released for a reason
Click to expand...
Click to collapse
What happens if we flash unlocked? I know there could be a reason, but could we possibly brick if we flash unlocked on AT&T?
ram4ufriends said:
What happens if we flash unlocked? I know there could be a reason, but could we possibly brick if we flash unlocked on AT&T?
Click to expand...
Click to collapse
There are only two versions of the latest firmware. Verizon, and non-Verizon. So yes, you should be able to flash the non-Verizon firmware fine. Probably no different from what you're on unless you haven't received the OTA to SD1A.210817.036 yet.
Even those with unlocked phones running on the Verizon network are fine to flash either version. Eventually, there will be only one firmware per month, just like they have for other Pixels.
I could probably flash my unlocked phone that I'm using on AT&T with the Verizon firmware and it would probably still be okay.
If you brick your phone, it's not because of which Raven (P6P) firmware you flash.
Hi, noob here.
In the process of rooting my Motorola E (2020) XT2052-1, i need to get the stock rom variant for my phone (unless a degoogled custom rom without issues exists - im doing this to remove google). Following these instructions:
https://forum.xda-developers.com/t/stock-rom-how-to-root-the-snapdragon-moto-e-2020.4195453/
My build is QPGS30.82-135-7 (US Cellular.).
I need to find my variant on lolinet but i cant find an exact match. What needs to be matched?
1) Can i use a higher version variant? Mine is -7 and on lolinet its -13:
XT2052-1_GINNA_USC_10_QPGS30.82-135-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC
2) can i use the retail version? I assume so, there shouldn't be hardware differences? This one is -7 like my build.
XT2052-1_GINNA_RETUS_10_QPGS30.82-135-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Thanks!
Yes, that update is correct, it is just one update ahead of what you had. You can also install retail firmware as long as you keep your bootloader unlocked.
fddm said:
Yes, that update is correct, it is just one update ahead of what you had. You can also install retail firmware as long as you keep your bootloader unlocked.
Click to expand...
Click to collapse
Thanks! Can you suggest what i should read up on (search keywords), to understand why the retail should keep the bootloader unlocked while the USC variant doesn't require it?
Each variant has a public key securely embedded, and the accompanying bootloader is signed by a private key. Only a retail device has the key to verify the retail bootloader, and there is a chain of trust past that to ensure system integrity.
fddm said:
Each variant has a public key securely embedded, and the accompanying bootloader is signed by a private key. Only a retail device has the key to verify the retail bootloader, and there is a chain of trust past that to ensure system integrity.
Click to expand...
Click to collapse
Apart from this, the US Cellular logo i've seen on boot, and possibly channel specific apps, are there other differences i should be aware of that guide my choice of the USC vs retail variants?
I'm leaning towards the USC variant if it has the advantage of being able to relock and the retail's is simply not having the logo.
Retail will not come with carrier apps and branding, and includes "full" gapps(carrier variants might exclude or swap certain gapps like the dialer for inhouse Motorola forks).