I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
RockStar2005 said:
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
Click to expand...
Click to collapse
If US software is not needed, that's is perfect. Anyone can confirm please?
tiunilohmu said:
If US software is not needed, that's is perfect. Anyone can confirm please?
Click to expand...
Click to collapse
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
RockStar2005 said:
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
Click to expand...
Click to collapse
Thanks for your info. Have you tried yours with at&t?
YW!
I haven't, but I started this thread which discusses both AT&T and T-Mobile and the XZ3. I suggest you check it out! Though it mainly looks at the single SIM H8416 version.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I have this model on AT&T but haven't flashed the US firmware. VoLTE is not available on the Taiwan firmware.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
iArvee said:
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
Click to expand...
Click to collapse
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
RockStar2005 said:
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
Click to expand...
Click to collapse
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
iArvee said:
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
Click to expand...
Click to collapse
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
RockStar2005 said:
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
Click to expand...
Click to collapse
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
iArvee said:
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
Click to expand...
Click to collapse
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
RockStar2005 said:
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
Click to expand...
Click to collapse
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
iArvee said:
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
Click to expand...
Click to collapse
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
RockStar2005 said:
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
Click to expand...
Click to collapse
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
iArvee said:
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
Click to expand...
Click to collapse
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
RockStar2005 said:
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
Click to expand...
Click to collapse
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
iArvee said:
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
Click to expand...
Click to collapse
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
RockStar2005 said:
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
Click to expand...
Click to collapse
Are you flashing the H9493?
Please let us know how it goes. If possible test out at&t too.
Related
THANKS GOD. FINALLY REPAIRED!!!
@DevShaft Check the attachments bro
I just would like to thanks so much Sony Repair Center in Laredo TX US for repairing my phone in just 4 days.
Usually It takes 14 business days, and for non-US takes more. ( mine is non-US version)
My phone is covered with warranty thou. Now, the phone looks like a brand new unit, and I'm so happy and satisfied with the service they provided.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The issues was:
-Unknown baseband, no IMEI, wifi doesn't turn on (radio functions wasn't working)
-The phone freezes and reboot Itself when updated to 4.2.2 or 4.3. so It was stuck on 4.1.2
In the attachments below:
-STATEMENT OF WORK
-My Xperia Z after the repair
NB:
The old mainboard was manufactured on 13W17. The new mainboard is manufactured on 13W47
of course the new mainboard's IMEI# matches the printed one on the bottom because they changed It too.
***I hope whoever have the same issues case that I had gets their device repaired***
Good luck guys, and thanks for all the suggestions and help!
Phone repair process summery:
March 13
Repair results thru live chat
March 09
Repair status check thru live chat:
-The attached thumbnails below are for my phone status before I send in for repair.
Open a case with eBay and get a refund.
If the problems were not mentioned in the description, eBay will side with you and make the seller refund.
Sent from my C6603 using Tapatalk
I have the same issue, I fix it with reflashing the rom, but everything start from the beginning.
lepi said:
I have the same issue, I fix it with reflashing the rom, but everything start from the beginning.
Click to expand...
Click to collapse
thx for the reply , but what do u mean everything start from the beginning?
can you please tell me with details, what did u do exactly ? and which firmware build did u flash in ur Z?
what's ur Z model? c6602 or c6603?
if possible provide me with screenshots
thx
kingvortex said:
Open a case with eBay and get a refund.
If the problems were not mentioned in the description, eBay will side with you and make the seller refund.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
thx for the advice... this doesn't work my friend!
@DevShaft please read my thread and give me your help!
i was in your thread about TA partition and I read so many interesting information!
if you have any idea how i can bring back IMEI, baseband, please let me know!
anything that would help me!
thanks alot
Return it. I don't understand why you're messing with it when you're entitled to a full refund.
You have already tried everything that might have fixed it.
As for the TA, editing it (or doing anything except backing up/restoring your own TA image) will result in a hard brick, so that is a dead end.
Sent from my C6603 using Tapatalk
Nidhal AKA the king said:
hello everyone,
I recently bought an Xperia Z C6602 variant (used condition) from ebay, but i didn't know that it has some problems as the onwer didn't mention that...
when i first time inserted my SIM card, it wasn't readable... i went to Settings, About, and i found that baseband is: unkown... also, *#06# shows Blank IMEI... i attached some screenshots below for the phone current state!
in all 4.1.2 builds C6602&C6603, the phone doesn't reboot or freeze.
I'm so familiar in flashing, using flashtool... so as i read in this forum that flashing and/or downgrading with a stock ROMS would fix this problem.. i have done this with many builds on 4.1.2 for C6602&C6603, in first boot i get this screen showing POWER OFF or Use phone, with a message pops up 3 time saying: FACTORY START UP SERVICE - Please wait for POWER OFF button
For versions 4.2.2 & 4.3 phone freeze & restarting itself
i tried to update using PC Companion, SUS, and even Flashtool, after first boot i got that same screen with same 3 repeated messages.. BUT, when welcome screen appears.. the phone dim, and when i click on power it's not turning on, so i restart and try to unlock lockscreen, then, phone freeze and keeps restarting....
N.B: I have never Unlocked Bootloader as you can see it's stats in the screenshots... I have never installed a Custom Rom such as CM..etc. the only thing I did is rooted the phone on a stock ROM and installed CMW.. all was done in Locked bootloader stats!
I've seen many Z users encountered the same issue, but for my case I don't know why and/or how this happened because It's a second hand bought! and the old owner did not mention anything about errors, or issues.
As you read about the phone condition, so you now know everything I went thru ever since i bought!
So, please anyone can provide me with more helpful information, links, repair tool, software...etc that would bring back the IMEI and so Baseband... would be so much appreciated
Please check the screenshots below!
Thanks to anyone in participation to help.
@pbmcmlxxi @Milad.Alef @shekharsuman @Hubriss @yahyaalbadry @mhbmutu
I took the phone to a smartphone repairshop today, when i showed him blank IMEI and unknown baseband he knew the cause of that problem!
The problem is that the original phone's baseband was lost during a sim unlock process, and a wrong baseband were installed instead. the initial (original) baseband MUST BE restored in order to have IMEI, Wifi, and the other radio frequencies back to life.. PROGRESS will take more or less two days! NOT a guarantee to get a successful restore.
in some other cases which it isn't a sim unlock related, but it's still a common problem. when you install a Custom ROM and you don't know what you are messing with, this could damage your original Baseband...and the phone will get bricked!
also, other cases of that issue occurred during update!
so we got two cases in here:
Baseband restore successful = Everything will be back intact.
Baseband restore fail = The phone will remain unrepairable.
Read&Learn:
A baseband processor (also known as baseband radio processor, BP, or BBP) is a device (a chip or part of a chip) in a network interface that manages all the radio functions (all functions that require an antenna). This may not include Wi-Fi and/or Bluetooth. A baseband processor typically uses its own RAM and firmware.
Keep in mind guys, It's still so risky to do a flash customized ROM, and/or unlocking bootloader. so, be very acknowledged of what you're going to do. I believe that rooting on a locked bootloader is the best and safest way to get the best off of your phone as It'll never damage the DRM keys (Digital Rights Management) and TA Partition.
play with everything in your phone but never do with the marked in red files.
If you ran out of warranty, this is probably the best solution to get it fixed if all kind of flashing, updating, or downgrading to stock roms didn't work like in my case.
Please if you know anyone else who has same case like us, just tag him here or send him my link, at least they can make a try. it really worth it.
Thank you all for your participation.
Good luck for us.
Click to expand...
Click to collapse
Hi Nidhal..thanks for tagging me.
I read your post & you seem to suggest that there is way to bring back these "dead" phones back to life.Can you elaborate how you are going about restoring it.I think you & I have the same problems.
What did the tech guys suggest they are going to do with your phone?Do let me know about your progress.I want to give my phone one last shot & if it doesn't work this time, then I'm actually going to go out & bury it in the nearest field. :laugh:
All the best buddy!
Hubriss said:
Hi Nidhal..thanks for tagging me.
I read your post & you seem to suggest that there is way to bring back these "dead" phones back to life.Can you elaborate how you are going about restoring it.I think you & I have the same problems.
What did the tech guys suggest they are going to do with your phone?Do let me know about your progress.I want to give my phone one last shot & if it doesn't work this time, then I'm actually going to go out & bury it in the nearest field. :laugh:
All the best buddy!
Click to expand...
Click to collapse
u welcome @Hubriss, sorry for the late respond, and also sorry to inform u that the phone failed to get repaired!
the only way to get it repaired is at Sony repair center!
if u there is a Sony repair center near your place just send it to them, even if it's out of warranty.. they charge u for a repair fee , but it's still better than to leave the phone unrepairable!
good luck!
kingvortex said:
Return it. I don't understand why you're messing with it when you're entitled to a full refund.
You have already tried everything that might have fixed it.
As for the TA, editing it (or doing anything except backing up/restoring your own TA image) will result in a hard brick, so that is a dead end.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
thanks for the advice!
will send to sony for a repair!
The cause of yours and many other users problem is that you or the previous owner flashed the wrong region baseband or RIL (radio interface layer) for your device. There are so many firmwares to download and flash, it is child's play for anyone who doesn't fully comprehend what he's doing to flash the wrong firmware and get in a lot of sh*t like this. Therefore it is crucial to always be sure you have the correct information and firmware (FTF) for your device as a backup (not to confuse with a recovery made backup that is!).
To solve this issue you need to get a hold on the correct and complete (which includes baseband!) firmware for your device, preferably the one it was running when first purchased, and flash it through Flashtool. That should solve the issue when done correctly
Yours is already at Sony Repair Center, so nothing you can do about it yourself at this point. I'm sure Sony will fix this easily. For your info, this problem you're having has nothing to do with TA.
DevShaft said:
The cause of yours and many other users problem is that you or the previous owner flashed the wrong region baseband or RIL (radio interface layer) for your device. There are so many firmwares to download and flash, it is child's play for anyone who doesn't fully comprehend what he's doing to flash the wrong firmware and get in a lot of sh*t like this. Therefore it is crucial to always be sure you have the correct information and firmware (FTF) for your device as a backup (not to confuse with a recovery made backup that is!).
@Hubriss
To solve this issue you need to get a hold on the correct and complete (which includes baseband!) firmware for your device, preferably the one it was running when first purchased, and flash it through Flashtool. That should solve the issue when done correctly
Yours is already at Sony Repair Center, so nothing you can try yourself anymore. I'm sure Sony will fix this easily.
Click to expand...
Click to collapse
thanks so much for the answer!
it's really helpful, I hope you've had answered It since long time before i send in for repair to sony. and your answer is really rich with information that i didn't get a chance to know despite the deep search i've done in the Google.
i hope for whom who ran out of warranty would try this out. at least i called Sony and they provided the country my phone was branded for!
this is so important to restore the original firmware and bring back baseband and so IMEI!
thanks again bro!
@DevShaft
So, Sony will easily fix my phone without replacing it with another one?
yeah, I thought this would damage the TA Partition or it's related to it! Thanks god it's not!
Nidhal AKA the king said:
@DevShaft
So, Sony will easily fix my phone without replacing it with another one?
yeah, I thought this would damage the TA Partition or it's related to it! Thanks god it's not!
Click to expand...
Click to collapse
I would say it is just a firmware flash for them, since they can retrieve all the info they need about your phone from the IMEI number which is located at the bottom side of the phone. Providing a refurbished one or repair the phone in question is a matter of costs analysis. So yeah, I think they will repair .
DevShaft said:
I would say it is just a firmware flash for them, since they can retrieve all the info they need about your phone from the IMEI number which is located at the bottom side of the phone. Providing a refurbished one or repair the phone in question is a matter of costs analysis. So yeah, I think they will repair .
Click to expand...
Click to collapse
well, for me i'd be happy and satisfied if they will repair the phone or either replace it with a fully working one without any issues!
thx again for the help bro :good:
i looked up the phone SI and after sony told me it's branded for Saudi Arabia, I found these SI numbers/versions below:
Saudi Arabia Generic SA 1270-8384 1270-6726 Saudi Arabia Generic SA 1270-8384 1270-6727 Saudi Arabia Generic SA 1270-8384 1270-6756 Saudi Arabia Generic SA 1270-8384 1270-6757 Saudi Arabia Generic SA 1270-8384 1273-7883 Saudi Arabia Generic SA 1270-8384 1273-7885
hopefully sony will finish the repair asap
Hmm. Now, this is very interesting information.
Every different region's FTF of a specific firmware version that I've flashed/seen all use the same baseband or I should say that the version number of the baseband is identical between regions.
Is this a case of Sony using identical version numbers on basebands that are actually different? If so, they are the only OEM that I've seen do that and it seems highly irresponsible of them or at least that it would cause issues for them internally when working with basebands.
If the above is not the case, could it be that the RIL is different in some way between regions? Someone needs to extract the RIL from different region's firmware and compare them to check that, as this is potentially vital information that should be appended to the thread when people upload FTFs.
If I have time to get to my PC later or at all this week, I'll extract some basebands and RIL from some different firmware versions I have saved and at least run a checksum on them. If I do, I'll post results here.
Sent from my C6603 using Tapatalk
@Nidhal AKA the king I stumbled on this thread more or less by accident after reading your post in the Backup TA thread.
I've got a Xperia T protoype here that is having exactly the same issues. All the screenshots you've posted could be from my phone (does the service menu crash when you try to open configuration?)
I actually only realized it was a prototype when I was about to type the IMEI in to the system of the local Sony contractor to send it in for repair.
"F...." was what I thought in that moment...no free repair for me
@kingvortex I was able to get it working with CM10, which is using the same baseband version as stock roms that don't work. Now that could fire your question about the differences in basebands using the same version numbers, at the same I have no idea what else could be wrong and whether this prototype is maybe even using different hardware components.
Also, flashing stock over CM and skipping the baseband did not help.
Link to my thread with some more information: http://forum.xda-developers.com/showthread.php?p=50901058
@DevShaft adding you just for the heck of it, maybe you've got an idea
Oh, by the way: when I got the phone, it was "running" (should say "stumbling") on branded firmware. I would guess prototypes would rather run on some other fw...
@steeserious
Thanks for the attention in participating in here, well, definitely we got the same issues, also, the service menu under bootloader unlock menu either freeze or gets opened after a while, and you get an FC msg but i click on ''waiting'' and also the sim-lock menu which it takes forever to open, if u are lucky it'll get opened with [?] each case!
except of the other screenshots i posted in the first OP, when i was trying to test the earpiece, under test menu, it freezes until i click on home or return button...
after u installed CM, do u get a beseband, wifi and cellular network working?
Yes, everything was working under CM10, and only CM10. Not 10.1 or 11. Also, Wifi was working with the oldest firmware or when flashing the ICS stock firmware module to the fw versions that didn't work with it.
I'd really like to get to the bottom of the problem though and get a stock rom running smoothly and fully working.
By the way, do they really make you send your phone all the way to the US if you're in Tunisia? Isn't there any local contractor for North Africa?
steeserious said:
Yes, everything was working under CM10, and only CM10. Not 10.1 or 11. Also, Wifi was working with the oldest firmware or when flashing the ICS stock firmware module to the fw versions that didn't work with it.
I'd really like to get to the bottom of the problem though and get a stock rom running smoothly and fully working.
By the way, do they really make you send your phone all the way to the US if you're in Tunisia? Isn't there any local contractor for North Africa?
Click to expand...
Click to collapse
yeah, i have seen custom roms with lots of bundles and options but i'm like u, i prefer the stock, the way it's polished and designed which is more sexier and faster than others...
well, first of all, we do have Sony Stores in here but they don't cover up a device or an electronic wasn't purchased from their store even if it's still under warranty.. but we do not have a sony repair service , cuz if i'd've bought it from one of their stores, they'd've send in to the nearest country with a repair service. let's say, like france.
So, what i did is , i sent an email to Sony customer services claiming my phone problem, but i didn't know the phone is still under warranty... so long story... explained to them that no repair service is available in my country, they advised to send the phone in for a repair, but they needed a valid US address. thanks god I have a friend, talked to them, and they agreed to give their home address... so yeah, provided Sony with a valid US address...etc, got some documents to print out, and RMA# in which they need to determine the phone's case and follow up thru the whole process... so eventually, sent to US TX with an express delivery took almost 5days, then the friend sent it in to Sony repair center in Laredo TX, been contacting sony for checking the phone's status repair, they don't disclose and/or have any detailed info, all they got me is : phone is still under repair, and yesterday i did call, and the ''chat agent'' said, ur phone was shipped, and yeah , my friend will pick it up tomorrow from UPS without knowing if they did repair or NOT, replace it or NOT... no clue bro...
told they , u should've at least send an email to the customer about the phone 's status repair, updates..etc. the agent was like, u will find a paper which contain all the info about the process was done to ur phone. so it's a kinda of a report.
omg so long story.. hope u enjoyed reading it :laugh:
hello please help me i need this programe this programe is only in phone please upload for me this programm my phone is bricked and need flash
https://www.verizonwireless.com/support/knowledge-base-116950/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You opened 2 topics. I answered in another one. Anyway here is the link for program www.motorola.com/verizonsoftwareupdatewin.
Thank you but this program is not the same
This programe cant to repair my phone this programe only install update if not update available so this program cant help me
Please sameone upload this program from the phone
From what I'm seeing, the repair program you linked IS the one for the DTurbo, so I'm not sure what you're looking for. Go download it from the link you provided, and use it.
If you want more advanced repair processes, you're probably looking for RSD flashing using Motorola's RSDLite software. You'll need an RSD-compatible image to flash (you can't use a TWRP or such image). As far as I know, there is no RSD image for the latest Marshmallow release, so you'll probably have to try the older LP version and see if you can apply that. Eg, see this page for info on how to use RSD: https://www.andromods.com/unroot-lo...-moto-droid-turbo-restore-unroot-unbrick.html
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
realbbb said:
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Doesn anybode know how long does it take usually for vzw to push new firmware out? Is there any way to rush it?
Having it as backup would be great, because I know I'll brick it sooner or later xD
hamza_iraki said:
hello please help me i need this programe this programe is only in phone please upload for me this programm my phone is bricked and need flash
https://www.verizonwireless.com/support/knowledge-base-116950/
Click to expand...
Click to collapse
schwinn8 said:
From what I'm seeing, the repair program you linked IS the one for the Droid Turbo, so I'm not sure what you're looking for. Go download it from the link you provided, and use it.
Click to expand...
Click to collapse
Yes, very strange. He provides a LINK to the software and says he needs a link to the software. There's even a choice of Windows or Mac downloads on that very page!
realbbb said:
The software upgrade assistant can do the full firmware, but currently only the lollipop full firmware is available. When Verizon adds the marshmallow firmware, it will do that as well. Just not available yet.
BBB
Red Knot
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Right. Unless your XT1254 bootloader is unlocked Verizon still owns your phone.(Even for those who are not Verizon customers, but are just using the Droid Turbo on other networks.) And they laugh at you.
please help i need this programe
hamza_iraki said:
please help i need this programe
Click to expand...
Click to collapse
You provided the download link yourself. That webpage link has the downloads for both Windows and Mac. Do you not see my screenshots? That arrow is point to the DOWNLOAD LINKS on the web page YOU posted.
Plus, someone already posted the exact download URL, even though it's from the page YOU gave.
Ej?iSixo said:
You opened 2 topics. I answered in another one. Anyway here is the link for program www.motorola.com/verizonsoftwareupdatewin.
Click to expand...
Click to collapse
See? Click that link, and it that program will automatically start downloading.
But that's not going to help you with locked bootloader to reinstall 6.0.1 until Verizon releases full firmware.
Always, always unlock your bootloader before installing any new firmware like this or you may never be able to do it. Plus, if something screws up, with an unlocked bootloader you have more options to fix it than with a locked bootloader.
Thank you sir i download this programe but is not same i can only with this programe upgrade the problem my phone have latest version so i cant upgrade again
Please you can tell option to fix my phone
Thank you
hamza_iraki said:
Thank you sir i download this programe but is not same i can only with this programe upgrade the problem my phone have latest version so i cant upgrade again
Please you can tell option to fix my phone
Thank you
Click to expand...
Click to collapse
This isn't the software (Windows version), here at this link?
http://www.motorola.com/VerizonSoftwareUpdateWin
The problem is you have taken the 6.0.1 OTA on a locked bootloader and Verizon has NOT yet released the full firmware version. You cannot use this tool until they do. See this quote from the Software Upgrade Assistant website?
The most recent software version (full firmware) will be available on the SUA/SRA tool within a week of a new software update. During this time, the SUA/SRA is unavailable for usage.
Click to expand...
Click to collapse
Obviously, it's been well over a week since 6.0.1 was released for the Droid Turbo -- but Verizon doesn't care. If they did, they wouldn't demand Motorola keep the bootloader locked in the first place! Motorola give free bootloader unlock codes for all the other Quarks (XT1250, XT1225). Only Verizon demands locked down bootloader for their variant. And then they have this OTA repair software which doesn't work unless they provide the full firmware to go along with it.
I'm sorry Verizon still controls your phone. With an unlocked bootloader we could help you. Right now you have to wait until Verizon posts the full firmware.
He can try using the repair function with the software
ChazzMatt said:
This isn't the software (Windows version), here at this link?
http://www.motorola.com/VerizonSoftwareUpdateWin
The problem is you have taken the 6.0.1 OTA on a locked bootloader and Verizon has NOT yet released the full firmware version. You cannot use this tool until they do. See this quote from the Software Upgrade Assistant website?
Obviously, it's been well over a week since 6.0.1 was released for the Droid Turbo -- but Verizon doesn't care. If they did, they wouldn't demand Motorola keep the bootloader locked in the first place! Motorola give free bootloader unlock codes for all the other Quarks (XT1250, XT1225). Only Verizon demands locked down bootloader for their variant. And then they have this OTA repair software which doesn't work unless they provide the full firmware to go along with it.
I'm sorry Verizon still controls your phone. With an unlocked bootloader we could help you. Right now you have to wait until Verizon posts the full firmware.
Click to expand...
Click to collapse
Interesting.. When did MM OTA started rolling out approximately?
I tried software myself and there indeed isn't option for "repair" , it simply says phone is up to date. Maybe it has to be on older ver SW or when they release firmware more options will pop out..
From this quote it seems to me that even when full firmware gets out it will only be available through SUA/SRA until somebody doen't extract it somehow.
Or VZW has place where it publishes firmwares?
I'm getting deeper with my downgrading experiment and it's just a matter of time when I'll brick phone.
koftheworld said:
He can try using the repair function with the software
Click to expand...
Click to collapse
He can TRY, but it won't work. Until Verizon realists releases the full firmware. I sound like a parrot, I keep repeating the same answer over and over. I'm sorry people don't like the answer.
It really depends on what exactly he did and what is wrong. Most likely he will need the full firmware, but that is exactly why I stated TRY. I appreciate that you are on here a lot answering questions, but please keep the snark down.
koftheworld said:
It really depends on what exactly he did and what is wrong. Most likely he will need the full firmware, but that is exactly why I stated TRY. I appreciate that you are on here a lot answering questions, but please keep the snark down.
Click to expand...
Click to collapse
Read my post with the quote directly from Motorola and Verizon and I clearly explained why it will NOT work right now, and exactly when it would start working.
Also, we know exactly what he did. He has a locked bootloader with 6.0.1 and tried downgrading via ADB to Lollipop. He's screwed up his phone and he also bought a phone with a "locked Google account". Ignoring the fact the phone may be "lost" or stolen, we are still trying to help him.
He's posting in two different threads about the same thing and we've been trying to help him -- but at this point he can only wait for the full firmware:
hamza_iraki said:
hello please help me i have phone xt1254 but not worked i need flash my phone with fastboot but the problem my bootloader is locked
please this my informations about my phone . i can flash my phone without unlock bootloader?
Click to expand...
Click to collapse
hamza_iraki said:
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
Click to expand...
Click to collapse
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
ChazzMatt said:
Read my post with the quote directly from Motorola and Verizon and I clearly explained why it will NOT work right now, and when it would start working.
Click to expand...
Click to collapse
I understand completely, and I'm saying that if the repair option is available he can try it. I'm going to to be so glad to not have this phone anymore so that I don't have to read your posts.
koftheworld said:
It really depends on what exactly he did and what is wrong.
Click to expand...
Click to collapse
We know exactly what he did. It's not a mystery. But besides him...
Most of these people bricking their phones on the 6.0.1 OTA are installing the OTA, then either
1) trying to install the OTA file again to "fix" something or
2) trying to downgrade back to Lollipop.
See this thread from a week ago for examples of both. I could show you even more if you wish. Like here:
babalovemaker said:
i updated twice and now holding a bricked driod turbo with bootloader locked. no back and no solution to downgrade or install yet
Click to expand...
Click to collapse
(If they had UNLOCKED bootloaders with TWRP installed, we could help them.)
Or third cause of bricking is ...
3) trying to install OTA on an encrypted phone.
Initially, encrypted phones couldn't handle the 6.0.1 OTA. Verizon paused the 6.0.1 OTA rollout for a few days, told people with bricked phones to send them in for replacement, and then resumed the OTA rollout -- without ever confirming they fixed the issue.
For the first two points, you can't reinstall OTA update again on a locked bootloader as it's basically only a partial firmware file which looks for the previous Lollipop firmware.
You also can't downgrade from Marshmallow back to Lollipop on a Droid Turbo locked bootloader.
Even if the cause was neither of those two scenarios -- or the encryption problem, it doesn't matter. Regrettably, his phone is a brick until Verizon decides to release the full firmware. Then he and others can use the Repair Assistant or flash via RSD. That's been said time and time and time again.
Or unless some dev comes up with some magic?
This situation has been going on for for WEEKS, in various threads with several people. Maybe you haven't kept up?
I feel very sorry for him, but there's nothing we can do.
Here's what he says the reason is:
hamza_iraki said:
hello please help me i have phone xt1254 but not worked i need flash my phone with fastboot but the problem my bootloader is locked
please this my informations about my phone . i can flash my phone without unlock bootloader?
Click to expand...
Click to collapse
hamza_iraki said:
first i buy this phone locked with google account access and after i try to flash my phone with other firmware with fastboot mode
now my phone is bricked i can only enter to recovery and fastboot
please samone give me rom for adb flash i need original firmware
Click to expand...
Click to collapse
hamza_iraki said:
I have latest version 24.81.5 6.0.1
I need official rom 24.81.5 with adb or fastboot
Click to expand...
Click to collapse
And THAT has not been released yet. OK? This has already been discussed many, many, many times over the past few weeks. New people coming in with this problem are not aware and we are having to give them the bad news.
It's Verizon's fault for not making the full firmware available.
---------- Post added at 07:05 PM ---------- Previous post was at 06:55 PM ----------
koftheworld said:
I'm going to to be so glad to not have this phone anymore so that I don't have to read your posts.
Click to expand...
Click to collapse
Look, I don't know everything. I'm not a dev. But I try to help people and I have helped lots of people. I do tons of research for my answers or it's based on hard won experience.
If I don't know an answer, I'm not going to pull one out of thin air. My answers are based on facts or personal experience.
I'm the one two years ago who pointed out the XT1250 = XT1254 (same radio bands, same FCC ID)when Verizon Droid Turbo owners didn't even know about that or even wanted to admit it -- and Verizon was lying through their teeth they had a worldwide exclusive, when they didn't even have a U.S. exclusive. I proved it to all the naysayers. I knew this because of my research/knowledge of the U.S. cell phone industry.
I'm the one who found the XT1225 had LTE band 5 (which AT&T uses) and HSPA band IV (which T-mobile uses) by doing modem software scan when Motorola didn't want to initially admit it. They left those bands off the official specs for some reason. (I know why, but too long a story for here.)
If I do answer and I even post direct links to manufacturer/carrier statements (research), and then someone else comes along right behind me and says the exact opposite -- then yes I will probably point out that is not correct answer.
But I'm always glad to help.
The reason for the confusion is that the GUI of the update assistant has been redesigned and it no longer looks like the screenshots that were provided in the OP. However, it still performs the same functions as the old version.
I recently bought what was supposed to be a "NEW Unlocked" Note 8 from seller on Ebay and when it arrived, I noticed that it was a few updates behind so I connected it to my WiFi and attempted to update it, but I received this error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I contacted the seller, but they were not helpful at all, so I installed the Phone INFO ★SAM★ app by vndnguyen to research the issue myself. The information the app provided was really confusing to say the least. First of all, the phones settings menu shows that the phones model number is SM-950U (US Market).
The model number provided by app however is SM-9500 (Chinese / Hong Kong Market)
Adding to that confusion, the phone seems to have both US and Chinese firmware components installed on it as shown by the following screenshot:
The CSC codes all seem to point to the phone originally being created for the Hong Kong market as shown in this screenshot:
However, when I checked the phones IMEI number, it comes back that it was originally a T-Mobile phone. Maybe that was just the last carrier that the IMEI was registered to I am not 100% certain about this, but there is definitely something very odd about this phone and so my questions are:
1.) Is there anyway (without tearing the phone apart) to tell exactly what model this phone is (950U or 9500) ?
2.) Why would anyone alter the phone like this / what advantages are there to doing this ?
3.) Is there anyway to actually update this device ?
mtcellph said:
3.) Is there anyway to actually update this device ?
Click to expand...
Click to collapse
You could update it with odin. It looks like the update center downloaded the wrong update.
SnowFuhrer said:
You could update it with odin. It looks like the update center downloaded the wrong update.
Click to expand...
Click to collapse
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
mtcellph said:
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
Click to expand...
Click to collapse
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
MrMike2182 said:
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
Click to expand...
Click to collapse
I doubt it's fake, just had some alterations on it. @mtcellph to see the model of the phone, boot into download mode. It should say.
--
@MrMike2182
I already got a refund from Ebay and they told me to keep the phone too so I am not worried about bricking it or anything like that.
@SnowFuhrer
This is the information from my Download Mode screen:
It shows the Carrier as TMB (T-Mobile) which would in theory be a SM-N950U model device, but I hoping more for an actual model number so I could be sure. Any other way to get a more definite answer would be welcome.
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
You might be right, but I would still like to update it if possible because everything else works on the phone.
Again if anyone has any sort of advice on figuring this mystery out, I would love to hear it.
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
iceepyon said:
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
Click to expand...
Click to collapse
So what is the use of it?
SnowFuhrer said:
So what is the use of it?
Click to expand...
Click to collapse
Most 3rd party device repair specialist would use working parts from similar devices to make a new device and sell it on for a profit.
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
From what I know the majority of the components used in the Note 8 are interchanged able with the exception of the SOC, motherboards and modems. While both the N9500 and the N950U run on the same SOC, they do not utilize the same modems. Which maybe what is causing your issue.
mtcellph said:
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
Click to expand...
Click to collapse
I really wouldn't flash anything to it period! Simply because you can't flash one hardware piece with the N9500 and then try to flash the N950U hardware piece because it doesn't work like that! If anything is going to work it would most likely be the unlocked N950U1 firmware but I would tread cautiously because if your modem needs N9500 and your board/CPU needs N950U it's just going to mess it up!
Edit: Also about wanting to update just for the security patch, it's highly unlikely that you'll EVER be the target of such security breaches.. Ask around, if you're not rooted it's seriously HIGHLY UNLIKELY!
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
SnowFuhrer said:
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
Click to expand...
Click to collapse
Yeah. But you would have to be extremely skilled in doing so.
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
mtcellph said:
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
Click to expand...
Click to collapse
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
SnowFuhrer said:
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
Click to expand...
Click to collapse
Thanks for the reply & I think so as well because I am just updating the version that is already flashed on the phone and the PDA is what contains the Android security updates I need if I not mistaken.
This seems like it would be a fairly trivial process, but other users have stated it's more difficult than it seems so I'm curious why they have come to that conclusion.
I think I'll give it a few more days to see if anyone else responds before moving forward just to be on the safe side.
Hi
I got the Xperia XZ1 Compact GO-02K Docomo. Can I flash G8441 firmware?
are you sure?
+1
did you find somethig
Its possible?
Does anyone know if this is possible?
I'm going to bump this, since I just got one of these phones (I'm in the US) and I want to get rid of all the Docomo junk and maybe go to a nice ROM.
Edit: I just found out that (unsurprisingly) the phone says that it is unable to have the bootloader unlocked. Is there a way to circumvent this? I've seen mentioned elsewhere that I still may be alble to root.
Hi,
I've got one of these too, and I'm trying to switch to a customized G8441 rom. I can't flash it with newflasher , i've got this error:
- Uploading signature C:\Users\USER\.flashTool\firmwares\Downloads\G8441_Customized FR_1310-8853_47.2.A.11.228_R4C\partition\partitionimage_0.cms
signature:0000053c
Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms
I dont know what it mean and i don't want to modify some firmware files to brick my phone.
I've read XZ1 JAPAN (SOV36) can be switched to global (G8431), so I assume it's possible too for XZ1 compact (SO_02k and G8441) because there are identical hardware.
Nosfay said:
Hi,
I've got one of these too, and I'm trying to switch to a customized G8441 rom. I can't flash it with newflasher , i've got this error:
- Uploading signature C:\Users\USER\.flashTool\firmwares\Downloads\G8441_Customized FR_1310-8853_47.2.A.11.228_R4C\partition\partitionimage_0.cms
signature:0000053c
Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms
I dont know what it mean and i don't want to modify some firmware files to brick my phone.
I've read XZ1 JAPAN (SOV36) can be switched to global (G8431), so I assume it's possible too for XZ1 compact (SO_02k and G8441) because there are identical hardware.
Click to expand...
Click to collapse
Thanks for posting, I'd really like to get this working. The SO-02Ks are fairly cheap and easy to get on ebay compared to the G8441, at least in the US so there would be significant value in finding a solution.
At this point I've lowered my standards from wanting to put a ROM on it, to just rooting so I can remove Docomo bloatware, to now where I'd just be happy being able to flash some US firmware onto the thing so I can at least send MMS messages.
I've got a brand new one for 230$ instead of 400$ for the global version, yes it's really cheap
You don't need root to remove bloatware, just read this guide.
But if you really want root (temporary only), you can flash rom 47.1.f.1.105 (android 8.0.0 ) and follow that . I did it but go back to 9.0.0 because camera wasnt working (something about drm key I think but I don't know that much about smartphone).
The only thing annoying is camera shutter sound I can't disable now.
Here is a bloatware list, just chekck if you need or not some app.
Nosfay said:
I've got a brand new one for 230$ instead of 400$ for the global version, yes it's really cheap
You don't need root to remove bloatware, just read this guide.
But if you really want root (temporary only), you can flash rom 47.1.f.1.105 (android 8.0.0 ) and follow that . I did it but go back to 9.0.0 because camera wasnt working (something about drm key I think but I don't know that much about smartphone).
The only thing annoying is camera shutter sound I can't disable now.
Here is a bloatware list, just chekck if you need or not some app.
Click to expand...
Click to collapse
Thanks for the bloatware uninstall stuff, that's fantastic! I gave up on rooting because I didn't want to go back to 8 and have DRM key issues. I do really need to get MMS working on this phone though, and as far as I can tell, it needs US firmware to be able to do that.
Have any of you read this - https://forum.xda-developers.com/xperia-xz1/help/xz1-sov36-t3916251
Hi, this isnt for compact xz1 (so-02k). I'va already tried and newflasher wont let me use global rom because of différent signature.
Has anyone found a way around the MMS messages being blocked on the SO-02K? Unlike what other's have said, using a different app like the google app does not solve the problem. I get an "MMS not available on network" message when I try to send something (regardless of whether the phone is on a network or not when I try to send it) and I cannot receive group messages. SMS works fine. This is really my only issue with this phone right now, so if anyone has any idea of why this might be the case we might be able to look for a way to circumvent it.
Nosfay said:
Hi, this isnt for compact xz1 (so-02k). I'va already tried and newflasher wont let me use global rom because of différent signature.
Click to expand...
Click to collapse
The point is have you read it and tried anything from it? Those with the device need to try any and all suggestions.
Yes, I've already read this topic, but I can't even flash my phone with global rom, newflasher doesn't allow it and I didn't found someone who success to.
Those with XZ1 (sov36) are not facing this issue and can flash global or JP rom.
Try an older version of Newflasher, a different rom, or try flashing different sin files to see if that gets you any further.
I've tried three différent version and many roms.
I dont want to modify sin files because I dont want to brick my Phone, I'm not confident enough?
I'll deal whith jpn rom, I'm fine with it actually.
Nosfay said:
I dont want to modify sin files because I dont want to brick my Phone
Click to expand...
Click to collapse
You don't need to modify them, you just need to flash them.
I dont get it, how am i supposed to do this? Replace sin files from global firmware by japanese ones? Is there a risk to brick my phone?
Nosfay said:
Replace sin files from global firmware by japanese ones? Is there a risk to brick my phone?
Click to expand...
Click to collapse
Replace Japanese ones with global. Have you tried flashing a global kernel first with fasboot and then the software. The chance of bricking your phone from flashing FW is slim to next to none.
SXUsr said:
Replace Japanese ones with global. Have you tried flashing a global kernel first with fasboot and then the software. The chance of bricking your phone from flashing FW is slim to next to none.
Click to expand...
Click to collapse
Yes I've tried with flashboot, but SO-02K is missing from device list and when I select G8441 with global or jpn firmware, it doesnt work.
Here's a free How-To on how i successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022 that was carrier locked to Verizon and now fully Unlocked.
DISCLAIMER:
*This does NOT trip Knox or Void your warranty and does NOT require a root or a paid service. **This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.***This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
You can read more on how this method works to force a carrier update to your device, here, on the Official Android dev site.
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here, Stock Firmware and ODIN Flashing Guide (XDA) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•(Optional?) Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process. Link: Android Dev Platform Tools (Official)
Step 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
NOTE:
It Is CRITICAL that we flash the U1 rom BEFORE putting in the desired carriers SIM, then reboot, let phone fully boot, ONLY THEN should we insert the desired carriers SIM.
Step 1b:
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE.
IMPORTANT! MAKE SURE YOU DOWNLOAD BOTH THE "U" ROM FOR THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED (XAA) ROM/Firmware.
IF YOU ALREADY HAVE U1 FIRMWARE
I.e "SM-G998U1xxxxxxx" - you can skip to step 2, but I would recommend reading through the next part.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm the device is now showing the "U1_XAA" in the Service Provider Software Version - it should say something like "SM-G998U1_XAA blah blah blah" - you just want to see the "U1" bit.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device.
! CRITICALLY IMPORTANT STEP !
We will now initiate a reboot, but BEFORE the device fully restarts, we need to force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold them directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery, please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select & Execute.
AGAIN, Very Important step! We MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, we need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in, essentially it should remain plugged in throughout this process.
We should now be back in download mode and be on "U1" as we have verified in the steps above.
STEP 3:
Now it's time to flash the ROM/Firmware from the carrier you wish to use. Make SURE you have the SIM from the same carrier inserted during this process as mentioned at the beginning. It doesn't need to be a working or activated SIM, just simply one from the carrier you wish to have this S21 work on.
Flash all items from the "U" ROM/Firmware as you did earlier, ensuring to use the "U" ROM/Firmware for your desired carrier as described above. Same deal with CSC here, DO NOT use the "Home_CSC", use the other.
BE SURE that you use the USERDATA file that comes with the "U" ROM/Firmware. Its Critical in order to get the phone working properly on the new carrier.
Start the Odin flashing process & wait.
Phone will Auto-Reboot.....
Done!
You should now be on the carrier you wish to use.
This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung.
Please comment your experiences/ issues etc below. Don't be afraid to ask for clarity of something.
PoC, results after doing above process pictured in this screenshot.
Good luck.
-k0mrade
Send me Crypto if I helped?
Before process, this message would appear shortly after inserting a new SIM in testing devices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After preforming above procedures I now find pictured below by running this activity:
com.samsung.ssu.unlock.MainActivity
And verify twice by checking my work in Settings>About>Software Information> Service Provider Software Version & Carrier Configuration Version.
For anyone whos still having trouble, try following the directions on this thread. Maybe they explain it a bit better or their process omits/includes parts ive missed.
Alternative Guide To Carrier Unlocking S21
Good Luck.
-
Have you attempted this on lower bootloader revisions?
iBowToAndroid said:
Have you attempted this on lower bootloader revisions?
Click to expand...
Click to collapse
I have not. But am very interested to see how it goes if you or anyone decides to give it a shot, it SHOULD work on any BL considering the method of attack. But I can't verify it does.
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason CCT remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
xDpakaX said:
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason XAS remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
Click to expand...
Click to collapse
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
What's the Baseband Version?
iBowToAndroid said:
What's the Baseband Version?
Click to expand...
Click to collapse
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
iBowToAndroid said:
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
Click to expand...
Click to collapse
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Yep then you're screwed. It can't done if Knox is tripped
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Is it still unlocked and rooted? That would make life another easier. We can repair the IMEI, baseband etc. It's worth a go if the phones just a paper weight right now imo. But ultimately up to you.
K0mraid3 said:
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Click to expand...
Click to collapse
Thank you! I'll give it a try and report how it goes.
Good luck! Worst case, look up a program called "Samsung TFT Module", just be sure to scan it for viruses and bad code if you have the ability.unless you are able to find the 2022 update of it, you'll have to settle for whatever version is available. It'll likely be old, clunky and out-of-date, half the program defunct, but a few key parts still work, and quite well. Don't forget ADB drivers. Let us know how it goes!
Proverbs2 said:
Thank you! I'll give it a try and report how it goes.
Click to expand...
Click to collapse
Ok, I tried to follow each step carefully, but I had to make one minor change to the procedure: after flashing the U1_XAA firmware, I had to power off the phone in order to insert the SIM card. (In the XCover Pro, the SIM card slot is obstructed by the battery, so there is no way to insert the card without powering off the phone and removing the battery.) After inserting the card, I booted directly into recovery and followed the other steps from there.
Unfortunately, it didn't work for me: the phone is still locked, showing the same message: "Sorry, your device can't be activated on another carrier's network..." Perhaps that's because I wasn't able to perform that one critical step, inserting the sim card while the phone is turned on. Any suggestions for a workaround?
K0mraid3 said:
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Click to expand...
Click to collapse
Yes, I followed the guide. The problem is that when I'm on U1 my phone doesn't ask me to reboot.
Hello. I did all on VZW SQU3AUDB phone. Did all steps.
I have question. But in first start after step 3 (i flash G998U VZW) i see: Sorry, your devic.... verizon message
STEP3: Now it's time to flash the ROM/Firmware from the carrier you wish to use
It min - i need to flash not VZW ROM? some other? I need to use Ukrainia operator sim. Or i need flash G998W or else?
can someone help me?
Does my bootloader need to be unlocked