I would like to start flashing some new ROMS. Why I'm not sure, because my random reboots are almost never. You have to flash new radio for the gingerbread roms. So when I restore a nandroid back up of my current ROM which uses the latest OTA will I have to reflash radio also?
Radio HAS to be flashed in hboot, recovery does not control it. So yes you would have to flash the 2.2 radio in hboot when restoring a 2.2 ROM. Its common sense, if you cant flash the radio in recovery why would you think a restore would revert it?
Lot of hostility there man... i knew that radios are flashed in hboot but i didnt know that recovery didnt back that part up. he was asking a legitimate question theres no need to be so upset.
mbh87 said:
Radio HAS to be flashed in hboot, recovery does not control it. So yes you would have to flash the 2.2 radio in hboot when restoring a 2.2 ROM. Its common sense, if you cant flash the radio in recovery why would you think a restore would revert it?
Click to expand...
Click to collapse
Due to my lack of common sense I was not sure if restoring effects radio. I haven't had to flash radio as of yet. But now that you mention it, when I updated to my latest ROM it was thru hboot using the RUU. Thanks for the answer.
Related
Ok.. I have read through some other posts..
First thing I did was flash the new radio (#1 on "Obligatory Radio thread).. I used hboot after putting the file directly onto the root of my phone..
Then I downloaded 2.1 Bamf.. i preformed the flash in ROM manger.. After all went through I had no service..
I re-hbooted the radio, just for safe measures.. still no service... To make things worse i can''t acess my HD through my computer..
HELP PLEASE!!
I am getting an
"application sync service (in process com.fusonone.android.sync.service) is not responding
and a
HTC DM (in process com.htc.android.omadm.service) is not responding
The Gingerbread BAMF ROMs require the Gingerbread radio. You flashed a Froyo radio instead. Go back and grab the right radio.
I was under the impression the radio I flashed was a GB radio.. it was a link directly from the BAMF thread.. If i am mistaken I am extremly sorry for wasting your time..
What is a correct GB radio?
The newest GB radio can be found here. I'm not sure which version was in the Radio thread, but it was the last one listed.
Thanks..
Although, now when i flash that radio... same thing happens.. No service..
Do I need to do anything special? I am using Hboot to flash it..
I would re-flash the rom and then install the radio again or revert back to your old rom and radio and then redo it. I always flash roms from the clockwork mod recovery screen as I have had issues doing it with rom manager.
And there we goo.. Thank you both VERY MUCH!!
No problem glad i could help!
First is there any specific improvement or reason I should flash MR2 since I'm planning on using CM7?
Should I definitely flash radio first?
Should I flash the radio from fastboot?
You can flash ROM but once you load it, you won't have signal. And you have to flash the radio zip in hboot. But i may be wrong.
Sora3087 said:
First is there any specific improvement or reason I should flash MR2 since I'm planning on using CM7?
Should I definitely flash radio first?
Should I flash the radio from fastboot?
Click to expand...
Click to collapse
many are saying better radio performance.
install rom. then flash radio in hboot. then use some sort of file manager to remove the radio file.
definitely disable fastboot
yes!!! cm7 is a joke and its basically just using apps from the market to make it so there really is no point. Just do a ROM flash
So i ran the RUU for ICS through the bootloader (i am s-off). After I booted into the stock OTA, I flashed my TWRP recovery and then restored my nandroid of NeoMax 1.6 i had made just before flashing the RUU. So my question is does restoring my nandroid I made before flashing the RUU wipe out my flash of the official ruu putting me back where i was before i flashed the latest ICS RUU? any clarification would be really great. I basically just wanted to get back to having my phone and rom set up how i liked it because i am so sick of doing it over and over again. Also, would restoring only certain parts of my nandroid in TWRP change anything? Thanks again for any help
Software wise, not really. Firmware wise, not at all.
I'm currently running Stock w Goodies 1.75, I'm S-ON & H-boot 1.12.
I'd like to flash my radio since it's all still on the original but from what I've read I can only flash my radio using recovery and need to be S-OFF to flash everything and do it from the bootloader. Given my current setup, should I 1) Just flash the radio from recovery or 2) Flash the ROM suggested in the LazyPanda thread (Fresh 5.1.1 w/ 1.13), get S-Off and then flash everything before moving back to my current setup? Are there any issues with going that route besides it just taking some time?
Thanks!
S-off is really the way to go. There's some risk involved so take your time. After you get s-off you can flash any updates directly without using an ruu or reverting to stock and taking ota
ericande said:
I'm currently running Stock w Goodies 1.75, I'm S-ON & H-boot 1.12.
I'd like to flash my radio since it's all still on the original but from what I've read I can only flash my radio using recovery and need to be S-OFF to flash everything and do it from the bootloader. Given my current setup, should I 1) Just flash the radio from recovery or 2) Flash the ROM suggested in the LazyPanda thread (Fresh 5.1.1 w/ 1.13), get S-Off and then flash everything before moving back to my current setup? Are there any issues with going that route besides it just taking some time?
Thanks!
Click to expand...
Click to collapse
just follow post number 2, i used fresh 5.1.1 and it worked perfect, then i flashed the new hboot, then the firmware then the rom of choice...just to be safe i rebooted the device after each install
cool, when I get some time I'll go with the recommended ROM and go that route.
Maybe not the place to ask, but anyone else other than flex have goodies 2.05?
Ask me about my ability to annoy complete strangers!
Thanks guys, I changed my ROM to the recommended one, Lazy Panda was really easy and now I'm back to my old setup but S-OFF with updated radios.
So I see a number of people reporting using Baseband: 1.13.11.1105, including Captain_Throwback. I'm on Baseband: 1.13.11.0830 and am having some trouble with the phone connection - dropped calls, static on the line, etc. but data is fine (in fact I can make voip calls through hangouts no problem, but incoming calls are normal phone).
I looked at C_T's firmware collection on themikmik but that only contains up to Baseband: 1.13.11.0830 with the 3.17 software version.
I'm S-OFF via rumrunner after having flashed the 2.10 hboot and 4.13 651.4 Sense 5 Android 4.3 - Deodex to update the partitions to the new format. I've since flashed CM11 snapshot M12. Same phone issues on the rooted Sense and CM11.
Thanks to Captain_Throwback for all the excellent guides and collections here. Any suggestions from you or anyone here on where to find the latest baseband, and if you think this or maybe a custom PRL may help. (Is it possible to flash a custom PRL in CM11 or do I have to flip back to my Sense nandroid first?)
Thanks!
The baseband you're looking for can be found with the 4.3 RUU. You can find said RUU in the first post of my Hboot thread (top link in my sig). Not sure how you updated your Hboot but not your firmware, but I suggest running the RUU. You'll remain S-off afterwards.
To answer your other question you have to be running a Sense ROM to install a custom PRL.
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
cmags said:
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
Click to expand...
Click to collapse
I would run the RUU. Once done, you'll need to unlock and install TWRP again. Then you can restore your backup. As far as recovery goes I'm not sure which is most recent.
Well, that was only partially successful, and I could use some suggestions.
I did a nandroid of my CM11 M12 snapshot image, and ran the RUU in your post (RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe).
Afterwards Hboot is 2.10, and Radio is 1.13.11.1105. Great. Bootloader remains S-OFF (expected), and unlocked (unexpected, but cool).
I run fastboot flash recovery TWRP-Recovery-2.8.0.3-jewel-CPTB.img. Boot into recovery, restore my CM11 image, and reboot. Phone just spins on the boot animation.
Rebooted into recovery, wiped cache/dalvik/system/data, install flash CM fresh, wipe again, then restore (without boot) - same issue. About to wipe again and try restoring Sense nandroid, or flashing roms (CM and Sense) anew to see if i get different results.
Any other thoughts? Any way to verify the partition layout? Any way to get a log of what its hung up on while spinning the boot animation?
Thanks!
The issue you're describing reminds me of the issue that comes about from being S-on and having to flash the kernel separately from the ROM. You say you're S-off so that's not the issue, obviously. If you ran the RUU then you are on the new partition layout. Not getting any errors in recovery when you flash the ROM, are you? You might want to 're-download the ROM, check the MD5, and flash again.
Got it sorted out. Something must have gotten corrupted in the nandroid. A stock nandroid worked fine. So i restored cm11 then flashed the rom over the top to fix the boot partition. Im all set now, though the updated baseband didnt fix the static and dropped calls. Must be a hardware issue.