Hey y'all. There should be two radios now. The T-Mobile and the Tellus. Wind should have another radio altogether. Could the powers that be please pull radio.img files and start up a quick guide on how to unlock the boot loader and flash radios. I am happy to contribute, but I'm new to HTC. I am running a T mobile phone on a Canadian network - I assume that a radio designed for here would work better (wrong or right).
My Baseband is 1.07.550L.04DC_20.64.550L.07D
Thanks.
Correct me if I'm wrong, but don't you have to have s-off to be able to flash a radio?
I flashed radios on my 3g slide and didn't have s - off
correct me if im wrong but if its an official radio, ex- signed update - s-off is there to check if its got official signature, it should be allowed to flash
I don't know much about HTC. I owned a nexus S and flashed a few radios with fastboot and adb. It helped alot through the search bug issue.
I see this full roms availble now
http://forum.xda-developers.com/showthread.php?t=1335703
The question is what will happen if I flash another providers ROM on top of my fully stock T-Mobile. The guide suggests that you just copy it onto an SD card on a fully locked phone and Voila. There doesn't seem to be an indication of someone switching ROM's ie. Tmobile to Wind. There are a few that tried the Telus Rom but no indication that it's worked for anyone yet.
FSean said:
I don't know much about HTC. I owned a nexus S and flashed a few radios with fastboot and adb. It helped alot through the search bug issue.
I see this full roms availble now
http://forum.xda-developers.com/showthread.php?t=1335703
The question is what will happen if I flash another providers ROM on top of my fully stock T-Mobile. The guide suggests that you just copy it onto an SD card on a fully locked phone and Voila. There doesn't seem to be an indication of someone switching ROM's ie. Tmobile to Wind. There are a few that tried the Telus Rom but no indication that it's worked for anyone yet.
Click to expand...
Click to collapse
I'm pretty sure you have to have SuperCID to flash another carrier's ROM, and you can't get that without full radio S-Off. The current HTC unlock method doesn't allow us to flash radio images, as well as other little things like splash screens. Until full S-Off is achieved, I don't think we'll be able to do any radio switching.
So would a carrier be able flash their ROM onto a phone - ie. walk into my provider and have them flash their software and CID information onto the phone - or better yet - could HTC theoretically change my CID information directly?
Related
Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.
my at&t variant of htc m8 doesnt connect to wifi.
i bought it from a friend.
it searches and scans the wifi networks but doesnt connect to it and it seems the range is low too coz i have another m8 and it catches 3 bars in the room while this one catces only 1.
mobile data wasnt working before as well. i installed new viper rom and the data started working without any effort but wifi is the same. i couldnt connect.
this problem was before i even flashed a custom rom.
All I can think, is RUU back to stock (or update, as the case may be) and see if the issue persists.
okay ill try..
can someone plz guide me? link to a thread? where i can find ruu?
also, i have now bootloader unlocked and custom softwre.. can i still flash ruu?
can someone plz guide me?
i m now on custom rom with s-off and bootloader unlocked
i have a backup of stock at&t stock rom (wifi wasnt working ....nor mobile data) which i had backed up before flashing custom rom (after which mobile data started working but wifi problem still persists)... soo after restoring the stock rom how should i update it? and of course i couldnt update via phone coz wifi wasnt working... so if i find a stock update flashable file on xda should i flash it straight away? what about the radios? and should i relock the bootlaodeR?
dragonflame8712 said:
can someone plz guide me?
i m now on custom rom with s-off and bootloader unlocked
i have a backup of stock at&t stock rom (wifi wasnt working ....nor mobile data) which i had backed up before flashing custom rom (after which mobile data started working but wifi problem still persists)... soo after restoring the stock rom how should i update it? and of course i couldnt update via phone coz wifi wasnt working... so if i find a stock update flashable file on xda should i flash it straight away? what about the radios? and should i relock the bootlaodeR?
Click to expand...
Click to collapse
That's a lot of questions, most of which aren't relevant to my previous recommendation (RUU - which is not the same as a stock ROM backup).
You can find links (and more info on RUU) to AT&T RUUs on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Latest RUU for AT&T is 4.28.502.2, and you fill find the download and instructions on how to run it near the bottom of the HTC support page linked for RUU 4.28.502.2 on the Index.
You'll need to relock the bootloader in order to RUU with the command: fastboot oem lock
RUU 4.28.502.2 will return you to a full stock image, and the latest official software available for the AT&T M8. Hopefully, this will help your WiFi issue as well.
Make sure you don't have any apps installed that would mess with it. I had one app that no matter how many times I tried to turn off my wifi it kept. It back on
I recently found a repository containing stock fastboot flashable firmware for pretty much every single Moto E variant out there (except Sprint XT1526, much to my dismay). I have a Sprint XT1526 which has its bootloader unlocked. I was reading about a US Cellular variant of the XT1526 and how it is network unlocked for domestic GSM/CDMA usage. Since the Sprint variant isn't unlocked domestically, and since both are the XT1526 model, I figured I'd try to flash US Cellular stock firmware through fastboot to see if it worked.
I tried both the 5.0.2 and 5.1 images from USC and both gave me the same results: everything flashed and booted fine, but the Baseband is still listed as being Sprint. The firmware packages include a modem for me to flash (called NON-HLOS.bin I believe), but even after flashing this US Cellular modem along with the rest of the files I just can't get the baseband to switch from Sprint to US Cellular.
Any help on how to get the Baseband switched from Sprint to US Cellular so I can use my T-Mobile SIM in this thing? There is a modem file in the stock firmware but there isn't a radio file. Is this the problem? I thought the modem was the same thing as the baseband, not the radio? But if I am missing a radio file is there any way I can get a US Cellular one?
P.S. I'm not sure if this is a bad sign like something broke after I tried to flash the wrong firmware or if it always did this, but now when I insert my T-Mobile SIM it isn't detected at all. It thinks I don't even have a SIM inserted when I actually do (yes, I checked to make sure it was inserted the right way)
EDIT: Did research on my own and it turns out I'm actually missing a radio file; just a modem isn't enough. Since there doesn't seem to be a place I can find a prepackaged radio, is there any way someone with a US Cellular variant could "extract" a radio image for me to flash?
EDIT2: Apparently the fsb and NON-HLOS images were all I needed all along, but flashing those like I did still didn't help. Looks like this just isn't going to work.
jasonmerc said:
I recently found a repository containing stock fastboot flashable firmware for pretty much every single Moto E variant out there (except Sprint XT1526, much to my dismay). I have a Sprint XT1526 which has its bootloader unlocked. I was reading about a US Cellular variant of the XT1526 and how it is network unlocked for domestic GSM/CDMA usage. Since the Sprint variant isn't unlocked domestically, and since both are the XT1526 model, I figured I'd try to flash US Cellular stock firmware through fastboot to see if it worked.
I tried both the 5.0.2 and 5.1 images from USC and both gave me the same results: everything flashed and booted fine, but the Baseband is still listed as being Sprint. The firmware packages include a modem for me to flash (called NON-HLOS.bin I believe), but even after flashing this US Cellular modem along with the rest of the files I just can't get the baseband to switch from Sprint to US Cellular.
Any help on how to get the Baseband switched from Sprint to US Cellular so I can use my T-Mobile SIM in this thing? There is a modem file in the stock firmware but there isn't a radio file. Is this the problem? I thought the modem was the same thing as the baseband, not the radio? But if I am missing a radio file is there any way I can get a US Cellular one?
P.S. I'm not sure if this is a bad sign like something broke after I tried to flash the wrong firmware or if it always did this, but now when I insert my T-Mobile SIM it isn't detected at all. It thinks I don't even have a SIM inserted when I actually do (yes, I checked to make sure it was inserted the right way)
EDIT: Did research on my own and it turns out I'm actually missing a radio file; just a modem isn't enough. Since there doesn't seem to be a place I can find a prepackaged radio, is there any way someone with a US Cellular variant could "extract" a radio image for me to flash?
EDIT2: Apparently the fsb and NON-HLOS images were all I needed all along, but flashing those like I did still didn't help. Looks like this just isn't going to work.
Click to expand...
Click to collapse
This had been poked at quite a but in the past with no success...
Good luck
dandrumheller said:
This had been poked at quite a but in the past with no success...
Good luck
Click to expand...
Click to collapse
I think I'm gonna throw in the towel now. I believe I know the problem: its not that I don't have the right files to change the radio/baseband, its that fastboot is still in secure mode (even though my bootloader is unlocked) which prevents me from flashing certain images like bootloaders, partition tables, and radios. If someone were to either leak an insecure bootloader firmware package or compile their own, then baseband switching would be as easy as flashing these files.
I now have an XT1526 with a dead SIM slot, but its not like I was using it anyway so I guess there's no loss
@jasonmerc your phone's SIM card slot isn't bricked... it's just still domestically locked, so it will show that error when trying to use a non-Sprint domestic sim...
PresidentMcCain said:
@jasonmerc your phone's SIM card slot isn't bricked... it's just still domestically locked, so it will show that error when trying to use a non-Sprint domestic sim...
Click to expand...
Click to collapse
I guess each variant is different then. Back when I had my Verizon one (before I did the SIM unlock) if I put in my SIM it wouldn't say I was missing a SIM card, it just said the SIM was not recognized/not valid
@jasonmerc Did you ever try flashing to the USC bootloader before trying a modem flash? I was thinking maybe the bootloader is the key to all this... but it's the highest risk flash
PresidentMcCain said:
@jasonmerc Did you ever try flashing to the USC bootloader before trying a modem flash? I was thinking maybe the bootloader is the key to all this... but it's the highest risk flash
Click to expand...
Click to collapse
Yeah I tried that but nothing happened. I was speaking with squid2 over PM about this, apparently on more modern phones a bootloader unlock doesn't guarantee you FULL access to every partition to change. The partition I'd need to alter to make it work, namely the ones that have to do with GPT, bootloader and modem, are part of this "restricted area" that you can't alter.
The only way we could alter the partitions needed to make this work is to obtain leaked engineering firmware for the XT1526, which when flashed gives you 100% full access to every partition. Leaked firmware is hard to come by, and I doubt Motorola would just hand it over if we asked them
EDIT: I notice in your signature you have something about a modified ROM intended for GSM usage on your Sprint Moto E. Does this ROM somehow enable GSM for domestic use or is that for non-USA GSM?
jasonmerc said:
EDIT: I notice in your signature you have something about a modified ROM intended for GSM usage on your Sprint Moto E. Does this ROM somehow enable GSM for domestic use or is that for non-USA GSM?
Click to expand...
Click to collapse
I flashed an XT1527 6.0 stock system.img and boot.img directly on the Sprint XT1526, and made some modifications myself to make it work with Sprint (through build.prop mods) and have been using it that way since.
It will still only accept a Sprint SIM though...
That's too bad changing out the bootloader didn't help