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

Root Weird...

K

Kaleb Randleaxe

Android Enthusiast
I'm running the previously "leaked" version of Android 2.2.1

Earlier today, I switched to Fission 2.5.7, and now I'm having a bunch of multimedia issues. Music players won't play my music files, Zedge ringtones won't work (anytime I click one I get a default ringtone which I suppose is put in place of corrupted tones), etc. etc.

Could this be the result of me being on 2.2.1?
 
Kaleb Randleaxe said:
I'm running the previously "leaked" version of Android 2.2.1

Earlier today, I switched to Fission 2.5.7, and now I'm having a bunch of multimedia issues. Music players won't play my music files, Zedge ringtones won't work (anytime I click one I get a default ringtone which I suppose is put in place of corrupted tones), etc. etc.

Could this be the result of me being on 2.2.1?
Click to expand...
try reboot? I just put gummy on a d2 yesterday and it was boot looping like crazy I pulled the battery and let it sit for 15 mins, problem solved. you never know try it.
 
You are on wrong kernel my friend. You need to upgrade your system. Sbf back to .15 and accept OTA update to
.340.
 
BuTbKa said:
You are on wrong kernel my friend. You need to upgrade your system. Sbf back to .15 and accept OTA update to
.340.
Click to expand...
I figured that was the issue, but, not being experienced with all of this ROM stuff, I didn't wanna attempt a fix of my own.

SBFing back to .15 will cause me to lose root, correct? And then, once on .340, I'll have to re-root/deodex and then apply the 2.5.7 Fission ROM?

EDIT: And just for clarification, what's the full number for the ".15" I have to SBF back to? 2.2.15?
 
So put 2.3.315 on my SD, boot into recovery and apply.

Manually search for OTA, apply update.

Then flash to Fission as normal?


EDIT: Scratch that. Google-fu kicked in, SBFing to .15 now.
 
Thank ya. Got a boot loop when trying to SBF to 2.3.15. Gonna try it again.

EDIT: Damn, still boot looping. :[ Dunno what to do now.

EDIT2: Ha, I remembered what I did last time I got a bootloop. Booted into clockwork and wiped data, now it's booted up. Doing *228, then gonna see if I can get pushed to the OTA.

EDIT3: Programming unsuccessful. Bleh. Maybe I can get the OTA over WiFi.
 
"System Updates" is blacked out (unclickable), and the phone won't program. Aye aye aye.

EDIT: Phone somehow popped up with the OTA even though I wasn't activated. Downloaded it but it got to 99% and then just... disappeared? So. Downloading the 2.3.340 .zip from TBH to manually update it. Hope that by recording these steps, I can help somebody else out if they run into these problems.
 
.340 is just system only .sbf. It wont upgrade your radio and kernel. If you search here I started thread with directions on how to install Octavio update manually. I would post link, but im on phone.
 
If you're still having problems, the .320 SBF and .340 system SBF files can be found here. Also, you don't have to deodex if you're installing a ROM.
 
I ended up resolving the issue last night (I just stopped posting 'cause it was like 4AM). I downloaded the .340 update.zip from Team Black Hat and manually updated to it. After that, my phone was able to activate and run normally. I then downloaded Fission Rom Manager and flashed to Fission 2.5.7, where I wanted to be all along.

Thanks for all the help. Cheers. (:
 
You must log in or register to reply here.
Back
Top Bottom