A few moments ago RUU leak 2.11.605.0 dropped in Development introducing yet another pair of radios to the Tbolt landscape. I came to the realization today when I saw someone refer to one of the Tbolt radios as "MR3.25", and I don't think it was by error. To date we've got MR2, real MR2, the MR2.5, the fake MR2.5, MR2.75, MR2.xx... and that's about where I really loose track of it. CDMA radio versions work, but then you end up hunting down what that radio really is and where it came from and it doesn't always address the LTE radio. I maintain a Q&A thread that tries to explain this stuff to noobs and it's simply impossible to explain all the tack-on "MR" names given to all these radios by different devs and users. They're beginning to make no sense I'm not going to explain it in those terms.
What I'd like to suggest here is that devs and users all begin to refer to radios by RUU number of origination. No need to use the entire number, just the first 3 digits, for example 1.70, or 2.10. Devs, if you're ROM is requiring MR2 radios, perhaps indicate "Requires MR2/1.70 or newer radio" To the users: At some point these "MR" names have got to confuse even the most veteran of us. I'd like to ask that these "MR" designations be abandoned in posts and replaced with RUU based designations as I've described above.
I feel there's a lot of confusion going around. Seems many people may not actually knowing what they're using. And there seems to be a general lack of common language regarding radios. This cannot be good for anyone. Please, lets all try to fix this somehow. It's only going to get uglier as more leaks and OTA drop.
loonatik78 said:
A few moments ago RUU leak 2.11.605.0 dropped in Development introducing yet another pair of radios to the Tbolt landscape. I came to the realization today when I saw someone refer to one of the Tbolt radios as "MR3.25", and I don't think it was by error. To date we've got MR2, real MR2, the MR2.5, the fake MR2.5, MR2.75, MR2.xx... and that's about where I really loose track of it. CDMA radio versions work, but then you end up hunting down what that radio really is and where it came from and it doesn't always address the LTE radio. I maintain a Q&A thread that tries to explain this stuff to noobs and it's simply impossible to explain all the tack-on "MR" names given to all these radios by different devs and users. They're beginning to make no sense I'm not going to explain it in those terms.
What I'd like to suggest here is that devs and users all begin to refer to radios by RUU number of origination. No need to use the entire number, just the first 3 digits, for example 1.70, or 2.10. Devs, if you're ROM is requiring MR2 radios, perhaps indicate "Requires MR2/1.70 or newer radio" To the users: At some point these "MR" names have got to confuse even the most veteran of us. I'd like to ask that these "MR" designations be abandoned in posts and replaced with RUU based designations as I've described above.
I feel there's a lot of confusion going around. Seems many people may not actually knowing what they're using. And there seems to be a general lack of common language regarding radios. This cannot be good for anyone. Please, lets all try to fix this somehow. It's only going to get uglier as more leaks and OTA drop.
Click to expand...
Click to collapse
I think the other terminology is more confusing. Mr is write ready for users to understand. It's chronological to go 2,2.5,3 etc
eallan said:
I think the other terminology is more confusing. Mr is write ready for users to understand. It's chronological to go 2,2.5,3 etc
Click to expand...
Click to collapse
But that's the problem... it DOESN'T do that! You've got MR2 leak, which often isn't noted as being a leak, then you've got MR2.5, than MR2.xx, then MR2 OTA which came out on a Froyo OTA, not a Gingerbread leak or OTA... And on top of that, they aren't even all being called the same thing. MR2.xx is going by possibly 3 different names, and the problem isn't going to get better with time. I can't send someone to 2 radio thread, tell them to download MR2, and know what they actually downloaded. I can't tell someone to download the MR2.xx and have any clue what they actually have. I'm not so concerned with what's chronologically correct. Chronology doesn't even suggest a better radio, so what's the point? If radios are identified by RUU of origin there is no confusion about what it is, where it came from, when it dropped... all that stuff can be VERY easily figured out. There's not flashing it before you can figure out what you just flashed. I really think this is the only way to go.
Dude, add a bit of spacing in your OP. It makes it a hell of a lot easier to read. Just a tip.
loonatik78 said:
A few moments ago RUU leak 2.11.605.0 dropped in Development introducing yet another pair of radios to the Tbolt landscape. I came to the realization today when I saw someone refer to one of the Tbolt radios as "MR3.25", and I don't think it was by error. To date we've got MR2, real MR2, the MR2.5, the fake MR2.5, MR2.75, MR2.xx... and that's about where I really loose track of it. CDMA radio versions work, but then you end up hunting down what that radio really is and where it came from and it doesn't always address the LTE radio. I maintain a Q&A thread that tries to explain this stuff to noobs and it's simply impossible to explain all the tack-on "MR" names given to all these radios by different devs and users. They're beginning to make no sense I'm not going to explain it in those terms.
What I'd like to suggest here is that devs and users all begin to refer to radios by RUU number of origination. No need to use the entire number, just the first 3 digits, for example 1.70, or 2.10. Devs, if you're ROM is requiring MR2 radios, perhaps indicate "Requires MR2/1.70 or newer radio" To the users: At some point these "MR" names have got to confuse even the most veteran of us. I'd like to ask that these "MR" designations be abandoned in posts and replaced with RUU based designations as I've described above.
I feel there's a lot of confusion going around. Seems many people may not actually knowing what they're using. And there seems to be a general lack of common language regarding radios. This cannot be good for anyone. Please, lets all try to fix this somehow. It's only going to get uglier as more leaks and OTA drop.
Click to expand...
Click to collapse
I agree 100%
Sent from my ADR6400L using XDA Premium App
After not finding it here, I found it over at RootzWiki. I think all would find something like this very helpful.
http://rootzwiki.com/showthread.php?t=2937
Sent from my ADR6400L using XDA Premium App
farkmeil said:
After not finding it here, I found it over at RootzWiki. I think all would find something like this very helpful.
http://rootzwiki.com/showthread.php?t=2937
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I have a link to a thread almost identical to that in my q AND a thread. It is maintained on XDA by Gu1dry. http://forum.xda-developers.com/showthread.php?t=1048128
http://teambamf.net/showthread.php/242-Radios!
Very clear, very organized.
adrynalyne said:
http://teambamf.net/showthread.php/242-Radios!
Very clear, very organized.
Click to expand...
Click to collapse
Mind if I use that link in my q AND a?
adrynalyne said:
Very clear, very organized.
Click to expand...
Click to collapse
I don't see both radios posted for each release on there...
0.01.69.0625r 1.39.00.0627r
From the 1.70.605.0 RUU:
CDMA: 1.39.00.0627
md5: c2b8d5d7583b8171bc9dd65781f10a45
LTE: 0.01.69.0625
md5: 51c04a8451b596f782cecac37235971c
see one but not the other. XDA link has both radios per release
rayjr13 said:
I don't see my radios all on there...
0.01.69.0625r 1.39.00.0627r
see one but not the other.
Click to expand...
Click to collapse
Kinda what I'm talking about...
What did you flash? Given Adrynalyn's reputation, his radio thread should be the final word and should match up with the Gu1dry thread.
rayjr13 said:
I don't see both radios posted for each release on there...
0.01.69.0625r 1.39.00.0627r
From the 1.70.605.0 RUU:
CDMA: 1.39.00.0627
md5: c2b8d5d7583b8171bc9dd65781f10a45
LTE: 0.01.69.0625
md5: 51c04a8451b596f782cecac37235971c
see one but not the other. XDA link has both radios per release
Click to expand...
Click to collapse
Thats because only Gingerbread offers both version numbers. As of GB, I have been doing so.
These phones are brick-prone, so I am not terribly exicted to flash all the other radios to see what they read.
Rest assured though, each of the radios I list have been pulled from unaltered, unmodified RUUs.
adrynalyne said:
Thats because only Gingerbread offers both version numbers. As of GB, I have been doing so.
These phones are brick-prone, so I am not terribly exicted to flash all the other radios to see what they read.
Rest assured though, each of the radios I list have been pulled from unaltered, unmodified RUUs.
Click to expand...
Click to collapse
+1
Sent from my ADR6400L using Tapatalk
loonatik78 said:
A few moments ago RUU leak 2.11.605.0 dropped in Development introducing yet another pair of radios to the Tbolt landscape. I came to the realization today when I saw someone refer to one of the Tbolt radios as "MR3.25", and I don't think it was by error. To date we've got MR2, real MR2, the MR2.5, the fake MR2.5, MR2.75, MR2.xx... and that's about where I really loose track of it. CDMA radio versions work, but then you end up hunting down what that radio really is and where it came from and it doesn't always address the LTE radio. I maintain a Q&A thread that tries to explain this stuff to noobs and it's simply impossible to explain all the tack-on "MR" names given to all these radios by different devs and users. They're beginning to make no sense I'm not going to explain it in those terms.
What I'd like to suggest here is that devs and users all begin to refer to radios by RUU number of origination. No need to use the entire number, just the first 3 digits, for example 1.70, or 2.10. Devs, if you're ROM is requiring MR2 radios, perhaps indicate "Requires MR2/1.70 or newer radio" To the users: At some point these "MR" names have got to confuse even the most veteran of us. I'd like to ask that these "MR" designations be abandoned in posts and replaced with RUU based designations as I've described above.
I feel there's a lot of confusion going around. Seems many people may not actually knowing what they're using. And there seems to be a general lack of common language regarding radios. This cannot be good for anyone. Please, lets all try to fix this somehow. It's only going to get uglier as more leaks and OTA drop.
Click to expand...
Click to collapse
I definitely agree.
Related
ive been trying to download the latest radios for WM 6.1 I keep getting a 404 when I click on any of the links provided. Is anyone else having this problem?
jspetrino said:
ive been trying to download the latest radios for WM 6.1 I keep getting a 404 when I click on any of the links provided. Is anyone else having this problem?
Click to expand...
Click to collapse
Just a suggestion, you might want to read the announcment on all of the Forums by Flar...
This is on the front page and at the top of the kaiser forum stickies
http://forum.xda-developers.com/announcement.php?f=378
ah, well i guess i have to wait to get my latest WWE radio... are there mirrors anywhere?
jspetrino said:
ah, well i guess i have to wait to get my latest WWE radio... are there mirrors anywhere?
Click to expand...
Click to collapse
This goes beyond just not searching... At this point you're not even reading. There are several radio rom posts in this forum.
Mods: Please shut down this waste of space thread.
Well it had to happen, in fairness, I know announcements are sometimes overlooked. Maybe they should be in 72pt extra large BOLD or something.
Actually I think I will leave this thread to drift around, just in case others fail to see the announcement. It will save folks having to answer if others have the same question.
Mike
mikechannon said:
Well it had to happen, in fairness, I know announcements are sometimes overlooked. Maybe they should be in 72pt extra large BOLD or something.
Mike
Click to expand...
Click to collapse
I think the 72pt font also needs to flashing and changing colors to really get people attention...because obviously reading is a lost art in this day and age.
AllTheWay said:
I think the 72pt font also needs to flashing and changing colors to really get people attention...because obviously reading is a lost art in this day and age.
Click to expand...
Click to collapse
Well, maybe not so, AllTheWay. I mean I feel kind of sorry for the poor guy. I mean, obviously he can't read and he has such a nice device. I can only imagine what contract he signed for his cellular service. It probably has an ETF of his first born or a kidney or something.
Maybe if the default announcements would show as a PM notice (that couldn't be turned off until a user hit's x number of posts) with a sexy man or woman (don't want to discriminate ) that reads the announcement with word highlighting for the user to follow along with. Maybe then people will actually read...
Or maybe not.
most people nowaday prefer to ask questions and want to get answer right there. They dont read anymore, not even skim/scan. Next time if you have an announcement, create a flash movie with audio that speaks what you want and put it up here. If they dont read the word in the flash movie, they could still hear.
so i just loaded froyo 2.2 and the A853_Telus_Upgrade_SHOLS_U2_03.11.0_USASHLSMR2TLSB1B2B506D.0R_Service1FF.sbf for the boot load, everythin works, but i have no signal. help would be greatly appreciated, thanks
Tonka, no offense intended, but why do we need four new threads from you, all pretty much relating to the same issue?
furthermore, if you had read the guide posted with the ROM, you would've known to back up your radio files BEFORE flashing...
after flashing and restoring them, if it's still not working, there are posts in the ROM's thread that include links to the radio files to various popular carriers, almost all of which work.
I got my radio files from someone on the forum here, you can too.
btw, RTFM. honestly.
im sorry, its jus i kept encountering other problems along the way, but would u please give me the link to these radio files, an tell me where id have to place them. thanks
TONKAFORCE said:
im sorry, its jus i kept encountering other problems along the way, but would u please give me the link to these radio files, an tell me where id have to place them. thanks
Click to expand...
Click to collapse
sure, here's a great link for you to get started with...
http://www.google.com
ur an asshole
TONKAFORCE said:
ur an asshole
Click to expand...
Click to collapse
thanks for the compliment.
to be totally frank, I had many of the same issues you did. From this forum alone, I'm up and running full time on the MotoFrenzy 2.2 build.
I only got working because there's plenty of other people who have had the same problem who have ALREADY documented the fixes.
If you look hard enough, I bet you'll find them too.
-- edit --
this reminds me of the old addage about teaching a man to fish... just in this case, it's about teaching a man to search.
well it would save me a lot of time if you could just help me, like i just have one question,i got the working radio files from system/etc/motorola/bp_nvm_default/
an copied:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
now i jus dont know how to replace them witht eh froyo 2.2 ones. could u help me?
I really can't. I already spent a significant amount of time searching for answers in the loins of this forum for myself... I don't have time to do it for you too.
To be honest its quite the selfish request you're making there... hmmm... and you call me an asshole then expect me to help. Ha. No thanks.
Sent from my Milestone using the XDA App
just check out the first couple of pages of dexter's post, it's all in there
not to interfere with the debate,
but an honest answer is also, if you cannot understand the steps explained, i would not recommend trying to install any mods for openrecovery and messing with the files in the system..
you can easily corrupt the image, and you will spend even more time on trying to figure out why A is not working , while B,C,D problem suddenly occur causing A not to function..
I know HTC made it easy for all modders to make custom firmwares using almost identical radio's and only in some cases, it goes really bad for some regions, but in our case Motrola decided to make the baseband a huge part of the drivers and way to resolve communication and even make it provider locked or complex in a way i cannot even explain. (preferred providers over others as example, custom mobile services as another)
many HTC mods, includes support for like 12-15 countries in one image, looking at "locale" supported, where motorola pushes 12 different firmwares out..i personally only mess with a UK as it worked fine for me, trying to make the other 11 work, would require much more support and engagement in the technical aspects of the mod..we are lucky a few document and write feedback on how they accomplished to make it work (telus as example)
I couldn't agree more.
Sent from my Milestone using the XDA App
got it all working
Removed by me.
Still something that should be considered though.
No disrespect intended but I would take this down before you get shut down. This is not the droid forum and this is how it is done here in the Captivate forum. There is more to each of these ROMs that separates it from one and other. Try running them one by one and you will see what I mean. Some are heavy, some are light, some are slower and some burn your freaden hand(hypothetically speaking of course.) A lot of hard work goes into each and every ROM and you will get a lot of crap for this post. Also, look at each ROM, do you see anything that is different among them? check out the firmware they are based on. Some are I9000, some are Vibrant and some are the new GB from the Nexus firmware. There is plenty that make them unique to the dev. Please consider removing this post, we want the Captivate forum to be a friendly place and this is definitely going to cause some issues.
adamholden85 said:
No disrespect intended but I would take this down before you get shut down. This is not the droid forum and this is how it is done here in the Captivate forum. There is more to each of these ROMs that separates it from one and other. Try running them one by one and you will see what I mean. Some are heavy, some are light, some are slower and some burn your freaden hand(hypothetically speaking of course.) A lot of hard work goes into each and every ROM and you will get a lot of crap for this post. Also, look at each ROM, do you see anything that is different among them? check out the firmware they are based on. Some are I9000, some are Vibrant and some are the new GB from the Nexus firmware. There is plenty that make them unique to the dev. Please consider removing this post, we want the Captivate forum to be a friendly place and this is definitely going to cause some issues.
Click to expand...
Click to collapse
Based on this post you should consider yourself lucky only one person saw the original post.
Sent from my Captivate.
I always miss the good posts! It definitely must have been something for you to respond like that, Adam.
Delgoth said:
Removed by me.
Still something that should be considered though.
Click to expand...
Click to collapse
Given only a very small number of people saw your original post, whatever it was is a bit hard to consider, isn't it?
I am constantly amazed at how many people have the gall to complain about ROMs. ROMs that the devs build for free, in their personal time.
Spend less time whining and more time flashing, you will see how little overlap there is.
Sent from my SAMSUNG-SGH-I897 using XDA App
I wasn't complaining i was suggesting that more of the devs work together rather than alone. As in there seems to be some overlap in some roms.
Delgoth said:
I wasn't complaining i was suggesting that more of the devs work together rather than alone. As in there seems to be some overlap in some roms.
Click to expand...
Click to collapse
So develop your own ROM with no overlap whatsoever.
polarbee said:
So develop your own ROM with no overlap whatsoever.
Click to expand...
Click to collapse
In binary.
On an abacus.
That you made from sticks.
Won't overlap a thing in existence that way.
God forbid some things overlap with limited sources i.e. i9000 ish and NO source for FROYO on the captivate... REALLY man? like 5 people actually DEV for the captivate and they all put out some good stuff. A few more port stuff from other galaxy s phones. Be thankful we have these guys. Or better yet, sell your captivate and go get an EVO there are TONS of roms for that. Then you can flash something totally different everyday so you get no overlap. You NOTICE how i randomly CAPITALIZE words? FAIL to you buddy.
I was a child and don't need proof of it lmfao. Rip hero cdma on that note.
megaghostgamer said:
Hey hater grow a pair of balls and show yourself and stop hiding in the bushes rating my threads 1 star like the lil sin you are. Get over it stop hating on others cause you can't develop for yourself or make good threads. Your probably just a little kid with no life starring at the computer screen all day. Prove me wrong and post like a real person If not just goes to show who you really are :silly:
Click to expand...
Click to collapse
Im not going to rate the thread, its good, but definitely not SUPER EASY, thats fixable however, as its just how the guide is setup which detracts from being SUPER EASY...
Numbers/Letters for steps, more spacing, less run-ons in sentence structure...
XDA is a site thats supposed to be for developers but id hazard a guess and say 95%+ are USERS and probably 95% of that 95% are only here from hap-hazard links from other sites and/or google search's and will get lost in your guide...
Dont misunderstand me, after being here on XDA it was EASY for ME to understand, but probably not for the majority of people.
NEEDLESS TO SAY, thanks for a great guide, its nice to see a refresh for the "how-to" guides every once in a while (yearly?)
ROM Manager won't install on the latest OTA of the HTC Hero by Sprint. Making this essentially a root-only guide. Unless by some chance it has not been updated.
DizturbedOne said:
ROM Manager won't install on the latest OTA of the HTC Hero by Sprint. Making this essentially a root-only guide. Unless by some chance it has not been updated.
Click to expand...
Click to collapse
This guide was late to the game.
There's a older version of cwm that works that's been posted several times, even recently.
Or just use "flash_image."
I read the wiki and I'm fine.
Sent from my SCH-I535 using xda app-developers app
I don't quite follow... he wrote this guide two months ago. It's OK, but I'd take a more remedial approach. I may submit my own, one that I crafted to help me through the process last year. There's definitely older ways to do things and newer ones as well, the newest being more straightforward.
As for the Hero, the later ROM published by Sprint blocks you from replacing the bootloader. You have to manually flash an earlier version of the Sprint ROM (2.27.651.5). Some enterprising folks have simplified it by creating an EXE that does it all, found HERE.
cytherian said:
I don't quite follow... he wrote this guide two months ago. It's OK, but I'd take a more remedial approach. I may submit my own, one that I crafted to help me through the process last year. There's definitely older ways to do things and newer ones as well, the newest being more straightforward.
As for the Hero, the later ROM published by Sprint blocks you from replacing the bootloader. You have to manually flash an earlier version of the Sprint ROM (2.27.651.5). Some enterprising folks have simplified it by creating an EXE that does it all, found HERE.
Click to expand...
Click to collapse
I've had my hero for ages ever since it was released I didn't know htc locked the bootloader. I'm getting tired of them doing that but this is the guide I used when I rooted my hero and I don't know why cwm is only available to 2.2+ ill have to post the apk. Sorry I haven't been around. As you see I have 3 other devices to maintain which is my signature.. The hero just so happens to be my slowest which isn't good. I love the hero don't get me wrong it has the best feeling on the outside. I mainly port ics/jb which hero doesn't play nice with. I have to release some roms over here soon
Sent from my VS920 4G using xda premium
I've only had HTC Devices since I first got my G1 in 2008 the reason I made this thread is every single HTC device(and Ive had every T-mobile one) I've had has had a pg--img.zip that you could load in HBoot so that that you can return back to stock, is there no such thing as one for the One S...or have I just overlooked? as this maybe my only alternative because of my issues with RUUs mentioned in my other thread.
kirkcody said:
I've only had HTC Devices since I first got my G1 in 2008 the reason I made this thread is every single HTC device(and Ive had every T-mobile one) I've had has had a pg--img.zip that you could load in HBoot so that that you can return back to stock, is there no such thing as one for the One S...or have I just overlooked? as this maybe my only alternative because of my issues with RUUs mentioned in my other thread.
Click to expand...
Click to collapse
2 thread, same issue =
Very true kind sir, but in my defense this thread was more of a question of if there are PGIMG.zips for the One S and seeing as I haven't really received much help with my other thread(thank-you to those that offered help) I decided to try another route after searching the threads and not finding an answer....without coming across as a douche may I ask how you felt that your reply was productive?
As productive a your thread bomb "bump". Your problem is unique, so one thread should be enough, kind Sir.
Btw, my guess is the lack of SOFF precludes Pdxxx installs.
Point taken, I by know means want to get into any verbal sparring with any of my fellow xda brethren, honestly when I seen an immediate response to this thread, only to see that it was not a suggestion to solve my problem I may have took offense and got a little testy...this whole ordeal is just a little frustrating as I've covered all the bases that I can think of.
El smurfo I do believe your correct about the Pgimg.zip.... I should of thought of that ?!?....told you this whole thing has me frustrated.
It does work, as far as I know, they are called PJ40IMG.zip. You can use them to upgrade HBOOT versions and radio possibly. But I think it has to be signed by HTC
Sent from my locked, tampered ville
Hboot didnt detect the PJ40IMG.zip :crying:
Check behind SIM cover, there is a small sticker with a PJ number, my international S4 model is PJ40100 and I believe the TMOUS has a different number and presumably the S3 variant has yet another number.