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

Root [ROM][WIP]Triump 2.2.2 Alpha From Source

BSydz

Android Expert
OK guys, This is completely built from scratch and a whole lot of stuff doesn't work. This the first build that I got to boot. I have to work out some issues, but figured I'd post it. I did not replace any files, just added all the missing files from the Stock ROM and used the stock kernel for know. So everything from the build is intact. A lot of work needs to be done, I figure some of you guys out there may be able to tinker with some of the stuff from the Stock ROM to see if anything works. Any way for now take it as nothing works, as i have not tested very much at all. Phone seems to work, but haven't tested data cause my dev phone is not activated. There are a couple force closes at boot but nothing continuous, mostly apps from Stock ROM. This is rooted and includes busybox.

Working:
Display
Touchscreen
Ril
Dunno what else, but if it is not listed it probably doesn't work.

Not Working:
Wifi
Bluetooth
Camera
USB SD mount

BSydz-Triump-2.2.2-Alpha_1-From-Source.zip


Let me know what you guys find, I'm sure a few files from the Stock ROM can fix some stuff, but haven't had a chance to test them out. Next on the list GB, then ICS, and continue work on JB. SCREW Motorola, I'll just do it myself. :D That should be in my sig. :D
 
OK guys, This is completely built from scratch and a whole lot of stuff doesn't work. This the first build that I got to boot. I have to work out some issues, but figured I'd post it. I did not replace any files, just added all the missing files from the Stock ROM and used the stock kernel for know. So everything from the build is intact. A lot of work needs to be done, I figure some of you guys out there may be able to tinker with some of the stuff from the Stock ROM to see if anything works. Any way for now take it as nothing works, as i have not tested very much at all. Phone seems to work, but haven't tested data cause my dev phone is not activated. There are a couple force closes at boot but nothing continuous, mostly apps from Stock ROM. This is rooted and includes busybox.

Working:
Display
Touchscreen
Ril
Dunno what else, but if it is not listed it probably doesn't work.

Not Working:
Wifi
Bluetooth
Camera
USB SD mount

BSydz-Triump-2.2.2-Alpha_1-From-Source.zip


Let me know what you guys find, I'm sure a few files from the Stock ROM can fix some stuff, but haven't had a chance to test them out. Next on the list GB, then ICS, and continue work on JB. SCREW Motorola, I'll just do it myself. :D That should be in my sig. :D

Crap! I haven't even been able to get CM6 to work. Now I feel like it can be done with the information out there.

Thank you, you have restored my resolve.
 
So is this like an attempt to create our own source in order to fix upper level roms?

jjonh,

To get used to the MSM/QSD Android Enablement Project I beleive BSydz started with Froyo, then Gingerbread and then Ice Cream Sandwich and finally Jelly Bean. Since the code, device files and building procedures are much different than CyanogenMod this is a whole new animal. This is simply Google AOSP but deigned specifically for the Qualcomm Hardware written by all the Qualcomm Developers released as open source.
 
So is this like an attempt to create our own source in order to fix upper level roms?

jjonh,

To get used to the MSM/QSD Android Enablement Project I beleive BSydz started with Froyo, then Gingerbread and then Ice Cream Sandwich and finally Jelly Bean. Since the code, device files and building procedures are much different than CyanogenMod this is a whole new animal. This is simply Google AOSP but deigned specifically for the Qualcomm Hardware written by all the Qualcomm Developers released as open source.
Yes, this is from source acquired through Code Aurora, I tried regular AOSP but before I worked out all the errors the CAF source finished coming in and I switch to that. Once I had JB booting, I got curious about the source that Moto did release. It didn't just work by any means, but after fighting with it for a while, I got it to build and then after some tinkering, I got it to boot, and that's where I am now. G60 you are right, it is a whole nother animal all together. So I am just getting to know, the differences in the setups between this and the CM ROMs.

Thanks for the kind words guys! Gotta get ready for work. :D
 
Another icecream? ugh I am confused. Can you take a shotscreen and post it here? I would like to see the design. please :)
 
Another icecream? ugh I am confused. Can you take a shotscreen and post it here? I would like to see the design. please :)
I gotta go but, it is the google android naming sceme, 2.1 eclair, 2.2 frozen yogurt(froyo), 2.3 gingerbread(GB), 3. for tablets only, 4.0 Ice cream sandwich (ICS), and 4.1 jellybean (JB). This is Froyo.
 
I gotta go but, it is the google android naming sceme, 2.1 eclair, 2.2 frozen yogurt(froyo), 2.3 gingerbread(GB), 3. for tablets only, 4.0 Ice cream sandwich (ICS), and 4.1 jellybean (JB). This is Froyo.

1.5. Cupcake. Added video recording and on screen keyboard to android. G1 days.
3. Honeycomb. It's an os that was put on forgotten tech like the xoom and the Logitech revue. Never open sourced.
 
Got a lot of spare time on your hands guys? ;)

Not really free time, but based on constant learning and growing as a team I think MTDEV is understanding more and more about Android and the marriage with the Triumph. I mean if you look at CM9 WIP thread, that thread is not even a month old yet and I have completely revamped CM9 from ground up to work specifically with the Triumph. If I can knock out the Camera, Wifi Tether, USB Tether and HDMI that will be the first complete ROM we have for our phone BSydz Froyo :) (had to do a play on words LOL).

Anyways there is nothing from stopping MTDEV at this point, not even the lack of source code any more. Since Dorregaray has been working with me on the Camera I have learned so much more about the source code, and also how to tear apart proprietary library files. Since I have learned so much on that front I am hoping I can do the same with the HDMI and make the proper calls in the source code to resolve it. I will also be posting everything I learned so everyone no matter what phone can learn from our trials and tribulations with the Triumph.

For those of you that have stayed true and waited patiently with our beloved Triumph and not jumped ship, good times are a coming!!!
 
Ah sounds cool guys....you remind me of cobani yoghurt hmmmm I am eating pineapple flavor! delicious and later turkey sandwich! :D
 
If we know, what file Moto changed from the source, does it mean that we (by we I mean you and MTDEV, of course) can build 2.3 from the source? or 4.0? Or even Jelly bean?
All we need is get AOSP (or in this case aurora) and adapt it to Triumph?
 
If we know, what file Moto changed from the source, does it mean that we (by we I mean you and MTDEV, of course) can build 2.3 from the source? or 4.0? Or even Jelly bean?
All we need is get AOSP (or in this case aurora) and adapt it to Triumph?

Since MTDEV is just starting out with CAF (Code Aurora) and just learning about tearing apart library files I do believe we can get all version of CAF (froyo, gb, ics, jb, etc) to work for our phone as long as they release the source code for the msm7630 we will always be able to build the code. It will of course not be an quick project but the fact we are learning the source it will just take a mater of time before we get through each version.
 
Look at it this way G60!! In one corner, the stock Triumph that Motorola /VM whitewashed us with. In the other corner look what you and MTDEV have given us. You guys are like pitbulls. You guys go for the jugular and don't let go. So you are right You will GRAND SLAM all of the CAF versions right out of the ballpark!!:boxing:
 
I believe in all you guys at mtdev...only thing I worry about is the amount of memory the newer os versions use...like if its so hard to get ics mem parameters in line how bad will jelly bean be and even beyond that...I think ics will be one of the last updates that will be portable to the triumph...jelly bean is probably iffy at best...could be wrong though
 
Bsydz,

You are the fraking Triumph master. Do you plan on setting up a repository with the fixes you have applied?
Thanks, I have been working to get a device folder setup, separate from the 7630_surf folder. I just got it to build a lil while ago from the triumph folder, about to test it out right now. Once I get it situated, and apparently fix some stuff now, as some functionality was lost after the switch, I'll post it to my github.

And anybody who wants to pull the source this is what I used to pull it in.
Code:
$ repo init -u git://codeaurora.org/platform/manifest.git -b  froyo_pumpkin  -m M7630AABBQMLZA203030.xml
$ repo sync -j4
I use -j16 but it all depends on your machine, I suggest -j4 as it should work for anybody.

Take the packages from
Triumph WX435 - Browse /WX435/CAYM_D_0_1010_2039_BP_2037_CDA_1024 at SourceForge.net
and integrate them in to the corresponding folders. Like build_2_038.tar.tgz is /build and system_core_2_038.tar.tgz is /system/core. Replace the kernel folder and set the defconfig to FB400_defconfig or use the stock prebuilt kernel. You will still have to put the stock boot.img but the source reads from the kernel I believe. I started with the 7630_surf folder and made a vendorsetup.sh in the msm7630_surf folder with
Code:
add_lunch_combo msm7630_surf-eng
and started adding things to the configs in the msm7630_surf folder.

If any body has questions feel free to ask. I'll try to get as much info out there as I can, I'm still trying to understand some of the code myself.
 
Also if anyone needs any of the stock source files for Motorola they are also here

http://mtdev.us/moto/

There is also a stock folder which has the stock boot.img ripped open to see all the base settings that where applied like rc files and such.
 
Back
Top Bottom