Ive tried to update baseband of my AT&T m8 to Taiwan radio, and after successful flashing it shows correct Taiwan radio on fastboot, but in about phone it shows unknown for baseband, and can't connect to anything and the phone reboots every few minutes.
The phone is unlocked has s-off and has supercid 11111111
Thankfully I did a backup of my AT&T radio before and was able to restore it, and it works. But I would like to try Taiwan radio since I'm going to be here for a year.
Also what I noticed which might not be related is that I couldn't flash radio using recovery, could only do it fastboot/adb method.
Well radio, hboot and recovery can only be flashed using fastboot. Thus will never work in recovery, as recovery can just install the corresponding OS.
Regarding the radio you wanted to try. Could be the OS is not designed to work with the Taiwan radio bands, or AT&T doesn't work with them in the region you're in at the moment. Another guess is, that the whole rest of your firmware, as well as you current stock ROM don't support the radio and you thus won't be abled to use it.
Sent from my HTC One_M8 using XDA Free mobile app
Is there a way to tell if a radio is supported by the ROM? I'm running ARHD 10.2, which is based on 4.4.3 stock rom 2.220.401.4. Or should I look for roms for Taiwan version of m8?
Thanks for your reply as it totally makes sense. Just it's strange they included recovery method in the radio thread, they should remove it to make it less confusing.
krismach said:
Ive tried to update baseband of my AT&T m8 to Taiwan radio, and after successful flashing it shows correct Taiwan radio on fastboot, but in about phone it shows unknown for baseband, and can't connect to anything and the phone reboots every few minutes.
The phone is unlocked has s-off and has supercid 11111111
Thankfully I did a backup of my AT&T radio before and was able to restore it, and it works. But I would like to try Taiwan radio since I'm going to be here for a year.
Also what I noticed which might not be related is that I couldn't flash radio using recovery, could only do it fastboot/adb method.
Click to expand...
Click to collapse
Right, so you installed a radio that was designed for different hardware and it caused problems. Experiment successfully completed.
Related
Long story.
Was originally a UK Orange branded HTC Desire HD, running OTG updated 2.3.5, unrooted
I originally unlocked the stock device using the HTCDev method, all went to plan. I then installed clockworkmod and from there installed jellytime 10.
All good so far. I then applied a sim unlock code so we could use other SIMs in the device. Although the unlock code was accepted, with a 'Success' message, we could not get the phone to log on to other networks. Googling this problem suggested that the SIM unlock needed to be done under the stock rom. So I went looking further and found these two files:
RUU_Ace_Orange_UK_1.84.61.2_Radio_12.28g.60.140f_26.05.05.27_M3_release_170856_signed.exe
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
Both of which were supposed to be compatible with the phone.
Neither would install when run on an XP machine with the correct HTC drivers installed. So I extracted the ROM.zip from the WWE RUU above, opened it with winrar, and manually FASTBOOT FLASHed the .img files within, including boot.img, lib,img, recovery.img, and others. Some would not copy or install, but those above definitely did. (flashing at 5 am!)
However, none of this worked, so I rebooted into clockworkmod and reinstalled jellytime 10 and its boot.img.
Now, no matter what rom i put on it, the rom cannot access the sdcard (although hboot and CM have no problem doing so) and the phone can see no cell networks.
the phone current state is:
ACE PVT SHIP S-OFF RL
HBOOT-2.00.027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011,9:06:24
Anybody got any ideas on how to fix my phone?
You unlocked the bootloader with 2.00.0027? I had a Canadian Desire HD with the same bootloader and I couldn't unlock the bootloader until I upgraded to 2.00.0029.
I followed the guide in this forum to unlock my bootloader, get s-off, root, load 4ext, and load a custom rom. By doing all of this, my phone automatically became carrier unlocked.
audit13 said:
You unlocked the bootloader with 2.00.0027? I had a Canadian Desire HD with the same bootloader and I couldn't unlock the bootloader until I upgraded to 2.00.0029.
I followed the guide in this forum to unlock my bootloader, get s-off, root, load 4ext, and load a custom rom. By doing all of this, my phone automatically became carrier unlocked.
Click to expand...
Click to collapse
I have the ability to flash whatever ROM i wish, but any and all that I've tried give me zero network availability. Can't enable it. Wifi works fine - but no cell ability.
When testing, is the bottom sim cover installed? Have you tried flashing a different radio?
audit13 said:
When testing, is the bottom sim cover installed? Have you tried flashing a different radio?
Click to expand...
Click to collapse
Yes, the antenna was in place when no network was available.
If you can tell me what radio to flash for an Orange branded UK Desire HD - and more to the point, where to find it! - I'd be happy to give it a try, provided I can get hboot to allow me to flash the radio.
SimonButt said:
Yes, the antenna was in place when no network was available.
If you can tell me what radio to flash for an Orange branded UK Desire HD - and more to the point, where to find it! - I'd be happy to give it a try, provided I can get hboot to allow me to flash the radio.
Click to expand...
Click to collapse
Here's a list of radios: http://forum.xda-developers.com/showthread.php?t=877295
audit13 said:
Here's a list of radios: http://forum.xda-developers.com/showthread.php?t=877295
Click to expand...
Click to collapse
Thank you. I've previously tried two from that list, Orange UK 1.84.61.2 / CSL-HK CHT 1.84.832.2 and HTC 3.12.405.1 WWE.
I had great difficulty installing them as the fastboot flash radio radio.img process would fail, saying remote not allowed.
I was unable to s-off the phone using the methods most pages talked about (froyo/gingerbread exploit), the AAHK was unavailable and frankly, I don't really know what I'm doing.
The WD98IMG.zip method refused to install the zipped radio.img. As a workaround I extracted the rom.zip from the HTC WWE RUU above, unzipped it to a folder, replaced recovery.img with CM recovery.img and also replaced the radio.img with the one from the Orange RUU. Zipped the lot back up, put it on SD card, and hboot picked it up and flashed it.
This got me a working ROM with CM recovery, at which point I installed jellytime11. Then I fastbooted and flashed the boot.img. Once in Jellytime (and here's a tip - if it fails to boot, go and format the cache again) the radio started working. Don't know how stable it is and given how difficult it seems for me to change the radio rom, I will need a good reason to change it again.
Never flashed a rom before three days ago.
I was also having issues with the radio after rooting, unlocking the BL, and getting s-off so I just loaded the most recent radio and it worked.
My baseband is 12.69a.60.29u_26.17.14.11.m.
It's easier to flash roms with s-off as you can just install from cwm without having to extract certain files from the zip.
SimonButt said:
Long story.
Was originally a UK Orange branded
Noticed that you was on orange UK I have a T-Mobile stock RUU in my dropbox. Orange and T-Mobile are joint. Not sure if this would flash back to stock or weather it would flash at all but to T-Mobile because they are the same. If you know what I mean?
IceCreamSandwhich ( LorD ClockaN ) S-OFF DHD
Click to expand...
Click to collapse
ykdr-scott said:
SimonButt said:
Long story.
Noticed that you was on orange UK I have a T-Mobile stock RUU in my dropbox. Orange and T-Mobile are joint. Not sure if this would flash back to stock or weather it would flash at all but to T-Mobile because they are the same. If you know what I mean?
IceCreamSandwhich ( LorD ClockaN ) S-OFF DHD
Click to expand...
Click to collapse
Yes please, send me a link to your dropbox file. Always handy to have a backup.
Radio problem now solved, I got hold of a working AAHK and just ran the phone through that.
Splash screen flashed - bootanim next!
Click to expand...
Click to collapse
Alright... ive spent several hours trying to figure this out .... i'm getting very annoyed by it.. i've visited several firmware posts on here and it still isn't working. My htc one m8 is from at&t and i do believe that my firmware version is 3.28.401.7 (not 100%) but i also tried 401.9 and that also didn't work. I am currently s-on. I'm trying to push this over through fastboot since i'm SON and i did relock my bootloader... im throwing my hands up on this and now i'm seeking help
401 is Euro firmware, and there is now way you flashed that if you are S-on.
What radio and hboot number? What ROM did you flash?
redpoint73 said:
401 is Euro firmware, and there is now way you flashed that if you are S-on.
What radio and hboot number? What ROM did you flash?
Click to expand...
Click to collapse
i went back to stock rom. i assumed that was my version. my bootloader is 3.16.0.0000 radio is 1.16.21331931.la11g
i want to install viper but it borks my wifi
PureLife90 said:
i went back to stock rom. i assumed that was my version. my bootloader is 3.16.0.0000 radio is 1.16.21331931.la11g
i want to install viper but it borks my wifi
Click to expand...
Click to collapse
I assume you were previously on a Euro based custom ROM, and that is why the phone is telling you the main version is 3.28.401.
"Firmware" is a confusing term. But when folks here talk about it in terms of the latest custom Sense ROMs, broken WiFi, long boot times, etc. it refers to certain modules that are included with the OTA, but not a part of the ROM. These include hboot, radio, WiFi, Bluetooth, and some others.
Firmware itself does not have a specific "number" per se. Folks here will usually refer to the software number that the firmware deployed with, for lack of any other point of reference. But this can be deceiving, as if you look at your own software number or main version, it is just telling you the number of the ROM, which will change whenever you flash a ROM. To know what firmware you are on, your best bet is to look at the hboot and radio numbers.
Your hboot and radio version indicate you are still on 1.x firmware, and therefore flashing any 2.x or 3.x custom ROMs will result in some serious bugs like you are experiencing (broken WiFi, also long boot time is common).
You need s-off to manually update the firmware. If you do decide to s-off and update the firmware, there are various guides for doing so. But for AT&T, I recommend the following thread, as Wonders_Never_Cease deals with the AT&T variant exclusively, and has the most experience with making the phone work seamlessly on AT&T's network.
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Your other alternative is to return to stock ROM and recovery, and update when the 3.x OTA rolls out (should be soon), which will also update your firmware to the latest.
Hey M8 forums,
My S4 recently self destructed and I'm jumping ship to the M8 for T-Mo USA, I have a couple questions to prepare for it's arrival.
I'm coming off the S4 CM12 nightlies, are the M8 builds unified? As in, I can flash the standard CM release on my T-Mo variant?
And can I please get a link to the unlocking and rooting thread? The one I found has a method, but for s-off, the link seems to be down.
Thanks and greetings!
Most info can be found here,
http://forum.xda-developers.com/showthread.php?t=2711073
?
As far as CM goes, I'm not familiar with T-Mobile variants... Sorry. ☺
As of now the M8 in cyanogenmod is unified, all the GSM variants are just labelled as "m8". and the CDMA variants have other names like cm-20140120-m8vzw for verizon.
Onto the rooting and unlocking, you can unlock using HTC Dev but S-OFF might be a little impossible if you get the m8 pre-installed with 4.4.4.
Honestly, to root all you need to do is unlock using the HTC Dev site and flash a custom recovery from TWRP or CWM.
then flash SuperSU not all that different from a Nexus.
Darth said:
Most info can be found here,
http://forum.xda-developers.com/showthread.php?t=2711073
Click to expand...
Click to collapse
Thanks for the dump, lots of good info in there.
i4GS said:
As of now the M8 in cyanogenmod is unified, all the GSM variants are just labelled as "m8". and the CDMA variants have other names like cm-20140120-m8vzw for verizon.
Onto the rooting and unlocking, you can unlock using HTC Dev but S-OFF might be a little impossible if you get the m8 pre-installed with 4.4.4.
Honestly, to root all you need to do is unlock using the HTC Dev site and flash a custom recovery from TWRP or CWM.
then flash SuperSU not all that different from a Nexus.
Click to expand...
Click to collapse
I bought it off a guy that bought it a few weeks ago I believe, I haven't gotten it yet to see. It was my understanding that SunShine works on all M8's up to Lollipop. Is that not the case?
And what is a firmware? I keep seeing around to flash the Lollipop firmware, is that just the radio.img file or the whole RUU or what?
A firmware could be reffered to a whole RUU , because the ZIP that updates from 1.x to 3.x is a firmware.
Essentially a Firmware contains the essentials for a basic update (HTC version) , Radio, boot, Kernel, Bootloader, modem, etc.
An Update Firmware or RUU will contain all the partitions ,
boot, system, bootloader,hboot,modem,radio, cache, recovery , and so on.
And to some sunshine will work and to some it might not, it's a risk you're going to have to take, (to get s-off) worth it.
Though we shouldn't have to go through all these cracks and breaks to get it.
I used an older method and it worked for me, never had to use sunshine.
i4GS said:
A firmware could be reffered to a whole RUU , because the ZIP that updates from 1.x to 3.x is a firmware.
Essentially a Firmware contains the essentials for a basic update (HTC version) , Radio, boot, Kernel, Bootloader, modem, etc.
An Update Firmware or RUU will contain all the partitions ,
boot, system, bootloader,hboot,modem,radio, cache, recovery , and so on.
And to some sunshine will work and to some it might not, it's a risk you're going to have to take, (to get s-off) worth it.
Though we shouldn't have to go through all these cracks and breaks to get it.
I used an older method and it worked for me, never had to use sunshine.
Click to expand...
Click to collapse
I was told that the older method ceased to work because it required a server connection to complete that is no longer up. And would using a RUU to get to Lollipop put the system back to S-On?
Flashing anything won't touch the S-OFF. You'd have to manually set that back to S-ON (but why would you want to do that!)
searched all day yesterday and seemingly i need s-off to fix my firmware (radio)?
if so how did it get the wrong one in from flashing a rom if you need s-off to change it?
Hboot 3.16
orang001
twrp 2.7.x.x ( any higher hangs at entering recovery )
leedroid os boots works fine except no comms most likely because of radio issue.
fastboot from pc working
update: flashed an older rom and i now have a working phone again with wifi and cellular working.
but looking in hboot radio still says invalid!
dont worry about it?
and/or upgrade hboot / firmware etc? then i can move forward with newer roms/android?
Your current hboot version is too low for all the available custom ROMs on Development section.
You need to do OTA update up to at least 4.19.61.3 or the best to 6.12.61.4
Once you do the update I believe your radio problem will be fixed.
Started happen after I uninstalled MultiROM, the phone bricked and I had to RUU it. After RUU I tried all kinds of ROMS ( Viper One, CandySIX, ICE, LeeDrOid, Sky Dragon, etc... ) But most of them do not work ( boot loop ) and ones that work have unknown IMEI, unknown Baseband, and keeps searching for signal ( drains battery super quick ). I have superCID, S-OFF, Unlocked, Rooted everything. I am thinking I have corrupted of deleted my EFS partition, could someone please send me their backup so I can flash it?:crying:
Thank you so much for you help and have happy holidays,
You're probably trying to install a 3.35 rom on a 3.y firmware where y is not the same as 35.
I did try to install 3.35 firmware before installing ROM
Flippy498 said:
You're probably trying to install a 3.35 rom on a 3.y firmware where y is not the same as 35.
Click to expand...
Click to collapse
I tried all kinds of firmwares, even the newest from HTC site 3.42 if I remember right. I tried go all the way back to 1.xx to 2.xx and then to the 3.35 and 3.37 the most used ones. All of them are fine, just unknown IMEI and baseband, sim not found.
What was your original firmware?
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
What was your original firmware?
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I don't know what my original firmware was, if you mean the firmware when I bought it. If you mean the firmware before I ran into these problems, then it was 3.41 I think the newest from the HTC website at that time.
kazukazawa9 said:
I don't know what my original firmware was, if you mean the firmware when I bought it. If you mean the firmware before I ran into these problems, then it was 3.41 I think the newest from the HTC website at that time.
Click to expand...
Click to collapse
I meant the one before the problems. But 3.41 isn't the complete version it should be something like 3.41.xxx.yy. The part with xxx is the important part.
I think you might have flashed a GSM RUU on a CDMA device. The partition layouts of those two versions differ and flashing GSM on CDMA (or vice versa) may lead to unrecoverable damages.
3.35.xxx.yy is only available for GSM and the only US firmware with 3.41.xxx.yy I know is 3.41.651.yy (Sprint - CDMA).
Flippy498 said:
I meant the one before the problems. But 3.41 isn't the complete version it should be something like 3.41.xxx.yy. The part with xxx is the important part.
I think you might have flashed a GSM RUU on a CDMA device. The partition layouts of those two versions differ and flashing GSM on CDMA (or vice versa) may lead to unrecoverable damages.
3.35.xxx.yy is only available for GSM and the only US firmware with 3.41.xxx.yy I know is 3.41.651.yy (Sprint - CDMA).
Click to expand...
Click to collapse
ouch, then what should I do now? I didn't know there were two RUU versions, I might have done the exact thing you said. Is there no way to repair it except for hardware repair?
kazukazawa9 said:
ouch, then what should I do now? I didn't know there were two RUU versions, I might have done the exact thing you said. Is there no way to repair it except for hardware repair?
Click to expand...
Click to collapse
If you're lucky you can recover your phone by flashing the latest 651/Sprint RUU. But I can't guarantee for anything.