yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Neo:
My phone was updated to the latest RUU and was running VERY HOT all the time. For months I tried different things to fix the issue to no avail. Then, I gave it to REV3NT3CH as a replacement for his bricked Rezound and he fixed it by updating from the first RUU and up the line with each revision. No more overheating, no more permanent wake lock. And you guys know me.. I know stuffs lol I concluded that there must have been something wrong along the way.
[HTC Rezound] acejavelin:
Fair enough... I trust both you and REV3NT3CH in all matters Rezound related, and logic does not always seem hold true in the world of Android... so if it works, I'm fine with it, just sounded... illogical :silly:
[HTC Rezound] REV3NT3CH:
i will say when i went to certain roms like sun_dreams sense rom and one other one it got slightly hot with extraneous use but not like it was
[HTC Rezound] flamewalker:
Unfortunately it seems I spoke too soon. I had 3 reboots today. It's never in the same app or doing the same thing. Never tweak any of the cpu settings or anything (other than to bring the minimum back to 384).

And here I was feeling lucky :p

---------- Post added at 11:07 PM ---------- Previous post was at 11:04 PM ----------

/facepalm... Does a nandroid not restore the cpu settings? Or was it back to 96 mhz since the first reboot all this time because I didn't select the restore cpu settings on reboot??
[HTC Rezound] Lazy8:
I have a feeling it's the leaked 04.05.605.2 that is causing the problems. I went back to 1 and tried to work my way up the RUU's. Getting to 3.14.605.12 it updates OTA to 3.14.605.13 and then wants to update to the global 04.05.605.14 but constantly fails I suspect because I am rooted.

I ran the leaked 04.05.605.2 and noticed the phone getting warm quickly again. So back to 03.14.605.13 and then hoping to go to the global 04.05.605.14.

But I can't find it ANYWHERE! does anyone have this? only file I could find was the rooted version that doesn't have the radios and firmware...

Any help is appreciated.

This is all in the hopes that I can run Tachyon without the phone feeling like it's going to melt and constantly rebooting.
[HTC Rezound] Neo:
Gonna look through my ancient archives..
[HTC Rezound] Neo:
Global OTA Package 4.05.605.14

This is all I could find:

http://db.tt/keMdFzn7
[HTC Rezound] Lazy8:
Thanks neo...downloading now...doesn't say what it is :P lol but I trust you! Fingers crossed this solves my issues with Tachyon.
[HTC Rezound] Neo:
Global OTA Package 4.05.605.14

I don't believe it's a RUU
[HTC Rezound] Lazy8:
Downloaded and changed to PH98IMG.zip it runs...gets to parsing and quits out...no error :(
[HTC Rezound] TheBr0ken:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Chances are that figuring this out gave you a better feeling of gratification and accomplishment than your lab would have. :D
[HTC Rezound] fudplayers:
It's going to be tough for me to ever leave this ROM. It's stable but the battery life is amazing. When I can go to work and get off of work and it's only dropped 1 or 2% all day, that's unheard of. Great job Neo!
[HTC Rezound] Smitelight:
Jrummy's Rom Toolbox is my favorite goto app for almost everything root, personally. I like only needing one resident app instead of the eight I'd need running at boot otherwise.

Also, Neo:

media.stagefright.enable-scan=trye

lolwut
[HTC Rezound] Neo:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

lol build.prop goof of mine? XD
[HTC Rezound] Smitelight:
On the RAGE 2.3 build.prop, anyway. We can blame CM, if you like. ;>

I was wondering why none of my sdcard ringtone/alarm/etc folders were showing up in my Audio menu.
[HTC Rezound] Neo:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Obviously should say =true

Thanks for finding my mistake
[HTC Rezound] brenuga:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Not quite getting that good of battery life, lol, but I agree with you. I will probably flash the new TRON for s***s and giggles tomorrow, but I have been a RAGE fan since 1.6 (late jumping on the train I know).

Neo has had his share of little minor bugs he immediately patched but has never had a mediocre rom. I could go back to neomax, his oldest Rezound rom at this point, and still be happy.

And that's not me giving fan service it's just the truth. When you see ppl clamoring for updates to his bare bones rom X, you know he's doing something right. Word.

---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------

Split change log??? Double RAGE = double change log?

Or, 'dude, I heard you liked change logs so I got you a change log for your change log.'

I'll be here all week, folks.
[HTC Rezound] nerdyessence:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

So I finally flashed the latest update, however, I'm not getting the governors for the kernel that everyone is talking about. Am I going to have to flash a kernel file?

Phones: HTC Rezound (current) | HTDroid Incredible
[HTC Rezound] Neo:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

What do you mean? The governor settings should be in performance options.
[HTC Rezound] brenuga:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

If you're s-on you have to flash the boot.img from the ROM zip after flashing ROM.
[HTC Rezound] nerdyessence:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

I tried that but must be doing something wrong. Will try again later today.

Phones: HTC Rezound (current) | HTC Droid Incredible

---------- Post added at 07:29 AM ---------- Previous post was at 07:27 AM ----------

I'm only getting the standard settings. No,

wheatly etc. So I thought I was doing something wrong.

Phones: HTC Rezound (current) | HTC Droid Incredible
[HTC Rezound] Neo:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Ah that's because I used the default governor in this rom. The next update will come with funky kernel
[HTC Rezound] Neo:
Finally made it to work! Time to Fire it up and get this Android 4.2 RAGE 3.0 in motion for possible release tonight!
[HTC Rezound] replica9000:
The only person I know excited to get to work lol
[HTC Rezound] GoldenCyn:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]
[HTC Rezound] nerdyessence:
Re: [ROM][JellyBean][AOSP][01.12.13] ┬─┬ ノ( ^_^ノ) v2.3 LINARO! [Android 4.1.2]

Ah, sneaky sneaky Mr. Neo.

Phones: HTC Rezound (current) | HTC Droid Incredible
[HTC Rezound] Neo:
I meant standard Chad Kernel lol

#FAIL

not default governor. Where's my head today? :P
[HTC Rezound] brenuga:
NICE. LMFAO. :laugh: This made my day, thanks. I would hit thanks on the post but I ran out of kudos today.:good:

---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------

He's excited to get to work cuz it lets him have time to work on building ROMS with minimal interruptions :p
[HTC Rezound] jski711:
Is anyone else having GPS issues? It can get pretty wonky at times but sometimes its spot on. Any ideas? Great ROM BTW. Thanks.OK just noticed if I turn on WiFi its spot on. I normally have WiFi off. Has that been the issue all along?
[HTC Rezound] brenuga:
Re: [ROM][JB][AOSP][01/25/13] ┬─┬ ノ( ^_^ノ) v3.0 LINARO! [Android 4.2.1]

And RAGE 3 is out!! Citizens of Earth, rejoice!
[HTC Rezound] Neo:
did you re-lock your bootloader? I don't remember how OTA's are supposed to be flashed
[HTC Rezound] Lazy8:
No I didn't relock the bootloader, but it didn't stop the OTA from 12-13...just going from 13-14 won't work. How would I go about relocking the bootloader?

I am s-off so I shouldn't have to lock the boot loader..

Redownloading again...hoping maybe I got a bad download. Why is this update so hard to find? and why doesn't this OTA update work if I am stock with stock recovery? The OTA for 12 and 13 worked fine? Weird?
[HTC Rezound] Neo:
Ya got me. I've always re-locked bootloader when performing a firmware update.
[HTC Rezound] drhile:
Yeah it should always work but always do an md5 check first. I'm almost certain that the bootloader should always be locked before attempting an ruu
[HTC Rezound] Lazy8:
I have no idea how to relock the bootloader...everything i'm searching and finding on here has to do with unrooting...any spoon feeeding would be appreciated :P

Update:

I redownloaded your file neo...no joy...it looks good but gets to "parsing" and bombs out with no error. At this point all I want to do is get to the latest RUU radio/firmware etc...I can't find a valid copy of the .14 file and I can't OTA update..it bombs out as well with "service unavailable" error. What the heck do I do now? I'm on HBOOT 2.25 and 424 radios...if I flash back my nandroid of Infection 2.9.1 it's going to have problems probably....uhg!
[HTC Rezound] drhile:
Use fastboot through the command prompt to relock it using the same binary you used to unlock the bootloader. If you don't have it anymore you'll have to get it. Scour the forums as I'm sure the answer is there. If you still have troubles just pm me and I'll walk you though the process
[HTC Rezound] Lazy8:
Thanks drhile, does this remove s-off? I do not want to go thru the paperclip trick again...not worth it.
[HTC Rezound] Uzephi:
S-on and bootloader lock are two different commands.
[HTC Rezound] drhile:
Couldn't have said it better. As far as I know s-off is permanent.
[HTC Rezound] Lazy8:
I thought so just wanted to make sure :) I am at work now and can't access my phone with a computer to relock the bootloader or send any commands, so I was thinking of flashing this http://xdaforums.com/showthread.php?t=2260154

and this

http://d-h.st/BIj over that...

should give me a complete RUU of 4.03.605.14 in a round about way...can't think of a better option right now with my limited choices.

UPDATE:

I couldn't run the OTA_rooted_missing_radios zip as it kept giving me a signature not verified error??? so I went into the stock recovery, remembered reading about the volume up key and power bringing up the menu from the red triangle screen. Tried running the zips there and still no go...just for the heck of it I decided to try Neo's zip he linked me earlier..the full RUU for global .14....and low and behold!!!!!! it worked!!! updated the phone and everything!!! sweet...going to try flashing tachyon now.

I don't know why the OTA wouldn't install while stock..maybe because I'm still unlocked bootloader....I don't know why non of the other .zip would work but some did..etc.etc..but the stock recovery let me choose a zip to install that did work...go figure.

Thanks everyone for your help :)
[HTC Rezound] Uzephi:
http://xdaforums.com/showthread.php?t=1612937

It isn't permanent
[HTC Rezound] Lazy8:
Help :(

I feel like such a newb again....so I've got the boot loader unlocked and I am still s-off but I can't flash anything...just keeps giving me the same error "signature verification failed"

All recoveries and roms I try to flash.....uhg...What am I missing?

NVM...I was using the wrong command.
[HTC Rezound] drhile:
fastboot flash boot boot.img or fastboot flash recovery (recovery name).img
[HTC Rezound] acejavelin:
fastboot flash recovery (recovery name).img

You can't flash the zip directly in fastboot, you have to extract the img file and flash it.
[HTC Rezound] Lazy8:
Yup! that too...didn't realize you had to extract the recovery.img from it. I tell ya, this has been one heck of a learning experience..lol! I don't think I spent this much time and energy on the phone..even when I rooted s-off...

And is appears even after ALL that work..it's still running hot...have yet to see a reboot though..running Tachyon 1.1.5 now
[HTC Rezound] drhile:
Oops typo I meant .img. Thanks for the catch
[HTC Rezound] flamewalker:
Same here... never thought I would learn as much as I've had to to fix my own goofups on my phone...kinda had to since I wanted to s-off to return my phone for replacement and be safe :p

---------- Post added at 03:55 PM ---------- Previous post was at 03:52 PM ----------

FYI you CAN go s-on, just know that you must be on stock recovery and ruu before doing so or you will (from what ive heard) hard brick your device.
[HTC Rezound] Uzephi:
You do not have to ruu.... As long as you are unlocked... You just HAVE to be on a stock hboot (not a hex edited or eng one)
[HTC Rezound] flamewalker:
My bad... stock hboot. I've always done stock everything for relock just to be safe anyways :p (only to send in for replacement)
[HTC Rezound] drhile:
Alternatively, you can use a hex edited bootloader for "customizing" it a certain way.
[HTC Rezound] Neo:
Because this rom appears to still be in good use, I will be updating it soon hopefully. New kernel and everything.
[HTC Rezound] drhile:
I love the variety of roms to choose from but I hate that I can only pick one! If you need a beta tester for this one I'll do it.
[HTC Rezound] Neo:
Back in the Game baby!

Thanks goes out to XDA Members rmcrowe and REV3NT3CH for stepping up and sending me a spare Rezound! I really appreciate the assistance and glad to be able to continue supporting this device :)

Thanks also to my donators out their for your continued contributions to me. It's always appreciated.

Thanks goes out also to those who remain active in my threads and answer all the questions that get asked on a daily basis. I wouldn't be able to keep this up without you guys!

This has been by far the most helpful group of members I've ever had the pleasure of providing for.

-Neo

(REV3NT3CH I'm going to be sending yours back to you once it arrives so you can continue to dev on it)
[HTC Rezound] flamewalker:
No, thank you!

FYI since I fixed the cpu setting again (dunno how/why it was back below 384... probably from the last reload), but since I re-ruu'ed from 1.0 back on up to current and restored infection, not a single reboot this week!

Might give tach another try this weekend... maybe... but then again I will probably be busy designing houses... so we will see :p
[HTC Rezound] jdmst71:
Is there a source for all the ruu files because I think I need to do the same to cure my reboot issue. Just started on this ROM and I love it besides the reboot that happens when I try waking up the phone. I did set the min clock to 384 but it didn't help. Getting rid of the lock screen helped 80% but still have those pesky few reboots per day.

---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------

Doh...I just saw the link for the shipped ruus in this forum. Is there only 4 releases? I thought the newest version had hboot 2.28 and the 2.23.10.0123r and 2.23.10.0124r radios? Maybe that's why I am having minor difficulty with reboots
[HTC Rezound] scy1192:
Newest HBOOT is indeed 2.28, but IIRC that update is only available OTA. I haven't had any problems with 2.27, and I haven't seen anyone else with problems, so I don't think that's why you're having reboots. Reboots are usually caused when a part of the OS crashes and it can't recover.
[HTC Rezound] REV3NT3CH:
There is a flashable zip for hboot 2.28 with the updated radios that was posted by flyhalf as far as reboots they are mostly caused by improper settings in the kernel under performance...as for the links for shipped ruu's here on xda they do not work...I can give working links but to downgrade as what the ruu's are for you need s-off and locked bootloader
[HTC Rezound] flamewalker:
If you want to do the full ruu from 1. thing, you must be s-off and locked bootloader as reventech stated. I would recommend a nandroid backup first too:

http://shipped-roms.com/index.php?category=android&model=Vigor

Download and install 1.0, 1.02, then 2.0, then 3.14.

Once on 3.14 do an ota check, will take you to 3.14.605.13. Then install 4.03. Then, download and install these from recovery:

http://www.wizwire.net/vigor/OTAPkg-3.14.605.13.zip (Only if you can't get the ota to install from check software upgrade menu)

http://www.wizwire.net/vigor/OTAPkg-4.05.605.14.zip

I was unable to install the ota, well, ota. Had to find and download it, then boot to recovery (stock recovery) and load the zip from there. Then, reload your custom recovery (if you are s-off, I think you can just name it ph98img.zip and reboot to hboot, I actually re-unlocked then used adb to push it, but you will get relocked if you lock the boot again), and restore your nandroid and make sure the cpu settings are min 384. I haven't had a reboot since.

Good luck!

Since then,
[HTC Rezound] Lazy8:
This is exactly what I was looking for when I was doing this last week...thanks for spelling it out...unfortunately it didn't fix my reboots...tachyon still had issues for me...I might try it again..maybe I borked something the first time...now it should go smoother...Thanks again for the links and everyone else's help
[HTC Rezound] flamewalker:
Same here re: tachyon but it did solve them for Infection for me.

I might give tach another go myself this weekend...
[HTC Rezound] jdmst71:
For anyone who runs all the shipped ROMs through their device from the link above please let me know...

Did the 1.02 exe work for you. I keep getting an error in windows before it even runs.

The 3.14 runs and updates automatically. The 4.03 file will not auto update after installing the ruu. On top of that the manual update file linked does not run in my hboot. It seems to stop after unzipping the file prior to parsing.
[HTC Rezound] REV3NT3CH:
The shipped ruu's in xda just doesn't work...I'll have a link for youvsoon
[HTC Rezound] kodiak799:
The only ones (the exe files) that worked for me were 1.00 and 3.14 (I had already been on Infection, and then back from Tachyon because it was buggy for me - probably because I had the 2.25 HBOOT and old radios). The OTA update to 3.15 kept hanging on me, so I moved on

I don't think it matters. I then flashed the 2.28 HBOOT and radios, flashed TWRP, and then flashed the global stock rooted 4.05 rom.

Then flash rom of your choice.

IMO, if you are S-Off, running any RUU should refresh everything on your phone, then grab the latest radios and flash your rom.
[HTC Rezound] blazin_phattys:
I flashed this latest version about a week ago after being on 2.3 for the last 6 months.

It's snappy and quick and all the things I need work pretty much work flawlessly. Thanks for the amazing work Neo!

As Neo has mentioned that he might continue developing this ROM, I'd like to add some feedback concerning some bugs.

1. Random reboots. Most of the time, it occurs when I'm turning my screen on. It locks up and reloads the OS. Occasionally, it will do a fill reboot.

2. Sometimes, while on the lock scree, when sliding down the status bar to see my notifications, the status bar will disappear and reload. I used to get this on another ROM, but it used to say something about System UI crashing. It doesn't on this ROM.

3. I have it setup so pressing the volume keys does not wake the screen up, but it still does.

4. I have it setup so long pressing volume keys skips tracks when the screen is off, but it doesn't work correctly. It usually turns the screen on and lowers/raises the volume or skips tracks immediately (sometimes)

5. Music controls on the lockscreen is selected but don't always display.

I'm tempted to flash all the RUU's sequentially this weekend to see if it will solve the reboot issues. Can I flash RUU on Juopunut's patched HBOOT or do I need to flash the stock HBOOT before? If so, where do I find 2.27 or 2.28?
[HTC Rezound] jdmst71:
I get the same reboot when turning the screen on and don't get any other reboots besides this wakeup. Usually only happens once a day. This ROM is so awesome that I have decided to just live with it. Running the ruus that I had available did not help with the lockup when turning on the screen.
[HTC Rezound] cm0803o2:
exFAT

Hi,

I just got a new SD card, and I formatted it exFat, and the rom doesn't recognize it.

I just want to be able to put a file that is greater than 4G onto the SD card, so here are my choices:

1) use a different kernel

2) format the card to some other file system

I do need Windows to recognize it, so what are the possible solution? Thanks for your help.
[HTC Rezound] acejavelin:
Must be formatted in FAT32... Any other partition type won't work. Format the card in recovery or use a 3rd party format/partition tool like EaseUS Partition Manager, Paragon, OE something similar.

So basically you won't get a file over 4GB in a single file and have it recognized by your phone and Windows.

Now, if you had Linux... You might be able to hack the mount points and make the SD card ext3/4, but Windows would not recognize it.
[HTC Rezound] replica9000:
I know there is a couple programs that allows windows to read ext2/ext3 filesystems. I don't know they are read only, or how reliable they are. I've used my sdcard formatted with ext4, the permissions are a pain, as each app writes files as "-rw-------" with it's own UID/GID.
[HTC Rezound] acejavelin:
I believe there are also restrictions in Android that don't allow SD storage to be anything but FAT32, changing the file mounting may break other things, never tried. What are trying to do that requires a file that big on the phone, if you don't mind me asking... There may be other ways to handle this.
[HTC Rezound] cm0803o2:
Not exactly true, see here, specially post #5:

http://xdaforums.com/showthread.php?t=2456286

So anyone know of a Rezound kernel that support exFat?
[HTC Rezound] blazin_phattys:
Can I flash ruu's with the unlimited.io patched hboot or do I need the stock?

If I need the stock hboot, where can I find it?

Which ruu has the latest hboot and radios?

Sent from my Infected Rezound
[HTC Rezound] REV3NT3CH:
there is no ruu.exe for latest hboot and radios...only a zip file thats uploaded via bootloader....to ruu.exe you must be s-off and have a locked or relocked bootloader....the ruu's posted here dont work...i have all the files from first ruu to most recent ota with the hboot 2.28....pm if need be
[HTC Rezound] replica9000:
In my experience, it's not where the filesystem is mounted, but if it's automatically mounted at boot. If Android can't mount a fat32 sdcard automatically, it claims there is no sdcard. If it sees there is one with a filesystem other than fat32, it claims it's corrupted, and asks to format it. Some apps like camera or benchmarking apps will pickup on this and not work correctly. Also recovery does not see it either.

Some phones like the HTC One use the same partition for /data and the sdcard. It's ext4, and uses fuse to emulate the behavior of fat32 permissions. I wonder if this would be possible on the Rezound? Might need some options included with the kernel.
[HTC Rezound] acejavelin:
I believe my Nexus 4 does something similar to this as well, but I am not aware of way to do this on the Rezound currently, that is not to say of our developers couldn't do this, in fact I am sure they could, but it seems like a lot of work with little benefit for a specific situation... To me, logic says go back to why you need it, you said you need to put files over 4GB on the phone (to large for FAT32), but why and what are these files for, is there a better/different way to handle this?
[HTC Rezound] replica9000:
Well for me it wasn't so much the file size limit, it is the unreliability of fat32 that I don't like. I don't watch movies on my phone, so the file size limit hasn't bothered me.
[HTC Rezound] acejavelin:
Gotcha... getting posts mixed up a little, it was [MENTION=4452132]cm0803o2[/MENTION] that was asking about files larger than 4GB,

But do you not think that FAT32 native would be more reliable than a native linux file system emulating FAT32 in software? I guess I never thought FAT32 was unreliable, I have rarely ever had issues with it.
[HTC Rezound] replica9000:
I've had several bad experiences with FAT, I've also been dealing with it since DOS. I have had one card go corrupted on the Rezound once. FUSE is only emulating the permissions (or lack there of) of FAT32, not really the file system itself.
[HTC Rezound] scy1192:
do you still plan on updating this, Neo?
[HTC Rezound] Neo:
At some point yes