• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Nov-13 MeanROM ICS v6.3 | 2.13.651.1 | Mods | Batt saver | OC 1.7 Ghz

I don't know if mikey was just testing the OTA updater tonight or what but I got an OTA update from it that said it was updating from 3.0 to 3.0. I started to let it go just to see what happened but it looked like it was going to download all 600+mb and i didn't feel like waiting so I cancelled. It will be interesting to see what happens with 3.1.

I'll let it go as long as I know it's from him. Worth that can happen is a wipe and reflash.
 
I had the same thing. I didn't see the point in it.

I really don't see the advantage to this except to know there is an update. I can dl it a lot faster on my laptop a lot quicker.
 
Just saw this at XDA:


mikeyxda said:
PLEASE IGNORE TONIGHTS OTA UPDATE NOTIFICATIONS

You guys will get an OTA update message in your notifications from tonight. Just ignore it. I'm still working out the kinks in the OTA updater app and website entries. Turns out every time you touch anything on the website account, even changing the text ROM name (which should not be a key field), it sends an OTA update notice even though the ROM, MD5, ROM ID, and ROM Date never changed.

Looks like there's a bug in the OTA Updater app where they specify that "ROM version" should be "human readable ROM number/name" but if you use spaces, i.e. "MeanROM ICS 3.0", it causes the app to always say an update is available. So that's what is causing the app to proclaim that MeanROM ICS 3.0 is an update to MeanROM ICS 3.0 even though I filled out the info properly. As expected, this will take a couple rounds to get smooth but I'm confident that between their updates and my avoiding known potholes, it'll be a smooth update process by 3.1 or 3.2.

Mike
Click to expand...
 
I just flashed 3.0 and after like 2 hours my phone and text service crapped out completely. Tried wiping and that did nothing, updated the PRL and profile and nothing, even reflashed and nothing. I am about to nand back to 2.9 and see if that helps.

Anyone else had this issue?

edit: Nanding back has fixed the issue...I will keep an eye on it the rest of the day and maybe reflash 3.0 this weekend and see if it just was a weirdo glitch.
 
3.1 is now available already!

Changes:
Fixed OTA Updater issues incl. download problems and always reporting "update available"
Updated OC voltages for greater stability
New "sticky settings" (see post 3). Example: flash 1.7 Ghz OC once and your 1.7 Ghz setting survives through dirty flashes!
Minor fix for Google Now
Updated core apps: Google Maps, Google+, and Play Store
 
handler313 said:
I just flashed 3.0 and after like 2 hours my phone and text service crapped out completely. Tried wiping and that did nothing, updated the PRL and profile and nothing, even reflashed and nothing. I am about to nand back to 2.9 and see if that helps.

Anyone else had this issue?

edit: Nanding back has fixed the issue...I will keep an eye on it the rest of the day and maybe reflash 3.0 this weekend and see if it just was a weirdo glitch.
Click to expand...

AFAIK my text has been working ok but I did have an instance today where I called my phone twice and it didn't ring... I'll try 3.1 and see if it is any better but I may have to revert as well.

Of course I'll try a wipe/flash first.
 
ovrrdrive said:
AFAIK my text has been working ok but I did have an instance today where I called my phone twice and it didn't ring... I'll try 3.1 and see if it is any better but I may have to revert as well.

Of course I'll try a wipe/flash first.
Click to expand...

Now it is happening with 2.9 as well. Literally just started 5 minutes ago.

Basically what happens is texts time out (despite having full service) no matter who I send to. Calls to other people seem to work but if I call my vm it just ends the call.

Now it works again out of the blue. this is crazy I have never had this happen on a phone before.
 
I'm not sure if this is mean ROM related but my email is no longer in my auto-sync.. And I don't know how to add it.. When I tap ad it only prompts to add a new email account. Any way I can add things to auto-sync?
 
3vodroid said:
I'm not sure if this is mean ROM related but my email is no longer in my auto-sync.. And I don't know how to add it.. When I tap ad it only prompts to add a new email account. Any way I can add things to auto-sync?
Click to expand...

Try holding power for 10 seconds (same as battery pull) if it was ok before.

Could just be a stuck bit somewhere.
 
EarlyMon said:
Try holding power for 10 seconds (same as battery pull) if it was ok before.

Could just be a stuck bit somewhere.
Click to expand...

I'll give it a shot... Thanks! It was there when I was stock unrooted.. I think I'm gonna flash Viper ROM tonight and that out ill see if it's just this rom
 
Changelog:

3.2

Changes:
Overclock to 1.9 Ghz with new EvilZ kernel
New OC options to support EvilZ kernel
Much snappier performance and better battery
Updated core apps: SuperSU, DropBox, Facebook, TuneIn, Play Store, Google Play Music

3.1

Changes:
Fixed OTA Updater issues incl. download problems and always reporting "update available"
Updated OC voltages for greater stability
New "sticky settings" (see post 3). Example: flash 1.7 Ghz OC once and your 1.7 Ghz setting survives through dirty flashes!
Minor fix for Google Now
Updated core apps: Google Maps, Google+, and Play Store

Files updated:
\system\build.prop
\system\app\Maps.apk
\system\app\Velvet.apk
\system\app\Vending.apk
\system\etc\init.qcom.post_boot.sh
\data\app\com.google.android.apps.plus-1.apk
\sdcard\MeanROM-ICS\overclock-1701.zip
\sdcard\MeanROM-ICS\overclock-off.zip
\sdcard\MeanROM-ICS\overclock-1809.zip (removed)
 
Rxpert83 said:
Changelog:

3.2

Changes:
Overclock to 1.9 Ghz with new EvilZ kernel
New OC options to support EvilZ kernel
Much snappier performance and better battery
Updated core apps: SuperSU, DropBox, Facebook, TuneIn, Play Store, Google Play Music

3.1

Changes:
Fixed OTA Updater issues incl. download problems and always reporting "update available"
Updated OC voltages for greater stability
New "sticky settings" (see post 3). Example: flash 1.7 Ghz OC once and your 1.7 Ghz setting survives through dirty flashes!
Minor fix for Google Now
Updated core apps: Google Maps, Google+, and Play Store

Files updated:
\system\build.prop
\system\app\Maps.apk
\system\app\Velvet.apk
\system\app\Vending.apk
\system\etc\init.qcom.post_boot.sh
\data\app\com.google.android.apps.plus-1.apk
\sdcard\MeanROM-ICS\overclock-1701.zip
\sdcard\MeanROM-ICS\overclock-off.zip
\sdcard\MeanROM-ICS\overclock-1809.zip (removed)
Click to expand...


already an update?? that was fast!
 
3vodroid said:
already an update?? that was fast!
Click to expand...
Hes on version 3.2 and he goes in .1 increments. Hes already had 32 updates in the time the phone has been out. :D This rom gets updated like crazy


If you are on a ROM and it gets updated you can do whats called a "dirty flash" to update it. This involves wiping dalvik cache and cache and then flashing the ROM.

Doing so will save all of your data and everything you've set up.

This should have gone out via the OTA updater though so that shouldnt be a problem.





Also note this update includes a custom kernel. You may have to fastboot flash it
 
Recoil1 said:
Did a full wipe and tried to install the zip via TWRP and it failed the first time. I then re-downloaded the rom from the other sight to the computer then put it back on the phone. Wiped all the caches and re-installed but still got a failed install.
Click to expand...

Are you checking the md5 hash before you flash it?

I never used to do that until I got my first bad flash that took me almost an hour to get working again. Now I check it on the computer when I download a new rom, then after I transfer it to the phone sometimes I check it again to be sure. No bad flashes here anymore...

Also, are you running the latest version of twrp?

Are you s-off or just htc unlocked?

If just unlocked you may have to use fastboot as mentioned above to flash the kernal for this rom because it has a custom kernal...


On a side note, this new rom is really zippy but I don't like that it overclocks by default. On the e3d that was ok because it basically had an underclocked processor and meanrom just ran it at the design speed but this one is not the same. I flashed the stock speed zip and it didn't stick so finally I used super tuner to slow it back down to 1.51 which I'm sure killed his script. Personally I don't see any reason to overclock this phone. I'd rather have an amazing battery and save the overclock for when I get bored with the phone in a year or so to breathe new life into it.

I'll try a full wipe later and see if it works right then. Great rom though, I just don't like the forced oc.
 
I'm having some issues flashing MeanROM 3.2. When I try flashing it it gets stuck at "flashing Boot image". I am s-on, but I flashed the boot.img from the zip in fastboot. I've tried wiping everything after flashing the boot.img and not wiping everything afterwards with the same result. I had no issue flashing CM10 or MeanROM 3.1. Should I flash 3.1 then use the OTA updater instead?
 
windsorclarenc said:
I'm having some issues flashing MeanROM 3.2. When I try flashing it it gets stuck at "flashing Boot image". I am s-on, but I flashed the boot.img from the zip in fastboot. I've tried wiping everything after flashing the boot.img and not wiping everything afterwards with the same result. I had no issue flashing CM10 or MeanROM 3.1. Should I flash 3.1 then use the OTA updater instead?
Click to expand...

not sure if this is it but have you updated your firmware like it suggests in the op? you actually can't update using a ruu unfortunately, but you can use the file linked in the op.

LATEST FIRMWARE
The 1.22.651.3 update comes with a firmware upgrade that upgrades the radio, PRI, etc. When running MeanROM ICS v1.4 or higher, the new firmware is not required, but it is recommended. Since the ROM will run with or without the firmware, you can install the latest version of MeanROM ICS and then install the firmware, or install the firmware first, then the ROM: order doesn't matter! What does matter is whether you are s-on (HTC unlocked) or s-off (LazyPanda). If you do run into trouble flashing the ROM first, however, try flashing the firmware (or radio) first to see if that solves the issue. So here's what you do:

Option 1 (s-on HTC unlocked): While there are other firmware bits in the latest RUU, people who are s-on can only update the radio at this time. For the 1.22.651.3 RUU, this appears to be OK and taking the radio firmware and not the PRI and other firmware bits seems to have little or no down side. So to update your radio firmware if you are HTC unlocked (s-on), flash this filefrom recovery. Because you are HTC unlocked (s-on) it is flashed from recovery just as you'd flash a ROM (using "install" from TWRP). You do not load this from the bootloader!
Click to expand...
 
Rxpert83 said:
Hes on version 3.2 and he goes in .1 increments. Hes already had 32 updates in the time the phone has been out. :D This rom gets updated like crazy


If you are on a ROM and it gets updated you can do whats called a "dirty flash" to update it. This involves wiping dalvik cache and cache and then flashing the ROM.

Doing so will save all of your data and everything you've set up.

This should have gone out via the OTA updater though so that shouldnt be a problem.





Also note this update includes a custom kernel. You may have to fastboot flash it
Click to expand...

Would you suggest that I just go for s-off? Would that be easier?
 
3vodroid said:
Would you suggest that I just go for s-off? Would that be easier?
Click to expand...

If you have an H-boot that can obtain S-OFF, that is ultimately the best option to have.

If you are on H-boot 1.15 S-OFF is not an option because HTC patched the vulnerability needed to get S-OFF in the most recent OTA
 
Crap... I'm on hboot 1.15 :(... Back when I accepted that OTA I had no intentions on rooting. I'm running Viper right now and really digging it :D but who knows I might want to go back to meanROM and when I do it looks like I'll be learning how to flash the kernel through fastboot.. I can't wait till CM10 is stable and everything works.. Bc I will definitely be using that as my DD and I know I'll need to flash a custom kernel for that.
 
You must log in or register to reply here.
Back
Top Bottom