Hey guys,
Just had a quick question. I'm not new to the rooting game and have been doing it for a while (g1 fwiw) but just had some questions since the new update came out. I'm s off so flashed the updated radios and packages from captain over in the android development forum. My question though is I don't ever remember having to flash an update like that. Ive flashed radios before but I thought the base came with the roms. Am I wrong? Is this different than usual for a reason or do I just have a bad memory. I might be wording my question weird but yeah, anyone with an idea?
I'm not sure what you mean, you flash the radio/firmware and rom and you're updated.
I guess my question is I thought all of that stuff usually comes packaged in a Rom. Except for the radio I thought the base and all that depended on what Rom you flashed and wasn't fixed.
Get_Out_and_Push said:
I guess my question is I thought all of that stuff usually comes packaged in a Rom. Except for the radio I thought the base and all that depended on what Rom you flashed and wasn't fixed.
Click to expand...
Click to collapse
Radios are stored in a separate partition from the ROM. I don't think I've ever seen a ROM package include one.
Sent from my EVO LTE
Roms are built off of different bases. That hasnt changed.
Flashing a rom will update the base (software version)
Rxpert said:
Roms are built off of different bases. That hasnt changed.
Flashing a rom will update the base (software version)
Click to expand...
Click to collapse
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Get_Out_and_Push said:
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Click to expand...
Click to collapse
Yes
Get_Out_and_Push said:
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Click to expand...
Click to collapse
Correct, the radios and other firmware bits are on the secured partitions that require a signed ruu in order to install if you are not s-off. The base software installs on the system partition so can be installed with just an unlocked bootloader through a custom recovery like twrp. That is why so many people that are s-on and the 1.15 hboot can't take advantage of the new radios. Their only option at this time would be to take the ota. They can however load the new kernel through fastboot or flash GUI and then install a custom rom that has the updated base.
Sent from my icrap 2 using Tapatalk HD
Related
I haven't seen a thread on this non of the guides either say anything about it. Just curious if your Hboot 1.5 and took that 2.17 update which was a software update and new radios.
Does that mean you still can use roms that were built or based off 2.08 was made off of or will you run into issue's.
Or do you have to stick around and wait for a rom to be based off the 2.17 update.
I know how to flash a kernel the right way and all just wonder about the older roms.
Thanks....
Does that mean you still can use roms that were built or based off 2.08 was made off of or will you run into issue's.
Click to expand...
Click to collapse
If you are rooted, yes. You flash any rom the same way, wipe everything and flash. Doesn't matter if you are flashing an older OS version or a newer one.
sitlet said:
If you are rooted, yes. You flash any rom the same way, wipe everything and flash. Doesn't matter if you are flashing an older OS version or a newer one.
Click to expand...
Click to collapse
Pretty much correct except that hboot 1.5 users have to flash kernels via a different method.
sitlet said:
If you are rooted, yes. You flash any rom the same way, wipe everything and flash. Doesn't matter if you are flashing an older OS version or a newer one.
Click to expand...
Click to collapse
I took the Jump last night so far no issues was just checking running virus ROM eternity . Anyways thanks.
I'm still using radios from an early ics leak. Was wondering if most roms include the latest kernel and radios or if I had to manually flash those separately.
I also already went through the soff process and was planning on flashing a new rom soon
Thanks
You must flash radios on your own. Roms do not include them.
con247 said:
You must flash radios on your own. Roms do not include them.
Click to expand...
Click to collapse
+1 and if they did it would be dangerous to do it
Sent from my ADR6425LVW using Tapatalk 2
If you're s-on, you need to flash the latest leak to get the latest radios, if you're s-off, there is a thread with the radios in the dev section you can use to update them.
Thanks ^_^ just wanted to make sure before I mess up my phone
Please bear with me, I'll readily admit that I'm a newb when it comes to flashing ROMs, etc. I rooted my TB with the all-in-one tool and loaded the ICS BAMF Leak. I presume this was essentially an RUU, since I didn't flash any separate radios or anything.
I'm looking for a different ICS ROM to flash, mostly due to the poor memory management on this build.
My question is this, and mainly for clarification- If I wipe/format everything except the SD card, I will have to FIRST flash the ROM, then flash the radio to get data working?
It was only a ROM, and radios don't come with roms but the ones you had when you rooted work with the leak.
To flash a new rom just do the same thing you did for the leak, i have never flashed a radio (except for testing the tool) in a year of having this phone.
trter10 said:
It was only a ROM, and radios don't come with roms but the ones you had when you rooted work with the leak.
To flash a new rom just do the same thing you did for the leak, i have never flashed a radio (except for testing the tool) in a year of having this phone.
Click to expand...
Click to collapse
Well, that's interesting. I installed the NuSense rom based off the ICS leak, and had to install the leaked radios to get data back.
either way, i got the rom flashed and the radio flashed and working.
Thanks for the rooting tool, BTW
ToastyZ71 said:
Well, that's interesting. I installed the NuSense rom based off the ICS leak, and had to install the leaked radios to get data back.
either way, i got the rom flashed and the radio flashed and working.
Thanks for the rooting tool, BTW
Click to expand...
Click to collapse
That is because santod modified the ril to work better with the leak radios. I get data just fine with the .19 radios.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
That is because santod modified the ril to work better with the leak radios. I get data just fine with the .19 radios.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
+1
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
I would do it just to be safe and I flashed the new radios and got faster 4g but only slightly faster
Sent from my ViperDNA infected with ViperBlue DNA
devilsaces said:
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
Click to expand...
Click to collapse
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
devilsaces said:
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
Click to expand...
Click to collapse
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
TJMac44 said:
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
Click to expand...
Click to collapse
Yeah, I can't remember a ROM for the thunderbolt that had the same level of customization as Viper. TBolt ROMS went more in the direction of trying to get the latest sense roms, most felt unstable, or to get ASOP. I have my ASOP fix with my Nexus 7 now so I don't mind sticking with just sense based roms.
TJMac44 said:
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Click to expand...
Click to collapse
I just flashed the new radio, planning on flashing ViperDNA this weekend.
After doing a little more research I came across this post:
http://forum.xda-developers.com/showpost.php?p=37535001&postcount=1
It turns out that there are 2 parts to a kernal, the kernal modules and the boot.img. I guess I DO need to flash the boot.img separately. The modules are already packaged with the ViperDNA Rom. Does this sound correct? When I was flashing ROMs with my TBolt I usually flashed different kernals separately so they were already together.
uppon2 said:
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details.
3. You now need all required kernel files you are planning to use with the ROM you have selected. Now for the Droid DNA at the moment the kernel is broken down in to 2 parts. The first file is kernel modules and the second file is the the boot.img. Now whatever ROM you choose to download and install, it should already be using a specific kernel. When you flash a ROM the kernel modules will already be installed for the specific kernel the ROM is using.
For example If you listened to my advice and are going to use ViperDNA, this ROM already comes with the kernel modules required for the kernel it is using. The only thing that is left for you to do is download the second part of the kernel which is the boot.img file. Every kernel needs both the kernel modules and boot.img files to work 100% without fault, and every kernel has different modules and a boot.img that will only work for that specific kernel.
Each ROM should give you a download link for the required boot.img so just make sure to read the first few posts - If you are planning to use ViperDNA then it can be found on the first page post number 2 of the ViperDNA thread and it is named Stock DSB System Write Boot.img -
* If that wasn't already clear enough I would like to say that if you are download a complete kernel zip separately (which you can do) then you will get both files required. The first is the "already included in the ROM" kernel modules and the second file will be the boot.img - You can find all of the different kernels here - as you can see in this list the kernel included in ViperDNA is the one named "[KERNEL]Droid DNA Cubed Kernel Stock" - Once you have finished installing a ROM then I would recommend having a look at some different kernels if you want. Down the very bottom of this post I have included instructions on how to flash a kernel so please check it out.*
Click to expand...
Click to collapse
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
evoimevo said:
My wife's Evo kept failing the 3.17 OTA so I moonshined it this week to allow her to get on latest firmware and software. She is stock other than S-off and root. I am fully aware that the firmware/radio and software are two different things. After getting S-off I flashed the current 3.17 bootloader firmware from Captain's thread and all went well and she is now on 1.13.11.0830 radio. Now I want to get her the software updates to move her from 3.16.651.xx to 3.17.651.4. My question is how to best do this. My thought is to flash the stock rooted deodexed rom but I didn't know if there was an alternative better way. Also, considering that an OTA upgrade of software is a dirty flash sort of, can I dirty flash stock rooted 3.17 over her current 3.16 without doing full wipe. Yes, I realize full wipe would be best and I am willing to do that if dirty flash is a mess. But, for time saving, is there any real danger in dirty flashing stock rooted 3.17 over her current stock rom with s-off and root? It just seems to me to be the rooted equivalalent of taking the OTA update.
Thanks for any advice.
Click to expand...
Click to collapse
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
thanks bigdaddy, I appreciate the response. Is there any downside to being on older software and newer firmware? I thought Captain TB or someone had said that the firmware and software are optimized to work together and shouldn't be out of sync. If that is the case I probably need to bite the bullet and go ahead and wipe and flash the stock rooted deodexed rom to get her the software update.
bigdaddy619 said:
Your firmware is updated.
Software is based on the rom you are running if you flash a 3.17 rom you will be updated in that area also.
As for dirty flashing it's not a good idea to dirty flash when going to a new base
Click to expand...
Click to collapse
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
lanewhit said:
Is it just me... Other than stock rooted 3.17, I'm not seeing any custom roms for this base. Im still using mean bean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I think it is kind of what bigdaddy was saying and what CTB has said...3.17 is the software update that brought the firmware update if done OTA. I believe what CTB did was extract the firmware so people could update the radio/firmware without installing the OTA or stock 3.17 ROM. So, you can have latest radio/firmware with CM10.2 for instance. In my case, my wife wants to keep stock as much as possible so I was trying to figure out best way to get her to most recent stock software without taking it OTA. I think the way to do that is going to be to flash 3.17 stock rooted rom. As you mentioned I haven't seen many/any roms built from 3.17 source if it has even been released at all yet. I moved to CM roms long ago and haven't used any Sense roms since meanbean 3.09 which last I checked hadn't been updated in months. There are plenty of CM10.2 based ROMs available that have tons of updates and fixes. I left my wife's stock because otherwise I get blamed every time Sprint or htc messes something up. This way I can say I didn't touch her phone. By s-off and rooting it and installing stock rooted deodexed I am opening myself back up to her wrath but so be it. It's better than her telling me 4 times a day that her phones says an update is ready but fails every time she tries to install it OTA. It's all about path of least pain. LOL.
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
lanewhit said:
I would flash the new rooted base. As I mentioned before, I'm on mean bean 3.09 with the updated firmware from the Captains thread and all has been working great.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Cool. Thanks for that info. I think I am going to do a twrp backup and a dirty flash of stock rooted first. I know that's not the best and most advisable route but dirty flashing is underrated. If things are wonky I will wipe and factory reset and flash again. Dirty flashing a new base on top of the old isn't THAT much different than getting the software update OTA. I trust dirty flashing more than I trust Sprint to be able to seamlessly deliver it. Probably do it tonight while she's asleep and see if she notices anything different tomorrow. I'll just blame Halloween spooks and goblins if things go wrong.