Edit 3: Well more news. I have found that it's a problem with OTA and the new base with ICS builds. Seems like the cpu settings aren't wanting to stick at all. It's min/max is set at 100%. Disabling Perflock with Antutu and Setcpu seem to not be working as well. I saw on a different forum that someone else was having this same problem and was suggested to flash BAMF's new sense boot img. This unfortunately did nothing. Am and two other people only having this issue? If so, man i'm unlucky
So I ran the OTA from Con247's thread here And now I am having crazy issues:
Code:
1) Battery is overheating like crazy. Staying at 114F consistently
2) Had the "Dead Battery + CWM" issue like seen [URL="forum.xda-developers.com/showthread.php?t=1489687"]here[/URL]
Now I have resolved the second issue, pain in the ass but solved. I was wondering if anyone had any advice for the first problem? Or if running an older RUU I'm thinking RUU_Vigor_VERIZON_WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_221502_signed.exe
Any issues with going back? Is it even possible? This is a good arguement for having S-off so I can flash whatever I want. Thanks for the help!
Edit1: After further testing I have found that I can run GB with the battery hovering around 88F-92F while doing nothing and about 94F-96F while syncing. (Just flashed CleanROM GBE 1.7.5 for testing) Stock (from RUU) is running cool at 82F-86F
Edit2: Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
My experience was similar. I think something in the OTA kernel is eating battery and causing heat. When I used that same process it didn't work quite right for me. I ended up RUUing to the latest official build and that helped some. Con's process does update your boot loader though and the old RUU will see that and fail. Your mainver should be updated too... So that can cause problems going back too.
I went to an ICS from and that helped my overheat issue some. I recommend the RUU and checking out one of those . You should see some improvement.
a-jive said:
My experience was similar. I think something in the OTA kernel is eating battery and causing heat. When I used that same process it didn't work quite right for me. I ended up RUUing to the latest official build and that helped some. Con's process does update your boot loader though and the old RUU will see that and fail. Your mainver should be updated too... So that can cause problems going back too.
I went to an ICS from and that helped my overheat issue some. I recommend the RUU and checking out one of those . You should see some improvement.
Click to expand...
Click to collapse
So run the acutal RUU? The latest or an older version?
If you took the OTA, you have to run the latest RUU. 2.01.xxx.xx.
So it seems that running the older RUU wouldn't work because it detects your version and will tell you that you have a newer version.
There's a new tool from drellisdee that will change your mainver using a script.
HERE: http://forum.xda-developers.com/showthread.php?t=1526316
So... I think you can use that and put yourself back to 1.x and run the 1.x RUU. You might want to check in that thread though. Also, I don't know for sure that it will revert your hboot and radios and such by running the older RUU or not. Worth a try though.
I also think I've read something about being able to revert the radios back to the original ones, not sure where that was though, and may have just been a post of someone else who thought it was possible.
Yeah good idea, I was thinking that too. I unfortunately cannot find an older RUU that isn't uploaded to FileFactory. Man that place is the worst. So what if every other uploader has shutdown in fear of persecution. And because of that they're severely overloaded. I need my RUU's dammit.
Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
I mis spoke above... When I used Con's manual method it updated my HBOOT (not bootloader) which caused the 1. RUU to fail (I was using an older method to rewrite my mainver to 1.000.00.000, or whatever).
I used the newest official RUU which I found on football's sticky'd post in the dev section. If that's missing now let me know and I can hook you up the flash able RUU file.
As for norms, there a a few threads on the topic, but I usually max out at like 125 when playing games or surfing on 3G 4G. That's too hot IMO, but I saw 140 once playing GTA when I was in the same place you are now.
nolimit78 said:
Yeah good idea, I was thinking that too. I unfortunately cannot find an older RUU that isn't uploaded to FileFactory. Man that place is the worst. So what if every other uploader has shutdown in fear of persecution. And because of that they're severely overloaded. I need my RUU's dammit.
Can anyone also give me some insight to normal battery temperatures? OC, stock, Heavy Use w/4g, Heavy Use Wifi, Screenoff... ect.)
Click to expand...
Click to collapse
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
con247 said:
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
Click to expand...
Click to collapse
con... I read a post by someone who thought you had a method to go back to the old radios... Was that incorrect?
Sent from my ADR6425LVW using Tapatalk
No I don't have one. It is not possible without S-OFF. Whoever posted that does not know what they are talking about.
con247 said:
Don't know what to tell you. You can't run the older RUU even if you set your main version back. It will see the newer hboot and fail.
I did not change anything from the OTA update package. I just added root and turned it into a flashable rom. Any problems that you have are likely due the new radios or the new OTA rom itself. Alot of people have had back luck with the OTA rom and new radios/firmware. That is HTC's fault. All I did was simplify the install for rooted users.
Click to expand...
Click to collapse
For the record, I wasn't hating on what you put together, I had an error during my first try, and once I got it to take something was just still off. I'm sure it was a user error!
a-jive said:
For the record, I wasn't hating on what you put together, I had an error during my first try, and once I got it to take something was just still off. I'm sure it was a user error!
Click to expand...
Click to collapse
I am fully aware that you aren't hating lol... I was just making sure that you know that you would have had the same experience if you had installed from the RUU.
con247 said:
No I don't have one. It is not possible without S-OFF. Whoever posted that does not know what they are talking about.
Click to expand...
Click to collapse
Yeah, I think they were mistaking what your Stock OTA ROM was for. Thanks for clarifying.
Sent from my ADR6425LVW using Tapatalk
OP updated with more findings. Also I re-read some of what I posted. I wasn't trying to place any blame on any one. Especially con247. You've, from what I've been seeing, have been a huge help around the community and I meant no disrespect.
Also-- coming from the 3D forums have really made me post apologies just to make sure nothing is taken the wrong way. I don't want to piss anyone off and have them not participate anymore. Effin haters are driving devs from our forums..
i am having the same problem with new new radios and firmware. nothing i have tried has given me the good battery life and low temps i had before the new radios. i really want s-off or someway of flashing the old radios. i was even wondering if ou could add the radio from the old ota to the new leak ruu and trick it into flashing the old radios but i doubt that would work.
Try using Scotts super wipe tool and re flashing the ROM. That's what helped me, I think my manual wipes kept missing things and freaking my phone out. Also reinstall everything from the market, my experience with restoring backup apps on a new rom has caused problems. Anyway these are all just suggestions that have helped me! Good luck!
Edit: since doing the above steps my Rezound hardly ever goes above 100 unless I'm tethering on 4g. And my battery life is good enough to get me through the day on the stock battery
Sent from my ADR6425LVW using XDA
Esandorf said:
Try using Scotts super wipe tool and re flashing the ROM. That's what helped me, I think my manual wipes kept missing things and freaking my phone out. Also reinstall everything from the market, my experience with restoring backup apps on a new rom has caused problems. Anyway these are all just suggestions that have helped me! Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
thanks I'm going to try them.
Sent from my HTC Rezound
nev310 said:
thanks I'm going to try them.
Sent from my HTC Rezound
Click to expand...
Click to collapse
Scott is testing a new kernel in the dev forum to try and help address the issues if what I already suggested doesn't work, check it out!
Esandorf said:
Scott is testing a new kernel in the dev forum to try and help address the issues if what I already suggested doesn't work, check it out!
Click to expand...
Click to collapse
ive been trying the kernel he posted and I'm still haveing the same issues.
Sent from my ThinkPad Tablet using xda premium
Related
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.....
http://forum.xda-developers.com/showthread.php?t=1509754
This new app for sensation/e3d etc. got me thinking. It is for devices that have S-ON but are unlocked. I believe I can fix all of our boot image installing woes with the process this app outlined. Once I finish my physics homework, I am going to get some scripts cooking and I think we can have roms install the boot images from recovery.
con247 said:
http://forum.xda-developers.com/showthread.php?t=1509754
This new app for sensation/e3d etc. got me thinking. It is for devices that have S-ON but are unlocked. I believe I can fix all of our boot image installing woes with the process this app outlined. Once I finish my physics homework, I am going to get some scripts cooking and I think we can have roms install the boot images from recovery.
Click to expand...
Click to collapse
That would be awesome if you could get that working. That would definitely have me unlock and root. I've just been screwing with my Inc waiting for this to happen. Thanks
sent from my sexy Htc Rezound
It will eliminate mainver error too.
con247 said:
It will eliminate mainver error too.
Click to expand...
Click to collapse
that would cut alot of thread derailing as well lol
Sent from my ADR6425LVW using Tapatalk
I saw this also and immediately thought that it would be awesome for the rezound hope you can get this to work
Sent from my Galaxy Nexus using XDA App
Its gonna work... it won't have the nice app but it will work. And it will be easy. Really Easy. For both devs and users
con247 said:
Its gonna work... it won't have the nice app but it will work. And it will be easy. Really Easy. For both devs and users
Click to expand...
Click to collapse
If you can fix my MAINVERSION error, I would forever grateful! Sick of having to go into the roms and changing the android info! Its just a pain having this S-ON to deal with.
Yeah it works Should resolve mainver problems
boogerburns said:
If you can fix my MAINVERSION error, I would forever grateful! Sick of having to go into the roms and changing the android info! Its just a pain having this S-ON to deal with.
Click to expand...
Click to collapse
What I don't get is why the devs can't just agree en masse which mainver they're going to use, and then everyone uses that version.
Well they shouldn't use one higher than the RUUs we have so we can restore if necessary. I have had to RUU before because I corrupted my cache partition once.
But some devs used the ICS leak mainver and some people were idiots and installed the leak before it was ready and got their mainvers higher than what we have RUUs for.
con247 said:
Well they shouldn't use one higher than the RUUs we have so we can restore if necessary. I have had to RUU before because I corrupted my cache partition once.
But some devs used the ICS leak mainver and some people were idiots and installed the leak before it was ready and got their mainvers higher than what we have RUUs for.
Click to expand...
Click to collapse
That's one of the reasons I wait a day or so to flash a new ROM if it just getting released. I always wait to see what the problems are first.
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
con247 said:
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
Click to expand...
Click to collapse
I didn't know about the entire mainver thing until the leak came out. I'm new to HTC phones and stuff. But I'm on the 2.x mainver just because I forgot to change it the other day when I was in a flash frenzy. Oh well
u can roll it back if you want
con247 said:
I just check it first and replace the android-info as needed. I am still on the 1.x mainver because I am careful and I was one of the first to flash the ICS leaks
Click to expand...
Click to collapse
This will be great once you get it running.
I'm curious what the reason is that you want to remain on 1.x when the official update brought the phone to 2.x? I'm on 2.x but running a ROM from 1.x even though they just came out with an update for 2.x because I want to keep the red theme made for it.
Btw... the dsb kernel was installed in recovery, like the AnthraX one is. Flashed a zip in recovery that made the PHzip that flashed as an update. Is this different than that?
I haven't flashed the new radios and stuff.
con247 said:
u can roll it back if you want
Click to expand...
Click to collapse
and how would one go about doing that? You mean that crazy method that could brick the phone? If that's the case, I'll just stick with the one I have
con247 said:
I haven't flashed the new radios and stuff.
Click to expand...
Click to collapse
Understood. I'm wondering why you've chosen not to, not why it hasn't happened technically.
feralicious said:
Understood. I'm wondering why you've chosen not to, not why it hasn't happened technically.
Click to expand...
Click to collapse
If it ain't broke, don't fix it... I don't want to risk ****ty battery life or something for better signal because I have no signal/speed issues.
WasabiWa83 said:
and how would one go about doing that? You mean that crazy method that could brick the phone? If that's the case, I'll just stick with the one I have
Click to expand...
Click to collapse
It isn't that crazy or that dangerous. I have flashed my misc a few times when I was seeing if I could hex edit the CID to HTC__001 instead of VZW__001 which would have allowed HTC dev unlock before we got their blessing.
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
The main reason I did not flash the leaked firmware is fear of the long process of going back or not really being used to flashing new firmware. Now that we have s-off is the process easier and if so what is it exactly?
EDIT: Also is there anything I'm missing by just flashing the patch for old firmware versus the upgrade itself...
From reading other posts, I don't believe that S-Off makes flashing firmware any easier. It just enables you to actually RUU back to an earlier version, which you could not do before. (Just be careful and follow steps other members have outlined in flashing back, especially if your 4G connectivity drops. Lots of threads on this issue.) That being said, I have not done S-Off myself (I haven't felt the risk was worth the reward yet), so I'm happy to be corrected if I'm wrong.
Unless you have some burning need to flash a new firmware, I would suggest against it. Some users have reported better signal and battery life, while many others have reported terrible battery life and overheating. I'm on the GB OTA firmware, and flashed CleanROM 4.2.2 with the old firmware patch. Based on other users' posts, ICS runs as well on my Rezound as those with updated firmware.
destro158 said:
From reading other posts, I don't believe that S-Off makes flashing firmware any easier. It just enables you to actually RUU back to an earlier version, which you could not do before. (Just be careful and follow steps other members have outlined in flashing back, especially if your 4G connectivity drops. Lots of threads on this issue.) That being said, I have not done S-Off myself (I haven't felt the risk was worth the reward yet), so I'm happy to be corrected if I'm wrong.
Unless you have some burning need to flash a new firmware, I would suggest against it. Some users have reported better signal and battery life, while many others have reported terrible battery life and overheating. I'm on the GB OTA firmware, and flashed CleanROM 4.2.2 with the old firmware patch. Based on other users' posts, ICS runs as well on my Rezound as those with updated firmware.
Click to expand...
Click to collapse
Cool. That is exactly what I wanted to know thanks. Sounds like I'll be using the patch as well.
cstrife999 said:
Cool. That is exactly what I wanted to know thanks. Sounds like I'll be using the patch as well.
Click to expand...
Click to collapse
The 4G issue has been resolved all thanks to a factory reset after you RUU. So the process of downgrading and upgrading RUU is very simple now. The only difference really is you will have newer radios.
Sent from my ADR6425LVW using XDA
i ran the leaked ICS OTA on the old firmware for about two weeks. Then i tried out Joelz Evita ROM and had to flash the Sense4 firmware. I tried it for a few days but still too many bugs with it, so i restored the ICS leak, then rebooted into hboot and ran the new firmware. I think my signal, download speed and battery all are better now. I'm loving the leak. If the leak is this good, I cant wait for the final.
Just curious, if I'm s-off and can/have flashed new radio and kernel is there still any reason to install the latest and greatest ruu? Are there any other benefits? Maybe I'm missing something but the latest roms from our awesome devs are being rebased on the latest leaks...I just don't see why flashing a ruu is needed. If I'm wrong or missing something please let me know. Thanks in advance.
Sent from my Rezound
Nah its has the same fw as last one just few bug fixed in software level
I'm not saying specifically the last one, I mean in general as new ruus come out. If vzw doesn't eol us that is. Thanks though.
Sent from my Rezound
in term of battery life i would stick to gb fw
but u can ics with patch and still got nice battery life
I've been rooted day one and s-off from the first day it was available and running cleanrom ics. GB sucked with sense for the half a day I used it. This was just an overall general question of "what's the point" and i'm sure others had similar thoughts. I'd hate for anyone to run a ruu for no reason just to have to re-setup their "got it the way I want it" rom of choice.
Sent from my Rezound
If you're flashing the radio and perhaps hboot updates every time, probably not. I guess the good thing about the RUU is that you flash everything together in a package that is known with some certainty by the manufacturer to all play nice. You can always nandroid your custom ROM back on afterwards.
That said...I independently flashed hboot once or twice, and radio several times, on my old Incredible without incident. I've only done the RUU, and only one time, on the Rez.
bluetooth_decay said:
If you're flashing the radio and perhaps hboot updates every time, probably not. I guess the good thing about the RUU is that you flash everything together in a package that is known with some certainty by the manufacturer to all play nice. You can always nandroid your custom ROM back on afterwards.
That said...I independently flashed hboot once or twice, and radio several times, on my old Incredible without incident. I've only done the RUU, and only one time, on the Rez.
Click to expand...
Click to collapse
Yeah I've update the hboot with latest jb and flashed the latest radio and kernel, no issues thus far and all is well...so I conclude ruus are a waste unless that's what you want to roll with is stock
Sent from my ADR6425LVW using xda app-developers app