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

Root ACK! this round of updates were bad

Caeadas

Well-Known Member
So i tried installing rom and kernel stuff today...was on CT2.5, KK 1.3 unofficial, and EJ06

Backed up with titanium backup and clockwork mod and saved to comp.
Odin'd to FA19 with root and CWM, booted into home screen
Loaded recovery and formatted SD-EXT, then installed CT3.1.2, then KK 1.4
Rebooted into home screen and set up wifi and market access
Downloaded Titanium backup from market...

And there's where things went kooky. As soon as Titanium Backup started installing, the phone vibrated a short pulse, the a few seconds later a Force Close vibration with no box or notification. Phone locked up for a few seconds, then reloaded lockscreen and scan SD card, like it rebooted. Tried it a couple times, same thing. Restarted phone and tried, same thing.

Booted back into recovery and reinstalled CTmod 3.1.2, but didn't install KK on top of it again. Now titanium backup is installed, but i'm getting a FJ19 system update. Checked baseband and it says i already have FJ19.

What should my plan of attack be? Should I try tinkering with it, or reload my backup?
 
use root explorer or something like that and go to /system, find the build.prop and open it with text editor. you should see EJ06 on one of the first lines, change that to FA19 and reboot

that should stop the update notification
 
use root explorer or something like that and go to /system, find the build.prop and open it with text editor. you should see EJ06 on one of the first lines, change that to FA19 and reboot

that should stop the update notification

Just tried it, had to mount R/W to get it to stick, but the update is still there, mocking me. do i need to change any other instances of EJ06 in the build.prop?
 
I think that cured it, at least for the system updates. I saved the zip file on my comp if anyone's interested, the filename is cc2718d69f1d.update_SPH-M820_EJ06_to_FA19.

I'm going to let it go for the night and see what happens. Only thing i'm wondering now is what happened with koumakernel 1.4 that made it dislike installing stuff. I thought formatting SD-EXT would eliminate any issues. Now without the SD partition, i'm getting full on internal memory. I'm gonna uninstall some games for now.

Edit: Deleting the zip from the cache got rid of the update. I didn't change to blood's build.prop yet. If i needed to, what would be the best way to do so?

And whats wrong with titanium backup?
 
And whats wrong with titanium backup?

Well, you experienced one thing first hand. I don't like trying to use an app that lives in a sandbox to manipulate things outside of that sandbox. Especially when I can do all the same stuff with a couple CP and tar commands in a terminal
 
Edit: Deleting the zip from the cache got rid of the update. I didn't change to blood's build.prop yet. If i needed to, what would be the best way to do so?

you can just overwrite the old one, make the permissions rw-r--r-- and reboot
 
Well, you experienced one thing first hand. I don't like trying to use an app that lives in a sandbox to manipulate things outside of that sandbox. Especially when I can do all the same stuff with a couple CP and tar commands in a terminal

I never even got to run it, the phone flipped out before it installed fully. Anyways, I figured i would give KK1.4 another shot tonight, updated kernel and then reformatted SD-EXT afterwards (I think i formatted before install last time). Tried to install several other apps off market, like Angry Birds, Pandora, etc. Every one would lock up and force close, then reboot. It's not letting me install anything from market.

Anyways, back to CTmod's kernel, and i'm gonna try the build.prop since its popping up updates again. Edit: Bloodawn's Build.prop works fine
 
Back
Top Bottom