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

Root JagerRom 1.7.3 Released

Jager & Hydra FTMFW!!! This phone feels like it is running extremely fast with 1.7.3 and ocuv version 7 kernel, compared to 1.6.2 with whatever kernel it had...I know it was another ejhart, but not sure which one.

Sent from my ADR6300 using Tapatalk
 
Who is that in your avatar btw? To me, it looks like a zombiefied version of the singer, Prince. :D

i guess you didn't watch chappelle show. well anyways thats from the episode where charlie murphy told a story about a time that he went to princes house and of course dave chappelle plays prince in the reenactment.
 
Seems like I am having an issue with SU priveleges. When I ran adfree and quickboot for the first time I had a freeze and automatic reboot. It didn't happen with Titanium or Shootme though....... IDK
 
i guess you didn't watch chappelle show. well anyways thats from the episode where charlie murphy told a story about a time that he went to princes house and of course dave chappelle plays prince in the reenactment.

great episode btw.


This rom makes me feel like finally rooting, but I've been so patient I almost feel like I should just wait for a froyo release.
 
great episode btw.


This rom makes me feel like finally rooting, but I've been so patient I almost feel like I should just wait for a froyo release.

yea that episode and the rick james one.



i felt the same way about if i should flash a rom or just wait until froyo. but now i've got the stock rom backed up with everything the way i like it and the jagerrom 1.7.3 how i like it. so now i can just switch back and forth without having to set anything up again.
 
do you really need to do all that, can't you just mount system and push them into system/app?

like this adb push mms.apk /system/app then adb reboot

so i'm not sure where i'm going wrong. I'm in adb shell and have tried both:

adb push mms.apk /system/app
and
adb push /sdcard/mms.apk /system/app

and get a not found error every time.

when i try:

cp /sdcard/mms.apk /system/app

i get a read-only file system error.

what am i doing wrong?
 
so i'm not sure where i'm going wrong. I'm in adb shell and have tried both:

adb push mms.apk /system/app
and
adb push /sdcard/mms.apk /system/app

and get a not found error every time.

when i try:

cp /sdcard/mms.apk /system/app

i get a read-only file system error.

what am i doing wrong?

Is your phone rooted?

Did you boot your phone into recovery mode (just download the app, quickboot, and use that to boot into recovery)?

Once you have booted into recovery mode, did you go into "partitions" and make sure that system and sdcard are mounted?

When you run adb shell, do you get the # prompt?

When I pulled Mms.apk out of the tar posted to this thread, it was named, "Mms.apk" with a capital M. Some or all of the commands you are running may be case sensitive (although I'd think you'd get an error if that was the problem you were having).
 
thanks! i wasn't in recovery. that is what was causing problems.

i couldn't get quickboot to work. it brings up su but just a blank screen that locks my phone. no option to allow. i had to long-press the power to reboot the phone. i ended up just running an adb reboot recovery to get to recovery.
 
hmmm... copied both mms files but still get an error message when i try to send an mms (something about process fail).

perhaps the permissions DO need to be changed?

i'm new to adb lingo though... do you need the full path or anything like that to run a chmod, or once the files are in the system/apps/ dir you you just run a chmod from the # ??
 
SU is working good for me now. The issue I had was just on the first run of only 2 of my SU programs, and since then it has been fine.

when I launch anything that needs SU permissions the screen just goes black and then about 30 seconds later a box pops up that says

"Activity SU Request (in application Superuser Permissons) is not responding."

I can force close or wait


:[
 
hmmm... copied both mms files but still get an error message when i try to send an mms (something about process fail).

perhaps the permissions DO need to be changed?

i'm new to adb lingo though... do you need the full path or anything like that to run a chmod, or once the files are in the system/apps/ dir you you just run a chmod from the # ??

This:

chmod 644 /system/app/Mms.apk
chmod 644 /system/app/Mms.odex

Will work from anywhere. Just adb shell and type these commands from the # shell. Doesn't matter what directory you are in.

If you're not sure if you need to type the path to a command like "chmod", type "which chmod" from the # prompt. That command will return the full path to the chmod command that will be run if you just type "chmod". If the which command doesn't return anything, then that means that the directory that the chmod command is in is not in your path (and you either have to add that directory to your path or type the full path when you run the command).

I'll be surprised if changing the perms on the Mms files fixes your problems. I did it just because 777 is generally bad and also because I wanted my files to have the same perms as the rest of the files in that directory (anal like that). Can't hurt to try though.

What are the sizes of your Mms files?

ls -ila /system/app/Mms*

What does that return?

Did you grab the Mms files from the tar that was posted to this thread? When I first tried this, I (stupidly) tried the Mms file posted to the guide to doing something like this on the moto droid. It was much smaller and didn't work.

I never got an error when I tried to send photos via sms, I just got a spinning clock. Anybody else try to send photos before putting the Mms.apk into /system/app? If so, what did you get when you'd try to send photos?
 
so i'm not sure where i'm going wrong. I'm in adb shell and have tried both:

adb push mms.apk /system/app
and
adb push /sdcard/mms.apk /system/app

and get a not found error every time.

when i try:

cp /sdcard/mms.apk /system/app

i get a read-only file system error.

what am i doing wrong?

before doing anything copy and past Mms.apk and Mms.odex to the root of your sdk/tools folder.

this is exactly what i did and it worked great for me: in the command prompt navigate to the tools folder of your sdk folder that is located on the root of your c drive just like you did when rooting. once there plug in phone and boot into recovery, go into partitions menu and mount system. after you have done this type this in the command line:

adb push Mms.apk /system/app

adb push Mms.odex /system/app

after running this first command it will first say something about daemon started successfully.

then last: adb reboot

that should be it.
 
Is it possible to request the Jager dev to adjust the optical trackpad so that the movement to scroll through home screens is reversed?

i.e., right now you need to scroll left to GO left. You scroll in the direction you want to go. I'd like to see the trackpad register scrolling like you would scroll a browser window: "turning" the page (movement opposite desired scrolled direction).

Is that possible?
 
before doing anything copy and past Mms.apk and Mms.odex to the root of your sdk/tools folder.

this is exactly what i did and it worked great for me: in the command prompt navigate to the tools folder of your sdk folder that is located on the root of your c drive just like you did when rooting. once there plug in phone and boot into recovery, go into partitions menu and mount system. after you have done this type this in the command line:

adb push Mms.apk /system/app

adb push Mms.odex /system/app

after running this first command it will first say something about daemon started successfully.

then last: adb reboot

that should be it.

thanks for the instructions. i followed exactly and all worked well... however, after reboot, i get the following when trying to send a message:

Sorry! The application Messages (process com.android.mms) has stopped unexpectedly. Please try again.

here's the listing of the two files:

C:\sdk\tools>adb shell
~ # ls -ila /system/app/Mms*
ls -ila /system/app/Mms*
1296 -rw-rw-rw- 1 root root 902253 Jun 20 02:22 /system/app/Mms.apk
1308 -rw-rw-rw- 1 root root 1156144 Jun 20 02:22 /system/app/Mms.odex

any ideas?
 
thanks for the instructions. i followed exactly and all worked well... however, after reboot, i get the following when trying to send a message:



here's the listing of the two files:



any ideas?

i would try restarting phone then try to send message again. if that doesn't work uninstall and reinstall mms. that usually fixes force close problems for me.
 
Back
Top Bottom