Possible Help From Rooted 5q Owner? - Zenfone 5 Q&A, Help & Troubleshooting

I have a friend who purchased a Zenfone Max M1 Pro made for the market in India (and maybe elsewhere) for use in the US. He did not realize that the bands used overseas would not be helpful in the US. I am trying to help him. He is on T-Mobile and really needs LTE band 4 so he can use his CellSpot device at his home. Sadly, the device he bought lacks this band.
I have been reading and trying several things since I rooted this device. First I tried the well documented approach using the QXDM utility. It turned out this did not work on this device. Not entirely sure why. But this user <https://forum.xda-developers.com/showpost.php?p=79713339&postcount=3> claims it is because the phone in question "does not have a programmable radio firmware" and "Network parameters are pre-installed in mcfg_sw.mbn files, also the per carrier volte parameters are embedded in this folder". He then says "mcfg_sw.mbn files can be deleted and installed by QFIL in QPST. "
So I am willing to try going this route. In looking around, it seems that users looking to change their phone's Qualcomm configuration have been finding users with "compatible" phones online and getting ahold of their files of this type and installing them + some additional properties changes. Sadly, Asus did not make a version of the Zenfone Max M1 Pro for the US market and so I have been trying to find another Asus Zenfone that seems possibly compatible from which I could try to do the same.
This brings me to this forum and post... In looking at the specs, the Zenfone 5q and the Zenfone Max M1 Pro seem to share many common features. It is true that one uses the Snapdragon 636 while the other uses the 630. But from what I have read, they employ the same modem. So I am hoping that I may be able to succeed using files from the 5q.
So I am asking to see if some rooted (you need to be in order to access the folder/files in question) 5q owners/users might be able to help. On the M1 Pro, the files are all located under this folder: /firmware/image/modem_pr/mcfg/configs. So I am guessing/hoping that the same location will be used on the 5q. It it is, could someone possibly zip up the contents of that entire folder and make it available somehow? I could then compare what you have to what I have here and maybe try some file swapping.
Any other tips/suggestions are always welcome too.
Thanks

Related

Unlock FDD LTE Band 3 (1800MHZ) on OnePlus 2

Hello,
I received my Oneplus 2 today and it does not support the LTE Band 3. It`s the north USA Version and i would like to ask if anyone figured out a method to unlock the LTE Band 3 (1800mhz) . It`s because the Hardware of the Oneplus USA Version is the same like the European version.
best ragards
That would be amazing if some one could figure that out. But as I did my research it seems that it's not possible that there's a hardware difference.
shlomi_vanono20 said:
Hello,
I received my Oneplus 2 today and it does not support the LTE Band 3. It`s the north USA Version and i would like to ask if anyone figured out a method to unlock the LTE Band 3 (1800mhz) . It`s because the Hardware of the Oneplus USA Version is the same like the European version.
best ragards
Click to expand...
Click to collapse
Should be the same procedure as the HTC M9 since they're the same processor. And for the prep work (drivers and enabling the modem diag mode) as in this thread for the OnePlus One.
TheManDroid said:
Should be the same procedure as the HTC M9 since they're the same processor. And for the prep work (drivers and enabling the modem diag mode) as in this thread for the OnePlus One.
Click to expand...
Click to collapse
Do the changes to the band stay after rebooting or upgrading the OS to a newer version? I wanted to unlock band 3 as well on my OP2.
I haven't tried writing the modem configuration yet to see if it sticks or not but was able connect the phone and read the configuration from it by following the instructions from the 2 posts I mentioned.
Say if you got Chinese oneplus 2 and changed software on it would it work on bands 20 I've seen this question asked before but can't find the post
Sent from my LG-H815 using XDA Free mobile app
anyone found a way to unlock band 3?
Have a look at this post
I suggest you to keep 3G instead of LTE because battery draining is so faster under LTE Mode. If you stay a place that have a poor LTE signal,that would be your battery killer.
acidreian said:
That would be amazing if some one could figure that out. But as I did my research it seems that it's not possible that there's a hardware difference.
Click to expand...
Click to collapse
Hi, this research includes some whitepaper research?, Does it actually has different hardware?, just wondering if someone knows this by solid proof?
To know if there is hope for us (Buyers of wrong OP2 version )
I'm using A2005 usa model in India and I'm unable to use it on Airtel 4G in India. When I spoke to the OnePlus customer service they said it will need to replace the motherboard as it's a Hardware issue. I'm waiting for the motherboard to arrive from china as they don't have it yet in India. So basically it's a Hardware issue on oneplus 2 unlike it's ancestors.
rahulrai said:
I'm using A2005 usa model in India and I'm unable to use it on Airtel 4G in India. When I spoke to the OnePlus customer service they said it will need to replace the motherboard as it's a Hardware issue. I'm waiting for the motherboard to arrive from china as they don't have it yet in India. So basically it's a Hardware issue on oneplus 2 unlike it's ancestors.
Click to expand...
Click to collapse
They will do it for free? Or what is the charge?
Ok, guys, I`ve unlock NVram to write. Now I can save any values to change enabled bands.
Intruction:
Requirements:
OnePlus 2 with TWRP and rooted.
QXDM Pro, drivers, etc, as described here http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
Stock ROM OnePlus2Oxygen_14_OTA_011_all_1512111634.zip.
Attached file.
Just unzip attachment and replace file in ROM OnePlus2Oxygen_14_OTA_011_all_1512111634.zip, in RADIO folder. Flash via twrp.
After boot you will see warning "NV backup corrupted" or something like this, dont worry.
Use QXDM to change band as you want, reboot and check. Voilya. But LTE will not work, because it is hardware issue, lol.
A few words about attached file. I just unzip this file from stock ROM, search AC 1Ah (6828 little endian) and DB 08 (56072, US LTE band) together and replace DB 08 with DF 10. Dont ask, what I did, I dont know, lol. But it is work.
Implex said:
Ok, guys, I`ve unlock NVram to write. Now I can save any values to change enabled bands.
Intruction:
Requirements:
OnePlus 2 with TWRP and rooted.
QXDM Pro, drivers, etc, as described here http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
Stock ROM OnePlus2Oxygen_14_OTA_011_all_1512111634.zip.
Attached file.
Just unzip attachment and replace file in ROM OnePlus2Oxygen_14_OTA_011_all_1512111634.zip, in RADIO folder. Flash via twrp.
After boot you will see warning "NV backup corrupted" or something like this, dont worry.
Use QXDM to change band as you want, reboot and check. Voilya. But LTE will not work, because it is hardware issue, lol.
A few words about attached file. I just unzip this file from stock ROM, search AC 1Ah (6828 little endian) and DB 08 (56072, US LTE band) together and replace DB 08 with DF 10. Dont ask, what I did, I dont know, lol. But it is work.
Click to expand...
Click to collapse
There is easier way to do that without corrupting the backup.
Simply change the value is QXDM.
Then in the phone dial *#268#
Press the NV parameters
Press the Static NV Force Backup.
This will copy the new values to the backup, and they will stick later on.
BTW, to be on the safe side, make sure to backup your dycnvbk, stanvbk and EFS.
Not working for me. Cause com.android.phone crash after dial. May be because my backup is corrupted. Later will try with stock backup. But thank you anyway.
I am using the stock image with the stock phone app.
I am using Mokee, chinese AOSP firmware. BTW, I just erased nv backup partition and keep playing with nv ram. Hope will not brick my phone ))
What version do you have? US/EU/CH?
In case you have EU, cab you PM me with qcn of your device?
Unfortunatelly I have US version.
I know a way to add bands in snapdragon 801 (i did in xiaomi mi note) never tried in OPT since it has all bands i need . but it should be the same. Search google for adding bands in mi note

[MTK] Unlock bootloader - account not bound to device.

Hi all,
as mentioned in the title, I am having issues trying to unlock the bootloader of a Redmi note 3 Mediatek edition.
Worth to mention is that I have, of course, applied for the unlocking permission and got it. I also have used the Xiaomi Updater tool to update to the last stable version.
The problem that I am facing right now is that every time I try to use the Mi Unlocker tool, it complains that the account is not bound to the device.
I checked and that is not the case and I also tried to follow many guides.
All of them refer to the Snapdragon version which (apparently) does not work with the Mediatek version.
What I am trying to ask here is if there is a known working procedure and/or workaround to this kind of problem or if any of you would now how to move from here.
Thanks
there is a probleme with there unlocking tool it refuse to work since begin 2018... they broke it and nobody is fixing it..... alot of people have this probleme (im on the kate model)
luca34 said:
Hi all,
as mentioned in the title, I am having issues trying to unlock the bootloader of a Redmi note 3 Mediatek edition.
Worth to mention is that I have, of course, applied for the unlocking permission and got it. I also have used the Xiaomi Updater tool to update to the last stable version.
The problem that I am facing right now is that every time I try to use the Mi Unlocker tool, it complains that the account is not bound to the device.
I checked and that is not the case and I also tried to follow many guides.
All of them refer to the Snapdragon version which (apparently) does not work with the Mediatek version.
What I am trying to ask here is if there is a known working procedure and/or workaround to this kind of problem or if any of you would now how to move from here.
Thanks
Click to expand...
Click to collapse
Did you bind the account to your phone in Dev settings? If you did, just simply ask the Customer service and they will help you to get it unlocked. Use Chinese to talk to them if you can.
tonyyang- said:
Did you bind the account to your phone in Dev settings? If you did, just simply ask the Customer service and they will help you to get it unlocked. Use Chinese to talk to them if you can.
Click to expand...
Click to collapse
Problem is that in the MTK version this option is on available under the Dev settings.. That is also the reason why I opened the thread with the MTK tag.

A2017G Japan - Lots of Questions...

Okay, so I used to love rooting my phones, but I mostly dealt with flagship phones in the US which made rooting and flashing a cakewalk. I understand some of the nitty gritty, so when I got my first phone in Japan, I was super excited about rooting it. But after reading this forum for hours, I have so many questions...my phone build is A2017G JPV1.1.0B03.
I read this but this mostly focused on using an update on this phone.
https://forum.xda-developers.com/axon-7/help/a2017g-japan-to-a2017g-european-a2017g-t3608411
1. If that thread is correct, that means I technically just have the European version of the phone with Japanese modems installed. Is that correct?
2. Also, does that mean (if I were not to root the phone) I would need to install a European Axon 7 Oreo update for it to actually work on the phone? Would the US version fail?
3. I can't seem to find the modem for my phone. I can upload some screenshots later but can someone clarify if I'm right that it's a "B03" or am I looking at the wrong information?
4. There is no Oreo release for Japan, so does that mean I can't flash an Oreo ROM because there won't be any modems for this?
That's all for now, but I'm sure I have a lot of follow-up questions to your answers. Your help is greatly appreciated.
Unlock bootloader, install twrp, instal "G" model bootstack, instal any custom rom, then flash "G" modem in twrp, reboot. No matter where you device are from, the model matters. If its "G", its a european version and its only what you need to know. If you want stock oreo and didnt recieve through OTA, download the update in ZTE website for your "G" version, put it in a sdcard then reboot your phone to recovey then select "install update from sd card" option.
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
RobboW said:
Basically, the model of the phone is printed on the back of it down the bottom.
A2017 is China version.
A2017U is US version.
A2017G is everything else (Global) version. It's not actually euro.
The modem software has to be for the actual model of the phone, not your location in the world.
Don't correlate software versions between Chinese, US and Global, they use different numbering systems. Only concentrate on what is for your model.
The rest of this pertains to A2017G as that is what you seem to have.
They start at B01 (usually pre-release beta) and go up from there but each new Android version eg Nougat, Oreo etc means the numbers restart from B01.
Nougat B03 has nothing to do with Oreo B03.
Look at the software version, A2017GV1.1.0 is very old, the 1.1.0 is the key to the Android version. 1.2.0 is Nougat, 1.3.0 is Oreo so you have Marshmallow at 1.1.0 and B03 release from that Android generation.
It seems confusing at first but it's actually quite simple.
Click to expand...
Click to collapse
I'm so used to dealing with multiple modems for the same model of phone in the US (between the major carriers and stuff) that I was overthinking it.
Thanks a ton. That simplifies things so much...and also makes me wonder why updating never occurred for the Japanese release. It's not like there isn't language support for newer versions of Android, but maybe not for the MIUI? I need to be more careful choosing my next phone then, though probably it should be an AOSP phone like the Zenfone or Pixel.
Guess I have my work cut out for me this weekend. Time to run a giant backup and start rooting. Thanks again for all your help. I like this phone (though I often accidentally hover/touch the home button when typing, and I hope there's a sensitivity fix for that :laugh so I want it to last for a while before I get my next one.
It's still a good phone, I look at new phones and think, hmmm, nice, but what will I gain on a daily basis? Nothing more to be honest. The A7 has enough power for me still. The one thing I could really use would be a higher capacity battery. Was looking at Huawei phones but now, well.....
For updates, they had issues with OTA and reverted to only releasing for a whole ROM download for update from SD card.
I personally won't apply an OTA for mine even now at Oreo. Must be a whole ROM to flash with the updater. That's all I've done with it since purchase and it works great still. A lot of people seem to have all sorts of weird issues after applying OTA updates.
Sweet. As someone with some experience with this stuff, do you have any tips or tricks I should know moving forward? I'm going to try rooting it tonight.
-EDIT: Quick little question, my phone says the Android version is 7.1.1 but that would be Nougat, right? Or is it actually Marshmellow?
7.1.1 yeah, Nougat. That doesn't make sense from your first post.
Was it used when you got it or new? Have you checked the model from what's on the back of it, not what software says it is?
I keep mine stock, can't advise on rooting etc. I use it with personal and work SIMs and it has to pass requirements including encryption to run Microsoft InTune and our company portal and use it in work mode. Bootloader hasn't even been unlocked. The most I did was uninstall some built in user apps through ADB.
I also have a 2017G bought in Japan. I unlocked it and worked on it based on this forum, and I can say that it behaves as any other 2017G. I am not interested to use the stock ROM, but yes, I remember that it was on Nougat version when I received it.
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
darth_antz said:
I have the A2017 (china). As above, update your phone to the region. As a result of having a china variant, i think i miss out on band 28 and some other essential bands for reception. I get 3G/low 4G connections and a lot of bad reception areas (countryside living). Its no problem.
Currently running AEX 6.5. Search some of my recent posts for how I updated to this version.
Click to expand...
Click to collapse
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
The Zenphone 6 is looking a viable buy now.
My Axon 7 is still good so not really looking but I did just get a new Axon 7 Mini for use as a media player. It still has AMOLED screen, stereo speakers, headphone jack, DAC for the jack etc. No hi res bluetooth though. Cost me AU$149 new in box from retail store. Bargain! How much is a dedicated music player which is crap at movies or just cant do them?
Chucked my 128Gb SD in. Sounds good playing through the car hifi, lower 3.5 jack output matches HU aux in impedance better than Axon 7 which can overload the input at high volume. Very balanced and clean sound.
TheZen said:
Appreciate it. I will try to work on it this weekend, as last weekend I just didn't have the time...
The phone was brand new when i bought it. It was on a "super sale" though, going for 12,000 yen (like 110 bucks or so). I was thinking about getting a Zenfone but if I could save the money and make it to at least Oreo I'd be happy. Been having issues with the battery whenever I use more than 2 apps at a time.
If you could link an unlocking guide and a ROM that worked well for you that would be great. I have one I plan to use but I'm always open to suggestions. After the first time, I'll feel more comfortable with it. In the worst case scenario that I brick this thing I'll just buy the Zenfone early :laugh:
Click to expand...
Click to collapse
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
darth_antz said:
Where did you get in on a super sale? website in Japan?
Obvious unlocking guide is this one https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693
Give yourself 2 hours to get the job done, and there are a few guides on youtube for unlocking the bootloader and installing TWRP (if you havent already).
If you cannot root the phone by your own discovery, I dont think you'll be up for installing a custom rom. It takes a degree of risk, and research. Being successful in the attempt is worth it.
Do a backup in TWRP, or get titanium backup pro (paid) to do a backup of your essential apps and data (email, messaging, google authenticator etc). I think titanium backup is better, especially if you are going from android 7 to 8 or 9 and different twrp versions.
If your phone boots following Oki's guide (Option 1), then scroll to the last page to my post about taking it to android 9 on AEX.
As your phone is A2017G, search for the necessary files in the forum corresponding to your modem. There are plenty of links.
Good luck and let us know you are successul!
Click to expand...
Click to collapse
I bought it at Rakuten Mobile. There was a super sale and it was like 80% off, lol.
I tried using the guide over the last couple of days and no matter what I've done, I can't seem to get to recovery after doing the flashing (step 9). I was able to flash a stock image back on, but then when I try again it's the same results. I'm at a loss as to why but...there's another guide using the Axon7Tool.
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
The downside is that I work two jobs tomorrow so I won't have time to try this new one out but I think I downloaded everything already. This is kinda frustrating though..
-EDIT: I used the unbricking guide to EDL flash the B10 Nougat and it is a different experience than what I had before...geez, seems the Japanese version was severely neglected. If I run into problems with the other guide I feel comfortable EDL flashing Oreo. Really appreciate the support guys, let me know what you think. Before I started this, my battery was lasting barely 8 hours with only LINE and Chrome being the main background apps...
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
GeoffUK said:
Not sure it's relevant here any more but I have a 128 Gb A2017 which I put a G build on, after being a bit miffed at some of the stuff (mostly Google based) I couldn't use on the original. I really don't know that much about what I'm doing but it all seems to work OK, though an old battery life problem has returned so I'm going to be asking elsewhere (probably) about how to replace the modem software. I also have a bit of a problem with GPS intermittently not working (going on and offline) but I suspect that's probably a hardware problem rather than the build. Mine is on
Click to expand...
Click to collapse
you can't. There are 3 modem variants by region (US, china, global) and many versions for each, but they are not interchangeable and flashing another has already wiped some IMEIs long ago (doesn't always happen though)

Mi 9t rom for K20

Yesterday I bought redmi K20...and already added account for bootloader unlocking...after unlock can i flash mi9t rom on K20 through fastboot?? Need your help..thanks in advance
of course
I have done it myself with Xiaomi Flash tool, all good so far.
Only problem is that Play Store is not certified so no Google Pay for me ...
seblog said:
I have done it myself with Xiaomi Flash tool, all good so far.
Only problem is that Play Store is not certified so no Google Pay for me ...
Click to expand...
Click to collapse
Could you confirm whether your Redmi K20 gained additional baseband functionality (e.g. B20) after flashing the official Global ROM (of Mi 9T)?
Asm Nasim said:
Yesterday I bought redmi K20...and already added account for bootloader unlocking...after unlock can i flash mi9t rom on K20 through fastboot?? Need your help..thanks in advance
Click to expand...
Click to collapse
Can you tell if it has AODs? If yes please show few of them.
Will there be a mod for dual speaker?
OMG|OTG|OTA said:
Could you confirm whether your Redmi K20 gained additional baseband functionality (e.g. B20) after flashing the official Global ROM (of Mi 9T)?
Click to expand...
Click to collapse
I think that the band20 issue is hardware related, so no software update can fix it.
Pejpi said:
I think that the band20 issue is hardware related, so no software update can fix it.
Click to expand...
Click to collapse
It's firmware not hardware
Guido83 said:
It's firmware not hardware
Click to expand...
Click to collapse
Hardware. The firmware has nothing to say when it comes to Bands.
Remember:
hardware (physical thing) - components, real stuff
firmware - device software, specifically designed for a device and its hardware
software - all apps, can be copied and destroyed
OMG|OTG|OTA said:
Could you confirm whether your Redmi K20 gained additional baseband functionality (e.g. B20) after flashing the official Global ROM (of Mi 9T)?
Click to expand...
Click to collapse
No, it's hardware related.
seblog said:
I have done it myself with Xiaomi Flash tool, all good so far.
Only problem is that Play Store is not certified so no Google Pay for me ...
Click to expand...
Click to collapse
You can easily fix that.
1) Install Magisk (you need TWRP)
2) Use Magisk Hide to hide Google, Google Pay and Google Play Services
3) In settings clean data and cache of Google Pay
4) Reboot to recovery (TWRP) and go to Advanced -> File Manager
5) Go here: /data/data/com.google.android.gms/databases/dg.db
6) Press chmod and write 440 - accept it. Then restart to system. Google Pay should work.
If you want to have the word "certified" in Google Play, you need download "Device ID" from Google Play, open this app then copy code from Google Service Framework (GSF) and go here: https://www.google.com/android/uncertified/. After entering the code from the GSF tab and pressing register, clear Google Play data and cache in the settings. Remember, to do this you need Magisk (root).
Zenderable said:
Hardware. The firmware has nothing to say when it comes to Bands.
Remember:
hardware (physical thing) - components, real stuff
firmware - device software, specifically designed for a device and its hardware
software - all apps, can be copied and destroyed
No, it's hardware related.
.
Click to expand...
Click to collapse
Firmware is special low level software to control hardware. In this case the modem firmware (non-hlos.bin) can control the qualcomm modem on each device in a different way even though the hardware is exactly the same. SD855 is always the same SoC (including its modem) on each device. With the low level software=firmware the SoC is controlled.
Guido83 said:
Firmware is special low level software to control hardware. In this case the modem firmware (non-hlos.bin) can control the qualcomm modem on each device in a different way even though the hardware is exactly the same. SD855 is always the same SoC (including its modem) on each device. With the low level software=firmware the SoC is controlled.
Click to expand...
Click to collapse
Yeah, that's why ROMs are called firmware. And that's why B20 can't be available in China version after Global ROM installed.
Zenderable said:
Yeah, that's why ROMs are called firmware. And that's why B20 can't be available in China version after Global ROM installed.
Click to expand...
Click to collapse
A ROM is consisting of firmware AND software parts. The only question is whether the modem part is open for changes or not. Telling to change the modem settings is impossible in general is just not true
The firmware vs hardware dispute seems hard to settle.
I still insist, though, that one rather simple way of putting all this to the test is to flash a Redmi K20 with the official Global ROM developed for the Mi 9T, whereafter a test is carried out to verify whether the Redmi K20 device has gained additional baseband functionality (e.g. B20 or some other band that is supported by the ROM/firmware of Mi 9T). If additional baseband functionality can be confirmed then we can assume that
(granted that the device also exhibits proper functionality in general):
a) the hardware of Redmi K20 and Mi 9T devices are identical
and
b) the baseband functionality de facto is firmware/ROM dependant — i.e. at least in this particular case.
We just have to find someone that can carry out this rather simple testing procedure.
OMG|OTG|OTA said:
The firmware vs hardware dispute seems hard to settle.
I still insist, though, that one rather simple way of putting all this to the test is to flash a Redmi K20 with the official Global ROM developed for the Mi 9T, whereafter a test is carried out to verify whether the Redmi K20 device has gained additional baseband functionality (e.g. B20 or some other band that is supported by the ROM/firmware of Mi 9T). If additional baseband functionality can be confirmed then we can assume that
(granted that the device also exhibits proper functionality in general):
a) the hardware of Redmi K20 and Mi 9T devices are identical
and
b) the baseband functionality de facto is firmware/ROM dependant — i.e. at least in this particular case.
We just have to find someone that can carry out this rather simple testing procedure.
Click to expand...
Click to collapse
Exactly, though I'd like to add: It's not just the global rom that needs to be flashed, but also the global modem firmware.
Please do that. As of yet, there are no posts, videos or documentation stating that the band20 issue can be resolved with "simply" changing the whatever root firmware, software roms etc (whatever you prefer) of the phone is needed.
It is indeed a little bit funny to think that they are physically making 2 different versions of the phone "just" for different band support (one of) if at all.
Anyways, if it truly isn't hardware related and a different software-rom-firmware is needed, but can't change it in any shape or form to make it work as intended I still do regard it as a fix that can't be solved. (as of now) - and if you are eager to buy yourself a new phone, just get the global version.
OMG|OTG|OTA said:
The firmware vs hardware dispute seems hard to settle.
I still insist, though, that one rather simple way of putting all this to the test is to flash a Redmi K20 with the official Global ROM developed for the Mi 9T, whereafter a test is carried out to verify whether the Redmi K20 device has gained additional baseband functionality (e.g. B20 or some other band that is supported by the ROM/firmware of Mi 9T). If additional baseband functionality can be confirmed then we can assume that
(granted that the device also exhibits proper functionality in general):
a) the hardware of Redmi K20 and Mi 9T devices are identical
and
b) the baseband functionality de facto is firmware/ROM dependant — i.e. at least in this particular case.
We just have to find someone that can carry out this rather simple testing procedure.
Click to expand...
Click to collapse
I have flashed the fastboot Global ROM , so all parts baseband, radio, etc...
How can I test if band 20 is available?
I am checking with cell info lite, but I never saw band20 used while using EE around...
Is there any specific tool that can test which bands are enabled?
its a polish site, but try using goolge translate and using this app:
http://www.bez-kabli.pl/viewtopic.php?f=12&t=51231
seblog said:
I have flashed the fastboot Global ROM , so all parts baseband, radio, etc...
How can I test if band 20 is available?
I am checking with cell info lite, but I never saw band20 used while using EE around...
Is there any specific tool that can test which bands are enabled?
Click to expand...
Click to collapse
Use network signal guru and click on "lock lte bands" there you can see all available like this
skleppo said:
Exactly, though I'd like to add: It's not just the global rom that needs to be flashed, but also the global modem firmware.
Click to expand...
Click to collapse
Is this, then, a fact beyond all doubt that these firmware entities, i.e. the ROM and Baseband firmware are two completely separate code packages?
Since there seem to be so many differing conceptions regarding this topic it would, for the sake of moving ahead in the inquiries, be of great importance to rule out all the existing and obscuring misconceptions.
An other question is how universally this applies when it comes to smartphones ROM and Baseband firmware implementations in general [I'm thinking of possible differences in implementation based on such attributes as smartphone brand/manufacturer, model, (geomarketing) version etc.].
---------- Post added at 07:11 ---------- Previous post was at 06:52 ----------
Guido83 said:
A ROM is consisting of firmware AND software parts. The only question is whether the modem part is open for changes or not. Telling to change the modem settings is impossible in general is just not true
Click to expand...
Click to collapse
Does this mean that the code package of the Baseband firmware (always) forms an integrated but separate part of the ROM code package or a code package that is completely separate from the ROM?
OMG|OTG|OTA said:
Is this, then, a fact beyond all doubt that these firmware entities, i.e. the ROM and Baseband firmware are two completely separate code packages?
Since there seem to be so many differing conceptions regarding this topic it would, for the sake of moving ahead in the inquiries, be of great importance to rule out all the existing and obscuring misconceptions.
An other question is how universally this applies when it comes to smartphones ROM and Baseband firmware implementations in general [I'm thinking of possible differences in implementation based on such attributes as smartphone brand/manufacturer, model, (geomarketing) version etc.].
---------- Post added at 07:11 ---------- Previous post was at 06:52 ----------
Does this mean that code package of the Baseband firmware (always) forms an integrated but separate part of the ROM code package or a code package that is completely separate from the ROM?
Click to expand...
Click to collapse
You wil find a non-Hold.bin file inside the ROM when you extract the ROM. This is the modem firmware
Guido83 said:
You wil find a non-Hold.bin file inside the ROM when you extract the ROM. This is the modem firmware
Click to expand...
Click to collapse
Is the suggested modem firmware file completely resistant to [all] alteration (due to proprietary code and/or encryptation) or is alteration possible but changes won't take effect when flashing?
Can this code package/file be flashed separately or does it always require flashing the ROM (or other corresponding firmware components)?

Bricked Mi Mix3 5G using Phone Clone

I bought a Mi Mix 3 5G, in Australia, for my partner who is in the Philippines. The phone is still under warranty. My partner attempted to clone data from a Samsung phone using Huawei Phoneclone. My error in recommending its use as I used it with Huawei phones and hadn't realised the software was Huawei specific. The Mi Mix now appears to be bricked (I'm in Australia so I can't physically access the phone). My partner took it to a Xiaomi dealer however they won't touch it as it has an Australian IMEI. Currently looking at sending it back to Australia so that I can attempt to have it repaired. Are there any opinions on whether the phone is recoverable? Her daughter is quite cluey in all matters about phones and if there is a way to re-flash the phone she could quite possibly do it. Any thoughts? Thank you. I haven't played with phone roms and I'm quite clueless in this area.
My partner tells me it is absolutely dead. No lights, no response
Hello,
You must be download miflash and stock rom with the firmware format.
https://xiaomifirmwareupdater.com/miui/andromeda/
I have tested with miflash but i think this is optional if your run manually the bat/sh script.
pommefrite8 said:
Hello,
You must be download miflash and stock rom with the firmware format.
https://xiaomifirmwareupdater.com/miui/andromeda/
I have tested with miflash but i think this is optional if your run manually the bat/sh script.
Click to expand...
Click to collapse
Thank you for your response. I will talk to my partner and her daughter, thank you again
No problems, i understand, if more details is needed, don't hesitate to ask question.

Categories

Resources