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

Root [ROM][ALPHA] Triumph CM9 v0.6.17.0 [FINAL]

OGWillikers said:
I downloaded the latest release 3 times. Same result each time. If this doesn't work, I'm going back to stock and going to sleep. Work in 6 hours, wooo.
Click to expand...

Hey OG, just to let you know you're not the only one having that problem. Although I didn't test it as extensively as you have, I deleted /system and the cache before attempting to update from .6.5 to .6.10.3 and I got the same error. I've got some ideas on what they might be. I'll let you know if I've found anything.

Edit: don't you love it when the first crack pot idea you come up with works? Okay, so basically I was able to get .6.10.3 to install by first wiping /system and the cache, then installing .6.5, then booting, the rebooting back to recovery and deleting cache again, then installing .6.10.3

I'm guessing it's not necessary to boot .6.5 and deleting the cache again but I wanted to leave it there in case I'm wrong. Basically, what I think the problem is is .6.10.3 is missing some critical file that causes it to boot loop if you don't upgrade from a previous version well living /system in tact. An actual dev might want to take a look into that.

Hope that helps!
 
hydrowolfy said:
Hey OG, just to let you know you're not the only one having that problem. Although I didn't test it as extensively as you have, I deleted /system and the cache before attempting to update from .6.5 to .6.10.3 and I got the same error. I've got some ideas on what they might be. I'll let you know if I've found anything.

Edit: don't you love it when the first crack pot idea you come up with works? Okay, so basically I was able to get .6.10.3 to install by first wiping /system and the cache, then installing .6.5, then booting, the rebooting back to recovery and deleting cache again, then installing .6.10.3

I'm guessing it's not necessary to boot .6.5 and deleting the cache again but I wanted to leave it there in case I'm wrong. Basically, what I think the problem is is .6.10.3 is missing some critical file that causes it to boot loop if you don't upgrade from a previous version well living /system in tact. An actual dev might want to take a look into that.

Hope that helps!
Click to expand...

I am going to give this a try also (use older nanobackup), the last 2 versions will not boot, stays stuck on boot logo. 6.10.3 has been downloaded 6 times md5 matched on all 6. All my installs are clean installs.
 
hydrowolfy said:
Hey OG, just to let you know you're not the only one having that problem. Although I didn't test it as extensively as you have, I deleted /system and the cache before attempting to update from .6.5 to .6.10.3 and I got the same error. I've got some ideas on what they might be. I'll let you know if I've found anything.

Edit: don't you love it when the first crack pot idea you come up with works? Okay, so basically I was able to get .6.10.3 to install by first wiping /system and the cache, then installing .6.5, then booting, the rebooting back to recovery and deleting cache again, then installing .6.10.3

I'm guessing it's not necessary to boot .6.5 and deleting the cache again but I wanted to leave it there in case I'm wrong. Basically, what I think the problem is is .6.10.3 is missing some critical file that causes it to boot loop if you don't upgrade from a previous version well living /system in tact. An actual dev might want to take a look into that.

Hope that helps!
Click to expand...


I'm glad that your "crackpot idea" worked, although I'm not sure of the reasoning as I am on the latest build and I always wipe absolutely everything before I update.
 
clintkev251 said:
I'm glad that your "crackpot idea" worked, although I'm not sure of the reasoning as I am on the latest build and I always wipe absolutely everything before I update.
Click to expand...

Well, that "crackpot idea" idea worked.
Thankshydrowolfy

I thought it was my build itself that was screwed up (last 2 versions), but then I downloaded from the first page here instead of building it and the same thing, couldn't get out of boot logo, downloaded many times and reinstalled just in case zip was corrupted, bad download, etc. gave up. Installing over previous build works fine.
 
wifi + bt working great with onlive 10.2 build alittle choppy at times but ill try that with a different Internet connection thanks mantera :3
 
Just wanted to confirm that I had the same problem that some people are having with the forever Motorola logo after flashing 0.6.10.3. I came from CM7 so I wiped everything (system, data, cache, and dalvik cache) then flashed the ROM and gapps. It also wouldn't boot into recovery for about 5 minutes afterwards (unrelated, but still scared me lol).
 
death2twitter said:
Just wanted to confirm that I had the same problem that some people are having with the forever Motorola logo after flashing 0.6.10.3. I came from CM7 so I wiped everything (system, data, cache, and dalvik cache) then flashed the ROM and gapps. It also wouldn't boot into recovery for about 5 minutes afterwards (unrelated, but still scared me lol).
Click to expand...


Try flashing an earlier version then flashing .6.10.3. I used .6.5
 
Interesting... It seems that my happiness rises and falls at the exact same rate that this thread rises and falls in the root forum...

EDIT: Hey look at that! I'm happy again!
 
garrmack said:
Interesting... It seems that my happiness rises and falls at the exact same rate that this thread rises and falls in the root forum...

EDIT: Hey look at that! I'm happy again!
Click to expand...

LOL.

And look! We need less than 2600 more views to break 100k. Come on people!! get to work and view this. :D
 
Hey mantera what did you all do to stop the phone fc's when you all was first buliding CM9 and do you think it would work on MIUIv4?
 
oldmanstatic said:
Hey mantera what did you all do to stop the phone fc's when you all was first buliding CM9 and do you think it would work on MIUIv4?
Click to expand...

The phone FC's stopped when we got the RIL working. So if you got the radio working and have service, then I would expect that the phone would not be fc'ing unless there was something else wrong.
 
mantera said:
The phone FC's stopped when we got the RIL working. So if you got the radio working and have service, then I would expect that the phone would not be fc'ing unless there was something else wrong.
Click to expand...

If you don't mind typing it how did you all get the ril working? I know yumbrad had to edit some files. Since MIUIv4 is based of CM9 shouldn't it have service or its something special to have to edit in MIUI to get the ril working?
 
oldmanstatic said:
If you don't mind typing it how did you all get the ril working? I know yumbrad had to edit some files. Since MIUIv4 is based of CM9 shouldn't it have service or its something special to have to edit in MIUI to get the ril working?
Click to expand...

The main commits, iirc, are these:

https://github.com/mantera/android_...mmit/56014becc1a2405bd25bd12ca3ed6581358121cb

https://github.com/mantera/android_...mmit/5ce53b9ddd1cc4b48c5b3ccd18d2641867cf822a

https://github.com/mantera/android_frameworks_base/commit/c36a4bd43ac205acb7de990558b2e89b22404365

You have to edit the frameworks files to get it to work on the VM cdma network.
 
mantera said:
Those fixes are in our local cm9. I have no idea which cm9 files that the MIUI files are based on.
Click to expand...

Yea they are based of the you made the other devs made I just toke a look those files and they are the same. Could the MIUI be different from CM9 settings?
 
mantera said:
It's possible. I don't think MIUI 4 is directly based off cm9 anymore like the old MIUI was directly based off of cm7.
Click to expand...

It is. I based my whole ROM off of yours. Only thing I needed to edit was the frameworks, apps, and media folder. Since I edited the frameworks folder that makes me believe it lies in there. I've tried replacing the CDMA folders located in /android/telephony/cdma with CM9 and the ones in /com/internal/telephony/cdma also. This seemed to fix it for the Optimus V, but to no avail on the Triumph.
 
gannon5197 said:
It is. I based my whole ROM off of yours. Only thing I needed to edit was the frameworks, apps, and media folder. Since I edited the frameworks folder that makes me believe it lies in there. I've tried replacing the CDMA folders located in /android/telephony/cdma with CM9 and the ones in /com/internal/telephony/cdma also. This seemed to fix it for the Optimus V, but to no avail on the Triumph.
Click to expand...

It sounds like you guys are going to have to do some smali editing instead of wholesale replacements.
 
mantera said:
It sounds like you guys are going to have to do some smali editing instead of wholesale replacements.
Click to expand...

Sounds like a lot of fun :) lol
If it's too much for me then I'll hand it off to another willing dev. I just can't make these kind of edits without testing them. Thataway I'm not uploading every 5 seconds for a test.
 
Posted this in the ICS development forum as well

https://developer.qualcomm.com/develop/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources
 
You must log in or register to reply here.
Back
Top Bottom