Rezound Newb - HTC Rezound

Hello everyone. I received a Rezound today! I'm not new to Android or ROM's, but the last HTC I had was the Eris. Can anyone recommend a ROM? I'm coming from a DX2 which only had a few ROM options. I have to say the choices for the Rezound are a bit overwhelming. Where should I begin?

If you want ics, start with cleanrom. It is stable and will give you a good ics experience. Once you get a feel for it, try out a few bamf roms, and sense 4 roms.
Welcome to the rezound
Sent from my ADR6425LVW using XDA

MrWilliams2 said:
Hello everyone. I received a Rezound today! I'm not new to Android or ROM's, but the last HTC I had was the Eris. Can anyone recommend a ROM? I'm coming from a DX2 which only had a few ROM options. I have to say the choices for the Rezound are a bit overwhelming. Where should I begin?
Click to expand...
Click to collapse
They're all great, but you just need to be careful about which one you select since most of us are now running the leaked firmware and some ROMs are designed specifically for that. It would probably be a good idea to use one of Scrosler's ROMs at first since he generally has a bunch of directions about what to do if you are on the old firmware. Essentially, you would flash Srosler's CleanROM and then flash a patch (though he might have done away with the patch). Just look at the different ROMs and read through the threads. There will be a ton of stuff to read, but you really need to in order to be ready so you don't mess anything up. But really, you can't go wrong with any of the different ROMs. I've tried every ROM on this phone and still haven't picked my favorite. They're all that good. I usually switch once a week
That being said, make sure that you are unlocked through HTC Dev. There are plenty of threads in the dev section that will get you started and tell you how to do that. After that, you'll have your bootloader unlocked and will be ready to flash a custom recovery. Make sure that you use Amon Ra's new release. 3.15 would be for those who have flashed the new firmware and 3.14 is for the old firmware. Don't use CWM because it's generally buggy for our phones. Welcome aboard

I highly recommend Rezrom 3.3, its amazingly fast and stable, and lllboredlll has the patch you can download if you do not want to update to the new firmware. All the roms are great though and its really just personal preference.

hardfallen87 said:
I highly recommend Rezrom 3.3, its amazingly fast and stable, and lllboredlll has the patch you can download if you do not want to update to the new firmware. All the roms are great though and its really just personal preference.
Click to expand...
Click to collapse
That one is really good, too, if you're looking for some very nice theme work. Every ROM I've tried has been fast, stable, and sexy as hell. Plus every dev here will be there to help you if something goes wrong with the ROM (if you didn't cause the issue, of course )
EDIT: IF you do want to flash the leaked RUU, even though you don't have to, but if you do, read everything that you can about it. How to do it, what to do if something goes wrong, everything. Then read THIS guide from Scrosler. It'll walk you through the steps pretty carefully so you don't mess up. But again, you need to read EVERYTHING that you can about flashing it so nothing goes wrong.

I have tried all the roms. They're all great! but the one I'm waiting on is Newts 4.0 sense. Should release the update today.

Thanks for the input guys!
I've successfully unlocked the bootloader and installed Amnon's Recovery. I'm downloading CleanROM Pro 4.3 right now. Hopefully that goes smoothly.
I didn't install the leaked firmware as my understanding it that once you do, you can't go back. I think it would be better for me to hold off on that for now until I fully understand what positives/negatives are of each. Have most of you upgraded to the leaked firmware?

MrWilliams2 said:
Thanks for the input guys!
I've successfully unlocked the bootloader and installed Amnon's Recovery. I'm downloading CleanROM Pro 4.3 right now. Hopefully that goes smoothly.
I didn't install the leaked firmware as my understanding it that once you do, you can't go back. I think it would be better for me to hold off on that for now until I fully understand what positives/negatives are of each. Have most of you upgraded to the leaked firmware?
Click to expand...
Click to collapse
That's right, once you update to the new RUU, there's no going back. At least not until we have S-Off. It would probably be best just to not update yet until the OTA is released. I know a lot of us are on the new firmware, but that's mainly because the newer ROMs were going to be new firmware only. Some of them still are and require a patch. I say just hold off, too. At least this way you will have no worries of not being able to return your phone.

Yes I have and don't let it scare you. It's just a matter of repeating what you just went through to get your Rezound rooted. It was well worth it for me.

Smooth sailing! I'll all ROM'd up. Thanks again guys!

Related

[Q] Rooting new Gingerbread leaked ROMS

Sorry for the n00b question. I have rooted and ROM'ed quite a few times, but I haven't messed with my new Thunderbolt much. I tried a few of the roms, but I wasn't really happy with any of them, so I reverted back to stock. Anyway, I want to give the new 2.11.605.0 Gingerbread ROM leak a try, but I haven't been really following these leaks much.
I know how to root and how to load the ROM, but is there a way to root these Gingerbread leaks? Is there an easy way to revert back to stock so I can get the real release when it goes OTA? If anyone has any links they could send me, that'd be great.
Thanks, appreciate it ahead of time!
normmcgarry said:
Sorry for the n00b question. I have rooted and ROM'ed quite a few times, but I haven't messed with my new Thunderbolt much. I tried a few of the roms, but I wasn't really happy with any of them, so I reverted back to stock. Anyway, I want to give the new 2.11.605.0 Gingerbread ROM leak a try, but I haven't been really following these leaks much.
I know how to root and how to load the ROM, but is there a way to root these Gingerbread leaks? Is there an easy way to revert back to stock so I can get the real release when it goes OTA? If anyone has any links they could send me, that'd be great.
Thanks, appreciate it ahead of time!
Click to expand...
Click to collapse
There are only a few stock nonrooted ruus out there. If u know how to flash a rom, then just go to the development section n poke around til u see a rom u like. There's also a few threads on how to revert to stock if/when needed. Football n DroidTh3ory just released the new 2.11 w a few version (rooted/deodexed/debloated etc)
Ah, yes. Been fiddling around since I posted this. Saw the new Revolutionary rooting method too, which is nice. Just saw they posted all those new versions. This is what I need. Thanks for the reply!
fairly new to the rooting process myself, the eris was my first android and rooted that running cyanogen, but it crapped out on me because i had an issue with the trackball. at any rate...
i've rooted my tb and have been having more and more force close issues, sometimes causing me to miss an alarm in the morning. no fun. i'd like to run the latest 2.11 ruu deodexed so i can theme it, i know i like to tweak with the appearance. currently just running stock sense with a root, no other mods, but i am curious if i flash 2.11, which radio(s) should i have? i've seen screen shots where it appears a person has 2 radios, i've seen posts with links to 2-in-1 radios for the lte/cdma networks and i've seen posts where ppl say to mix and match.
basically, i'd like to run something stable, fast and smooth without having to set extra alarm clocks! initially i rooted so i'd be able to take advantage of wireless tethering, but i'd like to do a bit more with it. could someone please advise??
Ruu
normmcgarry said:
Sorry for the n00b question. I have rooted and ROM'ed quite a few times, but I haven't messed with my new Thunderbolt much. I tried a few of the roms, but I wasn't really happy with any of them, so I reverted back to stock. Anyway, I want to give the new 2.11.605.0 Gingerbread ROM leak a try, but I haven't been really following these leaks much.
I know how to root and how to load the ROM, but is there a way to root these Gingerbread leaks? Is there an easy way to revert back to stock so I can get the real release when it goes OTA? If anyone has any links they could send me, that'd be great.
Thanks, appreciate it ahead of time!
Click to expand...
Click to collapse
I think I'm correct in saying that if it says "RUU" its an .exe file so it can be added without rooting. I have the 211 RUU and it installed without rooting. You cn use the Revolutionary method for s-off and it also roots your phone if you want to. However, I think there is no way of going back to s-on once you use revolutionary method.

[Q]Help me decide, to Unlock or not to?

Hey!
Today I recieved my new t-mobile uk Atrix, sent to me from England.
Before I got it I had a HTC Desire, rooted, CWM installed and running custom AOSP roms with 2.3. I really liked that setup, minimalistic and no useless bloatware.
I've tried to read up on the matter, but it's a jungle..
This is how I understand it:
If I update to stock 2.3, it will be harder to unlock it and install custom roms in the future. This is wrong, it would in fact be much easier.
There probably won't be any AOSP roms, because the Atrix is quite different from the other phone, with the webtop and fingerprint reader (which i probably wont even use)
If it wasn't for all the red warning text, it would already be unlocked and romed. So what to do? Unlock and search through the masses for a bugg free deblurred 2.3 rom, or just update with the stock update and run with Zeam launcher instead? Can you install a stock rom on a unlocked bootloader?
Any ideas? Other suggestions?
Thanks for your help!
lovfors said:
Hey!
Today I recieved my new t-mobile uk Atrix, sent to me from England.
Before I got it I had a HTC Desire, rooted, CWM installed and running custom AOSP roms with 2.3. I really liked that setup, minimalistic and no useless bloatware.
I've tried to read up on the matter, but it's a jungle..
This is how I understand it:
If I update to stock 2.3, it will be harder to unlock it and install custom roms in the future
There probably won't be any AOSP roms, because the Atrix is quite different from the other phone, with the webtop and fingerprint reader (which i probably wont even use)
If it wasn't for all the red warning text, it would already be unlocked and romed. So what to do? Unlock and search through the masses for a bugg free deblurred 2.3 rom, or just update with the stock update and run with Zeam launcher instead? Can you install a stock rom on a unlocked bootloader?
Any ideas? Other suggestions?
Thanks for your help!
Click to expand...
Click to collapse
i'd say go for it, just do your research beforehand. it's a pretty simple process, just flash the corresponding pudding .sbf and run the 'fastboot oem unlock' command while in fastboot mode.
then you can proceed to flash a copy of CWM Recovery and install CM7, which is as AOSP as it gets! it doesn't have Fingerprint Scanner or Webtop yet, but Top Men are working on it so expect it all up and working before too long!
Thank you for the respons!
so I basically do what this thread (http://forum.xda-developers.com/showthread.php?t=1196747) says?
Also, I saw a video where the person warned not to run RSD if you weren't on the newest, non gingerbread, release of stock. I assume that applies to t-mobile users aswell?
lovfors said:
If it wasn't for all the red warning text, it would already be unlocked and romed.
Click to expand...
Click to collapse
You and me both. I've had mine for a while (March) and have yet to take that leap. So far, running 2.3.4 O.T.A. w/root I am pretty satisfied. While I am certain that the experience would be greatly enhanced by flashing a different rom. I am simply too much of a chicken to take that leap. I've messed with a few other Android devices and was never too worried when flashing roms. But geez, all of those brick stories around here...
Whichever way that you decide to go, I am sure that you will be fine. The best of luck to ya.
Can anyone just confirm that I need to stuff in this order:
Root it.
Unlock bootloader using this method
Install a CWM, (probably gonna go with RomRacers)
Install a ROM.
ok i did the ota to 2.3 eventually used the autoscripter in general to root/unlock and aosp roms are starting with the cm7 beta once they have finished product its open game so far on cm7 beta myself totally worth it
JdgM3NT4L said:
You and me both. I've had mine for a while (March) and have yet to take that leap. So far, running 2.3.4 O.T.A. w/root I am pretty satisfied. While I am certain that the experience would be greatly enhanced by flashing a different rom. I am simply too much of a chicken to take that leap. I've messed with a few other Android devices and was never too worried when flashing roms. But geez, all of those brick stories around here...
Whichever way that you decide to go, I am sure that you will be fine. The best of luck to ya.
Click to expand...
Click to collapse
Im in the same exact boat. I've rooted other phones easily, but this one scares me for some reason.
Sent from my Atrix

[Q&A] The Definitive Answer on Mainver Issues-EASY SOLUTION

This is beginning to get out of control with all of the thread jacking and such with mainver issues. Anyway, read on.
NEW INFO: FLASH THIS: http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
PROBLEM SOLVED!
Old info if you care:
Q. What is MainVer?
A. MainVer is a string that HBOOT keeps track of that keeps the latest version of the RUU or PH98IMG.zip that has been flashed.
Q. Why does HTC have this?
A. In order to prevent downgrading with an RUU.
Q. I haven't run an RUU. How was my MainVer updated?
A. There are 2 reasons your MainVer could have been updated at this point.
The Original ICS Leak
DSB's new BAMF Rom (downloaded 1/17/2012 or later)
The original ICS leak that some of you flashed was still in RUU image form. Unfortunately, this was distributed with an updated MainVer string in the android-info.txt. When this was flashed, the new MainVer string was recorded into your device. DSB for some reason also included this new android-info.txt in his kernel PH98IMG.zip that is packed with his rom. I am not quite sure why he did that.
Q. What does this mean for me?
A. See new text at the top
Q. Why won't devs just add the new mainver to their roms to make my life easier?
A. They could, but then they would be forcing everyone to have this problem, not just you. It would also prevent everyone from using an RUU to repair their phones until a new one came out.
More Info:
No matter if you are going GB->GB or GB->ICS or ICS->GB you will need to have the correct mainver for your device. If you aren't having trouble going from rom to rom right now, you shouldn't even be looking at this guide. But if you got your mainver updated, you need to replace the android-info.txt for every single rom forever (until a new RUU comes out and it is safe to unify everyone's mainver)
Click to expand...
Click to collapse
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
WasabiWa83 said:
That was quick! Nice work, Con. Hopefully this will help everyone out having these issues. I'll make sure I bookmark this page to link to if anyone should have issues. Thanks!
Click to expand...
Click to collapse
Thanks! That is a good idea about the bookmark. Ill do that too.
Yeah I had to answer this question a few times... this Q/A should make it easier.
I want to be sure I understand this correctly. If I flash an ICS rom I need to use the android-info mainver source 3.10.605.7 and if I want to revert back to a stock rom I need to use the android-info mainver source 1.02.605.6?
I have not installed any ICS roms yet, waiting for some more of the bugs to get worked out. I've been reading where many people are having issues with installing ICS roms and struggling with reverting back to stock.
I will try to make that more clear. Hold on.
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
con247 said:
I will try to make that more clear. Hold on.
Click to expand...
Click to collapse
Thanks Con for the quick reply! I like to look over these forums and make sure I'm understanding some of the issues that are currently going on. I've been flashing roms for awhile but still consider myself a noob. Thanks again!
trickster2369 said:
I make a motion to sticky this thread. Anyone 2nd this motion?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yeah, definitely a 2nd for very this useful post. Especially since a lot of the ROM threads are getting off topic because of this. I saw Scott posted a link to this thread in his release posts. Good idea for the Devs to link back here too
Yeah this needs to be stickied...
Con... here is a post I did explaining Mainver... It is a bit more simplified, might be easier to follow for the new guys. (it also explains what RUU files are and what they do)
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
snowride20 said:
I am sorry but I am trying to make sense of all this. I am on Scott's CleanRom 2.1 will I need to use these instructions to go back to my stock room? This is my first HTC, I've only had Motorola phones up till now and I hate to admit it but this is all a bit over my head. I have been studying these forums for the last 2 days and I really have no clue how to use the backup I made of my stock GB Rom or even what kernel to use. I do regret not waiting to mess with this phone. Any help is greatly appriciated and I love all the work you have all put into this phone. Thanks in advance.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
You're pretty much good because Scott's ROM does not update your MainVer. This is only for those ROMs that updated the MainVer. All you will need to do is restore your nand and flash the stock rooted kernel with Scott's Clean Flash tool. It's really more simple than you would think. You can find the Clean Flash tool and the stock rooted kernel in the dev forum. Just make sure that there is no PH98IMG.img on your ext sd card before you try to revert to your nandroid. Once you have restored your nand, you need to get to HBoot using the clean flash tool to make sure that you flash the stock rooted kernel. If you have the PH98IMG on your ext SD card, you would be kind of boned. Hope this helps a little.
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
rboddy said:
So I flashed BAMF once, but it was weeks ago and I've since been using GingerSense without any issues, and that flashed fine after I tossed his boot.img back on, and then again after I did a full wipe a few nights ago. Is there any way to easily tell which mainver we're currently on? I'm assuming I'm ok since I haven't had to do anything else while flashing his ROM, guess I just wanna make sure.
Click to expand...
Click to collapse
I believe mainver only changed if you flashed rezound cubed 1.0.2. If you didn't flash that, like I did, you should be fine.
Sent from my ADR6425LVW using xda premium
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
rboddy said:
Well if that's true then yeah I'm ok, I see 1.0.2 is from 1/17 and I know I flashed it well before that, so I guess that explains why I haven't had any issues. Thanks!
Click to expand...
Click to collapse
Thanks, I added that date to the OP
It worked
Wasabi, I appriciate you giving me the little extra i needed to get back to stock. Thanks for the help.
So, is the MainVer stuck at the higher version number even if you manually flash the older boot.img from the PC?
The boot.img is independent of the mainver. Once you have it set higher, it can never go back. Possibly on an S-OFF device, but that would be pointless.
Oh thrill. So no ICS for us who flashed the dsb kernel? I hope the real HTC ICS is out soon then.....

Upgrade to ICS Firmware with S-OFF

Now that S-off is available is there a easier way of upgrading to the ICS firmware without having to lose root, have bootloader locked, having to unlock bootloader again and regain root?
Yes. Google android community rezound ics leak march 16. Download for both rooted and locked there.
johnc810 said:
Now that S-off is available is there a easier way of upgrading to the ICS firmware without having to lose root, have bootloader locked, having to unlock bootloader again and regain root?
Click to expand...
Click to collapse
Yes you can, but if you haven't noticed, people mixing and matching firmwares and hboots and ROMs without knowing what they are doing has been kind of a disaster today, since everybody now has S-OFF and is starting to screw around with crap they don't know about. The very fact that you are asking this question indicates that you shouldn't be flashing firmwares, radios, or HBOOTs until you've read up on each and can answer these types of questions on your own. Be careful!
If you aren't already aware of the sdcard issues, what causes them, and how to fix it, then you need to read a lot more before messing with anything else.
not trying to mix radios or anything like that just trying to upgrade my girlfriends phone an easy way. i found the gb firmware hboot but cannot find the ics firmware hboot
johnc810 said:
not trying to mix radios or anything like that just trying to upgrade my girlfriends phone an easy way. i found the gb firmware hboot but cannot find the ics firmware hboot
Click to expand...
Click to collapse
Just stay where you are! Your girlfriend will appreciate you much more if her phone just works correctly.. The ICS Firmware and radios are buggy at best and the results so far have been extremely hit or miss. GB is the latest working official firmware and HBOOT, so if you insist on running an ICS ROM, then use the old firmware patch. If you dont know what the old firmware patch is, then just leave your girlfriends phone alone.
Lol, the main reason I took s-off was so that I could get the ICS firmware out from under my GB. I can't tell you how much heat and battery problems that leak caused me! I will *not* be one of the first to d/l the ICS official build, no matter how much I liked actually using it.
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
johnc810 said:
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
Click to expand...
Click to collapse
Yeah, not getting it. Seems like the biggest problems with the ICS leak was the firmware. Why do you want that firmware?
johnc810 said:
haha i know what the ics patch is im no noob, i was just wondering if there was a flashable hboot with the ics firmware
Click to expand...
Click to collapse
There is, in the dev section there is a thread dedicated to radios in flashable zip format, and you can get the HBOOTs as well if you search. I highly recommend staying on HBOOT 2.11 and GB radios for now though, especially since the phone isn't actually being used by you.
i works well for other people ... it's his phone either help him or let him do what he wants even if that is bricking it ...
just help
im not sure if there is one sorry op
RoryHe said:
i works well for other people ... it's his phone either help him or let him do what he wants even if that is bricking it ...
just help
im not sure if there is one sorry op
Click to expand...
Click to collapse
Actually its not his phone, but then again I shouldn't expect people to actually read the thread either cause it never happens.
Having f***ed up my stuff mess with radios, I recommed you leave well enough alone. Its not nearly as staight forward on the Rezound as it was on the Inc, and there in lies my problem.
But I learned a lot today! So its not wasted experience.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Yeah I'd suggest you read a little more starting from the leak and forward. I had to reflash several time to get a stable ICS on my phone running the old-firmware patch, but then again I still ran into system problems. I have it all figured out now, and it didn't take long to solve the issue, but I'd recommend reading a bit. Jumping in the middle of development of rezound might be bad choice if you weren't here since day 1. .
dejahboi said:
Yeah I'd suggest you read a little more starting from the leak and forward. I had to reflash several time to get a stable ICS on my phone running the old-firmware patch, but then again I still ran into system problems. I have it all figured out now, and it didn't take long to solve the issue, but I'd recommend reading a bit. Jumping in the middle of development of rezound might be bad choice if you weren't here since day 1. .
Click to expand...
Click to collapse
Oh, now someone tells me to look before I leap.
I really should have known better...
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
heres my opinion, ics sucks. gb is silky smooth. jus sayin.
I say go for it. What could happen you piss your girlfriend off and spend the next 36 hr's trying to figure out what went wrong. Believe me I've been there. Lol
Sent from my ADR6425LVW using xda premium

New EVO LTE, should I run newest ruu then root?

I'm just wondering if this will be the best method and save me from having to fastboot flash kernels to use newest roms based on 2.13 I'm currently hboot1.15 with 1.22 firmware.
Thanks in advance. Ps not a noob so not afraid to "go deep" with my phone
Sent from my EVO using Tapatalk 2
Some people are holding out for a possible s-off, this will allow for firmware updates and the like while maintaining full write access to NAND. If this isn't a concern you can go ahead and update. The newest base doesn't really add much that isn't already in custom roms, it does cause some instability with a few roms that haven't updated their base. HBOOT 1.15+ requires you to fastboot kernel regardless. Some people have reported worse performance after OTA
Ok cool. So no big benifit of updating? I'm thinking of running latest Mean but honestly never fastboot flashed kernels b4. This is the first device I've got locked into a wack hboot that doesn't allow s-off.
Sent from my EVO using Tapatalk 2
You should read my guide, it has a lot of really helpful info. It will help answer a lot of questions and get you going faster. But in response to your question, you can run any rom/kernel provided its the same base. You can not however, flash firmware updates to your device without taking OTA
om4 said:
You should read my guide, it has a lot of really helpful info. It will help answer a lot of questions and get you going faster. But in response to your question, you can run any rom/kernel provided its the same base. You can not however, flash firmware updates to your device without taking OTA
Click to expand...
Click to collapse
Great guide, reading now thx
Sent from my EVO using Tapatalk 2
Thankyou, I've been pushing it harder then a politician with an agenda
I would highly recommend spending 0.99 to purchase Flash Image Gui. It makes it really easy for S-On to flash the kernel form the ROM zip, and then reboot to recovery and flash the full ROM. And no PC required to use the fastboot/ADB method.
You should take the update, those that don't will have problems, the new OTA includes a major upgrade to the radios. Those that have not taken the update and just use the new kernel with the new base software are having all kinds of problems with wifi, bluetooth, and holding their lte connections. All of these items were fixed in the new radio.
Now, the s-off argument, it is a fantasy! If you didn't s-off with the original bootloader 1.12 than you might as well upgrade to the full firmware of the new ota. You maybe waiting so long for a 1.15 s-off solution that your phone will have already been replaced with the next great phone that is released. Why handicap your phone with old firmware and radios when if you take the update now, you can still unlock your bootloader, flash twrp, and enjoy any of the custom rooted roms that are rocking the new base. Sense 4.1 and ICS 4.04 are worth the upgrade.
cruise350 said:
You should take the update, those that don't will have problems, the new OTA includes a major upgrade to the radios. Those that have not taken the update and just use the new kernel with the new base software are having all kinds of problems with wifi, bluetooth, and holding their lte connections. All of these items were fixed in the new radio.
Now, the s-off argument, it is a fantasy! If you didn't s-off with the original bootloader 1.12 than you might as well upgrade to the full firmware of the new ota. You maybe waiting so long for a 1.15 s-off solution that your phone will have already been replaced with the next great phone that is released. Why handicap your phone with old firmware and radios when if you take the update now, you can still unlock your bootloader, flash twrp, and enjoy any of the custom rooted roms that are rocking the new base. Sense 4.1 and ICS 4.04 are worth the upgrade.
Click to expand...
Click to collapse
You may or may not be right about the 1.15 s-off being a pipe dream, but I for one am having ZERO issues with the old firmware and the newest MeanROM. Wifi works fine, bluetooth works fine. No LTE here yet, so I don't know if that will be an issue. Until I see a problem that requires new firmware or a new radio, I'm sitting tight and keeping my fingers crossed.
Hey it may be a dream and a solution may not be found until the next latest and greatest but on custom firmware I can keep my fairly beastly phone running just as good if not better then a stock latest and greatest 2 years from now. I have no problems with 1.15 and there's no lte here yet. My WiFi works wonderfully and kushdeck is killing it with CM10. I'd just as soon wait
cruise350 said:
You should take the update, those that don't will have problems, the new OTA includes a major upgrade to the radios. Those that have not taken the update and just use the new kernel with the new base software are having all kinds of problems with wifi, bluetooth, and holding their lte connections. All of these items were fixed in the new radio.
Click to expand...
Click to collapse
I can say from my personal experience that this comment is absolutely false. I am sure that the new radios in the latest firmware are an improvement. However, if it ain't broke, don't fix it. I am HBOOT 1.15, S-On, running MeanROM 3.9 with latest kernel flashed via Flash Image Gui. I live and work in a well covered LTE area. I am having none of the problems that you mention. LTE speeds of ~25Mb down, 18 Mb up. Wifi is working great at home, work, or the coffee shop. Bluetooth sounds just a clear as it always has.
So, it is very functional as-is. I am sure there may be improvements in the latest firmware, but to say you absolutely will have problems is just a lie. My LTEvo is running smooth like butter and fast as a rocket.
Not to mention the fact that some ROMs are on the old base and have issues with the new base, there was quite a few threads here and in other forums about people wanting to jump back to an older base
Well, if you want to keep running old firmware, that's your option. Thankfully I am s-off and rocking MeanRom 3.9 with the latest firmware and very happy. The op asked a question and got a lot of one sided answers from the "wait for s-off crowd" and I wanted to chime in. I have seen a lot of posts in the MeanRom thread and others that they have wifi and bluetooth problems and the common denominator is running the old firmware with the new kernel and base. Also seen hundreds of posts by people in LTE fringe areas unable to hold their LTE without it constantly switching back to 3g which is one of the fixes with the new radios. And to the old base custom roms not working well with the new firmware that is false, the new radios work fine with those old out of date custom roms. Step into the future and enjoy a fast trouble free phone.
Sent from my A500 using Tapatalk
All true but I have seen plenty of people brick trying to jump back to earlier firmware
Thanks for all the comments. Currently I am rooted using HTC dev method. I have newest twrp recovery by using goo manager to overwrite the old twrp version that I had after using an older manual method to root.
I am running MeanRom 3.9 now. Found flash IMG app on play store pretty quick and its easy to use. Basically my phone is almost back to fully customized. I asked the question right when I got my replacement yesterday. Although I would like the benifits of the update, I'm kinda with the if it ain't broke don't fix it crowd. I'm not a fan of using adb to root but it def wasn't difficult at all. I'm just worried now that at this point to go back, ruu, update and such could be more harm then good at this point. Am I right?
Sent from my EVO using Xparent Blue Tapatalk 2
There's really not much harm, the biggest problem updating had been ROM compatibility and most developers are on the new base or are currently in the middle moving over. Those of us sticking with 1.15 are hopelessly awaiting an soff exploit that nay or may not come
Glad to see you're on MeanRom. Mikey is a great dev and fast with the updates. Since he is currently updating all of his tweaks to the new base, expect an update almost every day. The great thing about MeanRom is you don't have to wipe data between installs. And since you're already on the new kernel, when you update you won't have to flash it again, just the rom. Mikey now uses the ota updater app so you can use it to download the new rom each time and perform the install.
Sent from my A500 using Tapatalk

Categories

Resources