Related
Update: so far, described method doesn't unlock other bands. Need to find other ways.
Disclamer: You are doing this at your own risk.
The key point: Allowed bands are written in /system/vendor/firmware/telephony/ze550ml_XX_726x.tlv where XX is your region TW, WW, US, CN, etc.. Don't confuse by ze550ml in the name. It's for ZE551ML! I don't know how it is in ZE550ML, but should be the same according to name.
Region is hardcoded in SFI table OEM1. SFI is similar to ACPI found in PC. Flashing of firmware doesn't change this part. You may change firmware region to whatever you want, but region of your phone will remain the same and 4G band will remain the same as you had out of the box.
Since bootloader is locked, we cannot spoof SFI tables in kernel. But we can replace /system files.
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
Open file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and replace text inside ze550ml_TW_726x.tlv to ze550ml_WW_726x.tlv. Or you can copy file /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml.
Don't forget to reboot your phone before try 4G.
Unfortunately, i cannot test it by myself because my carrier work on 1800MHz which presents in all regions. So, i simply won't see any difference between regions.
Please report here about results.
Will hopefully be able to try it this weekend on my CN version (still need to root and update firmware first) and will report back!
So far, no go. Still trying to make sure I did it right but I believe I did. Still only seeing H+ and if I change it to LTE Only in the Device information menu I get no signal whereas I still had a LTE signal on my Nexus 4.
I did the following:
Copy file /system/etc/catalog/V1_DSDA_ZE550ML_US/telephony_config/V1_DSDA_ZE550ML_US_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_CN/telephony_config/V1_DSDA_ZE550ML_CN_726x.xml
EDIT: I did get an LTE signal quickly after I set the preferred network type to LTE only, but once I set it back to LTE/GSM auto it went away. Still trying to get t back but so far nothing.
Need to wait for bootloader unlock. In this case, it's possible to compile custom kernel with spoofed region.
All this is based in theory that hardware in all region are the same. If hardware different, then change of region is impossible.
hkdmjack said:
EDIT: I did get an LTE signal quickly after I set the preferred network type to LTE only, but once I set it back to LTE/GSM auto it went away. Still trying to get t back but so far nothing.
Click to expand...
Click to collapse
But if you don't change files, setting LTE-only doesn't give you LTE signal?
update: check folder /local_cfg/telephony_config
check if your changes reflected there. If not, then change xml file there.
don't forget to reboot.
Ok lets see if i am reading this right.
IF this works does it mean i can buy a China . CN . Zenfone 2 and them make it into a WW version so all 4 bands work ?
I am in the UK and need all 4g bands to work.
jacko5 said:
Ok lets see if i am reading this right.
IF this works does it mean i can buy a China . CN . Zenfone 2 and them make it into a WW version so all 4 bands work ?
I am in the UK and need all 4g bands to work.
Click to expand...
Click to collapse
The key word is "IF". Still no confirmation. May be need more changes. There is region mention also in /factory partition.
sorg said:
But if you don't change files, setting LTE-only doesn't give you LTE signal?
Click to expand...
Click to collapse
As far as I could tell. I got a weak signal on band 4 after making the changes, but I guess not strong enough that it's not connecting or drops pretty much right away if I'm reading the results from my LTE Discovery app right.
sorg said:
update: check folder /local_cfg/telephony_config
check if your changes reflected there. If not, then change xml file there.
don't forget to reboot.
Click to expand...
Click to collapse
Yup, rebooted but will try this tonight if I can find the time.
Screenshot is what I see in LTE Discovery when I set preferred network to LTE. It shows band 12 and earlier I saw band 4. Only difference is I performed the first suggestion this time, but I didn't revert my earlier change. It looks like I'm getting these two bands now but if you look up too there is no network connection.
By first suggestion I mean this:
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
I basically copied everything from ze550ml_US_726x.tlv to ze550ml_CN_726x.tlv.
Strange.
Oh, and I did check that other file and my initial change appears there as well.
Quick update. This morning as I was driving to work I saw the data indicator change from H/H+ to 4G a few times. I tried to run speedtest while on 4G, and got up to ~ 32 Mbps down but it did not work when speedtest tried to test the upload speed. Unfortunately it was only in a small area so I had it for all of 15 minutes or so.
hkdmjack said:
Quick update. This morning as I was driving to work I saw the data indicator change from H/H+ to 4G a few times. I tried to run speedtest while on 4G, and got up to ~ 32 Mbps down but it did not work when speedtest tried to test the upload speed. Unfortunately it was only in a small area so I had it for all of 15 minutes or so.
Click to expand...
Click to collapse
In /factory partition, there is several mentions of region.
/factory/PhoneInfodisk/country_code
/factory/PhoneInfodisk/PhoneInfo_inf
These files are not text, but binary. So, you need HEX editor to modify (region is coded by letters as usual TW, WW, CN, etc.).
And don't forget to backup these files, because it's not part of a firmware. If you lost/tamper them, then only backup copy can save you.
I recommend to backup whole /factory folder to be safe.
sorg said:
In /factory partition, there is several mentions of region.
/factory/PhoneInfodisk/country_code
/factory/PhoneInfodisk/PhoneInfo_inf
These files are not text, but binary. So, you need HEX editor to modify (region is coded by letters as usual TW, WW, CN, etc.).
And don't forget to backup these files, because it's not part of a firmware. If you lost/tamper them, then only backup copy can save you.
I recommend to backup whole /factory folder to be safe.
Click to expand...
Click to collapse
Thanks for the recommendation. I've been making backups of each file that I edited, just in case. Anyway tonight going to try a hard reset tonight because I've been having some other issues, then reflash the pre-root image and go from there.
sorg said:
Disclamer: You are doing this at your own risk.
The key point: Allowed bands are written in /system/vendor/firmware/telephony/ze550ml_XX_726x.tlv where XX is your region TW, WW, US, CN, etc.. Don't confuse by ze550ml in the name. It's for ZE551ML! I don't know how it is in ZE550ML, but should be the same according to name.
Region is hardcoded in SFI table OEM1. SFI is similar to ACPI found in PC. Flashing of firmware doesn't change this part. You may change firmware region to whatever you want, but region of your phone will remain the same and 4G band will remain the same as you had out of the box.
Since bootloader is locked, we cannot spoof SFI tables in kernel. But we can replace /system files.
So, if you have rooted Zenfone 2, then you can copy ze550ml_WW_726x.tlv to ze550ml_TW_726x.tlv if you want to convert TW model to WW model. (Similar for CN->WW). You need to open /system partition for write access (R/W). You can do everything in Root Explorer.
It may be that ze550ml_XX_726x.tlv files are protected by check-summ and name, so replacing the file my brake radio functionality. In this case you have to return you original ze550ml_XX_726x.tlv file and try another method described below.
Open file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and replace text inside ze550ml_TW_726x.tlv to ze550ml_WW_726x.tlv. Or you can copy file /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml to /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml.
Don't forget to reboot your phone before try 4G.
Unfortunately, i cannot test it by myself because my carrier work on 1800MHz which presents in all regions. So, i simply won't see any difference between regions.
Please report here about results.
Click to expand...
Click to collapse
Thank you for this information. I do not have a rooted ze551ml is there a way to root the ze551ml yet? I may have to attempt this when I get the moment. For now I will be monitoring this thread.
Mine is WW, I am in the US and I only get H+
sorrow777 said:
Thank you for this information. I do not have a rooted ze551ml is there a way to root the ze551ml yet? I may have to attempt this when I get the moment. For now I will be monitoring this thread.
Mine is WW, I am in the US and I only get H+
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Another quick update. I did both the first and second method in the first post, and LTE pops up sporadically. After doing the first method I lost signal (I wasn't even prompted to enter in my SIM PIN) until I also applied the second method, both times copying over the WW text over to the CN file. I've seen both band 2 and band 4, but it cuts in and out and the speeds are slow where I currently am. H+ also cuts in and out so I'm starting to wonder if I possibly got a phone with a bad radio. Ugh.
hkdmjack said:
Another quick update. I did both the first and second method in the first post, and LTE pops up sporadically. After doing the first method I lost signal (I wasn't even prompted to enter in my SIM PIN) until I also applied the second method, both times copying over the WW text over to the CN file. I've seen both band 2 and band 4, but it cuts in and out and the speeds are slow where I currently am. H+ also cuts in and out so I'm starting to wonder if I possibly got a phone with a bad radio. Ugh.
Click to expand...
Click to collapse
At which frequency bands does your ISP transmit FDD-LTE data?
Does anyone know why I can make calls but not receive them on my zenfone2 ? I have a T-Mobile Sim but I can do everything else just not receive call I need some help
Sent from my ASUS_Z00AD using XDA Free mobile app
graphO said:
At which frequency bands does your ISP transmit FDD-LTE data?
Click to expand...
Click to collapse
I'm receiving LTE signal on bands 2 and 4, but more prevalently 4.
And how can you see which LTE band is working?
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
What made your device hard brick
Sent from my SM-N910G using Tapatalk
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.
C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.
Says the file is gone
Sent from my SM-N930W8 using XDA Labs
It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792
yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot
i have same problem does any one sucess with this process ?
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?
same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.
Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?
yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution
Hey guys i need a ROM for Tab4 10 Plus (TB-X704L) .zip file because it is in a bootloop.
If you have the European wi-fi only version - http://lenovo-forums.ru/files/file/...s-proshivka-tb-x704f_s000037_170703_row_qfil/
If you have the European LTE version - http://lenovo-forums.ru/files/file/...s-proshivka-tb-x704l_s000035_170703_row_qfil/
If you have a Chinese tab you're SOL. Contact Lenovo.
They're in 7z format but any half-decent compression software made in the past decade will open it. WinRAR works, as does 7zip.
Read the page carefully. The files have a password, it is on the respective page. You will need to flash with QFIL, there are tons of guides on XDA telling you how to do this so I won't. Also this is at YOUR OWN RISK! I cannot personally help you further with your tablet because I don't have it.
Good luck!
I recently got not one, not two, but three ebay E5823's and was having trouble connecting to T-Mobile bands (3G and 4G) in the US
digging in, I managed to get into the service menu and discovered that the bands I need are disabled. Note that the phone remains on Edge all the time
I've read old threads like this https://forum.xda-developers.com/cr...ad-progress-please-leave-im-updating-t2871269 and this https://forums.oneplus.com/threads/...-qualcomm-devices-oneplus-one-edition.193610/ about unlocking certain disabled bands on Qualcomm devices, however all of the download links for the QXDM software seem to have disappeared. I did manage to find a copy of QPST but I'm not sure I trust it.
Qualcomm
I've tried flashing US and German firmware from the xperia-flashtool, but I don't think that overwrites the radio firmware
Has anyone else seen this? I assume I've got Chinese models? does anyone have a working link for QXDM?
The same thing happens with the b20 band (800mhz) with a z5c bought from China by ebay. I tried to connect the z5c by ADB via USB with QPST - Dfs tools qualcomm and it is not possible with the drivers available for Z5C, on the other hand with a Z3C I had no problems in modifying the bands.If I managed to connect the Z5C by ADB wifi but it does not allow writing anything. I can only send ADB commands but I can not access the z5c modem as these softwares require. I'm always talking about the Kernel-Firmwares I've had in my Z5c, maybe with others if Dfs tools detects it as & MI_04 as these softwares require.
At the moment I leave it as impossible because I think that these devices bought in china or are mobile development or are mobile with baseband and blocked features such as NFC or mirrorlink
trancazo71 said:
The same thing happens with the b20 band (800mhz) with a z5c bought from China by ebay. I tried to connect the z5c by ADB via USB with QPST - Dfs tools qualcomm and it is not possible with the drivers available for Z5C, on the other hand with a Z3C I had no problems in modifying the bands.If I managed to connect the Z5C by ADB wifi but it does not allow writing anything. I can only send ADB commands but I can not access the z5c modem as these softwares require. I'm always talking about the Kernel-Firmwares I've had in my Z5c, maybe with others if Dfs tools detects it as & MI_04 as these softwares require.
At the moment I leave it as impossible because I think that these devices bought in china or are mobile development or are mobile with baseband and blocked features such as NFC or mirrorlink
Click to expand...
Click to collapse
Did you find anyone else trying to do this? I can spin up a windows box, but I also don't have one handy, so I've yet to see how well QPST works.
I think I may just send this back, but it's troubling that there must be a stockpile of Z5C's out there with bands disabled being sold on the internet. I'd like to figure this one for that reason alone (so many perfectly good devices going to waste)
If you had heard about Sony products sold online that lack any of the specifications you can have in the local market and in fact I have a document that informs you of it as a development unit. Sony takes care not to violate laws and licenses such as the use of nfc or mirrorlink that are not allowed in all countries and that apparently are not limited to a simple change of stock firmware. Sony's own online repair software rejects the repair of mobile phones that are outside of the area to which they were destined, and Sony's own technical repair services do not take charge of imported smartphone from ebay. I think that it is not just about functionalities controlled by the drm keys, but also the programming of their chipset. there was a time that wasted many hours trying to make mirrorlink work in an import z5c and it was impossible for the car to detect it as a compatible device, when in its ROM it includes the necessary system files for it. To finish, I told you that even using the tools to modify code in qualcomm chipset and checking the modification of the band in * # * # service # * # *, in fact there is no change in the bands even if it shows as done. At least this is my experience with this type of smartphone and sony bought from Hong Kong or China.
I forgot. In the attempt to use band 20 in the z5c, I have flashed dozens of baseband and stock firmware from several countries that use 800 mhz for 4g in their networks and although using * # * # info # * # * could change the country of the base band, there was no effect with respect to each specific band.
stratosmacker said:
...
Click to expand...
Click to collapse
trancazo71 said:
...
Click to expand...
Click to collapse
Would you chaps be good enough to link to either the eBay auction or the eBay seller that you bought these from, so that others can avoid the same mistake? I'm sure there is more than one seller that is distributing these phones, so buyers may not be safe anyway, but at least we can steer people away from known-bad auctions.
Thanks!!
-- Nathan
Also, for what it's worth, the band list shown in that screen shot *exactly* matches the one for the Japan-market-only (manufactured for DoCoMo) Z5c variant model SO-02H, as you can see here: http://phonedb.net/index.php?m=device&id=8900&c=sony_xperia_z5_compact_td-lte_so-02h__sony_suzuran
I thought it wasn't supposed to be possible (at least according to other posts I've read) to flash E58x3 firmwares on SO-02H, and I also believe all of those have non-unlockable-bootloaders as well. It's almost like these Chinese refurbishers have a stockpile of SO-02H motherboards, and have managed to figure out how to shoehorn the E5823 firmware on them. I think this probably also explains why NFC doesn't work on these either, nor can be made to work (see the other thread).
Either that or it is an E5823 but somehow the baseband got flashed with the DoCoMo one. If that's the case, I'm not sure how you undo that...
I also have yet to see a E58x3 that shows anything other than "HWC_Kitakami_Com_010" for "HW Config rev:". Every single reference I have found for "HWC_Kitakami_Com_009" so far is about a Z3+. I haven't found any screenshots of the Service > Configuration screen from a DoCoMo Z5c, though.
-- Nathan
You can "shoehorn" docomo or other carrier variants with stock firmware by rewriting an xml file before bundling the .ftf to the model you wish it to be, it does not rewrite carrier info, imei, lock status, etc. Rewriting the boot configuration to test is another story (I have tested this extensively and there are many quagmires when altering the files the bootloader writes the boot status as); there is a thread where these two go back and forth about a software you can purchase to write straight to the loader itself and change the lock status, albeit losing the imei #'s was an issue if the process was not done correctly ( https://forum.xda-developers.com/xperia-xz1/how-to/update-xz1sov36-bootloader-allow-to-yes-t4140775 ). Maybe this is the software they are using on these 810s along with the xml modificaton to "repackage" these as a factory unlocked e5823? I will have to check out the software you recommended to write to the bands/frequencies and see if I am able to successfully include the 800 frequency with what is more than likely a phone from the same batch of z5 compacts that stratosmacker ended up with.
&(*) said:
You can "shoehorn" docomo or other carrier variants with stock firmware by rewriting an xml file before bundling the .ftf to the model you wish it to be, it does not rewrite carrier info, imei, lock status, etc. Rewriting the boot configuration to test is another story (I have tested this extensively and there are many quagmires when altering the files the bootloader writes the boot status as); there is a thread where these two go back and forth about a software you can purchase to write straight to the loader itself and change the lock status, albeit losing the imei #'s was an issue if the process was not done correctly ( https://forum.xda-developers.com/xperia-xz1/how-to/update-xz1sov36-bootloader-allow-to-yes-t4140775 ). Maybe this is the software they are using on these 810s along with the xml modificaton to "repackage" these as a factory unlocked e5823? I will have to check out the software you recommended to write to the bands/frequencies and see if I am able to successfully include the 800 frequency with what is more than likely a phone from the same batch of z5 compacts that stratosmacker ended up with.
Click to expand...
Click to collapse
do you know where i can find instructions on rewriting xml file to flash different bundle via flashtool. my problem is i backed up my ta on e5803 , unlocked bootloader, flashed via recovery custom rom , now my device shows as e5823 on flashtool , trying to go back to stock e5803 but fashtool gives me "the bundle doesnt match the connected device" error.
i need to flash e5803 stock .54 back to my phone to restore my ta.
thanks
sabotage154 said:
do you know where i can find instructions on rewriting xml file to flash different bundle via flashtool. my problem is i backed up my ta on e5803 , unlocked bootloader, flashed via recovery custom rom , now my device shows as e5823 on flashtool , trying to go back to stock e5803 but fashtool gives me "the bundle doesnt match the connected device" error.
i need to flash e5803 stock .54 back to my phone to restore my ta.
thanks
Click to expand...
Click to collapse
I can tell you: edit the fwinfo.xml before bundling. Open Xperifirm, before closing Xperifirm you need to edit the fwinfo.xml file (and you can delete the bundled file to repack the already downloaded firmware, in case you already have the ftf created). Change the reference of 5803 to 5823 in that file, what you are essentially doing is telling the compiler to bundle the .ftf for that model, a 5823 (which is what you are currently running); however, you just downloaded a system.sin for a 5803 that it doesn't unpack or read, only on boot will this change occur after flashing it. You are using windows or linux? You might need help finding the download folder for Xperifirm that your flash program is bundling from. If you need extra help, let me know. I'm assuming you came from a custom rom that wrote system unconditionally.
Ican tell you one thing.... these Sonys Z5 compacts are refubrished So-O2H with cracked firmware from E5823....
Opened bootloader.... Rooted....
They cannot have LTE 800 BC20 and sometimes also don´t accept GSM network.... these phones are hand maked at Pakistan.... so if they fall down home even on carpet, they will be totally crashed.... display, or rear case.... this is the difference between originals and these.... originals can fall and no problem....
Quality 0 ZERO..... copy okey....
95% of all Z5 compacts are these fakes..... Ebay nd so on....
so be carefull what you buy....
Originals have this IMEI 35428207---- that is important!
It si something like a car VIN number..... it begins same numbers.... and it is okey....
There are also some models with original so-02h firmware, there jumps fakin japan funky ninja and you know sh!t.... these are not cracked to E5823.... the are locked! these are funky.... lots of rice everywhere.... what a fak....
but no you dont get LTE 20 nono only fun....joke... jumping ninja locked botloader. Ninja
M1cr0n Cell said:
There are also some models with original so-02h firmware, there jumps fakin japan funky ninja and you know sh!t.... these are not cracked to E5823.... the are locked! these are funky.... lots of rice everywhere.... what a fak....
but no you dont get LTE 20 nono only fun....joke... jumping ninja locked botloader. Ninja
Click to expand...
Click to collapse
Were you on some kind of stimulants when you wrote this? Why so many smiley face emojis after every few words. Wow, and your reply really isn't helpful.
I have an E5823 here that I know for a fact was unlocked, I used it on other networks before but as the OP said, T-mobile isnt working. they run a different band that these E5823's do not have unlocked as they said LTE/3G etc is not working with them and tmobile.
If we could find a way to enable the bands it would be fixed and working, but for now nobody has figured a way to do it. My E5823 was imported from the european market. That is why it's missing some bands. As all of them should be which were not FCC cleared. the FCC regulates what bands could operate in which countries at that point in time which was 2014-2015 and this phone did not have authorization to unlock those bands.
So now we just have to wait and see if there is ever a way to fix it.
Hi,
got a friends SM-G950F. Its on G950FXXU5DSFB_DBT.
Tried to flash COMBINATION_FA70_G950FXXU5ASF1 via Odin. On the phone i get: only officaily released binaries are allowed
Saw here and here that it seems there is a COMBINATION_FA70_G950FXXU5ASF1_FIX file available, just dont be able to download it cause i only find dl on liveon and seems impossible to activate the free account to download the file.
so my 2 question:
1. will this file (G950FXXU5ASF1/_fix) generally work on G950FXXU5DSFB_DBT? as im a OnePlus guy i dont exactly know all parameters in the samsung naming convention. seems first comes model, then BL version. Thought rest would be language stuff wich wouldnt be important (for me) for combination use.
2. someone got this file or one combination file which should work on the version i got here?
thx for any help!
noe one can help or at least point me in the right direction?!
daSn00p said:
noe one can help or at least point me in the right direction?!
Click to expand...
Click to collapse
Just curious if you have unzip the file and then put it into AP section of Odin.
sure
then i got the message as written in intital post.
anything new?!
come on, nobody?!?