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

Root [Discussion - Developers _ONLY_] Building ICS from source (Isaac's github).

ziggy46 said:
yup i got it to boot... did you do a full wipe? and try redownloading the zip? :confused:


and yep it says "virgin mobile" then wierd characters. sorry about the horrible picture quality.
Click to expand...

I haven't tried downloading it again... well I did but my bandwidth was being sucked down so it would take hours instead of minutes so I'll try again in a bit... And that's kinda weird and cool that it seems to be connecting to the VM network... Although then again so was the Andro-ID although it didn't say it...

Edit: Now in CMW it says
Code: 
Random offset: 0x25c
... And it still gets stuck at the boot screen... :/
 
Does anyone know if the clock table is the default for the triumph? My phone is an oddball phone and won't boot if there are changes with the clocking table... :/ That would also explain why it won't boot...
 
ziggy46 said:
it shouldnt matter...
Click to expand...

Well there's something that's stopping it from booting on my phone :'( and if this won't even boot if there is a rom based off this chances are that it won't boot either... And I've had problems with kernals that aren't set to boot off default values make my phone not boot... Plus that's the only thing that I could think of as to why it won't boot.
 
You have to compile a kernel that uses the bi041p_ts.c driver for the MT (not the bu21018mwv for the Ideos X6). I'm guessing this is what Isaac did a while back to get the MT touchscreen working.

Also in GB and before, I believe the OS expects just a:

input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 255);

for a touch, and release is:

input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 0);

But for ICS, it expects more:

input_report_abs(bi041p.input, ABS_PRESSURE, 255);
input_report_key(bi041p.input, BTN_TOUCH, 1);

for touch on, and:

input_report_abs(bi041p.input, ABS_PRESSURE, 0);
input_report_key(bi041p.input, BTN_TOUCH, 0);

for touch off (according to TJ's changes in the xda thread posted). I was just in the driver code recently so this is making sense to me at least. But how to get this driver included in the ICS kernel is a different matter.
 
lifeblows10 said:
I know for a fact that is what he did. (Edit: Found it; https://gist.github.com/1328331/239f7b6a6fa1dd4e3d4c230891c7d77f8d41d474)

So... who wants to compile the kernel? Anyone?
Click to expand...

Progmanos already compiled an ICS kernel for the MT a few pages back:

http://androidforums.com/triumph-al...-ics-source-isaacs-github-18.html#post3764093

Try copying that zImage and replace it as your:

~/android/system/device/motorola/triumph/kernel

and recompile ROM, or just copy that boot.img into a kernel flashable zip.
 
progmanos said:
The ROM no longer gets stuck on the boot logo. It now boots to a black screen. However, I am unable to connect adb to it.
Click to expand...

Well shoot. You tried at least. :)

I just can't understand how we went from having a boot-able build to not having one. (Ok, I know why, I just don't want to understand it.)

Once I get my computer back up and running, I will attempt to build a kernel with the touch driver fixes. (In theory.)
 
progmanos said:
The ROM no longer gets stuck on the boot logo. It now boots to a black screen. However, I am unable to connect adb to it.
Click to expand...

I've never even been able to get it to boot... Well except when I put a cm7 kernel in it then it just booted to black screen and I could connect ADB to it... But what can I expect...
 
Here's a thought/idea...
What if we take the IDC file from a copy of Issac's build, and then build a new kernel with the right touchscreen driver?
 
austrie said:
Use edowar's github to find the kernel source he is using and switch the touchscreen driver file with ikarosdev's ICS touchscreen driver file, found on his github. Then compile the kernel with the new touchscreen driver file, then decompile the boot.img from this ROM and swap the zimage with yours; when you're all done with that, put the boot.img back in the ROM zip and flash it. By good chance it should work if you switched the right files. Though you will have to spend more time on ikarosdev's github since his github is more crowded; when you find the touch screen driver file, make sure you're on his ICS branch.
Click to expand...

Maybe this will work... This is what austrie posted for people with variants in the ideos x6 forum... IDK if that's what you guys already did but if not maybe this will work...
 
marc12868 said:
Maybe this will work... This is what austrie posted for people with variants in the ideos x6 forum... IDK if that's what you guys already did but if not maybe this will work...
Click to expand...

I wish he would have posted that on here! I'll go thank him on XDA. This is the plan of action I will take.
 
lifeblows10 said:
I wish he would have posted that on here! I'll go thank him on XDA. This is the plan of action I will take.
Click to expand...
]

Wish I had Linux to do this!~! If anybody DOES do this, I will donate from next check for touchscreen drivers...My buddy, who is afraid to root, will poop pants when he sees ICS!!
Thank you to ALL who helped!!!!

:D:D:D:D:D:D:D:D:D
 
You must log in or register to reply here.
Back
Top Bottom