Hello, I recently bought my Flyer, S-OFF'd, rooted, got CWM and custom ROM, everything's fine. In the HTC Desire section there are many threads about RADIO updates, mostly taken from new builds/RUUs/leaks: is there something like that for Flyer? Or can anyone point me to the latest RADIOs available so I can check against the RADIO I have now? Thanks!
I think the issue here is that there aren't a lot of releases from HTC for the Flyer that would have this in it, except for maybe the Honeycomb leaks. I don't know if a GB radio would work in HC and vice versa. I know what you're talking about though, in the DInc forums there's like 6 - 7 different radios you can flash from various leaks/official releases, and EVO radios were even compatible with them...so there were a ton of options.
I don't think that's the case with the Flyer. If I am wrong, someone correct me, as I only have a Wifi only version, but I just haven't seen radios around these forums in abundance.
I may be wrong but I believe there is serious risk in having a radio that does not match the hboot on your flyer. I would not suggest playing with radios
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
I may be wrong but I believe there is serious risk in having a radio that does not match the hboot on your flyer. I would not suggest playing with radios
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Let's go with "you're wrong," as it's pretty easy to swap out radios if you flash a bad one.
MattG987 said:
Let's go with "you're wrong," as it's pretty easy to swap out radios if you flash a bad one.
Click to expand...
Click to collapse
Indeed. And I don't think there's any link between hboots and radios. What are you on, guys?
"
Originally Posted by globatron
It will just fail. Revolutionary uses hboot protection. Even if it did manage to update hboot, the partitions are different as are the boot image bases. You'd just make a mess of the software and have to RUU, worst case you end up with a hboot/radio mismatch and have to send it back to HTC to be re-imaged.
You won't be stuck, for as of right now it's the *only* way you can have HC. HC system images are too big for the old partition layout.
Yeah a reasonable statement if you have a device with no unlock. Otherwise it's just as easy to apply su as a zip file, you need CWM either way.
thanks for the info. for what its worth, i had based my answer on updating to an official release HC from a HC leak,but in retrospect that dint make sense either,as you prolly wont get an OTA while on a leak ima just be quiet now
Originally Posted by globatron
No, don't be quiet...just learn from mistakes. If you don't keep trying it's pointless because nobody learns. If I didn't think you or others could benefit from the information then I wouldn't bothered with the explanations.
i agree with you completely,thats just my humor. got honeycomb installed and am very much enjoying my flyer.
just trying to keep in mind that what i know about phones will not neccessarily apply anymore. for example,the hboot incompatibility between HC and GB. revolutionary hboot works for everything on the phones,so we change radios around regularly. not that ive any reason to change the radio in my wifi flyer,but it never occured to me that mis-matching the radio and hboot oculd cause such a catastrophe that an ruu wouldnt fix it definately good info to have
thanks again for the info"
I did not pull the concept of mismatch radio/hboot from my ass
from my HTC Flyer P510e using xda premium
There is a very definite relationship between htc unlockable hboots and radios. With S-OFF hboots however no such issue unless you try to go back to S-ON and flash an unrecoverable configuration of hboot/version-main and radio. It an odd situation to get into but it is possible while there are no official HC RUUs.
HC hboot + HC version-main + GB radio = send to HTC for re-imaging or wait for an offical RUU.
A mismatched radio/hboot prevents the HTC unlock from working, and without unlock and hence without root you can't fix the main version and can't RUU.
As I said at the top so long as you stay S-OFF flashing a bad radio doesn't matter.
Thanks for the clear explanation.
I told that because I'm S-OFF so wouldn't mind trying some radios for a few days. So I ask again: what version are you using, guys? And what is your feedback about that?
Related
I have always wondered...why some people get s-off and some s-on and different versions of Hboot? anyone know?
its obvious what s-off and s-on does, but what are the differences between the Hboots? any advantages of one over another?
i only care about the radio version lol
seriously, the wifi signal sucks on my Telus Amaze, dont know if Tmo get better radio versions or not...
still waiting for s-off that we can easily flash radio
seansk said:
I have always wondered...why some people get s-off and some s-on and different versions of Hboot? anyone know?
its obvious what s-off and s-on does, but what are the differences between the Hboots? any advantages of one over another?
Click to expand...
Click to collapse
I don't know why some phones came with S-Off and the rest with S-On, but Hboot is kind of like the BIOS of a computer. Whenever there is an update, HTC will update the Hboot.
Just curious, if I'm s-off and can/have flashed new radio and kernel is there still any reason to install the latest and greatest ruu? Are there any other benefits? Maybe I'm missing something but the latest roms from our awesome devs are being rebased on the latest leaks...I just don't see why flashing a ruu is needed. If I'm wrong or missing something please let me know. Thanks in advance.
Sent from my Rezound
Nah its has the same fw as last one just few bug fixed in software level
I'm not saying specifically the last one, I mean in general as new ruus come out. If vzw doesn't eol us that is. Thanks though.
Sent from my Rezound
in term of battery life i would stick to gb fw
but u can ics with patch and still got nice battery life
I've been rooted day one and s-off from the first day it was available and running cleanrom ics. GB sucked with sense for the half a day I used it. This was just an overall general question of "what's the point" and i'm sure others had similar thoughts. I'd hate for anyone to run a ruu for no reason just to have to re-setup their "got it the way I want it" rom of choice.
Sent from my Rezound
If you're flashing the radio and perhaps hboot updates every time, probably not. I guess the good thing about the RUU is that you flash everything together in a package that is known with some certainty by the manufacturer to all play nice. You can always nandroid your custom ROM back on afterwards.
That said...I independently flashed hboot once or twice, and radio several times, on my old Incredible without incident. I've only done the RUU, and only one time, on the Rez.
bluetooth_decay said:
If you're flashing the radio and perhaps hboot updates every time, probably not. I guess the good thing about the RUU is that you flash everything together in a package that is known with some certainty by the manufacturer to all play nice. You can always nandroid your custom ROM back on afterwards.
That said...I independently flashed hboot once or twice, and radio several times, on my old Incredible without incident. I've only done the RUU, and only one time, on the Rez.
Click to expand...
Click to collapse
Yeah I've update the hboot with latest jb and flashed the latest radio and kernel, no issues thus far and all is well...so I conclude ruus are a waste unless that's what you want to roll with is stock
Sent from my ADR6425LVW using xda app-developers app
It appears that HBOOT 1.15 will not get s-off any time soon...Is it O.K. to upgrade to HBOOT 1.19 and wait then for s-off capabilities, or is 1.19 taboo also.
I am rooted, can I stall HBOOT 1.19 with abd, or would I have to root the phone again, and install a recovery...
There are 2 ways, ruu or revert to stock for ota. You must relock bootloader before ruu or ota. For the ota you need stock recovery as well. There's a few misconceptions floating around. First is that you need to update to run the latest base, this is simply not true, I'm running mikeys latest without issue. The second is basically the same but involving the aroma installer, flashes fine but sometimes kernel will not flash and you boot to bootloader. This does not mean you need to update only that the kernel did not like the new base, fastboot kernel and you'll be fine. Some people still have WiFi issues and others have LTE issues, both should have been addressed in the last 2 updates and people with the latest firmware are still having problems. To me this does not warrant relocking upgrading and going through the unlock again.
A lot of people including myself don't consider 1.19 an upgrade and like om said you don't nerf to update
Sent from my EVO using xda app-developers app
Always best waiting
In my experiences, it is almost ALWAYS best to wait. If for some reason 1.19 gets s-off before 1.15 then u can update. But for now, just wait. I got lucky and I'm 1.12 s-off either way warranty is gone so always get s-off whenever possible.
I keep seeing threads about s-off. I'll like people to be more specific as to what they're trying to achieve that they can't while being s-on?
Sent from my EVO using xda premium
Just the ability to directly flash software to partitions normally inaccessible, Firmware basically. Those of us s-on would have to flash back to stock, lock hboot, and accept an ota or relock and run the ruu
Also, don't know the details of any of it, but in the s-off bounty thread guy is donating a 1.15 hboot. U can flip a coin better than I can say what they will do with it then. Either update it to 1.19 or try and find the exploit on 1.15.
Personally, if I was a badass at finding exploits in HTC coding then I'd crack both like yesterday. But if I was that badass I'd have better stuff to do as well... Hoping for 1.19 s-off just for future development.
Anthonicia said:
Also, don't know the details of any of it, but in the s-off bounty thread guy is donating a 1.15 hboot. U can flip a coin better than I can say what they will do with it then. Either update it to 1.19 or try and find the exploit on 1.15.
Personally, if I was a badass at finding exploits in HTC coding then I'd crack both like yesterday. But if I was that badass I'd have better stuff to do as well... Hoping for 1.19 s-off just for future development.
Click to expand...
Click to collapse
there is a guy in the s-off thread saying he will give up his phone and i saw fuses sent him a PM reply about it hang in there guys
om4 said:
There are 2 ways, ruu or revert to stock for ota. You must relock bootloader before ruu or ota. For the ota you need stock recovery as well. There's a few misconceptions floating around. First is that you need to update to run the latest base, this is simply not true, I'm running mikeys latest without issue.
Click to expand...
Click to collapse
Quick question: Are you saying that if I wanted to run Mean ROM that I do not need to be in the latest OTA? I'm confused because I was under the understanding that we needed to be on 2.13. Please clarify for me.
Sent from my EVO LTE using xda app
No you don't, I ran meanrom a few days ago and today I switched to viper 2.02. Meanroms kernel installer worked fine, viper required fastboot but both run fine
Thanks for the quick response. Wow, I feel like a dumb *ss now. I've been holding out trying any new roms because I didn't want to come off of hboot 1.15.
Which rom do you like better so far between viper and mikey's?
Sent from my EVO LTE using xda app
The level of customization on viper is crazy, meanrom runs great with evilz kernel and is closer to stock. I'm still sifting through the different mods for viper and I've yet to check out any themes but so far but I'm still digging through it all
Sorry in advance. This is more of a confirmation than a question. Anyways, a friend and I have been in discussion about updating hboot. Now I'm s-off with hboot 1.19 and all I did was update to the latest radios. I'm more inclined to believe that that's all I need to do. My friend on the other hand says I should take the OTA or run the latest RUU, get everything including the hboot, then unlock the phone again and continue as normal. His reasoning is because he claims that the phone works better with the latest everything rather than just the radios. Is there any validity to his argument or should I just ignore him.
Sent from my rooted LTEVO running CM10.
Shahal said:
Sorry in advance. This is more of a confirmation than a question. Anyways, a friend and I have been in discussion about updating hboot. Now I'm s-off with hboot 1.19 and all I did was update to the latest radios. I'm more inclined to believe that that's all I need to do. My friend on the other hand says I should take the OTA or run the latest RUU, get everything including the hboot, then unlock the phone again and continue as normal. His reasoning is because he claims that the phone works better with the latest everything rather than just the radios. Is there any validity to his argument or should I just ignore him.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
I'm on hboot 1.12 s-off I just flash the updated firmware when it becomes available my phone works flawlessly. As long as you are running the DR hboot 1.19 you are good to go
I'm not an expert but what I do know is you NEVER want to take an ota if you're rooted. Also upgrading to the newest h-boot is only asking for trouble. Who knows what HTC has up their sleeve. You don't to end up getting burnt. I am on .19 and have the latest radios and firmware and all is working perfectly.
Sent from my EVO using Tapatalk 2
I just got my new Virgin Mobile HTC Evo V today. My previous device was a Samsung Galaxy-class phone (Infuse 4G), so I'm a bit lost with all of the HTC-specific terminology and procedures. All I've read seems to be written by and for people who already have some idea of what's going on. Sadly, I don't.
All I know is that my Evo V is on Hboot version 1.57. I basically want to put it in a state where I can flash ANYTHING I want, which I assume means that I'll need to be S-off with a custom recovery. Do I absolutely need to dowgrade Hboot? Must I be S-off? I just need an initial push in the right direction. If someone could give a brief synopsis of exactly where I need to start, along with some links to the corresponding tools, that would be very much appreciated. I hate feeling like a newb all over again, but hacking HTC doesn't seem to be nearly as simple or intuitive as it was with Samsung. I'm fairly adept at following directions, I just don't want to follow the wrong ones and do something stupid.
ApexPredatorBoids said:
I just got my new Virgin Mobile HTC Evo V today. My previous device was a Samsung Galaxy-class phone (Infuse 4G), so I'm a bit lost with all of the HTC-specific terminology and procedures. All I've read seems to be written by and for people who already have some idea of what's going on. Sadly, I don't.
Click to expand...
Click to collapse
Since you have an Evo V you might want to start here. There are no forums that are specific to the Evo V on XDA.
I do have a guide here in the general forum that works for getting root and S-OFF on the Evo V.
ramjet73
ramjet73 said:
Since you have an Evo V you might want to start here. There are no forums that are specific to the Evo V on XDA.
I do have a guide here in the general forum that works for getting root and S-OFF on the Evo V.
ramjet73
Click to expand...
Click to collapse
Isn't this 3D the EVO V? Thought they were the same D:
Sent from my shooter using xda premium
'Blu said:
Isn't this 3D the EVO V? Thought they were the same D:
Click to expand...
Click to collapse
Same hardware but not the same firmware and network configuration as was confirmed by Sprint users who flashed the "leaked" VM firmware last May. The custom ROM's can be configured for either carrier but not the firmware and the serial numbers (ESN's) are hard wired to a specific service provider.
Also, Virgin Mobile users also don't have the roaming options that Sprint offers.
ramjet73
ramjet73 said:
Same hardware but not the same firmware and network configuration as was confirmed by Sprint users who flashed the "leaked" VM firmware last May. The custom ROM's can be configured for either carrier but not the firmware and the serial numbers (ESN's) are hard wired to a specific service provider.
Also, Virgin Mobile users also don't have the roaming options that Sprint offers.
ramjet73
Click to expand...
Click to collapse
Well that sucks a tad bit. I forgot that the phones had very different network make up.
Sent from my shooter using xda premium
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
ApexPredatorBoids said:
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
Click to expand...
Click to collapse
Yes, you can unlock the Evo V 4G by selecting the Evo 3D on the htcdev website.
I don't consider downloading an all-in-one file "a lot of downloading" and if you think my guide is "convoluted" you're welcome to use the collection of guides that preceded it, including several on the other site that I linked above.
I've unlocked Samsung and other phones before and I know about the "one click" root utilities, but that's not the way HTC does things so we need to deal with it or stay stock.
ramjet73
ApexPredatorBoids said:
Gotta love a long and convoluted process that involves a lot of downloading. At the moment, I'm visiting a relative who doesn't have internet, so my only web access is to tether to my now-throttled data connection. Got about 6 more hours to go before the QADERSO download finishes. Thanks for the help so far. I took a quick peek at the htcdev site and unlocking procedure. I noticed that they don't have one that's VM specific. Should I just use the Sprint one when I get to that point?
Click to expand...
Click to collapse
It's quite a simple process, but it is a fairly long process. Takes about 30 minutes total to get unlocked, rooted, and running all good. Add that to getting ROMs and stuff. That totaled up to 3 days for me because I just could not find the best one, and I've found that Viper3D is great . Getting a 8000-9500 benchmark.
Success
Well, I didn't manage to bust it out in 30 minutes, but I got it done. Probably wouldn't have taken quite so long if I were less inept with command prompts. The "wire trick" was simultaneously simple and a huge pain in the ass. I spent probably 15 minutes doing it over and over and over. But all's well that ends well. I'm now HTCdev unlocked with S-off, and I'm running NegaLite BluROM. So, thanks, ramjet73, for the advice and putting your time into writing the guide.
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
ApexPredatorBoids said:
Well, I didn't manage to bust it out in 30 minutes, but I got it done. Probably wouldn't have taken quite so long if I were less inept with command prompts. The "wire trick" was simultaneously simple and a huge pain in the ass. I spent probably 15 minutes doing it over and over and over. But all's well that ends well. I'm now HTCdev unlocked with S-off, and I'm running NegaLite BluROM. So, thanks, ramjet73, for the advice and putting your time into writing the guide.
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
Click to expand...
Click to collapse
I myself have kept with the Jbear hboot and have been able to run the ROMs I wanted fine (that being MeanROM-ICS, Viper3D, and Harmonia) and it was all good. I have no clue about your other questions, sorry :[. I'm quite new to the Evo 3D and it doesn't seem as simple as my old One V.
ApexPredatorBoids said:
I do have a few general questions still:
-what will absolutely need to be flashed with fastboot; kernels, radios, alternate Hboot versions?
-as far as having some semblance of universal compatibility, should I be fairly safe sticking with Jbear's Hboot version 1.57.5757?
-is there another Hboot version I could flash that would be more likely to be compatible with the vast majority of available ROMs?
Click to expand...
Click to collapse
I usually recommend the JBear GB 1.50.5050 hboot. It will flash and boot all ROM's except the stock ICS ROM and one or two based on that version, as opposed to the 1.57.5757 version that won't boot any GB or AOSP based ROM's.
ramjet73
I've never been much of a fan of Android version 4.x. I just stumbled on what appears to be a very promising Gingerbread ROM, so it looks like I'm going to have to downgrade to Hboot 1.4. I'd assumed that since the phone came with ICS, I'd be stuck with 4.x. Apparently, that's not the case. I love me some GB.
ramjet73 said:
I usually recommend the JBear GB 1.50.5050 hboot. It will flash and boot all ROM's except the stock ICS ROM and one or two based on that version, as opposed to the 1.57.5757 version that won't boot any GB or AOSP based ROM's.
ramjet73
Click to expand...
Click to collapse
Will Jbear 1.50.5050 flash This ROM? I'm thinking someone posted in that thread that you had to be below Hboot 1.50 to flash it. If it will work with that ROM, could you supply a D/L or thread link?
ApexPredatorBoids said:
I've never been much of a fan of Android version 4.x. I just stumbled on what appears to be a very promising Gingerbread ROM, so it looks like I'm going to have to downgrade to Hboot 1.4. I'd assumed that since the phone came with ICS, I'd be stuck with 4.x. Apparently, that's not the case. I love me some GB.
Click to expand...
Click to collapse
Just be aware that all the GB ROM's are based on Sprint builds and as a VM user you will need to figure out what needs to be changed to get things like MMS working properly on the VM network.
I'm not saying you shouldn't do it, just be aware that it will take more than just flashing the ROM and you can get more help with the Evo V on the androidforums.com website in the forums for that version of the device.
ApexPredatorBoids said:
Will Jbear 1.50.5050 flash This ROM? I'm thinking someone posted in that thread that you had to be below Hboot 1.50 to flash it. If it will work with that ROM, could you supply a D/L or thread link?
Click to expand...
Click to collapse
Yes. The JBear 1.50.5050 hboot will flash and boot anything that the 1.4 or ENG 1.04 hboots handle and is based on a more current version of the Evo 3D bootloader. It also allows you to run more fastboot commands than a stock hboot like 1.4.
ramjet73
ramjet73 said:
as a VM user you will need to figure out what needs to be changed to get things like MMS working properly on the VM network.
Click to expand...
Click to collapse
Is it as simple as finding and using the proper APN settings, or is there more to it than that?
ApexPredatorBoids said:
Is it as simple as finding and using the proper APN settings, or is there more to it than that?
Click to expand...
Click to collapse
At least that, and maybe some changes to the build.prop file. I'm a Sprint user so I've never had to do it, but there are VM users here and on androidforums.com that can probably help answer that.
ramjet73