Correct me if I'm wrong but I read the most important compatibility aspects for porting from one device to another are processor compatibility and screen resolution. The specs for the HTC One Mini are almost perfect. Exact same processor and the screen resolution is almost identitical. There's an officially supported cyanogen release for that device. It would seem to me we could compile that build, using JMZs custom kernel were all using for the 610, and pull the drivers from our device, and that might be enough to do it.
I'm assuming that would basically be the case for any ruu or Rom. Alternately we may just be able to pull the drivers from a 6!0 and JMZs kernel and compile a stock android that way.
I'm a Linux guy but this is my first foray into hacking android so any opinions/advice/criticism would be welcome.
I would've posted this in the developers thread but I don't have a high enough post count.
I'm reading everything I can find regarding porting different roms to new devices so any links you guys can point me to, I would appreciate.
I'm in school for CS and am very interested in porting new roms for the 610. HTC is emailing me the source today.
Lets quit messing around and start using this underrated device to its fullest potential!!
Scurvy
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Help
MiniBlu said:
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Click to expand...
Click to collapse
If you're already working on a port, perhaps we can work together? I've never ported code or a ROM to Android but I'm a linux guy and I've got some programming under my belt. I have quite a bit of experience building kernels for linux machines, namely debian.
If there's any way I can help you, I'd love to learn some stuff from you as well, let me know. If you need someone to test it out and do some bug hunting let me know through PM on here or by email at [email protected]
U still trying to port cm11 on the desire 610?
MiniBlu said:
I have been working on porting cm11 and I think Its almost ready to boot but as for getting all the hardware working it may take a while. The desire816 seems to share some of the same hardware so I've started with its cm11 device specific code. I've built cm for my Asus tf101, tf300t and ainol novo fire but this is my first attempt at porting to a new device without someone else's base to work with so we'll see how I go. Best of luck to you and maybe we can share ideas as we move forward.
MiniBlu
Click to expand...
Click to collapse
Hi!, I wanted to ask if your still working on porting cm11 rom on desire 610. I've gotten the htc desire 610 but found out no roms came out for it. I have been checking everyday now :/ but cant find any roms. Thanks.
Superspacex said:
Hi!, I wanted to ask if your still working on porting cm11 rom on desire 610. I've gotten the htc desire 610 but found out no roms came out for it. I have been checking everyday now :/ but cant find any roms. Thanks.
Click to expand...
Click to collapse
Yes I am still working on but have other priorities at the moment. It is currently geting stuck at the boot animation and I havn't had time to investigate why. Hopefully I,ll get it sorted over the christmas break.
MiniBlu
Boot animation
MiniBlu said:
Yes I am still working on but have other priorities at the moment. It is currently geting stuck at the boot animation and I havn't had time to investigate why. Hopefully I,ll get it sorted over the christmas break.
MiniBlu
Click to expand...
Click to collapse
Oh nice great to know you're still working on it and it took me a while to change boot animation on the desire 610 but got it working also it's not located in system/media folder I found the boot animation and stuff located in customization/recourses folder got my bootanimation zip sent it there and changed the name too att_bootup.zip since I got a AT&T version and it started working. Although you probably know that already. And thanks for replying and good luck!
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:24 AM ----------
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
Sent from my HTC Desire 610 using XDA Free mobile app
zihan said:
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:24 AM ----------
Are you still work on desire 610？my device was desire 610t. I want to port the cm11 for my phone. but isn't bringup！
Sent from my HTC Desire 610 using XDA Free mobile app
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know what you are trying to say? I am attempting to to create device specific files to be able to compile cm11 for international desire 610 from scratch. When I get it working I will put them on github and you could then download them and merge them with synced cm11 sources yourself.
MiniBlu
Boot Animation
Superspacex said:
Oh nice great to know you're still working on it and it took me a while to change boot animation on the desire 610 but got it working also it's not located in system/media folder I found the boot animation and stuff located in customization/recourses folder got my bootanimation zip sent it there and changed the name too att_bootup.zip since I got a AT&T version and it started working. Although you probably know that already. And thanks for replying and good luck!
Click to expand...
Click to collapse
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
kingculex said:
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
Click to expand...
Click to collapse
You will also need an insecure kernel. The stock kernel has write protection on the /system partition so any changes made disapear after reboot. You can either try the JMZ-kernel which has write protection removed or If you want to keep stock kernel you can make your changes while in TWRP, just use ADVANCED, FILE MANAGER to copy files to /system or make your changes via ADB while booted into TWRP(twrp boot.img doesn't have write protection on /system). You might have to fix permisions on your files to but TWRP also has a SHELL or FIX PERMITIONS options you can do that with.
MiniBlu
Jmz Kernel
kingculex said:
A cm11 port sounds great but I have a question about the boot animation on the att version. I have replaced the att_bootup.zip file repeatedly and it does not seem to stick because it gets overwritten by the stock one repeatedly. I have made sure the boot animation is the correct size and even went so far as to edit the stock att_bootup.zip. My phone is unlocked, rooted, and has busybox. The animation seems to be overwritten when the phone is restarted.
Any ideas on what I am missing?
Thank you.
Click to expand...
Click to collapse
Most likely you are missing jmz kernel. I had that missing and everytime I restarted nothing sticked so flash that and you should be good. You'll find the download on this forum. Let me know if you don't find it.
Superspacex
Thank you both. I was indeed missing the jmz kernel. I downloaded and flashed it. It changed the att boot animation to the stock text android but now replacing the att_bootup.zip does nothing. Putting a bootanimation.zip into data/local or system/media does nothing. I can not even locate the android boot animation to edit it. I have posted this issue in the jmz kernel thread.
Any thoughts?
THIS HAS BEEN FIXED. Thank you for pointing me in the direction of the jmz kernel. The file permissions were set wrong and not 644.
The boot file is /system/resource/customize caves m under the name (carrier)_bootup.zip
HTC Desire 610 - Root, stock ROM, r/w protection disabled
whats the status of this port? I just purchased this device naively from bestbuy to use as a platform which requires an AT&T LTE radio without checking CM11 availability... My bad... I'll port it... What needs to be done? Mucho Experience hacking HTC Device, Android, and Linux Kernel...
lets do this...
Progress
hey guys I was just wondering how far along the port was , I am also a programmer but I have zero experience in android development so I am eager to test it out though.
Any news about port??
Why don't you guys just compile one.
As you have said the One mini have the almost same specs (same cpu i presume)
Just take the device repo from Cm github and find some local_manifests in their xda forum and compile it
Use the custom kernel you got there too
Should work if the cpu variant is the same
I'm from HD2 forum compiling Android L for it. Booted
Can't wait
Sent from my HTC Desire 610 using XDA Free mobile app
aazzam16661 said:
Why don't you guys just compile one.
As you have said the One mini have the almost same specs (same cpu i presume)
Just take the device repo from Cm github and find some local_manifests in their xda forum and compile it
Use the custom kernel you got there too
Should work if the cpu variant is the same
I'm from HD2 forum compiling Android L for it. Booted
Click to expand...
Click to collapse
Sounds simple enough the way you said also sounds like you have experience doing the compilation maybe you could assist here and we do the testing. To be honest i been trying the virtualbox and ubuntu to start doing that stuff on my own but its just not working out
Shattariff said:
Sounds simple enough the way you said also sounds like you have experience doing the compilation maybe you could assist here and we do the testing. To be honest i been trying the virtualbox and ubuntu to start doing that stuff on my own but its just not working out
Click to expand...
Click to collapse
Sorry bro, can't help with that, but the concept is there now, no need for port
tip, use vmware
But, if One mini 2 is the same thing, just flash it on top
Rename the hw files ex. hwcomposer.msm8960.so to hwcomposer.your devices hw name.so
Related
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
zelendel said:
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
Click to expand...
Click to collapse
I figured it might be something like that, would explain why I haven't found anything really helpful.. but then the question becomes how do people port it to other devices? I'm personally a fan of the functionality it has over CM, and it would give the users of my device something to play with(and me something to learn/experiment with) while we wait for ICS to get built. Hell, if I can find some good resources, maybe I could contribute to the ICS build before it is done..
But while the resources I've been finding here are good, I learn best by tinkering, just figuring things out, so the resources between what is offered here and the finished product would do me the most good.
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Silentbtdeadly said:
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Click to expand...
Click to collapse
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
xboxfanj said:
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
Click to expand...
Click to collapse
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Silentbtdeadly said:
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Click to expand...
Click to collapse
Actually, one more suggestion on the kernel. Using dsixdas kitchen, extract the boot.Img from amaze stock and sensation miui and go to boot.img-ramdisk folder and go to init.RC on both devices using notepad++ and find the line that says bootclasspath and copy it from miui to amaze stock. Then recompile using dsixdas kitchen and then test
Sent from my GT-P7510 using Tapatalk
Hi there,
I've created a (temporarily) fix for the Evervolv based Jellybean hot reboot problem we have when playing video/youtube for the HD2.
Since we use and share a lot of stuff from the great work of texasice and the rest of the evervolv team this will probably work on other qsd8k devices who suffer from the same issue as well (no guarantees)
I thought it would be nice to give something back to the community untill this is fixed by the dev team..
Download evjb_qsd8k_mediafix.zip - mirror (flash via recovery)
Try it and see if it works and Remember that all the flashing is at your own risk ! Always make a nand backup in recovery
Source: I am not a dev and I just like to experiment with libs from different devices so have not compiled this fix from source.
Instead I've taken these libs from the jellybean msm7x30 platform (Desire HD) and replaced them with ours. (dirty hack so to speak)
The good news is that they have sources so you will have to look there since they seem to be a bit ahead with development compared to our qsd8k platform...
I hope this information will help the real devs making a 'proper' fix.
Xylograph said:
Hi there,
I've created a (temporarily) fix for the Evervolv based Jellybean hot reboot problem we have when playing video/youtube for the HD2.
Since we use and share a lot of stuff from the great work of texasice and the rest of the evervolv team this will probably work on other qsd8k devices who suffer from the same issue as well (no guarantees)
I thought it would be nice to give something back to the community untill this is fixed by the dev team..
Download evjb_qsd8k_mediafix.zip - mirror (flash via recovery)
Try it and see if it works and Remember that all the flashing is at your own risk ! Always make a nand backup in recovery
Source: I am not a dev and I just like to experiment with libs from different devices so have not compiled this fix from source.
Instead I've taken these libs from the jellybean msm7x30 platform (Desire HD) and replaced them with ours. (dirty hack so to speak)
The good news is that they have sources so you will have to look there since they seem to be a bit ahead with development compared to our qsd8k platform...
I hope this information will help the real devs making a 'proper' fix.
Click to expand...
Click to collapse
Yeah, its pretty awesome, I have been watching YT Vids all day on me Nexus one, i really miss 720p though..
How does it differ from this fix? Has anybody tried both? I'm using this fix below and it works for me too (you've got to use trackball instead of touchscreen when flashing the zip though)
http://forum.xda-developers.com/showthread.php?p=30006406
Peccator said:
How does it differ from this fix? Has anybody tried both? I'm using this fix below and it works for me too (you've got to use trackball instead of touchscreen when flashing the zip though)
http://forum.xda-developers.com/showthread.php?p=30006406
Click to expand...
Click to collapse
It's the same though the zip you flashed is for the HD2 specific.. read that post you got it from
My N1 don't boot after flashing... it remain on the X....
fc_themaster said:
My N1 don't boot after flashing... it remain on the X....
Click to expand...
Click to collapse
You may need to free up space on the system partiton, this usually happens when the System partiton is out of space.
Sent from my GT-I9300 using xda app-developers app
Is this not required for Evervolv p4? My YouTube is working well already...
cnam said:
Is this not required for Evervolv p4? My YouTube is working well already...
Click to expand...
Click to collapse
I haven't checked the latest build/nightly to be honest so I don't know..
Have they fixed it?
i search this fix for htc desire hd (ace)
with unoffical cm10.
any link for this?
okay found HTC Desire , but not work
http://forum.xda-developers.com/showthread.php?t=1825181
humzaahmed155 said:
You may need to free up space on the system partiton, this usually happens when the System partiton is out of space.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmmm. I also am experiencing the hanging on boot, at X. Freed up some space in /system, still no dice. Any suggestions?
Hey all.
Well first i'm gonna talk a bit about myself.
I have Huawei Ascend G300, and before that i had Huawei Ideos X3 (my first android). I've been playing with ROM's flashing since almost the beginning but now i'm trying to learn a bit more. What i'm trying to do is to port a Sense ROM to my G300. From HTC One V to be exact (http://forum.xda-developers.com/showthread.php?t=1943412). I don't have any kind of experience in developing, this is my first try, but i guess i would learn more porting Sense than any other normal port as it is much deeper than others. Don't give me answers like "you can't do it based on your experience" or "if you want Sense buy HTC". This is Chef Central so i'm expecting tips from experienced Dev's. And this little project is just to learn more about how android works. Finally, i would get a decent HTC if i had money for it.
So, the guid i'm following:
http://forum.xda-developers.com/showthread.php?t=1707177
If you have more detailed guides please send them to me.
What i've done so far. In CM9 (base) i've edited init.rc copying from Sense ROM and compiled the boot.img back. I've tacken the keys from CM9 to Sense ROM. Copied the files that the guide told me to. After this i recompiled the Sense ROM. Tried to flash and got problems with updater script. So i took the updater script and binary from CM9 to Sense ROM and tried again. It flashed this time but doesnt get past Splash Screen.
I've not made changes in framework.res and build.prop yet (it's my next task).
So how am i going? Am i on a good path?
Thanks!
I'm also working on a sense port. And your doing well so far, however, I would recommend editing the updater - script to match your mount points from stock script instead of copying the stock script over. There are some important processes that run that are sense specific. I've only made it to boot animation so far.
Sent from my SPH-L710 using xda app-developers app
Let me also join you
jagannn said:
Let me also join you
Click to expand...
Click to collapse
Have you already started porting? If so how far have you gotten? We haven't made it to the lock screen yet.
Sent from my SPH-L710 using xda app-developers app
Ok, guys here's the link of the ParanoidAndroid ROM i have been trying to port from One V. I have the permission from 1ceb0x.
LINK: http://d-h.st/Rkj
Gapps: http://d-h.st/ul6
Thanks to 1ceb0x, for giving me permission to use his ROM, and Lloir for his CM9 base...
How to flash:
1. take a nandroid backup.
2. wipe cache and data
3. go to fastboot mode and connect your phone to pc
4. place system.img in the same directory as fastboot
5.open command line (terminal) and go to your fastboot directory
6. type fastboot flash system system.img
7. reboot
We really need stable 4.1 AOSP for me to continue working on this. Waiting.
Changelog
Code:
0.1-----Initial build
0.2-----Used Lloir's vendor and device trees, tweaked build.prop, removed hTC crap
0.3-----Rebased, now using Lloir's CM9. Also, link is now on Dev-Host.
0.4-----Fixed updater-script.
0.5-----Now ROM packed in system.img
Stereo8 said:
Ok, guys here's the link of the ParanoidAndroid ROM i have been trying to port from One V. I have the permission from 1ceb0x.
LINK: https://dl.dropbox.com/u/65113140/Desire_X_ParanoidAndroid_2.50_JB_4.1.2.zip
Gapps: https://dl.dropbox.com/u/65113140/gapps-jb-20121017-KonstaKANG.zip
Thanks to 1ceb0x, for giving me permission to use his ROM, and infernal77, for making a 1.18 software base...
Test this for me guys and I'm not responsible if anything happens to your device.
Good luck!
Click to expand...
Click to collapse
Cool! , just one problem dude you used the HTC Desire X Sense 1.18 as a base which is impossible since you need AOSP, AOKP, CM10 or any other Jellybean ROM for the Desire X as a base for this to boot , or am I wrong? but anyway testing
The Android Manual said:
Cool! , just one problem dude you used the HTC Desire X Sense 1.18 as a base which is impossible since you need AOSP, AOKP, CM10 or any other Jellybean ROM for the Desire X as a base for this to boot , or am I wrong? but anyway testing
Click to expand...
Click to collapse
yea, I thought something like that will happen... Well if it boots then I'm awesome, right..
Stereo8 said:
yea, I thought something like that will happen... Well if it boots then I'm awesome, right..
Click to expand...
Click to collapse
Yeah
ROM updated. I used system/lib, etc, and bin files from Lloir's device tree.
Does it boot?
Sent from my HTC Desire X using xda premium
I have no ideaaa... I don't have the phone...
Sent from my ToasterOven running Toastdroid 4.2
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
infernal77 said:
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
Click to expand...
Click to collapse
that's not even a whole lolcat
Lloir said:
that's not even a whole lolcat
Click to expand...
Click to collapse
Ok, don't know what I did wrong, it's "adb logcat >logcat.txt" when you reboot out of recovery after flashing, right ?
edit: Ok, here's what I did second time : full wipe, flash the rom and google apps, then opened my platform-tools folder and typed "adb logcat -v long >logcat.txt" which gave me this : https://www.dropbox.com/s/gszb1ked7e8yjky/logcat.txt
Like first try, the phone hangs during boot, with HTC logo
Stereo8 said:
I have no ideaaa... I don't have the phone...
Sent from my ToasterOven running Toastdroid 4.2
Click to expand...
Click to collapse
Which phone have you previously used? If you wanna blind port, you should at least have some experience of an HTC device before. Just saying ....
Regards
Sent from my HTC Desire X using xda app-developers app
Finally I uploaded the newest build to Dropbox... It includes:
- Lloir's system/lib, etc, and bin files...
-Superuser instead of SuperSU
-Removed hTC crap
-Removed hTC crap from build.prop
-Tweaked build.prop
infernal77 said:
Hey stereo, I tried it, didn't boot (stopped at the HTC logo), here's the logcat
https://www.dropbox.com/s/lb05u0rmbleqlym/logcat_booting.txt
Click to expand...
Click to collapse
dude try porting CM9 fist because there is a base available for it all you need is permission from Llior and a boot.img for CM9
The Android Manual said:
dude try porting CM9 fist because there is a base available for it all you need is permission from Llior and a boot.img for CM9
Click to expand...
Click to collapse
Um, I'm not sure if I'll be able to, I've been trying to get an angle on how all this stuff works and I get the basics but when I look at github, it's like Chinese to me (or Taiwanese, since its HTC). I've looked at countless guides to port CM9, set up VMWare and Ubuntu 10 but it's a steep learning curve. Last month I maxed out our bandwidth (100 gig) trying to set up a local mirror for the source, which kind of defeated the purpose :laugh:
infernal77 said:
Um, I'm not sure if I'll be able to, I've been trying to get an angle on how all this stuff works and I get the basics but when I look at github, it's like Chinese to me (or Taiwanese, since its HTC). I've looked at countless guides to port CM9, set up VMWare and Ubuntu 10 but it's a steep learning curve. Last month I maxed out our bandwidth (100 gig) trying to set up a local mirror for the source, which kind of defeated the purpose :laugh:
Click to expand...
Click to collapse
Source of cm9 is 7gb including all proto device trees .you need an extra 15 gb just for building. I'll help you set all things up, you just have to put in some effort and time....My build from source is ready. Uploading.
Regards
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Source of cm9 is 7gb including all proto device trees .you need an extra 15 gb just for building. I'll help you set all things up, you just have to put in some effort and time....My build from source is ready. Uploading.
Regards
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Here you go
http://d-h.st/QmB
regards
Sent from my HTC Desire X using xda app-developers app
Any test results?
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Any test results?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Status 7 (No error Message)
The Android Manual said:
Status 7 (No error Message)
Click to expand...
Click to collapse
OK, back to topic, I'll test stereo's new one, this is his thread
Yasir, why not make a joint thread by anyone here that wants to participate in getting a CM9 to the DX ?
"Project DX" or something, hopefully there's as many people showing up to the party as in Project X (the movie) lol
when you do logcats let it run for about 5minutes -.- also for status 7 just do a recovery log (go to report error under advanced) and put it here i'll check back later
Hey all, since a lot of folks are wondering about custom roms for the DX, I decided to start this thread to document my exploits in trying to compile CM9.
Basically, I'm new to Android (had an iPhone 3GS for about 2 years) so I'm going to need a lot of help and this is really going to start of very basic. But since I had my Desire X and been on this forum, I have met more and more cool people that are actively trying to help development for our phone, like stereo8,maartenxda and yasir, so I'm sure we'll be alright. None of this would be even possible if not for LLior that made the CWM recovery for us. :good:
OK, so to build CM9 you need a build environment set up specifically for the job, there's many guides out there on how to do this, but I found this one (props to mbroeders, OP of the tut) pretty good :
http://forum.xda-developers.com/showthread.php?t=1566224
Basically, building CM9 is done in linux, Ubuntu being the most popular version, and I'll be using the latest Ubuntu 12. If you don't use Ubuntu as main OS, you can still try this, but you'll need to set up a good (!) portion of your harddrive to install it in a virtual environment, like VMWare Player (free). Mind you, we'll be downloading the CM9 source, which ended up being around 10 gig on my pc, and we'll be needing at least another 16 gig to actually build CM9. To be on the safe, I set aside 50 gig on my drive for the virtual Ubuntu-pc in VMWare.
The guide I'm using will show you how to set up a general build environment, but since we are talking about the Desire X, which is brand new and without official CM support (yet?), we are going to have to adapt it to make CM9 for our phone. Several people have already worked on this, mainly Lloir, so I got his permission to use the stuff he's already done. A big thanks btw, from one and all
And this is basically the first time I'm going to need help. To adapt the build system specifically for the DX, we'll need to make a local_manifest file that points it to device and vendor trees LLoir has made. The local_manifest is supposed to go in the .repo folder of your CM9 source.
How do I do this ?
Goto cm9 wiki and install all prerequisites. Then do a repo init of the main build tree(cm9) and then add the device trees to manifest.xml found in .repo. after that , you sync via repo sync and then you setup environment through envsetup.sh and then you build for protou by brunch protou. Debug the errors you encounter. That's about it. If it doesn't boot after successful build, then the device/hardware/vendor/kernel trees need some sorting out .
Regards.
Sent from my HTC Desire X using xda app-developers app
help for local_manifest - Llior ?
Morning, googled some more, and found a template for a local_manifest.xml file I'm adapting for the DX.`I prefer to go as much by the book as possible for now, apparently putting these in manifest.xml can mess up your source.
So far, I have :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Lloir/protou" path="device/htc/protou" remote="github" revision="ics"/>
<project name="LLior/XXXXXXXXXXXXX" path="device/htc/msmXXXX-common" remote="github" revision="ics"/>
<project name="Lloir/android_vendor_htc_protou" path="vendor/htc/protou" remote="github" revision="ics"/>
<project name="Llior/XXXXXXXXXXXXX" path="kernel/htc/msmXXXX" remote="github" revision="XXXXXXXXXXXX"/>
</manifest>
The XXXX need editing, not sure which repositories though
manifest
Here you go, you can see it for your reference...
Attachment
CM9 - first build - result
Yasir Javed Ansari said:
Here you go, you can see it for your reference...
Attachment
Click to expand...
Click to collapse
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
infernal77 said:
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
Click to expand...
Click to collapse
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Hm, thanks for the input, Yasir. I was wondering about it, I just synced using the default.xml in the last post. I guess that means I was using the prebuilt kernel as well. Don't worry about the source code I synced, it's definitely cm-ics. As far as I can see, there aren't files relating to msm7k in Lloir's github. I'll see if I can find out about a device that uses the msm7k.
cheers :good:
EDIT : Yasir and me are working together on trying to get a CM9 to the Desire X, anyone that wants to help (preferably with experience) is welcome Use this thread to keep things organised. Thanks
update on CM9 - wip - all help welcome !
OK, update on what's happening :
Because our phone has a new Qualcomm processor there's no CyanogenMods out yet for any device that uses it, let alone by HTC, that we can compare it to. This could help us out a lot to get the device specific information and sources the build system needs to make us a CM9. This info and these files are contained in and referred to by the so-called device and vendor trees. Lloir has done the most work for the Desire X up to now in making these device and vendor trees, but since first test builds aren't booting, Yasir and me are going over them again.
By the way, if anyone knows more about why logcat doesn't work, that would be extremely helpful. All response I get is that logcat isn't in /sbin/sh. I tried adding it to a separate /sbin/sh folder in my test build, but no dice
Good news is I found out the MSM8225 chipset was designed to be fully backward compatible, both hardware and software, with the MSM7225A and MSM7227A phones, of which Qualcomm sold about a 100 million. So, I've begun studying the device and vendor trees for the HTC Explorer (Pico), which is a MSM7225A model. Important because it has the compatible 7225A chipset and uses the ARMv7 cpu instruction set - which is the same as the Desire X.
We'll keep you guys posted, also when we need testers. :good:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
OK, I'll leave the boardconfig for now (am checking the files alphabetically) and move on to device.mk If I see anything I don't get or differs from the pico source (has official CM9), I'll let you know here or through pm. I was thinking the same about the device and vendor trees, it's our starting point and we're stuck here already lol. I know about the githubs, I'll check the changes (if any) simonsimons made.
I was thinking though : don't we need the 1.18 kernel to do this ? I already flashed the updated kernel with the 1.18 ruu. I checked on htcdev and it only lists the 1.14 kernel source. Or is there a way to get it from a running phone ?
missing logcat....
Hi Guys,
I don't know why logcat is missing, but to obtain kernel messages you could run the "dmesg" command instead.
I would like to participate in DX porting. I got intermediate knowlegde in android, but I'm really good in linux and kernel stuff.
Are you guys hanging around in IRC somewhere so we cant talk directly?
currently I am compiling lloirs tree. It is running for some time already...
hang loose
maze
atmel-touchscreen.kl is not in any git
Hi Guys,
I still try building the stuff, but atmel-touchscreen seems to be missing so I decided to remove it from
htc/protou/device_protou.mk. Now it continues compiling ....
( device/htc/protou/prebuilt/usr/keylayout/atmel-touchscreen.kl:system/usr/keylayout/atmel-touchscreen.kl)
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
neXus PRIME said:
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
Click to expand...
Click to collapse
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
I'm sorry guys, haven't been able to do much for this project anymore...no time (holidays and starting training to become system administrator), not to mention I spilled coke all over my Macbook Pro
Lloir said:
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
Click to expand...
Click to collapse
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
neXus PRIME said:
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
Click to expand...
Click to collapse
You can still logcat on that screen if adb sees it
Sent from my HTC One X+ using Tapatalk 2
nopes. I have QtADB running in background with logcat ON all the time. Thats how i can never miss if it gets to boot. But i didnt check kmsg though.
My laptop is in a mess right now and i have jellybean source synced by mistake over night. Now i gotta go back to ICS and it will again take a day to sync as the net is crappy here.
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Lloir said:
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Tell me, should I use pre built kernel or use HTC provided sources?