This is a question about rom porting in general. I'm attempting to port Cyanogenmod 9 from the HTC Sensation to the HTC One S (with S3 processor). I am working up from pretty much 0 knowledge, I have learnt a lot so far although the amount that I don't know is still huge.
My situation:
I created my rom using one of the various guides on xda using a mish-mash of roms such as TrickDroid, Stock One S rom and CM9 for the Sensation.
I have a flashable rom (no errors during flashing with TWRP).
When trying to boot the rom, the boot animation plays but then the screen goes black and stays black.
The device does not respond to adb commands (such as logcat).
Comparison between the phones (Sensation : One S):
The same chipset.
Different clock speeds (1.2 : 1.7GHz)
Same screen resolution.
Different versions of sense (3.0 : 4.1).
My Questions:
What could be causing this failure to boot? Is it likely to be one of a few critical things or could it be anything?
Is the porting of roms between these two devices an achievable task for someone such as myself?
Which elements of a rom will be incompatible between two devices (i.e. what is it stopping me from just flashing a Sensation rom and it just working)?
What can I do to start troubleshooting as I can't get logcat to run?
Any other suggestions?
This is not a question about unbricking my device.
Thanks
Related
I have looked all over, and googled how to do this without any luck. Maybe I wasnt using good search terms, or just am not sure what I am looking for exactly. My hope is to port CM9 to the HTC Desire HD/Inspire 4G. Any help is much appreciated.
I think you can start off, by setting up your system to meet the following requirements like in this guide:
http://forum.xda-developers.com/showthread.php?t=1552090
The Codename for the Desire HD is "stallion" so you have to change the branch to stallion (if possible).
If you like to make a port yourself you should read the CyanogenMod Wiki first. There should be further information about the process of building a port. If you can find a device with similar hardware it could be possible to just build the port (at this point i'm very unsure myself), or else you have to modify the property files etc.
I think that's a lot lot of work to do.
My expreriences so far were from building a CM7 Port, modifying a kernel to work with Multipath TCP and patching the kernel for the Nexus S . But i haven't tried building a CM9 port so far.
I hope i could help you a bit.
Hey john,
i just wanted to know if you made any progress on the topic.
hey johwayne007,
Did you figure out the process for porting CM to new devices?
I just read about porting HTC Sense to non-htc devices (http://forum.xda-developers.com/showthread.php?t=1707177), while I got confused when he said "find a device that is preferably VERY similar to your device", so my first approach is to find a HTC with Cortex A9 (I9070 uses that), in which i got HTC ONE X, is this what definitely he means? (by the way, ONE X doesn't have a card slot, will this cause trouble?)
Another problem is that it requires a boot.img, my first attempt is to use Pure Vanilla(http://forum.xda-developers.com/showthread.php?t=2182697) as my base, and it doesn't have the boot.img, so i tried CYM10.2, it has the file but when I check on the HTC rom(http://forum.xda-developers.com/showthread.php?t=2349756)， the location of that boot.img is different. Is there any wrong?
This is my first time doing porting, so please forgive me for asking such question :laugh:
Hello, I am not-exactly-proud owner of PAP5400DUO, it has only 512 MB RAM and Quad-core CPU, so it is sometimes unresponsive and since there is no hope of it getting an update to KitKat. I searched for a custom roms, but I haven't found any (which is little troubling), yet the device can be rooted and MIUI recovery flashed (version unknown, I didn't root my phone yet). On my way when searching what do I need to build AOSP ROM I found out that I need a "device tree" which if I understood right is some specific information about my device (drivers etc) needed to compile a rom properly.
Which is quite an obstacle, because it is nowhere to be found, yet I stumbled upon a post that said that device tree can be created from scratch (yet probably by trial-error method).
All I need is to know if it is really worthy the time and struggle, I used to own HTC Wildfire S and have limited knowledge about ROMs, yet I am willing to study by myself, there are the main questions:
Is it everything possible?
Is the said recovery sufficient to flash KK? (hard to tell, i don't know the version, I know)
Would AOSP KK ROM improve the performance? (I hope so, but still its 512 MB RAM only)
Is it worth it? isn't there another way? (the kernel doesn't support SWAP, so maybe kernel update?)
As far as I know, flashing a ROM cannot brick the device (unless it harasses with Radio, which I really don't intend), so I can Always revert to backup and phone stays functional right?
Hello xda community. I'm usually the kind of guy who finds a solution wjtbiut asking but now it been a week since I do countless tries on porting a ROM and I fail.
So there are these 3 device all having the same hardware codenamed Ceres from nvidia, 2 of them comes with 4.3 but one of them has KitKat.
Blackphone, wiko wax, and 4game from explay are all the same with minor changes in hardware (such as the black phone is overclocked to 2ghz instead of 1.7 found on the other two) however the kernel that comes with the black hpone works with the other two devices too.
Nvidia has also released a stock "preview ROM" which also works with the kernel provided above, how ever no matter what libs or bin I change the camera and he buttons doesn't seem to work.
Now here comes the weird part, the ROM of the blackphone is pretty much the same with the nvidia one except its odexed (which I did deodex), yet everything works fine with it. Now if I replace everything as so many tutorials thought me from libs and the bin folder the phone is stuck in a bootloop. Worst part is I can't even do a logcat because every ROM has a weird adb driver called Ceres and there are no drivers for it on earth.
Can someone shed a light on how he hw drivers work and how to find their dependencies, and how come one ROM works and the other with same version and for same hardware doesn't?
I have been doing some research on XDA and some other sites to see what would be required to put android 7.0 on a nexus one.
I know, that sounds crazy, but I wanted to challenge myself and try to do something I should do more often - android development.
I have been sifting through the other nexus one ports and the builds and ports for the 2 phones similar to the nexus one, the HTC HD2 and HTC desire.
So far, It seems some developers have been successful in getting android 6 working on the HD2 and desire. I figured I would try to do so on the nexus one, seeing as it has identical hardware in a lot of respects.
I am wondering if my approach is on target. To get this to work, I think I would need:
-custom hboot to allow for booting off sd card for OS (internal memory too small for android 7, even if slimmed down)
-custom partitioning of sd card
-custom rom built from android 7 and nexus one hardware drivers
-porting of linux kernel from HD2 to nexus one
-boatload of debugging
-compile rom and kernel into one zip installation package
Is there anything else I am missing? I apologize if I am using the wrong terminology, I have only been doing this for a few days (but have been rooting and installing roms for years).
I figured it was my turn to dig a bit deeper and try development myself.
If anyone has any input, I would be all ears. thanks a bunch!
mods: If this post is in the wrong thread (or you think it should be pushed to nexus one thread), feel free to push it anywhere that makes sense. thanks!
I did some more research and I think It will make most sense to port the 3.0.101 kernel from the HD2 and then build the rom
I am going to try android 4.4.4 rom with the 3.0.101 kernel to see how that goes first.
The main questions now:
-am I going to need a new version of TWRP for the new 3.0.101 kernel, or can I get away with TWRP 2.6.0.0 recovery?
-will I need to make a new version of blackrose / hboot because of android 6.0 / 7.0 / new kernel?
thanks for any input!