I am currently rooted but still on the stock MR1 radio/ROM. I rooted following the instructions at
http://forum.xda-developers.com/showthread.php?t=996616
I would like to update my radio to MR2 (especially after having problems this weekend with indoor connectivity in some Long Island locations that have 4G). However, from everything I read, the MR2 radio requires an MR2 ROM (and won't work with the MR1 stock ROM that I'm currently running). I have not yet seen any instructions on how to upgrade the stock ROM to MR2 while rooted, nor have I seen a rooted stock MR2 ROM (only an unrooted MR2 stock ROM).
I'm not interested in installing any of the 3rd party ROMs that are currently out there. I plan to ultimately move to CyanogenMod which I previously ran on my Droid, but I'm waiting for it to progress to a more stable state (preferably "gold' release, but I might jump to it when it gets to a release candidate state if that looks stable/complete enough to me).
In order to update you'll need to flash the new rooted OTA ROM and the new radio. This thread has both http://forum.xda-developers.com/showthread.php?t=1160374. You will have to have ClockworkMod installed first so you can wipe and then flash the new ROM. I usually flash the radio first from the bootloader then the ROM but it doesn't really matter which you do first. Here are some instructions on flashing the radio http://forum.xda-developers.com/showthread.php?t=1055499 Check the MD5 of the radio to be sure its complete. I'm attaching an MD5 program that you can use to check the MD5 of the radio. Rename it MD5.exe. If the radio is not complete it could brick your phone.
I'm looking for an UPDATE method -- one that doesn't require wipe which means even with MyBackupPro backup/restore I still need to manually redo all my Android (non-app) settings.
Related
Hi there
I had 2,17 and upgraded to the leak rom 3.16. I did not use any locker or unlocker when upgrading. I am having issues with mail2web that it sends the same sent email several times. I think there is an active sync bug with the leaked rom. Anyways, I am trying to downgrade back to the official 2.17 and I when try to flash after the intial reboot it tell me error 328 invaild command
can anyone please help??
I had that same problem on one of the other roms. My email issue was fixed by hard resetting and reflashing the same rom. AS far as getting back to a different rom, not sure. You might need to find the older unlocker program from oilpro and cokeman.
Good Luck
As a matter of fact I plan on doing this within the hour. I'm ging to use the Re-locker tool and ill back report back with progress.
*Update*: Re-locker tool worked perfect Find it here
http://forum.xda-developers.com/showthread.php?t=363556http://forum.xda-developers.com/showthread.php?t=363556
Anytime you want to flash an "Official" Sprint ROM, you will need to relock the device.
Also, to make sure the reflash completely overwrites everything, I usually flash a ROM multiple times...
trying to downgrade bricked my mogul
I was having issues with the leaked rom, and wanted to downgrad back to the sprint 2.17, I was also geting error 328. and here is the part that bricked my phone, since i couldn't get teh official 2.17 to load i tried to load a custom 2.17 rom which said it installed 100%. However when i reboot i am now stuck in the preboot screen that says for testing only.
I had pretty much the same issue - upgraded to a 3.16 custom to try it out. Didn't care for the flakiness of it.
To downgrade, you will need to use the relocker to go back. After that I flashed a stock Sprint 2.17. Then unlocked again to get a 2.17 custome ROM.
I currently run BAMF 1.09 rom with the radio that goes along with it. I sold my phone and installed the original HTC Factory Rom but i forgot to install the radio to go along with it. the HTC Rom is about 6-7 months old so my question is what radio do i need for this? Also, i assume all i need to do is install the radio through bootloader and it should have a connection. Currently the verizon told the person i sold the phone to the radio was broken. thanks for your help in advance. I forgot to check but believe the ROM is FROYO.
Did you just restore from a nandroid or did you install a stock file? Your easiest bet is to install a stock file from the bootloader (JUST like a radio) to restore completely to stock.
http://forum.xda-developers.com/showthread.php?t=1310014
Just be careful.
Okay, so I ordered a USED Thunderbolt on ebay last week and it should be here tomorrow. I'm not entirely new to rooting and such as I have a droid 2 global now, but that's motorola which seems to be fairly different from HTC. Anyway I've been reading threads and have come up with a few questions.
For instance if my phone is rooted when I get it, how can I get back to stock. I won't know how it was rooted, and some guides say it matters, while others don't. Plus many guides say not to just flash an RUU over a rooted phone, but if it replaces the bootloader, radio, and system, why not. Isn't that basically like an SBF on a motorola phone? Can I then also do a data wipe from the hboot bootloader thing on my phone and end up with a perfect stock device without any risk? From what I understand some roots block this entirely on the phone though so maybe I can't. I'm not really sure how to know what is safe to do on a phone that I didn't previously own and would love a guide to how to check these things and what to do so I don't brick the phone.
Also I can't seem to find a functional link to any of the latest radios, does anyone have a working link, and do people recommend the leaked radio from the most recent leaked build, or an official radio? and if so what radio is official? the one ending in 906 seems to be the most recent that I think is official but I'm not sure, though I am almost certain the 916 one isn't official, it appears to have been released in january on rootzwiki, while the most recent leaked build was less than a week ago from what I understand, but I don't know if it has a new radio or not.
Aside from that I think I've got it all down. figure out how to get phone to most recent stock OTA update. get 4g lte sim card, activate, root using this method.
http://rootzwiki.com/topic/20864-tool-root-2116059-and-19-no-downgrade-or-data-wipe/
then if I don't have the most recent radio I can flash it in the hboot thing, and can use cwm to flash any rom I want and a recommended kernel (I'm thinking thundershed 1.5 for starters though wouldn't mind some recommendations. I love Cyanogenmod)
Does this sound about right?
Also I'm not sure how hboot on htc phones works aside from booting on power+vol down button, but does the hboot allow for clearing data and cache as well as flashing things? On my droid 2 global there is a bootloader than can only be used to flash sbf files to get back to stock ota, and then there is a motorola stock recovery on the phone that is used for flashing updated ota updates that are signed or wiping data/cache. Are these the same on htc or are there a 2 different ones on that phone as well? I do understand that no PC is required for the htc as the tool to flash an ruu is built into the phone even if it is an older one than what the phone is currently on right?
I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
morfinx said:
I've been doing a bit of reading on the steps to flash a custom ROM on the EVO LTE. To summarize my findings (and please correct me if I'm wrong about any of the following): I've noted that there is currently no way to achieve S-OFF with newer hboot (1.15 and 1.19), but you can still unlock the bootloader with HTC's official method. The disadvantage being (other than the red disclaimer splash screen at boot time) that you cannot flash a new radio firmware with HTC's official unlock method, where as you can with S-OFF.
So my question is, under what circumstances would you want to flash a new radio firmware?
Click to expand...
Click to collapse
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Rxpert said:
During OTA's theres usually a new radio released. That is supposed to help with various connections (data, wifi, LTE) depending on whats updated.
Click to expand...
Click to collapse
premo15 said:
You mainly just want to make sure that you're radio is from the same firmware version as the base of the ROM you're running. So if your ROM is based on the 1.22.651.3 software, you would ideally want the radio from the same OTA. It's generally not required, but you could have compatibility issues when running different versions.
Sent from my EVO LTE
Click to expand...
Click to collapse
So if I'm running a custom ROM, that means I can't get an OTA update right? In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
morfinx said:
So if I'm running a custom ROM, that means I can't get an OTA update right?
Click to expand...
Click to collapse
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the recovery mode, the OTA checks all/most of the files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
morfinx said:
In that case, if I used HTC's official unlock method and can't flash a new radio separately on my own, how do I get the new radio?
Click to expand...
Click to collapse
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio image contained in the OTA/RUU. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock the bootloader, run the RUU from the latest OTA/software version, which will update the radio, then unlock, flash custom recovery, make a nandroid of the stock ROM/kernel as a known good backup, then reload my previous nandroid to restore the custom ROM/kernel.
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
joeykrim said:
If you're running a custom ROM, you *might* be able to receive/download the OTA, but it will not update properly because the OTA checks all files in /system/app and /system/framework to verify they haven't been modified since the previous OTA before applying the new OTA. This check will definitely fail if any of the files have been modified in /system/app and /system/framework, which most custom ROMs make at least some minor modifications to the files in these directories.
Essentially, you'll have to get back to some form of stock to allow the stock bootloader to process the radio OTA. There might be a better way to approach this, but off the top of my head, I'd make a nandroid backup of everything, re-lock, run the RUU from the latest OTA/software version, which will update the radio, then unlock, and reload my previous nandroid.
Click to expand...
Click to collapse
Thanks for the explanation. Wow, that sounds like an enormous PITA.
joeykrim said:
As recommended above, it is generally a good idea to keep the software version in sync with the radio version, but personally I rarely update the radio and rarely have an issue .. but that is just my personal experience.
Hope that helps!
Click to expand...
Click to collapse
Maybe it's not as a big of a deal as I'm thinking then to not be able to update the radio (easily). I'm still on an OG EVO with S-OFF, and I haven't updated my radio for probably close to 2 years. All of my connections seem to be fine still.
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.