death2all110
Android Expert
That's completely up to you.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
fastboot flash radio (radio.img name here)
Death a few things here that might give issues. When flashed via recovery the radio.img is copied to /cache and then flashed from there so you DO NOT want to wipe after flash that might be why the version isn't updating as you are wiping it before its flashed. The radio is flashed after the reboot out of recovery. You reboot fully and then you can go back to recovery and wipe cache. Dalvik cache doesn't matter at all here. Just a warning a bad radio flash or a botched one will 100% irreverasably brick your phone and is the single most dangerous thing you can do to it. Triple check your md5sum before flashing and consider is it worth the risk if it is i suggest doing the method below instead of via recovery. Radios flashed from optimus recoveries I have 1 report of bricking but am unsure if user error caused it.
The preferred and safest way to flash a radio is via fastboot:
Code:fastboot flash radio (radio.img name here)
Good to know, thanks dre.
Off topic - I was chatting with Trident and he was saying that the preferred governor for the new kernel is ondemand. Why ondemand and not interactive? Just curious.
I like interactive better but either are fine.
No problems getting mms messages
Quick Question...my mom's Ally has been bugging her to update. I rooted it for her and installed Velocity. Will the OTA update install this radio? Will it screw up root or anything with the custom ROM? Is it recommended to ignore the update and manually flash this radio? Will the OTA Notification go away after a manual flash of this?
Well that was plural not singular...sorry. Questions.
The OTA update will fail during installation if you're running a custom ROM.
Manually flash the radio.
The OTA notification will stop after you accept the push, again the installation will fail and Velocity will boot again, completely unchanged.
Thanks for the quick and direct answer.
Actually this command does not work on the ally. otherwise i would have done that. ive tried it numerous timesDeath a few things here that might give issues. When flashed via recovery the radio.img is copied to /cache and then flashed from there so you DO NOT want to wipe after flash that might be why the version isn't updating as you are wiping it before its flashed. The radio is flashed after the reboot out of recovery. You reboot fully and then you can go back to recovery and wipe cache. Dalvik cache doesn't matter at all here. Just a warning a bad radio flash or a botched one will 100% irreverasably brick your phone and is the single most dangerous thing you can do to it. Triple check your md5sum before flashing and consider is it worth the risk if it is i suggest doing the method below instead of via recovery. Radios flashed from optimus recoveries I have 1 report of bricking but am unsure if user error caused it.
The preferred and safest way to flash a radio is via fastboot:
Code:fastboot flash radio (radio.img name here)
I have a question, just to be sure i don't brick my phone....I recently reflashed to v6, then the recovery image, updated all the way to zvc...i then flashed velocity 0.3, my baseband shows mvb, and the update tried to install(failed of course). Should I not flash this because it's likely a reporting error? or does the velocity rom actually flash the mvb baseband and i have to flash the mvc?
If you updated all the way to ZVC then you have the new radio. It is a reporting error, do not flash it again.
so'k...my fault...maybe I should put it in my sig, but then maybe not lol (think I might change my avatar, though)...Electrical Engineer at Clemson University (in SC). Can't code worth a crap lol.
I too went to school for Engineering in SC, was Electronics Engineering, and in Greenville, but not much of a difference? lol
How do we know if we have this update on a custom rom already so we dont go and do it again?