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.
Related
Hi all,
Just spent the last six hours trying to get my One X onto JB- well I got it on finally but now have lost WIFI/BT/Data and signal.
I started with bootloader 00.93.0000 I think, then attempted to install JB. This didn't work... So I tried to upgrade the bootloader to 1.31.
I then installed RUU 2.17.401.2 Radio 2.1204.135.20 trying to revert the damage of installing JB with wrong bootloader and upgrade the bootloader thinking .91 was the reason I couldnt update using fastboot commands, it would always hang as it was pushing the file.
I think the above RUU gave me the wrong radio. (was asking for date/time on bootup)
I then used the JBFWTOOL which have me the 1.31 bootloader and then I reflashed Revolution HD 14.
I then installed revolution 9.7.2 thinking it was to do with JB but this hasn't worked either.
It worked the second time around but I have no signal/bt/wifi.
Device ID is HTC_001 s-on
Believe it was O2 but was unlocked I use a 3 sim card in it.
I can still get to the bootloader menu etc
I don't know what else to do. The RUUs wont work due to bootloader and I haven't found any info on just changing wireless packacges like you can with odin.
Please help!
you never mentioned flashing the boot.img
1- update bootloader(seems you already did) and unlock and install cust.recovery
2- flash the boot.img file included in ARHD's rom.zip from the bootloader, fastboot flash boot C:/location_of_boot.img_on_pc
3- install the arhd rom.zip from cust.recovery
Note: sadly since you have installed a new hboot (anything greater than 1.23) there is no way to use an old RUU (ICS), new RUU's wont be released anytime soon (unless leaked)
hence, i recommend properly installing your JB and stick with it, after all its much better than ICS , unless you experience one of the hardware bugs.
Once the newer (1.33) bootloader is released(should be this week), it should fix all currently known bugs, and then you are safe to flash use latest ARHD or Maximus Roms for daily use.
Hey everyone,
I'm new to this whole Rooting and Custom Rom Thing, so today I sucessfully unlocked my bootloader and installed the latest Cyanogenmod 10 build, unfortunatly there is no way that the newest build starts successfully on my phone it keeps stuck with the HTC logo (I've tried all of the boot.img loading and cache deletine before). Then I installed the second latest cyanogenmod and it worked just fine. My phone started and I could configure all of the important things but now I am experiencing trouble with the Wifi. Everytime I try to Activate the Wifi it disables itself instantly. Does anyone have a solution to this problem?
And furthermore I am experiencing another trouble with my HTC:
When I was in Stock firmware (and also now with ARHD Custom Rom) my WiFi seems not to work properly. I can activate it, but it keeps loosing connection although it seems to be still connected with the Wifi but if i try to connect to the internet by browser or something else, the phone keeps telling me that there is no internet connection. I welcome all of your tipps and solutions!
It would also be great if some of you could tell me which Rom is the Best Built on 4.2.1 in terms of Battery Life and Stability.
Thanks for your help!
Best Regards,
DevastatedMind
Do you have the latest hboot for your cid?
And, for me, the best rom 4.2.1 is Ice Cold Jelly
I have the same problem.
With my WiFi and 3G
I had it with ARHD and now with VenomX.
The only thing I can think of is the hboot 1.39
It may be caused by your hboot
Where can I get the latest HBOOT? And how do I install it on my device?
Thanks you already for your help!
Use this procedure for upgrading your hboot.
Not follow the steps 2-3-4, download the firmware.zip and copy it in folder when you have fastboot
For the hboot, see this thread.
You know you cid?
I have the latest hboot 1.39 and have the same problem.
So upgrading might not be a good idea.
Bas. said:
I have the latest hboot 1.39 and have the same problem.
So upgrading might not be a good idea.
Click to expand...
Click to collapse
With which rom you have the problem?
And if this is a problem with a rom, write in that thread..
leditor force
I had the problem with ARHD and VenomX
Upgrade hboot, installed ARHD, reinstall ARHD, install VenomX same problems.
With ViperX, have you choise no at voice of kernel during the installation?
No if I remeber correctly I chose Yes (to backup).
Was this wrong?
You have to choise no when you are installing ViperX
If I may ask whats the difference?
So my CID is o2_____102
What does that mean for me now?
Bas. said:
If I may ask whats the difference?
Click to expand...
Click to collapse
Because the voice: "yes" install modules for a kernel custom, and if you have flashed the stock kernel, you don't have to choise yes, but no
DevastatedMind said:
So my CID is o2_____102
What does that mean for me now?
Click to expand...
Click to collapse
I don't see your cid in the thread that i linked.
What is your hboot?
1.36?
Yeah my HBOOT is 1.36 according to fastboot.
I own a German o2 Branded One X.
And when I read out my CID I get this as an response:
o2___102
Where can I get now the latest Hboot?
I tried downloading some software from HTCdev.com but as it looks like it is the exact same that I have already installed on my phone.
my build nr. is: 3.14.401.31 CL128187
I'm pretty confused at the moment. Actually.
DevastatedMind said:
Yeah my HBOOT is 1.36 according to fastboot.
I own a German o2 Branded One X.
And when I read out my CID I get this as an response:
o2___102
Where can I get now the latest Hboot?
I tried downloading some software from HTCdev.com but as it looks like it is the exact same that I have already installed on my phone.
my build nr. is: 3.14.401.31 CL128187
I'm pretty confused at the moment. Actually.
Click to expand...
Click to collapse
For your cid is the latest hboot..
If you have problem with a specific rom, you have to write in the rom thread.
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.
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.
Hello,
I've just received my One M8 some days ago. It came with Lollipop and I immediately did a system update to 6.0 Marshmallow.
Next step was unlocking bootloader and rooting it by installing LeeDroiD (based on stock Sense). At this point I discovered that the phone did not want to connect to my car audio and my bluetooth speakers. The One M8 simply does not show these devices. It DOES see my Moto G and my laptop computer's bluetooth which implicates that BT is not 100% broken. Sadly I can not say if it ever worked well, because I did not check with original HTC Android.
System information:
Bootloader unlocked, S-ON
HBOOT: 3.19.0.0000
Radio: 1.29.214500021.12G
Open-DSP: v51.2.2-00593-M8974_FO.1015
OS: 6.12.401.4
I've also tested bluetooth on CM13.0 and a SkyDragon version of stock Sense ROM, but same result.
Not being able to use my hands free calling in my car makes this devices a useless brick for me
Is it possible that the initial system update did not work properly? I'm thinking about flashing a 6.12.401.4 RUU (altough I'm already on this firmware) what might get hard, because I'm S-ON and Sunshine keeps telling me that my ROM is not stock enough.
As far as I know I can not flash a RUU of the same version when I'm not S-OFF. But in order to get S-OFF, I need a stock Android system...
Any ideas? I'm ready for anything
dyfk3l said:
Is it possible that the initial system update did not work properly? I'm thinking about flashing a 6.12.401.4 RUU (altough I'm already on this firmware)
Click to expand...
Click to collapse
RUU is what I would try, for 2 reasons:
1) RUU is a "cleaner" way to update, it re-writes all partitions. OTA often just patches what has changed, plus migrates user data, which can often lead to random issues.
2) It sounds like you went straight to a custom ROM. So its best to RUU to a full "stock" baseline, then see if you still have the problem.
Be aware that RUU will wipe the phone, so backup any data you want to keep accordingly.
dyfk3l said:
As far as I know I can not flash a RUU of the same version when I'm not S-OFF. But in order to get S-OFF, I need a stock Android system...
Click to expand...
Click to collapse
RUU of the same version is fine (for "repair" such as in your case) with s-on. The limitation is running an older version RUU, which is only possible with s-off.
A RUU update worked for me!
Thank you for the note that flashing the same version is fine on S-ON. It was no problem; after that I could easily S-OFF via root and Sunshine.
Bluetooth is working fine now! I never was a friend of OTA updates and I never will be. So it was the right way going the clean way. :good: