I'm no stranger to custom recoveries or flashing custom roms, but man, I've been trying to get a handle on this thing.
I just bought a Huawei Mate 8 (The model number on the back is NXT-TL00). I'm guessing it's the Chinese version.
Can someone give me an idiots guide to see what firmware I'm on and flashing this thing with a custom rom? I keep seeing references to having "Firmware Bxx", and I'm not even sure how to check that.
This is a vanilla phone straight from eBay and the official build Number in the settings screen reads NXT-TL00C0B197. I'm assuming that means I'm on B197? Does that mean I need to update all the way up into the B3xx's to install the newest roms?
I feel like a complete idiot. I'm used to just unlocking a bootloader, installing a custom recovery, and flashing a rom. It seems like like this is going to be a little more difficult coming from something like a Samsung or LG. Just need some friendly advice. Thanks in advance XDA Folks.
Hello.
Im coming from LG , and yes , its a bit more difficult.
this phone have some variants on different country, but hardware is same , or nearly on all models
Im french and i bought one in china and receved a DL00.
I was able to transform it into an europeean version to get rid of chinese bloatware. my phone is L29C432 B320. C432 is the european rom model. B320 is version of the rom. I always stick to my model to avoid any problems
Yeah, you are on B197.
Its easy as ****. First of all check if you got single or double sim card phone (guess its dual-sim chinese phone )
then if u dont mind - unlock bootloader (check guide, its on the forum, easy access to find it )
then flash TWRP and root your phone (again, a guide + software from here ->http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
then - install a software that you want to :
thanks to @jbmc83
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
L29 = international version, unlocked, dual sim
L09 = international version, unlocked, single sim, only available in 3/32 GB
now everything is clear. just ask , people are nice here and able to help you bro.
have a good time with your phone
ps. i dont like to flash custom roms so i recomend you to do it like this -> unlock -> flash TWRP -> flash http://forum.xda-developers.com/showpost.php?p=65544452 from here -> Root -> delete unneccecary apps with root delete program and you are ready to rock like us
what's the result ?
Anyone tried to install a European Software on this Phone Model NXT-TL00 please ?
Thank you
Hello,
I live in Switzerland and have a Exynos Galaxy S7. Will looking for accessories on Aliexpress, I noticed that the refurbished US variants sell for a huge discount compared to the SM-G930F (up to 80$) version. I saw that the G930F seems to support all LTE bands will the other are more constrained (but the AT&T version supports all the bands used in Europe as well). So my question is are they simlocked? Would they work in Europe (out of curiosity)?
Thanks
No advices?
You can get carrier unlocked US models which will accept any SIM, and they should work in the rest of the world. Of course network availability would vary, but you've already checked that. So if the US model supports all the bands your carrier uses you should be fine.
Only problem is the US model has a locked bootloader, so you can't use a custom recovery or ROMs. From memory root is possible but doing it is a bit different.
I'm not sure if you'd be able to flash your carriers CSC onto a US model phone, since the CSC would be built for the 930F. Which means OTA updates etc might not reach you, and you'll have to manually flash firmware updates.
Beanvee7 said:
You can get carrier unlocked US models which will accept any SIM, and they should work in the rest of the world. Of course network availability would vary, but you've already checked that. So if the US model supports all the bands your carrier uses you should be fine.
Only problem is the US model has a locked bootloader, so you can't use a custom recovery or ROMs. From memory root is possible but doing it is a bit different.
I'm not sure if you'd be able to flash your carriers CSC onto a US model phone, since the CSC would be built for the 930F. Which means OTA updates etc might not reach you, and you'll have to manually flash firmware updates.
Click to expand...
Click to collapse
Thanks a lot for your detailed answer
I'm looking at upgrading from my Moto E4 and settled on the Galaxy S7 over the Pixel due to the MicroSD slot. I now have questions as to which version to get.
I understand that it's relatively simple to flash the unlocked firmware on any of the devices. Could I just simply find the cheapest, good shaped S7 and flash the unlocked firmware and be satisfied?
I'm currently on Sprint's 1-year free service promotion until September 2018. So Sprint compatibility is needed for a while. After that, I want the freedom to be able to hop back to AT&T or Verizon (or one of their MVNOs).
Should I just buy a Sprint S7 now, then when my service is up, flash the new firmware then? Or should I buy a T-Mobile version and flash the 930U firmware right away? The universal unlocked model is significantly more expensive, so I just want to make sure I'm covering all my bases.
Depends on your goals. Flashing via Odin is quite simple and easy for the S7, but the US models all have a locked bootloader. That means you can only flash stock firmware files, and nothing custom. No ROM's and no TWRP.
If you're happy with than then you're set, if not you'll need the international Exynos model, as it can be unlocked and flash custom.
Beanvee7 said:
Depends on your goals. Flashing via Odin is quite simple and easy for the S7, but the US models all have a locked bootloader. That means you can only flash stock firmware files, and nothing custom. No ROM's and no TWRP.
If you're happy with than then you're set, if not you'll need the international Exynos model, as it can be unlocked and flash custom.
Click to expand...
Click to collapse
no ROMs is OK with me. the exynos version won't work on my current provider, so can't go that direction anyway.
My Uncle got me a verizon galaxy s7 from USA and now I am trying to run a 4G sim in it but it isn't working as VoLTE is not activating ( something called Advanced HD Calling) as verizon wants verification for it and as the device is here we can't do that
I was thinking of flashing an Indian Firmware on it
Will that help me ??
Or is there anything else I can do.
Please Help.
update 1 : I managed to unlock the bootloader
If it's a Verizon S7 it'll be a G930V which uses Snapdragon, you can't flash Indian firmware on it because India uses the G930F model which has Exynos SoC.
Also despite the bootloader unlock option being available and toggleable in developer options, it doesn't actually do anything on USA models. Don't attempt to flash custom recovery, it'll brick.
Your best bet would be to flash the unbranded USA firmware (G930U) which should rid the phone of Verizon, however it's unlikely that'd let you use local carrier VoLTE.
I can run an Indian Sim in this device its just that the Volte doesn't work
I can still make it work with an app from the provider
should i just make do with the app or try the unbranded firmware?
also the other s7 my uncle sent me has FRP locked and the seller can't obviously give me his gmail to unlock it.
Is there anything I can do to bypass it or do I have to send it back to USA? also i have no clue if it has OEM unlocking enabled
For those who aren't already aware, G996U is the model number of all of the US carrier versions of the S21+. The G996U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit the firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=322091
U1 firmware: https://www.androidfilehost.com/?w=files&flid=322092
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to an S21, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
Initial U firmware and AT&T USERDATA are posted, along with U1 firmware. U firmware is not yet accessible in the firmware download tools like SamFirm and Frija, but if anyone wants a different carrier's USERDATA (for flashing bloatware to a U1 device or for converting a U device from one carrier's bloatware to a different one), let me know and I'll get it for you
Are the firmware in OP compatible for the S21 (Non-plus)?
craznazn said:
Are the firmware in OP compatible for the S21 (Non-plus)?
Click to expand...
Click to collapse
This thread is in the S21+ forum, not the S21 forum.
This thread is for model numbers G996U and G996U1, not G991U or G991U1.
If you're looking for S21 firmware, that will be found in the S21 forum
I agree with you
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
3BeersKen said:
Does the firmware control the SIM lock? So, can you flash the U1-XAA firmware and use say a phone purchased from AT&T on another carrier? Or do you need to do the SIM unlock before flashing?
Click to expand...
Click to collapse
SIM unlock always goes much deeper than firmware. Flashing U1 will never automatically unlock any model - the unlock has to be done separately. If desired, I can provide a recommendation for a professional 3rd party business to do the unlocking, for any interested users who may not meet the carrier's unlock requirement(s).
Thanks. That's what I figured, but wanted to make sure. I like to get off of the AT&T firmware as quickly as possible as you can't get their updates unless you have an active SIM in the phone.
3BeersKen said:
You can't get their updates unless you have an active SIM in the phone.
Click to expand...
Click to collapse
Correct. They're A-holes like that haha
iBowToAndroid said:
Correct. They're A-holes like that haha
Click to expand...
Click to collapse
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
yijinsa said:
I got TMobile s21+ and want flash to u1,do you know which odin should I use, thanks
Click to expand...
Click to collapse
3.14.1 patched
I don't have my S21+ yet but it will be here soon. I ordered from Samsung and selected the Verizon version as unlocked was considerably more expensive.
Does anyone know what Verizon specific bloatware the S21+ has?
Are there certain apps which can be uninstalled with the U1 version but not the Verizon U version?
Are there any potential speed benefits on the 5G network that would be lost using the U1 version, or features like tethering that won't work?
For updates in the future, would they arrive faster on the U1 version, slower, or the same?
My main purpose in flashing from U to U1 is to free up the maximum amount of space of the 128 GB while still retaining 100% of the speed and features I would have with the Verizon version.
Thank you for educating me! It's been a couple years since I flashed my Note 8.
I order a unlocked S21+ U1 version straight from Samsung and didn't have to put in any VZW info.
There is a buttload of Samsung bloatware but no VZW except fot MyVZX
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
iBowToAndroid said:
Yes, that seems to be a common issue with T-Mobile S21s - all 3 models
Click to expand...
Click to collapse
You think there will be a fix for this? It's weird that dialer codes also don't work.
x1tymez said:
Have anyone here with T-mobile version stuck on TMB/TMB/TMB after going to U1 firmware?
Someone over S21 Ultra have this problem, but I'm not sure if Android 11 tinker or T-mobile side. Used to be XAA/XAA/TMB
Click to expand...
Click to collapse
I've got a T-Mobile locked that I was able to get flashed over to U1 without much trouble. Shows mode number SM-G996U1 now, build number shows same.
edit: Nevermind, I see the TMB/TMB/TMB
krisology said:
You think there will be a fix for this? It's weird that dialer codes also don't work.
Click to expand...
Click to collapse
Dialer codes don't work? On which firmware?
iBowToAndroid said:
Dialer codes don't work? On which firmware?
Click to expand...
Click to collapse
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
krisology said:
XAA U1, VZW U1, stock TMB U, and I've tried the TLI U1 above and couldn't get it to work. Using google dialer, I input the codes like *#*#27262826#*#* and as soon as I type the last star it just disappears and nothing pops up. I tried with T-Mobile and Verizon sim.
Click to expand...
Click to collapse
Dialer codes usually don't work on VZW firmware, whether U or U1. But they almost always work on TMB and all others.
Have you tried *#06# ?