I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)
From what I can see, Windtre is a specific carrier. I would go with The standard version for unlocked phones. If that's wrong then the process should abort itself before making any changes
The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.
azthemansays said:
I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)
Click to expand...
Click to collapse
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.
motolio said:
From what I can see, Windtre is a specific French Canadian carrier.
Click to expand...
Click to collapse
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
motolio said:
Italian Canadian
Click to expand...
Click to collapse
That's a new one.
mike.s said:
The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.
Click to expand...
Click to collapse
motolio said:
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.
Click to expand...
Click to collapse
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.
Dude, I would not start with the Windtre one. Sounds like it could just be a striped down/limited version. It looks like that rom might specifically limit access to specific bands that Windtre doesn't allow their customers to access.
I found this on Reddit about the pixel 7:
Google "even limited the band bandwidth on NR, like 20mhz for N3
It isn't a huge problem, unless some operator add/remove bandwidth on a certain NR band
This is the case with WINDTRE (Italy, 222-88): they recently added 20mhz to their N78 spectrum (before it was max 40mhz on some regions, others 20mhz, now every region is 60mhz) and now you can't use their N78 at all
Why?
Because on their carrier policy, WindTre SIMs can use only 40mhz, 20mhz and 40+20mhz on N78 (last case is NR CA, not 60mhz)
It's really great to have a 900€ phone (Pixel 7 Pro) that can't connect to N78 thanks to Google "
Good luck. Let us know how it goes!
mike.s said:
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
That's a new one.
Click to expand...
Click to collapse
Lol. Word
azthemansays said:
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.
Click to expand...
Click to collapse
If you find a good back up process, lemme know. I need a good recovery option, too.
I did find this elaborate process on Reddit: I HAVE NEVER TRIED IT.
https://www.reddit.com/r/GooglePixel/comments/ovlnbj/_/h7akg6l
motolio said:
Good luck. Let us know how it goes!
Click to expand...
Click to collapse
You guys had me worried, and couldn't even get the phone to get the update notification (to check the version of the update).
But when I was looking at downloading the two versions on Google's ROM depository I noticed that you can directly update the phone through Chrome on my desktop???
Man, has tech changed since my last phone (Mi A1 on Oreo)...
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Gave up on backing up my phone, so I just exported/uploaded the settings for my launcher + AOSP mods + a couple of others then just went for it.
Thanks again for the assistance!
azthemansays said:
I noticed that you can directly update the phone through Chrome on my desktop???
Click to expand...
Click to collapse
Hope does this work? I've never encountered that option
motolio said:
Hope does this work? I've never encountered that option
Click to expand...
Click to collapse
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone
azthemansays said:
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone
Click to expand...
Click to collapse
Oh wow. Thanks! I had no idea about this. I'll give it a try next time I have time to phone out!
Thanks again
azthemansays said:
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Click to expand...
Click to collapse
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.
mike.s said:
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.
Click to expand...
Click to collapse
All I know is that I didn't get a warning, the global ROM's bands are working with my carrier's (Public Mobile - a subsidiary of Telus) after being flashed, and as you've stated Google hasn't been open with the differences... so I'm going to err on the side of caution (and international compatibility) and stick with what works.
I may revisit it if I travel inter-provincially and discover issues with coverage, but the US bands are what are compatible with what's used in Ontario.
Related
I am getting my Sony "U.S" Version just because of its warranty, is there a way i can Enable the fingerprint. Please help
currently all you could do is flash the International firmware. I haven't really looked into anything though personally. I'm not sure how they disabled it, maybe changing a 0 to 1 somewhere but I doubt it.
Yes I got the US version from Amazon and just flashed the CE1 firmware and fingerprint works after flashing that firmware
Sent from my G8142 using Tapatalk
Buy it from the UK. Same warranty. No need to flash anything. Save about $100.00
NO BRAINER!
jaseman said:
Buy it from the UK. Same warranty. No need to flash anything. Save about $100.00
NO BRAINER!
Click to expand...
Click to collapse
It doesn't have US warranty, probably you have to send it back to UK. Personally I don't care about warranties, never had to use for any of my many phones until now partly because don't keep the phone that long. The other advantage buying from Amazon US is ease of return in case you don't like the phone. If you played with it before and 100% sure you like the phone and will definitely keeping it, then yeah better to buy from clove and save the extra $150 or change.
kirdroid said:
Yes I got the US version from Amazon and just flashed the CE1 firmware and fingerprint works after flashing that firmware
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Can you post a simple guide to do this with some links on where to get all the tools firmware, flashy oil etc... Also I think there are some alternatives for the firmware such as the US and European version any differences between them?
samurayx89 said:
Can you post a simple guide to do this with some links on where to get all the tools firmware, flashy oil etc... Also I think there are some alternatives for the firmware such as the US and European version any differences between them?
Click to expand...
Click to collapse
I used the newflasher tool in the below link. Personally this is my first Xperia device in a long time and haven't used the Xperia flashing tools before.
https://forum.xda-developers.com/showthread.php?t=3619426
1. Make sure you have the right drivers installed. I installed Xperia companion tool since someone mentioned that should install all the drivers. I also installed the flash tool and fastboot drivers from Xperia flash tool since I had issues putting my phone in flash mode. If you are using Windows 10 you have disable verify driver signing in boot before installing the flash tool drivers.
2. Download the firmware of your choice, I chose CE1 (Central Europe) firmware over other Asian firmware.
3. Then follow the instructions in the thread to flash.
Main issue I had was putting my phone in flash mode. But apparently flash mode doesn't have any screen like recovery etc. You just have to turn off your phone then while holding the volume button down connect your phone via USB. That should put in flash mode even though you don't get any screen to say it's in flash mode.
Once I put in flash mode everything went fine by following instructions in the thread.
Thanks,
So when you downloaded the files with XperiFirm and used NewFlasher did you delete any of the files or just drop newflasher into the created directory and flashed everything.
samurayx89 said:
Thanks,
So when you downloaded the files with XperiFirm and used NewFlasher did you delete any of the files or just drop newflasher into the created directory and flashed everything.
Click to expand...
Click to collapse
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
kirdroid said:
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
Click to expand...
Click to collapse
Does Google Assistant work for you on the CE1 firmware? It's not popping up for me at all.
Yadiel2007 said:
Does Google Assistant work for you on the CE1 firmware? It's not popping up for me at all.
Click to expand...
Click to collapse
Yeah working fine no issues here (long press home button to bring up assistant) ... Even ok Google works fine as well when screen is on.
kirdroid said:
Just dropped all newflasher files into the created firmware directory and just ran the newflasher application from that directory. It flashed everything in there.
I know the thread says if you want you can remove specific things from the firmware directory if you don't want to flash certain things. But I didn't see any reason to do that and I never care about wiping my device since all my info is backed up in the cloud and takes around 30 minutes to restore and be up and running again. Just to be safe I flashed everything so that it doesn't screw up anything. I haven't used the Xperia flash tools before so kept it simple.
Click to expand...
Click to collapse
Do you still have Volte working after flashing the CE firmware?
tdgillihan said:
Do you still have Volte working after flashing the CE firmware?
Click to expand...
Click to collapse
Also curious about volte, I bought mine from Best Buy yesterday and it doesn't have Volte on T-Mobile in the us. I'm hoping flashing the CE firmware enables it.
HigherSensation said:
Also curious about volte, I bought mine from Best Buy yesterday and it doesn't have Volte on T-Mobile in the us. I'm hoping flashing the CE firmware enables it.
Click to expand...
Click to collapse
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
tdgillihan said:
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
Click to expand...
Click to collapse
I'm pretty sure it's the US model because the fingerprint sensor is disable.
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
tdgillihan said:
Hmmm, that's weird. My understanding was that it was enabled on the US version but not on the international. Are you sure you don't have it?
Click to expand...
Click to collapse
HigherSensation said:
I'm pretty sure it's the US model because the fingerprint sensor is disable.
Click to expand...
Click to collapse
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
Sorry, my bad, mixed up my forums. Comments deleted.
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
Must be an Branding/Software issue i guess.
On the unbranded EU version, both is available.
wifi calling: Settings -> Wireless&Networks -> Wi-Fi Calling
VoLTE: Settings -> Wireless&Networks -> Mobile Networks -> Enable VoLTE
Tuerkay said:
Must be an Branding/Software issue i guess.
On the unbranded EU version, both is available.
wifi calling: Settings -> Wireless&Networks -> Wi-Fi Calling
VoLTE: Settings -> Wireless&Networks -> Mobile Networks -> Enable VoLTE
Click to expand...
Click to collapse
Are you sure it has nothing to do with your service provider?
I bought mine from the UK (not sure if it is the same as the unbranded EU version you mention) and when I look for those same settings they do not exist.
I am in the US running on AT&T as an unlocked go phone customer.
afuller42 said:
there is no VOLTE on this phone, no menu options for advanced calling like wifi calling either.
Click to expand...
Click to collapse
jaseman said:
Are you sure it has nothing to do with your service provider?
I bought mine from the UK (not sure if it is the same as the unbranded EU version you mention) and when I look for those same settings they do not exist.
I am in the US running on AT&T as an unlocked go phone customer.
Click to expand...
Click to collapse
Could be that the settings are not available unless your carrier/plan supports them. Pretty sure anyone slipping a T Mobile sim in has those services.
Hello forum, sorry if the question i am going to ask is a bit noob. I have a mate 9 (MHA-L29C605B111 CUSTC605D111). The thing is i am getting annoyed by the notifications in numners not the icon. The thing is via FF i only find the MHA-L29BC605B111 CUSTC605D162. That cust is the same as a friend of mine which has the icons. My questions are:
1) Is there a command to enable the icons?
2) Is there any risk via FF to change from C605 to BC605 as is only OTA-MF?
3) Is this the correct way to change the CUSTID?
Thank you for every help you may give me as i am new in the huawei world!!:good::good:
The_Pacifier said:
Hello forum, sorry if the question i am going to ask is a bit noob. I have a mate 9 (MHA-L29C605B111 CUSTC605D111). The thing is i am getting annoyed by the notifications in numners not the icon. The thing is via FF i only find the MHA-L29BC605B111 CUSTC605D162. That cust is the same as a friend of mine which has the icons. My questions are:
1) Is there a command to enable the icons?
2) Is there any risk via FF to change from C605 to BC605 as is only OTA-MF?
3) Is this the correct way to change the CUSTID?
Thank you for every help you may give me as i am new in the huawei world!!:good::good:
Click to expand...
Click to collapse
1. No. Huawei uses numbers in old ROMs. But in new ROMs you can select numbers or icons.
2. You can not change ROM via OTA-MF in this case. This type of ROM contains difference between previous version and current only. If you will flash it over other ROM (non-native) - ROM will not be flashed. I don't know what difference between cust D111 and D165.
Symbol 'B' in MHA-L29BC605 means beta or test.
Maybe, you can flash but ROM version is same B111, so very little chances to flash by OTA type.
If you're not planning to sell phone or not using special functional from your mobile operator, it is better to rebrand on world or china ROM. The most popular are C636 (Asia Pacific), C432 (Europe), C00 (China). But you will lost ability to return on your customization, cause there is no full version of your current ROM.
Hey man, check out this thread...
https://forum.xda-developers.com/mate-9/help/huawei-mate-9-mha-l29c605b111-help-t3638341/page2
5[Strogino] said:
1. No. Huawei uses numbers in old ROMs. But in new ROMs you can select numbers or icons.
2. You can not change ROM via OTA-MF in this case. This type of ROM contains difference between previous version and current only. If you will flash it over other ROM (non-native) - ROM will not be flashed. I don't know what difference between cust D111 and D165.
Symbol 'B' in MHA-L29BC605 means beta or test.
Maybe, you can flash but ROM version is same B111, so very little chances to flash by OTA type.
If you're not planning to sell phone or not using special functional from your mobile operator, it is better to rebrand on world or china ROM. The most popular are C636 (Asia Pacific), C432 (Europe), C00 (China). But you will lost ability to return on your customization, cause there is no full version of your current ROM.
Click to expand...
Click to collapse
Many thanks. I am a little afraid of rebranding at the moment. I do not understand de process correctly and I do not want to mess up my phone. I do not understand what is important about my operator, as this phone is not from an operator or the man who sell it to me said that, as i live in argentina this phone is not available here and i do not know from which country is from. Is there a posibility that i get otas or i will be stuck in this?
The_Pacifier said:
Many thanks. I am a little afraid of rebranding at the moment. I do not understand de process correctly and I do not want to mess up my phone. I do not understand what is important about my operator, as this phone is not from an operator or the man who sell it to me said that, as i live in argentina this phone is not available here and i do not know from which country is from. Is there a posibility that i get otas or i will be stuck in this?
Click to expand...
Click to collapse
Where is your phone from? How you bought it?
Unfortunately, phones with extra customization are not updated often. I reviewed many stock ROMs, and ROMs with cust are hosted without FullOTA type even! So it is very hard to restore original state back.
Imho, if anyone wants buy Mate 9 and don't want problems with ROM or flashing process, he/she must buy phone with popular region.
I don't wander what Huawei included in addition to region when named cust. Maybe, it is special settings for domestic mobile operators, maybe some bloatware, maybe something else.
About existing OTAs.
Need to download them all and check what is inside. Changelogs are different, so it is chance that files are incremental. But I will travel for 2 weeks and without ability to get internet. Sorry.
I bought my phone to a guy who import them here in argentina. But i do not have any carrier branding in the ROM and i put my chip and it is not branded. Does my carrier affect in the time of the updates or no? As is not branded. I just reading reddit that the chip you put in the phone affects otas as mine c605 is destinated to colombia and mine is from argentina. Is really true that? In addition that since i bought the phone (1st May 2017) never received an OTA and still on october 2016 security patch.
5[Strogino] said:
Symbol 'B' in MHA-L29BC605 means beta or test.
Click to expand...
Click to collapse
Thanks for clarification. I was wondering why they changed C to BC for some firmwares.
5[Strogino] said:
Where is your phone from? How you bought it?
Unfortunately, phones with extra customization are not updated often. I reviewed many stock ROMs, and ROMs with cust are hosted without FullOTA type even! So it is very hard to restore original state back.
Imho, if anyone wants buy Mate 9 and don't want problems with ROM or flashing process, he/she must buy phone with popular region.
I don't wander what Huawei included in addition to region when named cust. Maybe, it is special settings for domestic mobile operators, maybe some bloatware, maybe something else.
About existing OTAs.
Need to download them all and check what is inside. Changelogs are different, so it is chance that files are incremental. But I will travel for 2 weeks and without ability to get internet. Sorry.
Click to expand...
Click to collapse
Well man. Thnxs for all your info. I got the guts to rebrand this thing. Everything went OK in the first try. The only weird thing that make me crap my pants was that after the rebranding process (When i has finished intalling in the EMUI recovery) the phone start rebooting as crazy :crying: :crying: . It posted huawei logo, then black screen and start rebooting not allowing to enter either fastboot or ADB, after some time doing that the phone booted OK :victory: . Then flashed again the same model option and it was all a huge success :highfive:. Was the rebooting normal o not? Because in the guide that was translated to spanish that was a bit more accurate did not mention anything neither here. Any way, my phone is OK now i have the icons that was the thing that bothered me a lot and i am happy with that, THANKS TO EVERYONE :highfive::highfive:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
ecc25 said:
Hello,
I bought an S7 from eBay, it was marked as a "new" and "UK" phone. I factory reset the device on receipt and apparently worked fine to start with. However, there have been a few problems (poor signal, battery life, echoes in video calls) and I noticed the device was still on Android 6, so wondered if an update to Android 8 might help (?).
There is no menu option available to update Android so I started looking into flashing firmware. On further digging, the device seemed an official SM-G930F but "United Arab Emirates" appears in the "About Phone" section.
I downloaded some stock firmware (Android 8, UK Vodafone which is the network I expect to run it on) and tried flashing with Odin 3.13 and it failed with error "unsupport dev_type" on the phone screen. Any suggestions?
I also noticed that in "Download mode" the phone said it was a "SM-G930V". I wondered if this was why the flash had failed. For the SM-G930V I only seem to be able to get USA/Verizon stock firmware. Might this work or would I have trouble using this in the UK?
Any help would be much appreciated. I'm a newbie in this area so apologies if any of these questions are answered elsewhere.
Many thanks,
Edwin
Click to expand...
Click to collapse
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
cooltt said:
Go to the play store and install Sam phone info, then look at what chipset it lists, you don't want it to be Qualcomm Snapdragon, Eyxnos is what you want to see.
G930V is US Verizon firmware
Report back please.
Click to expand...
Click to collapse
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
ecc25 said:
Thanks for your reply! The "hardware/board" is "qcom/msm8996". Where does that leave me?
I noticed that the Bootloader & Baseband Versions begin G930VVRU but the PDA and CSC versions begin G930FXXU. Not sure if that means anything.
Thank you!
Click to expand...
Click to collapse
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
cooltt said:
Well the person who sold it to you is a liar for starters, it's not a "brand new UK device", it's a US S7 (G930V) Originally bought for the Verizon Network in the states. They are difficult to do anything with as the Qualcomm boot loader is locked down.
So your first option is to update the firmware to the latest Verizon Oreo, probably not worth it since that firmware is designed to work on a couple of frequencies only.
Next option is to flash unbranded US firmware with a modified version of Odin that ignores mismatch devices etc and just installs the firmware. You will need to use this version of Odin from this thread >>> here Odin 13 PatchD.zip is the one you want.
Unzip, run Odin, place phone into download mode flash firmware. You will need to download G930U from Sammobile or undato.com The 3 letter code should either be USC or XAA.
Any questions please ask.
Also before flashing please remove you google account off the phone.
Click to expand...
Click to collapse
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
ecc25 said:
Thank you for these detailed instructions -- much appreciated!
Presumably using this version of Odin carries a high risk of bricking the phone if I get anything wrong?
Out of interest, what's the reason for removing the Google account?
Cheers,
Edwin
Click to expand...
Click to collapse
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
cooltt said:
Because it's a further complication with FRP lock you just don't need after flashing. Just add the google account after flashing and your good to go.
With regards to flashing yes there's always a risk that something can go wrong, that's why you take your time and follow the steps exactly. In your case it's pretty straight forward and remember nothing changes on the external SD card, so anything you want to keep can be moved there before flash.
I would also mention that theoretically you could flash UK unbranded (BTU) but it's for G930F Exynos devices so best at this stage just get the device on unbranded Qualcomm and working on UK networks.
let me know how it goes.
Click to expand...
Click to collapse
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
ecc25 said:
Hello,
I've just tried doing what you suggested (I think!) and I got a failure. Odin said "FAIL! (Auth)" and the phone said "Secure check fail: apnhlos". I tried rebooting and got a security error. So I tried Odin again and it passed.
However, now the phone won't boot, it alternates between "Samsung Galaxy S7" and a blank screen. In recovery I get:
"#fail to open recovery_cause(No such file or directory)#"
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed..."
Any ideas?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
cooltt said:
Ok, so try an earlier G930V firmware and please make sure you are placing the file in the right places with Odin. The US carriers have all updated their firmware and often closes the loophole which allows the patched Odin to work. Then it's just a question of waiting until someone develops a workaround again.
Also you can pick up an S7 from ebay for about £100 now, your always going to have problems with a qualcomm device on UK networks. Where about are you in the UK?
Click to expand...
Click to collapse
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
ecc25 said:
Thanks! Actually shortly after posting I found a suggesting of using CSC not HOME_CSC, which enabled the flash to work (at the expense of phone data, as expected).
The device still does have a few issues though, as you predicted. Is the radio hardware different for Qualcomm? Might need to buy another then. Any advice to avoid being scammed on eBay again?!
Thanks so much!
Click to expand...
Click to collapse
Well you could flash G930U which opens up all of the radios for the US and you may have less issues but US and European devices have different chips so your never going to be able to flash any EU generic firmware. I'm addition the US and Europe are different cellular regions with different operating frequencies. You can get by with what you have but never get full functionality.
I think you were just unlucky with this phone on ebay, there are plenty which are genuine EU region devices.
I managed to get VoLTE working on the xz2cd (H8324) with T-Mobile USA using the xz3 (H8416) USA firmware oem-*.sin files.
Thank you to all the others that figured out the process details so all I had to do was try every combination - see the other VoLTE threads in this forum to guide you on the actual steps. Also thanks to Androxyde and Igoreisberg for the flash & download tools!
I have this working with the H8324_Customized NOBA_1313-6167_52.0.A.8.25_R5B firmware, I happen to choose, replacing only the oem-*.sin files from the XZ3 H8416_Customized US_1316-4522_52.0.A.8.25_R10B firmware. When you set both lines to "LTE (preferred)" and you'll be able to make LTE calls on both lines, however it may only show [HD] calling on the line you configured last I think but it'll be VoLTE on both.
Enjoy and thanks again to all the other threads that guided me through this long but worthwhile trial process. I wish the carriers didn't make LTE VoLTE provisioning difficult, why didn't they just make it universal like 3G.
Note: I was able to separately get Wifi-Calling to appear using the H8276_Freedom CA_1313-8876_52.0.A.8.25_R3B oem-*.sin files but it wasn't functional on T-Mobile USA - I think someone with a little bit more knowledge might be able to get this to work, unless you can point me in the right direction.
Someone please make an open firmware thin/light/compact dual SIM phone with Wifi-Calling/VoLTE (removable battery a bonus)!
Do you think the files would be the same on the H8314 US edition? i'm assuming you need to be rooted for this to work?
Hey Mike, Can you please share(download link) OEM*.sin files of USA firmware for Volte Settings
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
VoLTE provisioned on XZ2 but calls are still made over 3G
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
I just talked to a T-mobile specialist, and he confirmed that my phone should work and no need to register or do anything if it supports all bands!!! As he told me "only check for compatibility" and mine is compatible! ?
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Is there anyway to get volte working for tmobile on the h8314?
XZ2C H8314 VoLTE working on T-Mobile USA
colonelcack said:
Is there anyway to get volte working for tmobile on the h8314?
Click to expand...
Click to collapse
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 4(66) just fine, I cannot confirm band 12 even though the phone spec supports it. It appears only Short range VoLTE is working on the phone unless someone else can confirm with this method, My Band 12 tower is behind a hill and i am 20 miles from it) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
XZ1 oem files on XZ2 for VOLTE and VOWIFI calls.
nicogu said:
Im wondering if we can flash the OEM files from the US XZ1 Compact to get T-Mobile VOLTE and Wifi calling? I would try it myself but I cant find one of these phones at a reasonable price. If I do I will try and report back if anyone cares. I am glad at least VOLTE seems to work with this workaround.
Click to expand...
Click to collapse
You will need to try this. I was not so brave. The reason is the difference in the build IDs and oem.sin file names between the XZ1 (Old) and XZ2 (Current as of July USA Customized builds).
Mixing and matching files is easier when you are doing so off the same build ID. Thats why V0LTE worked on my XZ2 using XZ3 oem.sin files, they were from the same build ID and had the same names even though the sizes were slightly different.
It may work if the format of the oem.sin file did not change between the XZ1 builds and XZ2 Builds. The more different the builds, the higher the risk of something going wrong.
---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------
gigili said:
I’ve done the same for my XZ2 (not compact, H8266). The VoLTE button is now active, but calls are still making over 3G. Any suggestion?
Click to expand...
Click to collapse
Enter *#*#4636#*#* in your phone dialer app, select phone information, and select LTE only - Reboot, if you cant make calls after that something else is wrong.
---------- Post added at 01:33 AM ---------- Previous post was at 01:31 AM ----------
hitemup92 said:
Were you ever able to get this working? New XZ2 owner and of course I bought this within a week is the announcement about all non VoLTE devices being kicked off in January..
Click to expand...
Click to collapse
Got this to work, no VoWIFI though - look further down the thread.
depsilon said:
Yes VoLTE works but no VoWIFI with the following method:
Download USA Customized for XZ2C (H8314) and use only the two oem...sin files from XZ3 (H8416) USA Customized. (overwrite the two files in the XZ2C stack)
Use newflasher tool. (I deleted all .ta files and userdata file to avoid losing existing data)
To put the phone into flash mode, power off, hold the vol down button and plug in your usb cable while holding the button until you get a dim green light.
The device will show up in device manager under USB and you can run newflasher as administrator. Please search for a tutorial - there are many that are very good with screenshots of the files you want to move into the newflasher folder.
Some hangups I ran into when setting up and flashing -
Installing flashtool drivers required disabling driver signature enforcement on win10 (Flash device did not show up in usb in device manager until this was done)
For safety, after the flashtool driver install, I performed a repair on xperia companion app in case of any driver conflicts.
Running newflasher again, I got an error: Unable to open ./boot/Apollo_XBootConfig_MiscTA.ta! after multiple system files had been flashed.
But not to worry, the command window said the phone exited flash mode, but got error 933 - unable to sync. - No worries though, just make sure the command window states the phone is out of flash mode somewhere, disconnect your cable and power up your phone.
Then you will get an android message saying your carrier settings will update after reboot and the phone may reboot.
Once rebooted, enter *#*#4636#*#* in your phone dialer app (Takes 30 seconds after fresh boot for the menu to come up) , select phone information, and select LTE only (Note: VoLTE Provisioned will have the slider set to the right, but grayed out - Before the re-flash, the slider was set to the left and grayed out), reboot again. (If you click the 3 dots and look at IMS Status, you will see IMS status Registered, VoLTE Available and UT interface Available - Before the re-flash status was not registered and not available)
Now when you make a call, it will say "HD" in your dialer while on a call and your signal indicator will no longer say 3G when calling.
VoWIFI does not work, but you can use whatapp or something else like googleFi if its a must have, but in my case, I did not want to have to buy a new phone in January when they turn off 3G - Phones are too darn big now anyways and I love the display on this phone.
Notices will go out starting AUG 4th if your phone is marked as not supported using T-Mobile IMEI BYOD online tool - Their tool said my phone does not support VoLTE (Not fully true - It just does not have Band 71 for Long Range VoLTE but will use Band 12 just fine) T-mobile currently does not have a whitelist like AT&T, so If the UE (User Equipment - ie. phone) is configured properly, the network will handle the rest. I hope this practice does not change.
I made the mistake of calling sony and t-mobile for support and they both kept blaming each other, the reason they don't know why VoLTE does not work on some phones is they really don't know enough about their network or the basebands in the phone or the software build process and details about android sin files - as they should not either cause if the network engineers, device manufacturers and software developers all do their job and stick to industry standard practices, it will just work anyway.
The advantage to using this method, is you are using completely stock USA files - My bootloader is locked and i am not rooted BTW. My XZ2C is only carrier unlocked.
The build number of both Roms I used was the same 52.1.A.3.49 XXX - Good Luck.
BTW - Some people were asking what modem config is working with VoLTE on T-mobile USA - to get the modem setting type *#*#7378423#*#* and in the service menu select software info, under Current modem config the value reads:
row/tmobile/vl/us
Click to expand...
Click to collapse
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
H8314 Flash tools
colonelcack said:
Thank you so much for the detailed instructions! Only one question... Where do I download these files from? And the tool? Can you link me...
Sorry it's been a long time since I've done any xda stuff
Click to expand...
Click to collapse
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
depsilon said:
H8314 Flash tools
I dont have direct links, but here is an excellent walkthrough that calls out all the tools -
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Search for flashtool on XDA there should be links for that, but you only install the drivers from it, not the tool.
You also need the xperia companion software download from sony website for any missing drivers from flashtool.
Search XDA for newflasher, thats what you will actually flash with - https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
the firmware download utility is xperifirm software - https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
It's been a while but wanted to thank you for taking the time to write out these steps. I finally took a shot with the incoming shutdown of 3g for my XZ2, but unfortunately it did not work. Similar to what gigili said, while VoLTE appears to be provisioned the calls are dropping to 3g/HSPA like they originally were. After setting to "LTE Preferred" and rebooting, calls would not be made at all. I also saw "Unknown" under the Modem Config, and from what you said it should reference T-Mobile after flashing the OEM sin files.
I tried this using the latest firmware available on XperiFirm for the XZ2 (Customized US H8266 - my device is H8276) and the XZ3, which I used to grab the two OEM sin files. The firmware is 52.1.A.3.137.
Using UnSin, I unpacked both "oem_X-FLASH-CUST-B6B5.sin" files in both firmwares, and under modem-config there are a bunch of folders, and each one seems to have a conf files pointing to "mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn."
I read in another thread that T-Mobile maybe has some way of blocking this workaround now, but I'm not entirely sure if that is true? Totally understand if you've moved on from the device as it's been a while, but am admittedly curious if there's a specific firmware version that this works on I could try to salvage the device.
Volte xz2/xz2 p/xz3 solved
Samir solanki said:
Volte xz2/xz2 p/xz3 solved
Click to expand...
Click to collapse
Details on exactly how?
I will create complete guide thread for the same
Samir solanki said:
I will create complete guide thread for the same
Click to expand...
Click to collapse
Thanks I'll watch for it
I am working to bring support for T-Mobile VoLTE on the xz2c to LineageOS 18.1. As of this writing, official LineageOS builds for this device do not support VoLTE unless it was already enabled and working in the stock firmware.
I have submitted some patches which may resolve the issue for TMO and probably other carriers as well. They work for me, but testing has been limited. If you are interested in using LineageOS instead of the stock ROM, and you are willing and able to build LOS yourself on linux, consider giving my patchset a try. Please read the patch description fully before attempting a build: you will need to obtain and mount some additional files first. The LineageOS wiki has additional instructions for creating a build environment.
EDIT: My patch is part of official LOS 18.1 starting with nightly 20220401. There is no need to build it yourself.
cbs228 said:
---
Click to expand...
Click to collapse
You are a saint for working on this. I bought a H8324 XZ2c recently and was super disappointed it didn't work, so I am back to my XZ1c. Super frustrated. If you ever get a pre-compiled ROM, I would love to try. In the meantime I will try to compile it myself in the coming days despite my technical illiteracy.
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage? Considering how old the other solutions for trying to get VoLTE working, I am hesitant to try any especially funny business of switching old firmware files from other phones around.
xperiaperson42069 said:
If that doesn't end up working, what stock firmware is available with T-Mobile VoLTE enabled and working, so I could step up from that to Lineage?
Click to expand...
Click to collapse
As far as I am aware there isn't any stock firmware that works "out of the box." The xz2c is listed as "unsupported" by t-mobile, which probably means there isn't any sort of stock ROM out there that works. Sometimes carriers do release "branded" ROMs, but there's nothing like that for this device AFAIK.
LinageOS is designed to be installed "on top" of an existing stock ROM. If you attempt to install it after you have flashed another distro (like an AOSP build), you will likely just make a brick. If you do end up bricking your device, do not despair. You can use Emma to restore your device to factory condition. Emma is available on the Sony Developer World website, and there are many guides available for it.
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
I'm running MetroPCS software on a Amazon device
I'm running Cricket software on a MetroPCS device &
I'm running Amazon software on a MetroPCS device
Cons on both I've come across so far.
Cricket software on a MetroPCS device I get Boot screen says Bad key in top left corner before loading the device.
Amazon software on a MetroPCS device I get a Boot screen says untrusted device before loading the device.
Pros is they both work great.
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
Since you did that when you have the time, try to go back a lower build or your OG Build and check if you still have data and sim accses. I ask because (I have a RETUS) and since I flashed the latest one available "PPO29.114-108 May 1 Security Update" can't go back to OG Build it came with without losing data and sim detection. Something was updated in that build that even if you flash back it broke that. I even flashed the modem to check but no still no data or SIM detected at all. Only all fine in the most recent build.
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
I am guessing that it is still sim locked to metropcs after flashing this?
twfs said:
I am guessing that it is still sim locked to metropcs after flashing this?
Click to expand...
Click to collapse
Flashing a Carrier or Retail ROM won't ever unlock a Carrier Lock device. If it were that simple don't you think we will ever have this issue. Hell the term network lock won't even exist in a perfect world.
---------- Post added at 03:24 AM ---------- Previous post was at 03:22 AM ----------
twfs said:
I am guessing that it is still sim locked to metropcs after flashing this?
Click to expand...
Click to collapse
And yes there are several Motorola Devices that are firmware interchangeable. Been doing it since the first Moto X times. Only benefit from this procedure no bloatware and faster updates that's it. Oh and better performance since it doesn't include crappware
Medfordite said:
Last night as part of rooting, I was getting issues with the MetroPCS Ocean firmware with the update failing message. I took a look at the RETUS firmwares and saw the latest so I took a chance and was able to flash the Retail version with no problems, booted up and 'worked out of the box' so to speak. It is also lighter on the features since it doesn't include the MetroPCS apps. I am not going to try rooting with this one, but it seems to be quite stable and an a little faster if that makes any sense.
Your mileage may vary!
You assume any risk by attempting the same thing on your device, but I figured it would be something someone would be interested in knowing.
Click to expand...
Click to collapse
PartyDroid said:
I'm running Cricket software on a MetroPCS device &
I'm running Amazon software on a MetroPCS device
Cons on both I've come across so far.
Cricket software on a MetroPCS device I get Boot screen says Bad key in top left corner before loading the device.
Amazon software on a MetroPCS device I get a Boot screen says untrusted device before loading the device.
Pros is they both work great.
Click to expand...
Click to collapse
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
disobey said:
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
Click to expand...
Click to collapse
PSA. If you flsh Cricket, Metro etc Roth the RETUS Latest firmware you won't be able to go back to you LG firmware. That firmware updates the Bootloader and that preventa going back to a lower workifn version. You can doing what I posted earlier by while flashing back to OG Firmware skip flashing modem and fsg bins and don't execute the modem erase commands.
disobey said:
I'm interested in flashing my MetroPCS g7 stock unrooted to the Amazon rom if you care to point me in the right direction please.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/official/AMZ/
Ok I bricked my phone via magisk update, I was on MetroPCS variant of Ocean firmware. Now I manually flashed RETUS PPO 29.114-108; It seems to be running fine other than saying my device is not certified....is there a custom recovery that will work for Ocean RETUS using twrp? Should I try to re root using magisk systemless-ly copying boot.img? Thanks for info and any input would be greatly appreciated! Thanks
PartyDroid said:
https://mirrors.lolinet.com/firmware/moto/ocean/official/AMZ/
Click to expand...
Click to collapse
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
nashi20002003 said:
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
Click to expand...
Click to collapse
I'd like to know as well, I got 2 of these Moto G Power 7's from Metro PCS and would love a stock ROM without all the metro bloat. Not sure on Metro's unlocking policy if they will unlock it and what bands this all has if it has CDMA or is it GSM only?
chennault05 said:
Ok I bricked my phone via magisk update, I was on MetroPCS variant of Ocean firmware. Now I manually flashed RETUS PPO 29.114-108; It seems to be running fine other than saying my device is not certified....is there a custom recovery that will work for Ocean RETUS using twrp? Should I try to re root using magisk systemless-ly copying boot.img? Thanks for info and any input would be greatly appreciated! Thanks
Click to expand...
Click to collapse
If I were you I will stay away from Magisk until they update the app, still damaging the boot.img files..
Omar04 said:
Flashing a Carrier or Retail ROM won't ever unlock a Carrier Lock device. If it were that simple don't you think we will ever have this issue. Hell the term network lock won't even exist in a perfect world.
---------- Post added at 03:24 AM ---------- Previous post was at 03:22 AM ----------
And yes there are several Motorola Devices that are firmware interchangeable. Been doing it since the first Moto X times. Only benefit from this procedure no bloatware and faster updates that's it. Oh and better performance since it doesn't include crappware
Click to expand...
Click to collapse
Do you know if there is a way to sim-unlock a Metro device? Searched on eBay, no luck... thanks.
edwardxi said:
Do you know if there is a way to sim-unlock a Metro device? Searched on eBay, no luck... thanks.
Click to expand...
Click to collapse
Note to Admin: I am not sure if this link is allowed if not please remove this message..
https://www.ebay.com/itm/264407271128?ViewItem=&item=264407271128
PartyDroid said:
Note to Admin: I am not sure if this link is allowed if not please remove this message..
https://www.ebay.com/itm/264407271128?ViewItem=&item=264407271128
Click to expand...
Click to collapse
thanks, I found one on eBay for $38... too expensive, used to around $10
nashi20002003 said:
Can we get directions on how you guys are doing this please. I've tried using the back to stock directions but extracting a different firmware but it's not working. I have Metropcs.....I extracted Tmobile firmware and use the back to stock commands...but when rebooting its' still Metropcs....please help with some directions.
Click to expand...
Click to collapse
Instructions are in the thread back to stock.
Secondly, I'm on MetroPCS and flashed the retus2 firmware (BestBuy versions) no MetroPCS bloatware. Flash the retus2 and you'll be fine.
edwardxi said:
thanks, I found one on eBay for $38... too expensive, used to around $10
Click to expand...
Click to collapse
You probably won't find one cheaper. $10 ones are ones that give you a code to unlock. Unlocking a MetroPCS/TMO G7Power with the Server unlock app requires a person to remotely connect to your phone and edit your NV files. Currently they are changing the imei to a different model phone that they can generate the unlock codes for. Since they are using a different model phone imei, activating on Sprint Network could be an issue since Sprint is picky as to what phones they put on their network.
If I flash "retail" firmware on a TMO Sim locked Moto G7 power will it ask me for an unlock code that I don't have? Bought it on eBay and TMO says its eligible to unlock but refuses because I'm not the original owner. Bootloader is unlocked.
EDIT: Figured out my issue. Was my fault. Flashed the RETAILUS firmware on my MetroPCS model.
Thanks OP!
Also to add to this, the Metro model is NOT supposed to be compitable with Verizon due to lack of CDMA.... Well Magically the phone now supports CDMA so it has a CDMA radio in it!