I have been searching and haven't found the answer, I was just wondering since I am on CM6 nightly 8/1 (Froyo 2.2) and am fully rooted, can I just download the updated Radio and Wimax versions from the ava3 thread:
h**p://forum.xda-developers.com/showthread.php?t=720682 (Sorry I'm not allowed to post links yet)
and flash those via the recovery? or will that brick my phone?
thanks!
Triumph said:
I have been searching and haven't found the answer, I was just wondering since I am on CM6 nightly 8/1 (Froyo 2.2) and am fully rooted, can I just download the updated Radio and Wimax versions from the ava3 thread:
h**p://forum.xda-developers.com/showthread.php?t=720682 (Sorry I'm not allowed to post links yet)
and flash those via the recovery? or will that brick my phone?
thanks!
Click to expand...
Click to collapse
I flashed another froyo/sense build and then flashed radio/wimax...then went back to CM6 and there were no problems, and the radio showed as the latest version within the phone. So I don't see that would be an issue.
A lot of people, including me, are using the latest radio from the froyo OTA over our CM6 and it works just fine. I haven't seen a noticeable difference though.
ok thanks DanBergundy and admorris
The latest updates with radio/wimax make a HUGE difference in 4g speeds. Of course, if you're using CM6 you don't have 4g, but you may want to give another Froyo/Sense build a try if you're in a 4g area.
Related
----------------------------------------------------
Original Text:
----------------------------------------------------
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU, RUU_Hero_C_Sprint_2.20.651.1_signed_test, and re-push flash_image or does it even really matter which hboot I'm running on (figure hboot is the only thing permanently stuck on phone from RUU)?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Any thoughts welcome
-----------------------------------------
This is sorta deprecated now that we have Root on the Release RUU, so repurposing the thread.
My new question: Now that i've rooted the Official Release version, can I restore my old nandroid backup without breaking my phone?
I did a nandroid backup of my fully-set-up Fresh 2.1.2 Install before I ran the Official RUU to 2.27.651.5 and now I'm wondering if it will break anything to "restore" that backup.
Again, any thoughts are welcome.
diaknia said:
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU and re-push flash_image or does it even really matter which hboot I'm running on?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Click to expand...
Click to collapse
to my knowledge if your hboot changes from 1.56 to the one from the official you will lose root as of now, the test RUU still has root but its super buggy, why would you want to flash the official or the test anyways, theres roms here that blow the stock ones out the water, but once again to my knowledge you WILL lose root. And the test ruu with root has mad issues you should do a search bro as far as upgrading to the newer hboot well im not sure if it has features but the devs are still trying to break root in the new hboot.
check this out bro just in case you already flashed it http://forum.xda-developers.com/showthread.php?t=693449&highlight=hboot
I have not yet flashed the Test RUU.
From what I understand the Test RUU still has su built in, so all I need to do is re-push flash_image to get a custom recovery back on it and I'm golden from there.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
diaknia said:
I have not yet flashed the Test RUU.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
Click to expand...
Click to collapse
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
good to know
dirkydirk23 said:
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
Click to expand...
Click to collapse
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
diaknia said:
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
Click to expand...
Click to collapse
There is nothing wrong w/ the hboot. and the hboot isn't even the thing blocking root. The audio issue seems to differ from phone to phone, I have never had audio issues on my phone.
Thanks for the responses, regaw and dirky.
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
On a side note.... i'm an eager follower of the official RUU ROOT thread on the dev sub-forum, Regaw, keep up the good work. Still feel bad for you that you've been stuck without root so long...
When you crack the thing, and I maintain hope you will, that's when I'll probly go and upgrade to the Release RUU.
diaknia said:
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
Click to expand...
Click to collapse
Basically this.
abcdfv said:
Basically this.
Click to expand...
Click to collapse
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
dirkydirk23 said:
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
Click to expand...
Click to collapse
If you had run the test ruu and already pushed flash_image and custom recovery back to the phone then you can restore the original hboot in about 10 seconds if you want.
From recovery flash the .zip attached here and the hboot will revert to 1.41 instead of 1.47.
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
diaknia said:
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
Click to expand...
Click to collapse
I am curious about this also. Currently running fresh 2.1.1 previously from a 1.5 root and was thinking about updating to the .5 ruu and doing the root and than restoring a nandroid
so uhh yeah, after being on stock froyo for a bit and them coming back to cyanogenmod i couldnt help notice the way wayy better reception and all that on froyo. and so i asked a question before about what does that and you guys said drivers and whatnot which im assuming is the "radio" that you all talk about in roms. so is there by any chance some way of getting this better radio on cyanogenmod? cheers
Just flash the latest radio and you're all set. I believe the latest is 7.13.35.05.
rajasyaitan said:
Just flash the latest radio and you're all set. I believe the latest is 7.13.35.05.
Click to expand...
Click to collapse
will that work? thats all i have to do? if so do you know where can i get the radio to flash then? and also, are you sure that would work lol? seems too.. simple
curto said:
will that work? thats all i have to do? if so do you know where can i get the radio to flash then? and also, are you sure that would work lol? seems too.. simple
Click to expand...
Click to collapse
I flashed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=841932
It works well...
entropicamente said:
I flashed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=841932 n
It works well...
Click to expand...
Click to collapse
i already have that radio lol. i believe the froyo one is 7.14
Sent from my Legend using XDA App
curto said:
i already have that radio lol. i believe the froyo one is 7.14
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That radio is taken from the rom with Froyo released for Vodafone devices.
You probably have already installed it when you have flashed the latest OTA with Froyo. I'm not sure, but I don't think that installing CyanogenMod overwrites the radio installed by the stock rom.
entropicamente said:
That radio is taken from the rom with Froyo released for Vodafone devices.
You probably have already installed it when you have flashed the latest OTA with Froyo. I'm not sure, but I don't think that installing CyanogenMod overwrites the radio installed by the stock rom.
Click to expand...
Click to collapse
actually now that ive taken a look at my screenshot of that froyo rom ive got in my sig (the one im talking about that i was trying with the amazing wifi reception and all that) the radio is actually 7.05 and that other number in front of it is an older version too. so does that mean the older versions are better or what? i get better wifi reception and all that on an older radio? anyways im sure you see my point, so now im confused lol
curto said:
actually now that ive taken a look at my screenshot of that froyo rom ive got in my sig (the one im talking about that i was trying with the amazing wifi reception and all that) the radio is actually 7.05 and that other number in front of it is an older version too. so does that mean the older versions are better or what? i get better wifi reception and all that on an older radio? anyways im sure you see my point, so now im confused lol
Click to expand...
Click to collapse
7.05? Or is it 7.13.35.05? If you do lurk around more and read through the radio update threads, some people already mentioned they have better reception on older radio. I can't verify that but the latest radio do make my reception better. Or you can try flashing a few radio update and see which has the best reception.
rajasyaitan said:
7.05? Or is it 7.13.35.05? If you do lurk around more and read through the radio update threads, some people already mentioned they have better reception on older radio. I can't verify that but the latest radio do make my reception better. Or you can try flashing a few radio update and see which has the best reception.
Click to expand...
Click to collapse
alright that sounds good then. is there like a main list or something where they all are or do i have to search through all the threads in development to find them?
Hey, i was just wondering what the most up to date, or best custom radio is to use on the mytouch4g and where i could find it! Thanks a bunch!
MT4G
CM7 RC4
I didn't think there were custom radios, just newer one's released by tmobile? Though I'd like to know what the latest release is as well.
Sent from my HTC Glacier using XDA App
The latest radio for the MT4G was part of the most recent OTA update (the one that upgraded Android to 2.2.1). The version number is 26.03.02.26_M.
TeeJay3800 said:
The latest radio for the MT4G was part of the most recent OTA update (the one that upgraded Android to 2.2.1). The version number is 26.03.02.26_M.
Click to expand...
Click to collapse
This is no longer valid. 26.08.04.30 is the newest radio.
aussiehairspray said:
This is no longer valid. 26.08.04.30 is the newest radio.
Click to expand...
Click to collapse
Why did you dig up this thread? I posted that a month ago when it WAS the latest radio...
Over time, this post and the subsequent thread got way too big and there were way too many people asking way too many questions that were addressed here already. So, in the interest of everyone's sanity, and to make things a little easier to find, I have decided to split this into one post per device. Please find the appropriate thread for your device:
I9020T
I9020A
I9023
D720
M200
CHANGELOG:
January 14, 2011: Split into multiple threads.
December 18, 2011: Add IML74K full ROM link for I9020T and I9023 courtesy of Star Shadow.
December 17, 2011: Add 2.3.6 -> 4.0.3 upgrade for I9020T and I9023. Add GRJ22 -> GRK39F upgrade for I9020A courtesy of canadian_psyko.
October 2, 2011: Add full ROM link for GRK39F for I9020A. Add GRJ22 full ROM for I9020A courtesy of kibmcz.
October 1, 2011: Add link for GRK39C -> GRK39F update for I9020A.
September 30, 2011: Add references to 2.3.6/GRK39F for I9020A, but don't have any links yet.
September 27, 2011: Add GRK39F for I9020T and I9023
September 24, 2011: Add GWK74 for D720
September 2, 2011: Add GRK39C full ROM and 2.3.4 -> 2.3.6 packages for I9020A.
August 2, 2011: Added full ROM package for GTJ61 for I9020A.
July 26, 2011: Added build reference.
July 25, 2011: Added Android 2.3.5 Nexus S 4G update.
June 10, 2011: Added Korean M200 information.
May 17, 2011: Added 2.3.3->2.3.4 OTA update for I9020A and added an entry for a full 2.3.4 flashable I9020A ROM in case anyone wants to create one.
May 10, 2011: Added Nexus S 4G and OTA file (GRJ06D->GRJ22).
I upgraded my Nexus S (Carrier: Videotron/Canada), model I9020XXKB3 (GRI54) without any problem with the full ROM to 2.3.4.
Sent from my Nexus S
Thanks for posting all the info!! What about those on the i9020 with kb1? Will any of the full rom's work?
And does anyone know if 2.3.4 works with fring yet?
Sent from my Nexus S using XDA App
ctai320 said:
Thanks for posting all the info!! What about those on the i9020 with kb1? Will any of the full rom's work?
And does anyone know if 2.3.4 works with fring yet?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
As long as you have an I9020T, any of the full ROMs will work. They will NOT work for I9020A.
Sent from my Nexus S using Tapatalk
oldblue910 said:
As long as you have an I9020T, any of the full ROMs will work. They will NOT work for I9020A.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
What's the easiest way to tell the 9020A from the 9020T?
TheSystemHasFailed said:
What's the easiest way to tell the 9020A from the 9020T?
Click to expand...
Click to collapse
I9020A is the Rogers/AT&T variant. I9020T is the T-Mobile version.
I have a i9023 GRI40 KB3, with Clockwork recovery.
Should I use Build GRI54/KB3 Radio/KA3 Bootloader or GRI40/KB1 Radio/KA3 Bootloader
icewar23 said:
I have a i9023 GRI40 KB3, with Clockwork recovery.
Should I use Build GRI54/KB2 Radio/KA3 Bootloader or Build GRI54/KB3 Radio/KA3 Bootloader
Click to expand...
Click to collapse
Did you manually flash the KB3 radio? As far as I know, no factory installation of GRI40 ever had the KB3 radio. GRI40 was always paired with KB1...
Actually, I flashed CM7, so maybe that's where the KB3 radio came from. The thing is I forgot to make a nandroid backup of my original ROM, so I would like to get it.
Sorry I forgot to mention that.
So are you running CM7 or are you back to stock?
CM7. I can't go back to stock because I forgot to make a nandroid backup of it before flashing CM7. Thanks.
So if you're running CM7, then that's not where KB3 radio came from, but rather that's where GRI40 came from. Your i9023 originally came with stock GRI54 and KB3 radio, then when you flashed CM7, it kept the KB3 radio but downgraded your build since CM7 is based on GRI40, not GRI54.
In that case, if you want to be running stock, I would recommend flashing the 2.3.4 OTA full ROM package to your phone. It will give you Android 2.3.4 with the KD1 radio. It works fine on i9023 with KB3 radios. That is the only one of the ROMs that I listed that will work with your phone.
Click the very last link in the original post (under i9023, Android 2.3.3 (GRI54/KB3/KA3). That's the file you want. You can flash that in ClockworkMod and you'll be on stock 2.3.4. Because you're running CM7 right now, you will also need to wipe your data and cache, plus it'd be a good idea to wipe Dalvik cache too.
Thank you for your time sir!
icewar23 said:
Thank you for your time sir!
Click to expand...
Click to collapse
My pleasure.
oldblue910 said:
I9020A is the Rogers/AT&T variant. I9020T is the T-Mobile version.
Click to expand...
Click to collapse
Much appreciated... I also found another thread that mentioned this.. just takes awhile sometimes with flood of information always flowing on these forums.
Thanks again.
hello,
is it possible to find a Full ROM Package signed 2.3 or 2.3.1 for I9020T ?
thank
athome93 said:
hello,
is it possible to find a Full ROM Package signed 2.3 or 2.3.1 for I9020T ?
thank
Click to expand...
Click to collapse
They don't exist as far as any of us know. The closest thing you'll find is the Odin 2.3.1 firmware which you can flash in fastboot mode but if you want a signed zip of the full ROM that is flashable using the stock Android 3e recovery, unfortunately you're out of luck.
Sent from my Nexus S using Tapatalk
Having incorrectly used the wrong ROM from here to upgrade to 2.3.4 I have lost clockwork and super user. Also I can no longer connect in fastboot mode with ADB commands.
See here for full explanation
Any help greatly appreciated.
Acne
Is there a list of all radios that available?
And is it ok to pair any of the radios with any of the other ROMS?
I face constant 3g data dis connectivity with my telco here and thinking to try the different radios to see which one is better.
Hey guys.. My Shift 4G has been rooted for quite some time, and I had been running CM 7.1 RC1 most recently.. After the past several weeks, I have experimented with various ROMs and Radios.. At one point I did upgrade the radio firmware to 1.08.00.0506 and the WiMax Radio to 27240.
I had also experimented with the rooted 2.76.651.4 Sense ROM posted by x99percent.. I wasn't thrilled with Sense, and ended up going back to CM7.1 RC1.. I also downgraded the radio 1.07.00.1129 and WiMax back to 27167.
Since I was playing around with the various ROMs and Radios, my Shift will never charge above 85%.. I am familiar with clearing batterystats.bin - and had tried various measures to get the battery to charge above 85%.. I used Battery Monitor, and it showed that basically around 85%, the Shift was turning off the internal charging circuit (Current would show usually less than 100mA..)
Thinking that perhaps something was sticking around from my various experimentations, I decided to use the original RUU (RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.1129_NV_SPCS_1.52_1103_release_160079_signed) to revert back to stock and start over.
One of the things that came up when I ran the RUU was it showed the current image version as 2.76.651.4.. This was even though my radio was 1.07.00.1129. Does anyone know why that would be reported that way?
I'm currently on the original sense RUU, and now it appears to be charging correctly. Once it does, I'll re-root and go back to CM7.1 RC1.
Thanks,
Rick
RickNY1971 said:
I had also experimented with the rooted 2.76.651.4 Sense ROM posted by x99percent.
...
One of the things that came up when I ran the RUU was it showed the current image version as 2.76.651.4.. This was even though my radio was 1.07.00.1129. Does anyone know why that would be reported that way?
Click to expand...
Click to collapse
Makes sense to me.
...and wrong forum.
Once your on the RUU how are you going to root again with a s-on bootloader?
Sent from my HTC Speedy Ball'o Fire using xda premium app not tapatalk
x99percent said:
Makes sense to me.
...and wrong forum.
Click to expand...
Click to collapse
Sorry about posting to the wrong forum.. I PM'd the mod to have it moved to Evo Shift 4G General.
The thing that did not make sense to me was the fact that I had restored my Nandroid backup from CM7.1 RC1, and restored the radio with the bootloader to 1.07.00.1129. I ran the RUU against CM7.1 RC1 and radio version 1.07.00.1129.
sparksco said:
Once your on the RUU how are you going to root again with a s-on bootloader?
Click to expand...
Click to collapse
I used the orignal RUU for Froyo -- not the Gingerbread RUU.
Oh my bad haha. I was about to say...you should be good to re-root then no? I flashed the new radio's manually just fine over cm7. Still on the same radio's and cm7 to this day
Sent from my HTC Speedy Ball'o Fire using xda premium app not tapatalk