Related
Hey all!
I rooted my phone quite a while ago and have been running das_bamf_remix_1.7 and am thinking of switching to a different rom, the only thing is that I see all these requirements for mr2 or 2.5... and my question is, do these usually come with the rom? If not, what are the best steps for flashing these radios and what exactly do they do?
Thanks guys.
Hi, that is exactly what I was trying to figure out too.
Can the radios be updated independent to ROMs?
I am currently at rooted stock rom.
Should I install the radio to, say MR2, and the install the custom ROM?
Thanks for your help!
The radios do not normally come with the ROM's and would need to be updated separate using the HBOOT process. GB would need the MR2 or MR2.5, Froyo would use the MR1 radios. I don't have the links right now to point to the radios but if you search here you will find them pretty quickly.
Here is a link for some info on the radio's.
http://forum.xda-developers.com/showthread.php?t=1045081&highlight=radio
Thanks alot! I think I was able to install both the custom rom and the radio (in that order).
I wish if someone could help a bit more...
Regarding the 'Gingerbread Related Bricking'
http://forum.xda-developers.com/showthread.php?t=1096104
Could this apply to Das BAMF Remix v2.1 + MR2.5?
This is the combination I have tried...
Here is another link to the Radio's.
http://forum.xda-developers.com/showthread.php?t=1154010
fooooo - Yes you are correct with the rom then the radio flash. As far as the bricking, did you brick or are you just curious about it bricking?
I am completely stock but flashed the mr2 update.. reboots have completely stopped but my signal and 3g (currently not in 4g area) are extremely slow.. although they appear to be slower while pdanet v3.0 tethering.. any info or advice?
Also can anyone point me to a thread that lets me go back to completely stock
Thanks
The bricking issues seem to have subsided since the release of the MR2 radio. I think it was suspected that the original leaked GB radio initiated the bricks.
krime - As far as running MR2 on stock I would imagine that the problem is that MR2 & 2.5 are for the GB-based ROMs (and das bamf 1.8.6) and as such won't work with stock froyo. But I haven't been on stock for a while so maybe somebody else knows for sure.
krime922 said:
Also can anyone point me to a thread that lets me go back to completely stock
Thanks
Click to expand...
Click to collapse
Last link under REF|Guides
http://forum.xda-developers.com/showpost.php?p=12481600&postcount=1
"Next, push exploits.zip and misc.img."
Ok so basically download the stock firmware and exploits, when it gets to the adb commands (from the above on) im lost... Do I download the sdk starter package on android sdk website or? A complete guide-for-dummies would be appreciated
I am coming from 1-click DroidX so my rooting ability is negligible.. however because MR2 apparently does not belong on stock froyo.. I kinda have to in order to go back to complete stock.
I would of posted in the dev forum but I havent met the minimum required posts lol
Thanks for your responses
ksmitchell said:
Here is another link to the Radio's.
http://forum.xda-developers.com/showthread.php?t=1154010
fooooo - Yes you are correct with the rom then the radio flash. As far as the bricking, did you brick or are you just curious about it bricking?
Click to expand...
Click to collapse
It looks like it's working fine!
I just wanted to make sure I wasn't on the bad combination of ROM and radio that could brick the phone.
Glad it seems fine. Thnx!
krime922 said:
"Next, push exploits.zip and misc.img."
Ok so basically download the stock firmware and exploits, when it gets to the adb commands (from the above on) im lost... Do I download the sdk starter package on android sdk website or? A complete guide-for-dummies would be appreciated
I am coming from 1-click DroidX so my rooting ability is negligible.. however because MR2 apparently does not belong on stock froyo.. I kinda have to in order to go back to complete stock.
I would of posted in the dev forum but I havent met the minimum required posts lol
Thanks for your responses
Click to expand...
Click to collapse
First: Don't post questions in the dev forum. I know you didn't, but you said you would have if you had enough posts. Only development of hacks and ROMS and such belong there just FYI. As to your question, J-Case's root tutorial that is stickied in the dev forum has an easy ADB installer. Use that it's the easiest way to get ADB up and running. Search XDA and Google for tutorials on how to use ADB. I don't have links, but its pretty easy to find the info. Once you have done that go to the dev forum and look for J-Case's sticky thread on how to properly return to stock. This should get you back on totally stock unrooted MR1.
Sent from my HTC Thunderbolt
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.
These are stock ROMs.
Rooted, busybox,zipaligned and bash has been added using dsixda's kitchen. Both odex and deodex versions are available.
for anyone that was looking for them
Shooter_Sprint_WWE_1.11.651.2_deodex.zip
http://dev-host.org/zayk4z6jyx5q
Shooter_Sprint_WWE_1.11.651.2_odex.zip
http://dev-host.org/j2j58ra3qzs6
Shooter_S_Sprint_WWE_1.13.651.7_deodex.zip
http://dev-host.org/1qgablydl1tj
Shooter_S_Sprint_WWE_1.13.651.7_odex.zip
http://dev-host.org/t6ff574lnx63
Shooter_S_Sprint_WWE_2.08.651.2_deodex.zip
http://dev-host.org/z07mwdoj5frw
Shooter_S_Sprint_WWE_2.08.651.2_odex.zip
http://dev-host.org/glybx8i6vrxg
Shooter_S_Sprint_WWE_2.08.651.3_deodex.zip
http://dev-host.org/qoxr883gyigu
Shooter_S_Sprint_WWE_2.08.651.3_odex.zip
http://dev-host.org/zxikgapmbi2y
Shooter_S_Sprint_WWE_2.17.651.5_deodex.zip
http://dev-host.org/hqkar642vqrn
http://d01.megashares.com/dl/EGkGrrQ/Shooter_S_Sprint_WWE_2.17.651.5_deodex.zip
Shooter_S_Sprint_WWE_2.17.651.5_odex.zip
http://dev-host.org/60nw6kjevvto
http://d01.megashares.com/dl/srTe15g/Shooter_S_Sprint_WWE_2.17.651.5_odex.zip
Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_odex
http://d-h.st/Jkx
http://d01.megashares.com/dl/AcxqYDO/Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_odex.zip
Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_deodex
http://d-h.st/vE5
Provided by Flashalot, if you have any question please pm flash
2.18 modified to work with any hboot
Odex
http://d-h.st/dBN
Deodex
http://d-h.st/0aM
Thanks!!!! This will be very useful to many!!!
Sent from my PG86100 using xda premium
Any way to make a stock rooted PC86IMG? It would save me a ton of time if I ever have to wipe super clean if I screw something up.
retnuh730 said:
Any way to make a stock rooted PC86IMG? It would save me a ton of time if I ever have to wipe super clean if I screw something up.
Click to expand...
Click to collapse
I second this... Maybe there is one floating around in another thread somewhere.
For what version ? and why just curious
Well it'd be nice to be able to basically RUU the phone back to fully stock without using a pc (mine is broken currently). I have the Eng hboot and s-off so it'd be nice to have one of the original RUUs before hboot 1.5. I've recently been having issues with any recovery I run and feel like a fresh start from scratch would help a lot.
joehunni said:
Well it'd be nice to be able to basically RUU the phone back to fully stock without using a pc (mine is broken currently). I have the Eng hboot and s-off so it'd be nice to have one of the original RUUs before hboot 1.5. I've recently been having issues with any recovery I run and feel like a fresh start from scratch would help a lot.
Click to expand...
Click to collapse
these are rooted roms these dont include hboot.img files
if you want RUU's
http://tiny.cc/ntcz6
I just got my Evo 3D 2 days ago & rooted but still on 1.13.651.7
will this latest update break root?
long as you use the rooted ones your fine
and update your radios
http://forum.xda-developers.com/showthread.php?t=1193101
Good stuff, glad this sticky was created. I remember there being a stock one with Beats added and HotSpot unlocked. Does anyone know where that one is?
eXplicit815 said:
Good stuff, glad this sticky was created. I remember there being a stock one with Beats added and HotSpot unlocked. Does anyone know where that one is?
Click to expand...
Click to collapse
yeah that's dastin1015's ROM, should be on the first or second page.
also, I win, I voted for the sticky thanks lufc! and of course mr.esp
il Duce said:
yeah that's dastin1015's ROM, should be on the first or second page.
also, I win, I voted for the sticky thanks lufc! and of course mr.esp
Click to expand...
Click to collapse
Yeah, I've seen this one, but it's not quite it. The one I'm talking about is a completely UNTOUCHED ROM (even the boot screen is stock), and only has the Sprint HotSpot unlocked and Beats included. I may be wrong, but I could've sworn I ran this ROM for a couple months. I unfortunately deleted the zip file, before I realized I couldn't find it anymore. Any of the Devs out there interested in creating this?
eXplicit815 said:
Yeah, I've seen this one, but it's not quite it. The one I'm talking about is a completely UNTOUCHED ROM (even the boot screen is stock), and only has the Sprint HotSpot unlocked and Beats included. I may be wrong, but I could've sworn I ran this ROM for a couple months. I unfortunately deleted the zip file, before I realized I couldn't find it anymore. Any of the Devs out there interested in creating this?
Click to expand...
Click to collapse
I think smokin1337 put up a zip to unlock hotspot and add beats to a stock deodex rom, should be on the 2nd or 3rd page.
il Duce said:
I think smokin1337 put up a zip to unlock hotspot and add beats to a stock deodex rom, should be on the 2nd or 3rd page.
Click to expand...
Click to collapse
Yeah, I'm doing that right now. Thanks for your help, just wish I had remembered where I got that ROM from.
Mirrors?
Can you post mirrors please? filesonic is saying sharing privileges are no longer available. I am looking at the 2.17 roms
Tplane37 said:
Can you post mirrors please? filesonic is saying sharing privileges are no longer available. I am looking at the 2.17 roms
Click to expand...
Click to collapse
Yep...same here...looks like Filesonic is scared that the gov will do to them what they did to Megaupload. What a bunch of crap.
adding mirrors
Mr.Esp said:
adding mirrors
Click to expand...
Click to collapse
Thank you. This Megaupload takedown is definitely changing a lot around the internet.
Mr.Esp said:
adding mirrors
Click to expand...
Click to collapse
You are the MAN!!!!!!
fixed more host coming
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.....
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