Related
' .... We still haven't tested whether the device is actually a tri-band phone that is just software-limited to being a dual-band phone, but postings on the net seem to indicate that it is not actually a tri-band phone. But even though we think we know, we still need someone with access to a European phone in USA...'
is it already tested???
Not sure. But it isn't. We're pretty sure of that: radio parts are different.
And don't try to flash a 900/1800 modem with 900/1900 firmware either: you'll ruin it.
Not tri band
There are two different devices.
PW10A1 is 900/1800MHz
PW10B1 is 900/1900MHz FCC ID: NM8SN
Only the PW10B1 is approved for use in the USA. The RF components are different, even though the Bootloader is common between both devices.
In other words, you will ruin it if you flash it with a different GSM version, but it is possible to flash it back using bootloader, right?
Zviratko said:
In other words, you will ruin it if you flash it with a different GSM version, but it is possible to flash it back using bootloader, right?
Click to expand...
Click to collapse
No, the bootloader method of flashing currently only covers the WinCE (main) ROM, not the GSM ROM. There is a way, but we simply know too little at this time... Progress is being made though...
I now have a confirmed report of the XDA not being a tri-band device. A friend of my took an European XDA to the US yesterday. Like we expected the device is not working there. Even not when switched to "GSM1900".
This confirms the idea of an universal bootloader and different GSM stacks. The European/Asian XDA is simple not working on GSM1900 networks. If you travel a lot, it's better to buy a T-Mobile or AT&T device as those devices work on GSM900 and GSM1900...
Anonymous said:
I now have a confirmed report of the XDA not being a tri-band device. A friend of my took an European XDA to the US yesterday. Like we expected the device is not working there. Even not when switched to "GSM1900".
Click to expand...
Click to collapse
Ah excellent. We all knew it wasn't, but now at least someone has tested it.
This confirms the idea of an universal bootloader and different GSM stacks. The European/Asian XDA is simple not working on GSM1900 networks. If you travel a lot, it's better to buy a T-Mobile or AT&T device as those devices work on GSM900 and GSM1900...
Click to expand...
Click to collapse
It's really much better not to speak of bootloader in connection with the modem part. The bootloader resides in the first 256 kilobytes of the main ROM. The rest of this ROM (32 MB - 256 kB) is taken up by the operating system, with a little room to spare for contacts and other things which are explicitly saved to flash by the user. The OS ROM can be flashed using the RUU program (also called Programme A by HTC), but it can also be flashed using the bootloader, residing in the same ROM.
The modem is a different contraption alltogether. It has its own processor, RAM (256 kB) and ROM (4 MB), and is possibly only wired to the main processor with a serial port (operating at 115 kbps). The modem holds the software loaded in using the Radio Stack Upgrade (also called Programme B by HTC). The 900/1800 and the 900/1900 modems have both different software and different hardware. Flashing software of one into the other makes it not work anymore, and we're not sure whether there's always a way back.
We're learning more and more about the modem upgrade process. But we still advise against playing around with the modem. Upgrade if you have to (maybe skipping 4.14 and wait for higher versions if you haven't upgraded yet), but if you're not deeply technically inclined then don't **** with it beyond that unless you wanna risk losing it.
Hi,
so...
my advantage with AP 3 Dual (SPL 1.20) shuts down while i try to connect with umts network.
When i try to connect he simply shuts down and i can only restart hin by pressing the powerbutton.
So...i've insstalled SpB, AP 3 addons: task manager, temp realvga comm manger, snapvue, htc home screen, opera 9.5 build 405 (irus addons), pocket rar, tcmp, realvga with german language....
does somebody have an idea why he's doing this?
no ideas?
the connection with hsdpa worked.
Knopfgesicht said:
no ideas?
the connection with hsdpa worked.
Click to expand...
Click to collapse
suggest you do a hard reset and setup connections before anything else if it works then its some where else
HTC Advantage 7510 no 3G
Anyone make a fix for the 3G in the US? I use AT&T and they have the same UMTS bands as the phone's claimed specs but AT&T said it won't work. So, I know that some patches or roms have been created to fix other phones with this same problem. Has someone done something similar for the 7510?
Quincy
It could be also a BATTERY problem.
In the Excalibur section device shutting down while trying internet connection is a well known problem due to battery problem. A lot of power requested (CPU, radio) old or defective battery.... shut down!
qsworld said:
Anyone make a fix for the 3G in the US? I use AT&T and they have the same UMTS bands as the phone's claimed specs but AT&T said it won't work. So, I know that some patches or roms have been created to fix other phones with this same problem. Has someone done something similar for the 7510?
Quincy
Click to expand...
Click to collapse
Probably want to post your question in the new 7510 sub-forum.
qsworld said:
Anyone make a fix for the 3G in the US? I use AT&T and they have the same UMTS bands as the phone's claimed specs but AT&T said it won't work. So, I know that some patches or roms have been created to fix other phones with this same problem. Has someone done something similar for the 7510?
Quincy
Click to expand...
Click to collapse
if it has the same bands, it will work. and as far as I can remember my athena worked fine on 3G on ATT when i was in the USA..
Picked up a second hand X1 and trying to work out which model it is. Having a few issues with 3g-2g switching and signal strength and want to make sure I have the best ROM installed.
Attached is the one it came with, everything is fine except the signal sometimes drops out all together even though my Samsung Mega 6.3 has 3 bars of 3G and 4 of 2G in the same location.
Bluetooth also seems to be a bit flakey with my LG Google watch sometimes disconnecting.
Turning Bluetooth on and off fixes it but its not a real solution as I need it for notifications. I also need to stick with 4.4.2 for my Google watch to work.
Any suggestions? Is this a stock rom?
the rom installed on your device is the latest for the 7D-503L ( Huawei Honor X1). wich means it's supposed to be the more advanced ROM for this specific one.
To check if your device is also a 7D-503L, look at the back of it, the model number is printed at the bottom, even if it'sprinted in chinese.
No model number printed anywhere, guessing its the Chinese version. Bad 2G/3G reception is driving me crazy on this thing, not much use as a phone if I can't get receptions.
Callers sometimes have to wait a couple of seconds before they can hear my voice too which is really embarrassing. I might try an earlier rom, looks like I am on some beta version.
7D-503LV100R002C208B011
mingonn said:
No model number printed anywhere, guessing its the Chinese version. Bad 2G/3G reception is driving me crazy on this thing, not much use as a phone if I can't get receptions.
Callers sometimes have to wait a couple of seconds before they can hear my voice too which is really embarrassing. I might try an earlier rom, looks like I am on some beta version.
7D-503LV100R002C208B011
Click to expand...
Click to collapse
Try to install the last international ROM (B102 for 7D-501L, will go to b103 by OTA after install) adpated to the 7D-503L:
http://pan.baidu.com/s/1jGrBBOq
your you can try the 7D-503L B009 ROM, which is supposed to be the more signal-stable:
http://www.emui.com/nsp/geturl.php?path=7D-503L_EMUI3.0_Android4.4_V100R002C208B009.zip&rid=963
If the install fail for this last rom, it means that your model is not a 7D-503L
let us know
Djiban said:
Try to install the last international ROM (B102 for 7D-501L, will go to b103 by OTA after install) adpated to the 7D-503L:
http://pan.baidu.com/s/1jGrBBOq
your you can try the 7D-503L B009 ROM, which is supposed to be the more signal-stable:
http://www.emui.com/nsp/geturl.php?path=7D-503L_EMUI3.0_Android4.4_V100R002C208B009.zip&rid=963
If the install fail for this last rom, it means that your model is not a 7D-503L
let us know
Click to expand...
Click to collapse
B009 sounds like its the best rom for this phone but its only 4.2 and I need 4.4 for my LG Android watch to work. There is a B010 out so I will try than next but I am not hopeful.
Pretty sure the problem is with the switching between towers on low signal. I can go from 4 bars to no signal in an instant in the same location at home. I tried a different networks SIM card and still no good at home. The same SIM card in a cheap 2G phone and I get 3 bar and no drop outs.
How Huawei can get is so wrong is beyond me.
In the CBD today where there is good coverage I had no problem at all with calls or signal but on the train home it was useless.
The same trip with my Galaxy Mega 6.3 gives me pretty good connection and data all the way home. I love this phone but I will have to go back to my Galaxy Mega if I can't resolve this signal issue.
B009 is KitKat 4.4.2, 400 DPI, EMUI 3.0 .
Install this ROM. (and then check if your device is a 503L, revealed by achieving the installation)
If still signal issues, try the 501L B102 adapted to 503L.
Unlocked AT&T-branded PadFoneX. I'm getting low reception on Band 4 and no HSPDA+ reception whatsoever.
I upgraded the unit to the PadFoneS firmware and did the four Asus upgrades to bring it up to date with no better result. Applied the 99.99.99 down-grade back to KitKat and still no love. I use the APN settings for Fast T-Mobile USA and have tried others as well. My Huawei MediaPad Pro T1 8.0 gets strong T-Mobile reception and then switches over to HSPDA+ coverage once I enter my office building. The PadFone gets weak 4G LTE and then switches over to EDGE once I enter the building.
I was really hoping to replace my 8-inch Huawei with the PadFone but the radio reception just doesn't compare and I can't stand being forced to use EDGE inside my office building when I know that T-Mobile HSPDA+ coverage is usable within my building using the Huawei Phablet.
Can someone please please please help me in "fine tuning" this thing for T-Mobile. By the way the PadFone is rooted and I've unlocked the bootloader as well. Maybe there is updated modem firmware to flash? I just don't know what else I can do..
If you get HSPDA+ coverage from T-Mobile on your PadFone can you please share your configuration and APN settings??
Thank you!!!!!!
Chris R.
I have a PFX flashed to PFS Kitkat running on T-Mobile. Connects to the LTE network fine using the fast.t-mobile.com APN. Yes, reception seems to be on the weak side, but it gets the job done for me. Suspect that Mediapad gets a better signal due to it being larger = larger antenna.
HSPA works fine for me as well, but as this is an AT&T/International device, you'll only connect to HSPA on Band 2 (1900MHz). It lacks HSPA Band 4 (1700MHz/2100MHz) for T-Mobile's more extensive 3G network. It looks like that Mediapad has HSPA Band 4 (http://pdadb.net/index.php?m=specs&id=7233&c=huawei_mediapad_t1_8.0_pro_4g_td-lte_t1-821l), so that's probably why it's able to get HSPA signal while the PF does not.
Thank you!
xtermmin said:
I have a PFX flashed to PFS Kitkat running on T-Mobile. Connects to the LTE network fine using the fast.t-mobile.com APN. Yes, reception seems to be on the weak side, but it gets the job done for me. Suspect that Mediapad gets a better signal due to it being larger = larger antenna.
HSPA works fine for me as well, but as this is an AT&T/International device, you'll only connect to HSPA on Band 2 (1900MHz). It lacks HSPA Band 4 (1700MHz/2100MHz) for T-Mobile's more extensive 3G network. It looks like that Mediapad has HSPA Band 4 (http://pdadb.net/index.php?m=specs&id=7233&c=huawei_mediapad_t1_8.0_pro_4g_td-lte_t1-821l), so that's probably why it's able to get HSPA signal while the PF does not.
Click to expand...
Click to collapse
Thank you for your detailed answer! Finally, someone that understands this stuff! Hey, could I get the exact model number of your model?? I'm wondering if I could buy one like yours and then have it unlocked..curious...
Thanks!!!
Chris R.
crodgers79 said:
Thank you for your detailed answer! Finally, someone that understands this stuff! Hey, could I get the exact model number of your model?? I'm wondering if I could buy one like yours and then have it unlocked..curious...
Thanks!!!
Chris R.
Click to expand...
Click to collapse
My device is the AT&T Asus Padfone X (ASUS_T00D). On the white label under the back cover it lists the manufacturing date as 2014/05/31 and is H/W Revision 1.6 (PFX was launched in July 2014, so this is probably a launch model). Bought it from Ebay a year ago pre-unlocked. Used it on AT&T's firmware for a few months before flashing the latest Asus Padfone S (ASUS_T00N) Kitkat firmware, "WW_11.10.7.18". I think I had to manually set my APN, but was able to connect fine.
Looking at the signal levels, the PFX pulls in -108dBm at my desk, while my Moto E2 pulls in -100dBm, both on LTE Band 4. Moto devices tend to have better radios, but I didn't expect the smaller, budget Moto E2 to pull in a better signal than the PFX.
OK, now I'm confused....
xtermmin said:
My device is the AT&T Asus Padfone X (ASUS_T00D). On the white label under the back cover it lists the manufacturing date as 2014/05/31 and is H/W Revision 1.6 (PFX was launched in July 2014, so this is probably a launch model). Bought it from Ebay a year ago pre-unlocked. Used it on AT&T's firmware for a few months before flashing the latest Asus Padfone S (ASUS_T00N) Kitkat firmware, "WW_11.10.7.18". I think I had to manually set my APN, but was able to connect fine.
Looking at the signal levels, the PFX pulls in -108dBm at my desk, while my Moto E2 pulls in -100dBm, both on LTE Band 4. Moto devices tend to have better radios, but I didn't expect the smaller, budget Moto E2 to pull in a better signal than the PFX.
Click to expand...
Click to collapse
I pulled the back cover off of mine, it too is a T00D and, get this, manufacturing date was 2014/05/22 (!!!) FCC ID is MSQT00D, and H/W is 1.6 (!!).
I too did the X-to-S conversion and yesterday I applied each successive update until I got to the very latest 12.2.2.43 (16 Dec 2015).
So if we have nearly identical hardware, is there anything that I can do to improve reception? Could you send me the settings you used for APN?
Thanks!
Chris R.
By the way, your Moto is the better device, the lower the db number the better AFAIK..
crodgers79 said:
I pulled the back cover off of mine, it too is a T00D and, get this, manufacturing date was 2014/05/22 (!!!) FCC ID is MSQT00D, and H/W is 1.6 (!!).
I too did the X-to-S conversion and yesterday I applied each successive update until I got to the very latest 12.2.2.43 (16 Dec 2015).
So if we have nearly identical hardware, is there anything that I can do to improve reception? Could you send me the settings you used for APN?
Thanks!
Chris R.
Click to expand...
Click to collapse
Don't know how to improve the reception, but here's my APN settings:
Name: T-Mobile LTE
APN: fast.t-mobile.com
MCC: 310
MNC: 260
APN Type: default
APN protocol: IPv4
APN roaming protocol: IPv4
Bearer: Unspecified
Everything else is set to Not Set/None.
I didn't set up the MMS proxy as I'm using a tablet data-only plan on the PFX. (I think data-only plans come with free SMS/MMS, but I don't use it.)
crodgers79 said:
By the way, your Moto is the better device, the lower the db number the better AFAIK..
Click to expand...
Click to collapse
I know, which is why I was surprised that the cheap budget Moto E2 got a better signal than the PFX
crodgers79 said:
By the way, your Moto is the better device, the lower the db number the better AFAIK..
Click to expand...
Click to collapse
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Thanks..but consider this..
Justatechie said:
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Click to expand...
Click to collapse
Thanks! I did read through all these threads searching for an answer before I posted my question. the first time I did the X-to-S conversion I thought exactly what you said (destroyed the efs partition containing the modem info). So I went back and loaded the 99.99.99.99 version posted on the Asus site which is supposed to restore it to factory settings and back to KitKat but that had no effect. Since 99.99.99 is for the PadFone S maybe that doesn't make use of the partition under KitKat, I don't know.
What I would dearly love to load is a flashable version of the original AT&T software (thereby restoring the partition and the modem info). I saw one guy had posted TWRP backups of stock but when I tried to restore them to my phone the script bombed and it aborted.
I agree with the other gentleman, I need UMTS Band 4 - (1900/2100) for this thing to work well in my area and it looks like this phone doesn't support it. If I could find someone familiar with QPST to tell me if that band is unlockable that wold be great!
Thanks!!!!
Chris R.
Unfortunately QPST couldn't work with this device, idk know why.
You could find out by searching through using the xda search engine, but the question is, did you back up your modem for this device prior, because it could be restored when the phone is on a stock fw, then you could create an efs backup afterwards.
To answer the question with the tarp backups, those were created from the repacked twrp version so flash that first and back up everything before you restore back to at&t fw. I don't think the quarx version could work with that since the repacked was based on the nexus 5. (Similar parts) (be aware that you need to wait a couple of mins for the black screen to go away, on that version of twrp.)
The thing is that I could use band 2 and 4 on at&t with this fw, (I did not restore my efs partition since the conversion since I lucky live in a good area) but it looks like band 4 doesn't work for t-mobile, hmmm maybe it is incompatible like the other guy said, but we'll see. After wards you gotta see if these bands would restore upon restoring back to the at&t fw.
Justatechie said:
I probably know why you are not receiving a a good signal on your device.
The thing is when you do the conversion, from padfone x to padfone s, the partiton gets overwritten and causes some of the bands to be lost.
That partition is called the efs partition, and probably you have lost some bands that probably would have worked better before you flashed.
The side effects can be seen through the software when additional call settings does not work. (SIM doesnt get recognized)
That is a known problem, and to avoid that you had to back up the efs partiton prior to the conversion so you could restore those kinds of connections after the conversion.
--- You had to use adam outlers repacked twrp version to do all that.
I know many of the guides there have replaced mine but they forgot that one thing that has been talked over, and thanks to tjsooley and the people during that time, they were able to figure it out.
Click to expand...
Click to collapse
The EFS partition contains the modem, yes, but this isn't the issue here. When it comes to bands used in the USA, the Padfone S firmware has all the bands the Padfone X uses except for LTE Band 17, which is only used by AT&T, and would not affect T-Mobile in this case. I was able to use my PFX-converted-to-PFS on T-Mobile without restoring EFS fine.
Thanks!
xtermmin said:
The EFS partition contains the modem, yes, but this isn't the issue here. When it comes to bands used in the USA, the Padfone S firmware has all the bands the Padfone X uses except for LTE Band 17, which is only used by AT&T, and would not affect T-Mobile in this case. I was able to use my PFX-converted-to-PFS on T-Mobile without restoring EFS fine.
Click to expand...
Click to collapse
I think the PadFone's lack of UMTS Band 4 is what's keeping me from getting HSPDA+ inside my office building. Once I head into the building my 4G on Band 4 reverts to Edge (ugh!) and I have a 14Gb tethering plan so that I can run my tablet while inside the building..arrggh!
Thanks for your response!
Chris R.
Hey everybody,
So recently i bought this international unlocked Galaxy S9+ (SM-965F/DS Exynos processor) off Amazon and it's great, everything is fine with the one major exception being that at home my signal is pretty poor and i get extremely delayed text messages coming in and calls taking forever to dial out or failing to connect. Not a problem, i'll turn on Wi-Fi calling, right? Wrong, option isn't available, some detail: I'm in the US on T-Mobile, updated to the latest Pie OS update, i'm very tech-capable and used to do tier 2 tech support for Verizon. Long story short, I've tried everything in the book including FDR and fresh setup as well as clearing system cache etc. and it's looking like the ONLY solution to get Wi-Fi calling (and subsequently VoLTE that i didn't realize wasn't enabled until researching and checking myself) enabled is to flash the ROM with a T-Mobile OS. Unfortunately i'm coming up negative trying to find the firmware for this phone. Plenty of resources out there for the SM-965U(Snapdragon), but none for the SM-965F(Exynos) as of yet as far as i can tell (and before any ignorance jumps in here as i've seen on other threads, NO the SM-965U software will NOT work on this model phone as it runs a different processor, non-Snapdragon Exynos chipset)
So, that all being said, is anyone out there working on a fix for this, is it likely i'll ever get a fix for this, and/or is the fix already available and I've just completely missed it? Any information or help would be greatly appreciated. Thank you for your time and consideration.
bahruuk said:
Hey everybody,
So recently i bought this international unlocked Galaxy S9+ (SM-965F/DS Exynos processor) off Amazon and it's great, everything is fine with the one major exception being that at home my signal is pretty poor and i get extremely delayed text messages coming in and calls taking forever to dial out or failing to connect. Not a problem, i'll turn on Wi-Fi calling, right? Wrong, option isn't available, some detail: I'm in the US on T-Mobile, updated to the latest Pie OS update, i'm very tech-capable and used to do tier 2 tech support for Verizon. Long story short, I've tried everything in the book including FDR and fresh setup as well as clearing system cache etc. and it's looking like the ONLY solution to get Wi-Fi calling (and subsequently VoLTE that i didn't realize wasn't enabled until researching and checking myself) enabled is to flash the ROM with a T-Mobile OS. Unfortunately i'm coming up negative trying to find the firmware for this phone. Plenty of resources out there for the SM-965U(Snapdragon), but none for the SM-965F(Exynos) as of yet as far as i can tell (and before any ignorance jumps in here as i've seen on other threads, NO the SM-965U software will NOT work on this model phone as it runs a different processor, non-Snapdragon Exynos chipset)
So, that all being said, is anyone out there working on a fix for this, is it likely i'll ever get a fix for this, and/or is the fix already available and I've just completely missed it? Any information or help would be greatly appreciated. Thank you for your time and consideration.
Click to expand...
Click to collapse
I'm currently researching the very same issue... So far i hypothesize , with no knowledge, that if it is rooted, you can then change the csc settings and configure it for TMO, thus enabling WiFi calling. If someone can confirm, that'd be great, otherwise i'm trudging slowly to verify.
Root and use tekhd detonator.
CynicalHeight00 said:
Root and use tekhd detonator.
Click to expand...
Click to collapse
Well i looked at this and it looks like a non-stock rom i'm sure wrought with problems that unfortunately is not helpful. My goal here is to have my phone work and continue to get standard updates with original and licensed (more or less) software and have it actually work. I'm not interested in a full OS replacement pre-loaded with a bunch of adblockers and other crap the designer thought would be useful, just want my standard features enabled and nothing else to change if at all possible. Also, if you believe my statement here is in error please explain, your one line really isn't very helpful, and nowhere on their website is there any description as to what tekhd detonator does / is supposed to do / what it will break. I'm certainly not risking bricking my phone when their own website says under all of its S9+ related material that it's for Snapdragon which the variant i have again doesn't use Snapdragon.
bahruuk said:
Well i looked at this and it looks like a non-stock rom i'm sure wrought with problems that unfortunately is not helpful. My goal here is to have my phone work and continue to get standard updates with original and licensed (more or less) software and have it actually work. I'm not interested in a full OS replacement pre-loaded with a bunch of adblockers and other crap the designer thought would be useful, just want my standard features enabled and nothing else to change if at all possible. Also, if you believe my statement here is in error please explain, your one line really isn't very helpful, and nowhere on their website is there any description as to what tekhd detonator does / is supposed to do / what it will break. I'm certainly not risking bricking my phone when their own website says under all of its S9+ related material that it's for Snapdragon which the variant i have again doesn't use Snapdragon.
Click to expand...
Click to collapse
This is going to be a hassle trust me. even with the Snapdragon models from different CSCs VoLTE and Wifi Calling do not carry over. An ATT 965U would have to be reflashed with the TMobile CSC and USERDATA files to get access to TMobile features. U are trying to do this with an Exynos model. I think you would have to root and install a custom firmware that has the TMobile USERDATA embedded.
Good luck.
can the U1 be flashed to the verizon u firmware? i thought i read someone tried this, but suspected it didn't work because he had previously used the phone with verizon with the unlocked firmware...
methcat said:
can the U1 be flashed to the verizon u firmware? i thought i read someone tried this, but suspected it didn't work because he had previously used the phone with verizon with the unlocked firmware...
Click to expand...
Click to collapse
You can flash the G965U onto the G965U1 and vice versa. It's been well documented that this will let us go from one carrier firmware to another as well as let us have the unbranded carrier firmware. The only catch to this is the bootloader version of the firmware your wanting to flash. The firmware one wishes to flash must have a bootloader version equal too (or greater then) what is currently on the phone.
If your trying to ask about flashing the U1 onto an exynos variant then the answer is definitely no. You can't flash firmware from a different model onto a different model.