[FINAL] OMJ's HTC EVO 2.2 Custom ROM v4.6 | FroYo 3.70.651.1 | *Updated 3/29/11*

[tech-9]

HEY OMJ GREAT JOB YOUR ROM LOOKS AWESOME!!!! ONE THING IS I CAN'T SEEMED TO DOWNLOAD IT!!! NONE OF THESE LINKS WORK!!! PLEASE CHECK INTO THIS OR IF SOMEONE HAS A WORKING LINK PLEASE POST IT!!! THANKS

[iknowsquat]

Originally Posted by tech-9

HEY OMJ GREAT JOB YOUR ROM LOOKS AWESOME!!!! ONE THING IS I CAN'T SEEMED TO DOWNLOAD IT!!! NONE OF THESE LINKS WORK!!! PLEASE CHECK INTO THIS OR IF SOMEONE HAS A WORKING LINK PLEASE POST IT!!! THANKS

[Pushes Play on his tape recorder]
If you are getting lots of code when you click the link then right click on it and select Save As.

[That0neUser]

Originally Posted by iknowsquat

adb remount

will make /system read-write.
It wont "stick" so it will revert back to Read only by itself. I'm not 100% on what reverts it back but I know adb remount is not permanent.

adb remount works fine when the phone is all booted up, however after flashing I get a one-way ticket to Bootloop City if I replace framework-res.apk.

If I try adb remount in recovery I get "remount failed: Invalid argument"

If I simply do adb push to replace framework-res.apk it loooooks like it works, but after booting up the phone and doing adb pull, it's still the old file...nothing is updated. I'm assuming this is because /system wasn't mounted when I tried to push.

I'm too much of a n00b to figure out how to resolve this, even after a couple hours on Google.

I did figure out a quick-fix, which is making a flashable update.zip, but I'd like to know how to do this using ADB for future reference.

[iknowsquat]

Originally Posted by That0neUser

adb remount works fine when the phone is all booted up, however after flashing I get a one-way ticket to Bootloop City if I replace framework-res.apk.

If I try adb remount in recovery I get "remount failed: Invalid argument"

If I simply do adb push to replace framework-res.apk it loooooks like it works, but after booting up the phone and doing adb pull, it's still the old file...nothing is updated. I'm assuming this is because /system wasn't mounted when I tried to push.

I'm too much of a n00b to figure out how to resolve this, even after a couple hours on Google.

I did figure out a quick-fix, which is making a flashable update.zip, but I'd like to know how to do this using ADB for future reference.

Sorry, missed the recovery part. The mount code from recovery is different:
adb shell
mount /dev/block/mtdblock4 /system

I'm no adb pro but I'm 99% on that mount code.

[Riley]

Originally Posted by iknowsquat

[Pushes Play on his tape recorder]
If you are getting lots of code when you click the link then right click on it and select Save As.

lol, now that's funny. its the little things that make me laugh

[Sauske]

Does OMJ make a senseless version of the rom?

[iknowsquat]

Originally Posted by Sauske

Does OMJ make a senseless version of the rom?

Nope.
And I wouldnt hold your breath waiting for one
He has said repeatedly that he's a Sense guy and currently has no plans for Senseless.

[Sauske]

Originally Posted by iknowsquat

Nope.
And I wouldnt hold your breath waiting for one
He has said repeatedly that he's a Sense guy and currently has no plans for Senseless.

Thanks for the update didn't know that! I was trying to run snes emulator but it wouldn't work! long story short I need a senseless rom, but no big deal!

[Hawaii Tom]

Cyanogen is one that says he will never add Sense, so try his ROM, up to v.6 now.

[Sauske]

Originally Posted by Hawaii Tom

Cyanogen is one that says he will never add Sense, so try his ROM, up to v.6 now.

Thanks, I have to read more but if I'm not mistaking his version doesn't have wimax and somthing else that was important to me that I deemed not worth the rom...but ill recheck!