Ok.I've heard some good this about the 11.19 radio, I am on the 07.28 radio and from what hear the 11.19 radio is better on battery life. Im running redemption 2.3 and I want to flash 11.19 radio. I have the file but how do I install it.
Dinc
Rename the file to PB31IMG.zip, make sure theres not a file with the same name, put on root of sdcard, reboot to hboot/bootloader. The phone will check for an update, hit yes. Let it do its thing, reboot to recovery and flash a kernel of your choice cuz the radio update erases ur kernel...sometimes it doesnt say the radio updated...just reboot again.
Do not attempt the radio update twice in a row it will brick your phone!
Sent from my ADR6300 using XDA App
Make sure you have s-off. unrEVOked forever.
Sent from my ADR6300 using XDA App
Sorry lol. But how do I get into the boatloader. I knw how to get inti hboot but not bootloader.
Dinc
snapper915 said:
Sorry lol. But how do I get into the boatloader. I knw how to get inti hboot but not bootloader.
Dinc
Click to expand...
Click to collapse
Same thing.
Sent from my ADR6300 using XDA Premium App
Oh ok. Well I put the file on the root of my SD card ,rebooted to hboot and nothing happened. What am I doin wrong.
Dinc
snapper915 said:
What am I doin wrong
Click to expand...
Click to collapse
What is HBOOT saying when you boot into it? When you enter HBOOT there should be a delay of a second or two, then it should check for the presence of PB files on the SDCARD
Most common mistakes that people make:
They don't format their SD card to FAT32
They mess up the file name (like PB31IMG.zip.zip)
Yes the file has zip beside it. So what do I need to do. Do I need to rename the file without adding the zip. And I'm pretty sure that my SD card is formatted right. Cause I'm constantly flashing roms and kernels.
Dinc
snapper915 said:
Yes the file has zip beside it. So what do I need to do. Do I need to rename the file without adding the zip.
Click to expand...
Click to collapse
It needs to be PB31IMG.zip
If it is PB31IMG.zip.zip then rename it to PB31IMG.zip
snapper915 said:
And I'm pretty sure that my SD card is formatted right. Cause I'm constantly flashing roms and kernels.
Click to expand...
Click to collapse
Flashing through recovery is different than flashing through HBOOT. Just because you have successfully flashed through recovery does not mean for sure that your card is formatted to FAT32. Check that your card is the right format.
Yep. I tested it on my other dinc that I don't or can't use it worked perfect. Now which radio are must people recommending. I hear good things about 11.19. I'm currently on 07.28. And my signal isn't that good at all around my house.
Dinc
Ugh
pete_kowalski83 said:
Do not attempt the radio update twice in a row it will brick your phone!
Click to expand...
Click to collapse
One of the greatest mistakes made by anyone or any group for the incredible, was the flash in time that unrEVOked decided to release ONE thing as a patch; and forever and ever the absolute fallacy that you cannot flash the radio twice was born.
The ONE thing that this applied to (which is LONG gone) was a patch; and if you tried to patch the patch, you bricked. That has nothing to do with flashing a full on radio.
Of course, flashing a radio is generally dangerous, so you wouldn't want to keep flashing it over and over anyway; but UGH when will that die?
snapper915 said:
Ok.I've heard some good this about the 11.19 radio, I am on the 07.28 radio and from what hear the 11.19 radio is better on battery life. Im running redemption 2.3 and I want to flash 11.19 radio. I have the file but how do I install it.
Dinc
Click to expand...
Click to collapse
First of all, forget everything you've heard about a particular radio. Baseband performance is extremely subjective based upon individual variables. Basing selection of a radio on someone else's experience is like saying, "His favorite color is blue, therefore mine should be blue as well."
Take each of the baseband versions for a test drive for a few days apiece to see which one gives you the best overall performance.
jdmba said:
One of the greatest mistakes made by anyone or any group for the incredible, was the flash in time that unrEVOked decided to release ONE thing as a patch; and forever and ever the absolute fallacy that you cannot flash the radio twice was born.
The ONE thing that this applied to (which is LONG gone) was a patch; and if you tried to patch the patch, you bricked. That has nothing to do with flashing a full on radio.
Of course, flashing a radio is generally dangerous, so you wouldn't want to keep flashing it over and over anyway; but UGH when will that die?
Click to expand...
Click to collapse
+1
Every time I see that posted, I want to beat my head against the fall. Flashing a radio over itself will not brick the phone. As you've stated, this held true for the one leak from unrevoked released as a .diff patch. The basebands we're dealing with now are full versions and include error checking.
najaboy said:
+1
Every time I see that posted, I want to beat my head against the fall. Flashing a radio over itself will not brick the phone. As you've stated, this held true for the one leak from unrevoked released as a .diff patch. The basebands we're dealing with now are full versions and include error checking.
Click to expand...
Click to collapse
Post a link to where it says its ok then...havent heard that and whats it to you if were trying to be safe jackass
Sent from my ADR6300 using XDA App
jdmba said:
One of the greatest mistakes made by anyone or any group for the incredible, was the flash in time that unrEVOked decided to release ONE thing as a patch; and forever and ever the absolute fallacy that you cannot flash the radio twice was born.
The ONE thing that this applied to (which is LONG gone) was a patch; and if you tried to patch the patch, you bricked. That has nothing to do with flashing a full on radio.
Of course, flashing a radio is generally dangerous, so you wouldn't want to keep flashing it over and over anyway; but UGH when will that die?
Click to expand...
Click to collapse
Well CLEARLY i havent read that, rather b safe than sorry
Sent from my ADR6300 using XDA App
Ok, I flashed 11.19 radio and it worked perfect. do these things need to settle before I notice any difference. If there are any difference in theropy the two.
Dinc
Flashing a radio over a radio is like flashing a Rom over a Rom. Not a problem.
Sent from my Magnolia Incredible
One thing I've wondered is radio compatibility with new software versions. It seems with my og droid when I went from 2.0 to 2.0.1/2.2, there were required baseband updates. Same with my fascinate, but on the same platform. When we went to DL09, although still 2.1, the radio update was required. I've noticed old radio versions being the culprit of a few CM7 issues also.
Sent from my ADR6300 using XDA Premium App
Wow - I've been amazed how peaceful these forums were. Somebody explains the situation, states it wont cause a problem and gets called a "jackass" - that's productive.
As it was pointed out, flashing a radio can go wrong and brick your phone, so why would you do it over and over? Do you play russian rullette?
I find it funny that those who "heard" flashing the same radio 2 times will brick your phone INSIST that you have to PROVE it is wrong - though it's fairly obvious their phones are still working so they clearly have no personal evidence!
Scott
pete_kowalski83 said:
Post a link to where it says its ok then...havent heard that and whats it to you if were trying to be safe jackass
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Hold up there, Pete... no need to be so acerbic about it. The only radio that would cause a brick if flashed over itself was the 2.05 .diff patch that was released by unrevoked. That one could brick their phone by flashing a radio image over itself is merely a persistent myth that, like most urban legends, refuses to die. One of the frustrating aspects is when it's repeated by a well respected member of the community. That being said, the posts from Adrynalyne clarifying this were relatively easy to overlook given the sheer volume of posts around that time regarding the Froyo update.
http://androidforums.com/1522874-post8.html
The danger before was when we were using radio patch files. They have no error checking, just overwrite whatever the hell they want. So it only works once.
These are full images. Two of them were built by a member of Unrevoked (2.05 and 2.07). I had their blessing to post this thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=8029185&postcount=99
adrynalyne said:
Flashing the same radio should be fine. That was only true if the radio was a patch file.
Click to expand...
Click to collapse
Related
Hi, I have been flashing many ROMs and trying different tweaks with my evo since I got it. However I have decided to flash the new radio which I have not done before. What are the critical steps involved in insuring I do not brick my phone?
Also, is there an advantage with installing updated radios through Hboot with the pc361 file over recovery? I know there is none currently for the newest, but was wondering if there is any advantages. Thanks for the replies.
Sent from my PC36100
If you're going to flash a radio through recovery just make sure your getting it from someone who knows what they are doing. Also make sure you have plenty of charge on your battery and make sure not to remove your battery during the flash.
The only advantage of running a PC36IMG is you get a fesh clean system. I don't think it matters that much but like formatting c: and reinstalling some people like to run an RUU every few months. As long as you get your radio_update.zip from a reputable source then there is no advantage, regarding the radio, to running a whole PC36IMG just to get a radio out of the deal. Flashing a radio from recovery will not affect anything else you have set up already.
nebenezer said:
If you're going to flash a radio through recovery just make sure your getting it from someone who knows what they are doing. Also make sure you have plenty of charge on your battery and make sure not to remove your battery during the flash.
The only advantage of running a PC36IMG is you get a fesh clean system. I don't think it matters that much but like formatting c: and reinstalling some people like to run an RUU every few months. As long as you get your radio_update.zip from a reputable source then there is no advantage, regarding the radio, to running a whole PC36IMG just to get a radio out of the deal. Flashing a radio from recovery will not affect anything else you have set up already.
Click to expand...
Click to collapse
Can you also answer this question. Why is the only Hboot we can use for root the .76 version? Is there something inherent with it or is it that no one has altered the .79 version yet? Thanks for taking the time.
rafroehlich2 said:
Can you also answer this question. Why is the only Hboot we can use for root the .76 version? Is there something inherent with it or is it that no one has altered the .79 version yet? Thanks for taking the time.
Click to expand...
Click to collapse
the .76 version is the engineer build. .79 is the consumer build
Just read about the Bootloops and recoveries being lost for no reason off AOSP roms. What is everyone's opinion on this situation?
Sent from my PC36100 using XDA App
I've had boot loops in both aosp and sense roms. Usually they correct themselves with a reflash. I saw someone post earlier that their nandroid backups where gone but not really, they just werent showing up in recovery. I dont see how a rom could cause a deletion of a nandroid on your sd card. I think when an issue like this arises it's probably because some did something they werent suppose to. You having problems with an aosp rom? Keep in mind I dont use aosp roms any longer, I like the convenience of sense (prl/pri update, dial a contact, rarely a 4g or gps issue)
I haven't had any issues with aosp roms either. I just read in this thread:
that off of aosp Roms that there recovery just disappears and nothing but bootloops off the white htc screen.
ooo scary stuff... Ill stick with sense lol F-that!
I think it's a bunch of BS and people covering their asses because they forgot to put on the ENG hboot and figure out how to flash a new recovery image.
ENG hboot. How would you know which one it is drma. **** I need to check which one it is. haha
marcusva79 said:
ENG hboot. How would you know which one it is drma. **** I need to check which one it is. haha
Click to expand...
Click to collapse
Eng boot is like the original, which comes s-off, so bootloader is always s-off. You can check by going into the bootloader and checking your hboot version.
I know mine says s-off,hahah. While reading both those articles i see that everyone on there that has been having that issue use unrevoked.
drmacinyasha said:
I think it's a bunch of BS and people covering their asses because they forgot to put on the ENG hboot and figure out how to flash a new recovery image.
Click to expand...
Click to collapse
I've tried helping a few of the guys having trouble, with everything I know how to do. I've had them try flashing recovery images every way I know how. Perhaps you wouldn't mind stopping by the thread http://forum.xda-developers.com/showthread.php?t=1009672 and seeing if there's something that was missed? I don't know fastboot too much, other than how to flash an RUU with it, but one of the guys had successfully downgraded to the .76 Eng Bootloader to try just that. Maybe you could offer some assistance? Because everything else has seemed to fail, Everything. Whether you think it's BS or not, your help would be appreciated.
I was Flashing the OTA 2.2 Froyo Leak a while ago and it just didnt finish for some reason. Now when I try to turn it on it Vibrates 5 times and has a green blinking light.
Also it is S-ON now for some reason as well.
I have looked everywhere and cannot find a solotion.
Any help is appreciated.
Edit* I have tried flashing other roms and still nothing, (I can access HBOOT but not Recovery) and I cannot flash recovery either. Everything but Hboot is gone. And i tried flashin Ruu and it says main system too old.
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
carngeX said:
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
How can I get S-OFF then? I can access Recovery but it doesnt do me any good it wont read my sd card.
I have no idea what I did, but it rebooted itself and its working
this is EXTREMELY weird. I had the phone plugged in because I wanted to root, but i was first getting the SD Card files off and when I unplugged the phone the same thing happened already....
So then I plugged the phone on again, went into HBOOT and ran the image until it told me it cant be read, and rebooted and back to normal....
Any idea what happened? I just wanna get opinions out of curiosity.
cvbcbcmv said:
cool. But no you don't want to be s-off for flashing the RUU back to stock, then you actually flash a s-on image first.
Click to expand...
Click to collapse
He said he was trying to flash recovery and other ROMs to try and get it to work though too... You can't flash custom recovery without being S-Off.
If you want to flash back the RUU, and go back to complete unrooted stock... then yeah, you want S-On.
carngeX said:
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
SteveG12543 said:
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
eljean said:
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
Click to expand...
Click to collapse
Like I said previously, 5 vibrates is usually a hardware issue, meaning you're most likely going to have to send it in for replacement. There's been a few people to recover from a 5-vibrate brick, but they had gotten lucky. You can search the forums and try to find how they fixed it (can't remember the thread off hand, just do a search for 5 vibrates and you'll get lots of results).
carngeX said:
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
Click to expand...
Click to collapse
I guess so, idk tbh lol. I've had my Inc since day one, and rooted it rather early.
Sent from my Droid Incredible running a random CM7 nightly.
yeah except i bought off ebay so i cud flash to boost. and i did but then i got too curious and ended up with bad nv items on the phone fixed it, then my meid came as <not available> (which still remains and i believe is the problem) and now this... i cant unplug my fone or it will die on me...
i need to get S-OFF and i might be able to fix it... any ideas on how to do this through HBOOT
i need to flash a rom thats what i need to do, because ihave no drivers.., thats the hardware issue and my meid but thats not importatn
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
k_nivesout said:
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
Click to expand...
Click to collapse
How can this be possible? Can you just show me a quick summary and show me links to this method of rooting
Sent from my ADR6300 using XDA App
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
k_nivesout said:
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
Click to expand...
Click to collapse
Oh no is I bought 2 bricked phones from ebay as a wholesale and im trying to fix both of them which have different issues.
eljean said:
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
Click to expand...
Click to collapse
oh **** theres a fix for this lol i never knew
JoelZ9614 said:
oh **** theres a fix for this lol i never knew
Click to expand...
Click to collapse
Yeah the guide was released last month
Sent from my ADR6300 using XDA App
So I was reading a post about someone who was potentially able to downgrade hboot 2.16 hw4 2.3.3 to hboot 2.10 via bootloader and a PC63IMG.zip that had 3.70 in it. So I tried on my 2.3.3 s-On evo and sure enough it failed. It wouldnt work because it was an older version. So, I extracted the PC63IMG.zip and replaced the hboot 2.10 with hboot 2.16 (renaming hboot 2.16 to hboot 2.10) from the post in the dev section. I used winrar and with normal compression rezipped the files and signed in android kitchen. it actually loaded the files and went through checking them, but once check it kicked me back to the main menu of the bootloader with no error or messages. I tried the same with the file with no compression when zipped and signed and i got an error stating that it was a wrong file. and didnt even pass the check. So have I stumbled upon something simple and useful? Can someone help me look into this further and maybe it will get us somewhere. Or am I a dumb?
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
You do know the dev section is for more than ROM's. Moron. This is a post from someone attempting to find root and you show your true intelligence level.
Sent from my PC36100 using Tapatalk
spotopolis said:
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Click to expand...
Click to collapse
He wasn't serious about porting anything, common thing to do when someone posts in the wrong section (especially in development).
On my main note, any modification of an "official" PC36IMG.zip would break HTC'S signature and the bootloader would not accept the update.
Sent from my PC36100 using XDA Premium App
He's attempting to Flame I believe. Due to a lot of mis placed posts. However, I do not find this to be mis placed. It is valid, and just the fact that it tried to run is great. farther then most have gotten, and the way I see it, any good inputs/thoughts should be welcomed warmly.
Sent from my Xoom using XDA Premium App
So now what I am trying to do is download, extract, and replace the hboot from http://www.megaupload.com/?d=VSFLE9CD with the 0.76 hboot, repack, resign, and test in the bootloader. This is all really simple stuff and thats why I am wondering if it will work. Because its so simple something like this was overlooked.
HipKat said:
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
Click to expand...
Click to collapse
as far has my bootloader says for now it has the latest everything unfortunately. hboot 2.16 hw4 and all that. I was surprised that I was able to get passed the check without an error doing this though and its why I posted. I have 4 minutes left on the new PC63IMG.zip downloading before I can try to mess with it.
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
sivarticus85 said:
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
Click to expand...
Click to collapse
I am about to attempt now after signing the zip with kitchen.
spotopolis said:
I am about to attempt now after signing the zip with kitchen.
Click to expand...
Click to collapse
You will be my hero if this works.
Damn! Same thing. I loaded up the latest update with the older hboot renamed to match the new one it replaced. rezipped with normal compression, signed PC63IMG.zip with latest kitchen, it loaded the modded PC63IMG all the way in the bootloader and passed that, then started checking the file and then just went to the main menu again with no errors.
Is it possible that it is not doing anything because it thinks im loading up the same version it is running? Could I simply change another file to make the bootloader think Im uploading a newer version so it would take the update?
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
That sucks. Oh well can't hurt that you tried.
Otta way to think out of the box. I hope u get somewhere with this buddy. I would love to help but I know nothing. Lol. I can make lock rings. That's bout it. Good luck
Sent from my PC36100 using Tapatalk
androidsupra said:
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
Click to expand...
Click to collapse
I know that but if you don't sign with the kitchen it wouldn't have even gotten this far correct? So its something right? Even if it doesn't work, its another thing on the list that has been tried and maybe it will lead to something else. You never know with electronics. A single random chip could be made slightly different from others and it changes everything. No way to know until you try.
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of tricking the bootloader. And the cycle continues.
androidsupra said:
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of pricking the bootloader. And the cycle continues.
Click to expand...
Click to collapse
Is that not the point of this community? Someone trying to use some other persons idea and expand on it? Who cares if it ultimately doesn't work? Its information.
Greetings!
Thanks for stoppin' in. Hate to clutter the posts, but all my browsing/searching through the site thus far has lead me to older links that don't seem to answer my questions.
My history with my HTC Droid Incredible has always been a mix of positive and negative. One thing I've always been plagued by is a hit-or-miss experience with my call signal and messages.
Details:
-Incoming calls don't ring and go straight to voicemail (I use google voice).
-Many calls are plagued by static or generally poor signal.
-Text and image messages are often not received, or when they are, they often arrive hours after the fact (even the next day).
I've been told that flashing a ROM to a rooted device may include flashing the radio and that each ROM may include its own copy of a radio version. Is this true?
Is flashing the radio typically part of the ROM?
What version of the radio is considered best or most efficient for a VZW HTC Droid Incredible currently?
Is it worthwhile to flash the radio separately?
I'm currently on the beta ICS Miui rom and running smoothly aside from a small handful of buggy behaviors. I've seen these issues on stock as well as Cyanogen 7 and other MIUI ROMs. This is also my second (or third?) Incredible, having had it replaced under Warranty in the past and have typically always had some issues of this kind. Typically, I've just considered some of it to be part of the luck of the draw when using a cell phone.
Anywhos, thanks for the help, folks! If you need further details, please feel free to ask.
No custom roms come with radios that i have ever seen.
Flashing a raido may help your situation and it may not. As to which radio, it is really a matter of which one works best for you.
Here is a page with a bunch of radios that are all compatible with the incredible, even the ones labeled evo. http://dinc.does-it.net/radios
I go with the 07.07 radio (GB update version) it works fine, that or the newest Evo radio. 08.08 or 12.19. I live in a splotchy signal area and from playing with it, it seems the newest ones work best for me.
Sorry for the late reply. Thanks for the suggestions and input - I'll look into it as soon as I have a chance to get to a computer and such.
Looks like I need to re-flash my ROM as it is, given the alpha of Miui ICS I've been using isn't behaving very dependably at this time.
After I figure out a way to back things up and actually load into recovery (another mysterious issue has recently cropped up where I cannot get past HBOOT), I'll get a fresh ROM done and try another radio.
Anything I should be aware of regarding the radio with consideration to the process or eventually returning to stock if needed?
Kudos!
Sent from my ADR6300 using XDA
General Update:
I tried a number of different solutions to my recently developed issue of being unable to boot recovery. I could get into HBOOT, but every time I tried selecting Recovery, it would default into another reboot of HBOOT. ROM Manager hasn't been any assistance either, as directing it to load into Recovery only brings up HBOOT.
On a whim, I decided to go ahead and try re-flashing Recovery (first option in ROM Manager), despite it showing that it was updated to the latest edition. I then attempted to reboot into Recovery right after and ...drum roll... it worked! Go figure. -_-;; ah well! Figured the suggestion of re-flashing the Recovery might help others looking for a solution.
I'm going to go ahead and see about wiping and flashing a new, stable ROM and then I'll jump into the radio suggestions above.
Thanks again!
Naming patterns?
bukithd said:
I go with the 07.07 radio (GB update version) it works fine, that or the newest Evo radio. 08.08 or 12.19. I live in a splotchy signal area and from playing with it, it seems the newest ones work best for me.
Click to expand...
Click to collapse
I'm looking at the link provided by the other person above and seeing interesting naming patterns. IIRC I'm currently on the 2.15.00.07.28.
Just want to make-sure I'm reading this right - is 2.15.10.07.07 newer than 2.15.00.11.19? I would guess so, plus I'm gathering that it was the version you suggested.
Further, what are the effects of using an EVO radio? Sorry for being such a noob, but I'm honestly curious!
Thanks.
Nothing wrong with using an evo radio. I use the 07.28 myself but its because it works best in my area.
Sent from my ADR6300 using xda premium
wigmuke said:
I'm looking at the link provided by the other person above and seeing interesting naming patterns. IIRC I'm currently on the 2.15.00.07.28.
Just want to make-sure I'm reading this right - is 2.15.10.07.07 newer than 2.15.00.11.19? I would guess so, plus I'm gathering that it was the version you suggested.
Further, what are the effects of using an EVO radio? Sorry for being such a noob, but I'm honestly curious!
Thanks.
Click to expand...
Click to collapse
Correct, 07.07 is newer than 11.19 radio. 11.19 was released in November of 2010, 07.07 was in July of 2011.
Thanks! Learn something new everyday.
I completed flashing the radio! Yay.
Didn't realize at first that it needed to be flashed via HBOOT (though I should've assumed such based on the name), rather than Recovery, but got it taken care of w/o incident.
Immediately, I've seen an increase in signal strength (max bands), and received a text msg that would've been sent earlier this morning. I'm looking forward to seeing further improvements!
Thanks everyone for your assistance.
i use the evo 08.08 radio and it works like a charm...i tried all the radios but i found this one works the best!
How are you guys flashing these radios to your incredible phone? I kept trying by booting into HBoot and renaming the radios to PB31IMG.ZIP but it won't flash it, because the Security mode is ON S-ON. I have the OTA GB update with 07.07 but I can't seem to turn S OFF
dAii7 said:
How are you guys flashing these radios to your incredible phone? I kept trying by booting into HBoot and renaming the radios to PB31IMG.ZIP but it won't flash it, because the Security mode is ON S-ON. I have the OTA GB update with 07.07 but I can't seem to turn S OFF
Click to expand...
Click to collapse
You must have s-off to flash radios. One question, what is your hboot version? To attain s-off for:
.92 then follow this guide here
OR
1.02 then follow this guide here
The only experience I have and can reliably speak on is installing radios while s-off AND having hboot .92. I can't speak to the success rate of installing a radio with hboot 1.02, it's entirely different and unfamiliar to me.
I recently started using the 12.19 evo radio and it is much better regular signal wise although somehow 3g seems spottier