Herro all!
If my research serves me right, HTC has yet to release the source code for the kernel used in the Desire Z. I've tried compiling a kernel from Cyanogen's repo https://github.com/CyanogenMod/htc-kernel-vision but it doesn't boot. I pulled the config from the stock ROM and disabled some (supposedly) unnecessary drivers so that it would compile.
Does anyone have working kernel sources for Sense ROMs? I hope to make this thread a unified effort to fix the available sources.
That's odd. It should work on both. My kernel boots fine on the stock sense rom. And if you look at developer.htc.com the only kernel source released is the desire Z, the G2 has the source of all system files
Sent from my T-Mobile G2 using XDA App
You're probably running into the same issue I did when i started building Vision kernels. The base offset is different for these boot images, it needs to be 0x04000000.
rmk40 said:
You're probably running into the same issue I did when i started building Vision kernels. The base offset is different for these boot images, it needs to be 0x04000000.
Click to expand...
Click to collapse
Thanks. I'll test and post my repo up when I get something going.
Can someone who knows? Post a TUT to build the vision kernel? That's the only thing i am missing on my mac
Thanks if anyone does it.
i think that link is broken plz test it
rhcp0112345 said:
Can someone who knows? Post a TUT to build the vision kernel? That's the only thing i am missing on my mac
Thanks if anyone does it.
Click to expand...
Click to collapse
I second this request.. I was able to compile for my G1 and ever since I got my G2 I have been unable to get it to work... It has to be something that I am doing wrong but I can't figure it out.
a TUT and thread for support would be great!
Sent from my HTC Vision using XDA Premium App
can someone confirm for me that to compile Gingerbread I need a 64 bit system?... I have compiled froyo from cm github and have had trouble ever since I tried gingerbread... and I read today that 2.3 requires a 64 bit system... Is this true or is it outdated info?
Thanks for your time.
Sent from my HTC Vision using XDA Premium App
TheNewGuy said:
can someone confirm for me that to compile Gingerbread I need a 64 bit system?... I have compiled froyo from cm github and have had trouble ever since I tried gingerbread... and I read today that 2.3 requires a 64 bit system... Is this true or is it outdated info?
Thanks for your time.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
theres a guide on how to compile gingerbread on a 32bit system. i dont have a bookmark bu search it on google, its a Chinese site if not mistaken.
Ok I think I may have found a similar site... I just wasn't sure who to believe... Thanks for your time.
Sent from my HTC Vision using XDA Premium App
Related
I can flash any Rom but cm 6... I've tried diff recoveries etc... I tried the new clockwork fix koush released and nothing has worked... someone heeeelp!
Sent from my ADR6300 using XDA App
It just stays on the white HTC screen after install
Sent from my ADR6300 using XDA App
Same thing happened to me with Skyraider 3.3 because I tried to flash a different kernel at the same time. So flash a stock kernel or one of koush's custom ones. Then reflash CM6.
Also you should've wiped data & cache before you flashed any new ROM.
I always wipe etc when flaming a Rom... do you have the slcd?
Sent from my ADR6300 using XDA App
i tried that...and same result...im thinking its a framework issue..but i dont know exactly..really frustrating tho!..someone help lol
Some people were running into this issue with ShadowROM and I think the conclusion they came to was that they had different drivers.
is there any way to fix that?
i know i cant be the only person with an SLCD screen running into this issue
If it is indeed a driver issue, you could always build the rom yourself and pull the drivers directly from your phone. That is of course assuming that HTC didn't rename the drivers
Sent from my ADR6300 using XDA App
That is beyond me to do... lol
Sent from my ADR6300 using XDA App
CM6 is not built for use with the SLCD version of the Incredible; refer to the full update guide for the Inc in their wiki.
http://forum.xda-developers.com/showthread.php?t=808972
The maker of shadowrom has the SLCD INc now, i'm sure if he gets a fix. He'll share the info with CM sourse
Having the same problem. I'm thinking of attempting to flash the N1 CM6 then flash the IncDoes N1 port update over it. Should fix the problem being that the N1 runs and slcd display and has no issues. I'll post back and let you know the outcome. Before i go through all that though, does anybody know if they added support for the slcd in any of the nightlys?
Its actually a kernel issue...flash the rom then flash an aosp kernel and it will work...where is that n1 port?
Sent from my ADR6300 using XDA App
I have tried king klick and koush kernels after installing shadow rom and com....dosnt work...shadowrom says its slcd driver issue....have you gotten it to work personally?
SamuraiXDroid
samuraixzodus said:
I have tried king klick and koush kernels after installing shadow rom and com....dosnt work...shadowrom says its slcd driver issue....have you gotten it to work personally?
SamuraiXDroid
Click to expand...
Click to collapse
I ask in the ShadowROM IRC channel last night and they told me the same thing: SLCD driver issue. Since one of their devs now has an SLC Dinc they are working on fixing the problem...hopefully soon.
Yeah CM6 doesn't play too nice with the SLCD.
I have the SLCD and I am running Virtuous 3.1 with custom kernel and the IncRevo theme.
Couldn't be happier!
Koush test #2 kernel and it will work just fine.
doug piston said:
Koush test #2 kernel and it will work just fine.
Click to expand...
Click to collapse
Is the procedure: flash rom, gapps, kernel then reboot? Can you share link to the kernel? It is not in the Incredible section at Cyanogen webpage.
Jaxon2319 said:
Its actually a kernel issue...flash the rom then flash an aosp kernel and it will work...where is that n1 port?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I tried a KK kernel supplied by the guys at ShadowROM but that didn't work, so curious to try with the Koush kernel mentioned above.
Androidnite said:
Is the procedure: flash rom, gapps, kernel then reboot? Can you share link to the kernel? It is not in the Incredible section at Cyanogen webpage.
I tried a KK kernel supplied by the guys at ShadowROM but that didn't work, so curious to try with the Koush kernel mentioned above.
Click to expand...
Click to collapse
http://db.tt/I5MG7Zl here is the kernel from my dropbox since I can't find the link.
Sent from my ADR6300 using Tapatalk
Could someone point me to the repository containg the vendor overlay for the desire on a gb 2.3.7 build
e.g. here is the code i would use if building for the incredible
code:
cd ~/mydroid/system/device
cd htc
mkdir inc
cd inc
git clone http://github.com/koush/android_device_htc_inc.git inc
What i want to know is what url should i put in place of the red text for the desire?
Thanks I'm new to this
You could just use an extract from a working Rom or phone using the extract or unzip sh in the cm repository
Sent from my HTC Desire using xda premium
Are you suggesting i build it for a generic device and add drivers afterwards?
Pull the ones from cm7? Seems like a decent plan.
No you build everything specific for the bravo. You use the extracted proprietory files to complete the source
Sent from my HTC Desire using xda premium
rootSU said:
No you build everything specific for the bravo. You use the extracted proprietory files to complete the source
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Ye but apart from the proprietary files he'll also need the vendor folder containing all device specific non proprietary files and make-files for desire as well as a script to pull the proprietary files, and this seems to be the one he's looking for.
Non of the above is included for the desire in AOSP, so he'll need to get it somewhere else like from the cm7 project.
And device. Possibly hardware too
Sent from my HTC Desire using xda premium
Thank you for all the replies i'm still rather confused but i'm going to try using the vendor overlay for cyanogen with the make files and script and just see what happens
Sent from my HTC Desire using XDA App
Yep it should work ok, even though the make-files could need some adjusting. As a second option, Oxygen is also open source with desire support, so you could borrow those as well, but they should be pretty similar to the cm ones.
Rootsu when could you give me a short explanation of how you went about building etc. I have set up the builds environment and can build a rom for the emulator or nexus s. All i'm trying to do is build a basic stock GB ROM for the desire as part of teaching myself how to develop Android roms I understand dgb was a similar room for you which you have since worked on and published to these forums
Sent from my HTC Desire using XDA App
I used the redux 1.2 github repository to start with. I started there as for me it was the best Rom.
All I had to do to compile was get the proprietory files using the extract.sh
What I then did was learn my way around the source and work out how to change what needed changing. Swapping out the majority of the source with the Google repository.
There's still stuff I need to learn though, like changing the kernel but time is an issue for me.
I would recommend using redux or oxygen source as a starting point if I were you as cm is very different to pure aosp. I didn't know oxygen sources were available....
Sent from my HTC Desire using xda premium
A simple guide containing the oxygen and dev-null git links:
http://forum.oxygen.im/viewtopic.php?id=688
Thanks everyone really helpful
Sent from my HTC Desire using XDA App
I'm trying to create a barebones Rom but I have never had to mess with the internals much, I've already removed all the apps for the alpha test but I was hoping someone might be able to write a tut on this? Or point me in the right direction?
Thanks in advance.
Sent from my HTC Wildfire S A510e using XDA
What is a barebones ROM? I like the name.
Sent from my HTC Wildfire S A510e using XDA
It will be my Rom with a custom kernel but with nothing on it apart from the needed parts from which users will be able to customize to their liking rather than having loads of crapware, the idea came from tinycore Linux.
Sent from my HTC Wildfire S A510e using XDA
lynuxlover said:
It will be my Rom with a custom kernel but with nothing on it apart from the needed parts from which users will be able to customize to their liking rather than having loads of crapware, the idea came from tinycore Linux.
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
Cool, cause the most roms have to much build-in.
Sent from my HTC Wildfire S A510e using XDA
lynuxlover said:
I'm trying to create a barebones Rom but I have never had to mess with the internals much, I've already removed all the apps for the alpha test but I was hoping someone might be able to write a tut on this? Or point me in the right direction?
Thanks in advance.
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
Download my senseless rom and look inside the zip to see what i removed after alot of trial and error whats in the system/app folder is as barebones as it gets
jermzii said:
Download my senseless rom and look inside the zip to see what i removed after alot of trial and error whats in the system/app folder is as barebones as it gets
Click to expand...
Click to collapse
Ahh thanks jermzii did that now I have 150mb free space internal storage WooP!
Hello there! I was wondering if it is possible to port sense ui from htc to xperia s.
I've read many threads about porting and also porting sense. Found this guide on xda:
http://forum.xda-developers.com/showthread.php?t=1707177
But i had some issues. I tried CM9.1 as Base and one v rom as port rom (extracted ruu and copyed over some folders)
-> didn't boot... i had no problems while flashing... but then there just came a stock android bootscreen logo but nothing happend.
I wasn't sure about which device would fit the best for porting and how to get started the best.
Would be nice to get some help!
Thanks!
You want only the UI or the whole Sense?
Full sense!
I know its hard to do it but i really like sense!
And i think its worth it
lenniz said:
Full sense!
I know its hard to do it but i really like sense!
And i think its worth it
Click to expand...
Click to collapse
Indeed it is really hard. You'd have to get a dev that would want to have such a big job...
Which devs do we have for xperia s?
And who would do this?^^
Do you have xperience with porting Roms?
Sent from my Xperia S using xda app-developers app
lenniz said:
Which devs do we have for xperia s?
And who would do this?^^
Do you have xperience with porting Roms?
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
There aren't many, mostly none wants to do it and I don't have experience. I can't badly change a png myself without my phone almost exploding.
Sent from my LT26i using Tapatalk
Thats Bad/ sad.
I know sense is very complex
I would try to do it myself for the beginning but i dont have much experience.. all i need would be some information on how to get started and which device would make 'sense' to port sense from.
But i also know i can't do it alone. Sadly I dont have the knowledge.
Sent from my Xperia S using xda app-developers app
lenniz said:
Thats Bad/ sad.
I know sense is very complex
I would try to do it myself for the beginning but i dont have much experience.. all i need would be some information on how to get started and which device would make 'sense' to port sense from.
But i also know i can't do it alone. Sadly I dont have the knowledge.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
I think the Sensation HD would be a good choice. I don't know if it has the latest Sense, but it is the closest HTC device to ours (basically, it is the same thing with different design and UI)
Alright..
For porting, do i have to use a stock Rom or can i also try to port a custom Rom of the HTC sensation or would that make it harder?
And if i use a stock Rom, do i have to extract the Rom from a ruu or are there other ways to get stock Rom?
Sent from my Xperia S using xda app-developers app
lenniz said:
Alright..
For porting, do i have to use a stock Rom or can i also try to port a custom Rom of the HTC sensation or would that make it harder?
And if i use a stock Rom, do i have to extract the Rom from a ruu or are there other ways to get stock Rom?
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
I think any custom Sense should do.
Sorry, don't know anymore
Would be amazing to make this possible !
Okay but thanks
Sent from my Xperia S using xda app-developers app
you could just google for "htc sensation hd stock rom", there are so many sources serving the stock roms.
Of this is really that simple everyone would do it,but unfortunatly it's not :/
I know that there are many sources but i've never seen a stock rom as zip file .
You always have to download ruu and then extract firmware and kernel files..
But at least it is not the Problem to get a stock Rom
Sent from my Xperia S using xda app-developers app
lenniz said:
Hello there! I was wondering if it is possible to port sense ui from htc to xperia s.
I've read many threads about porting and also porting sense. Found this guide on xda:
http://forum.xda-developers.com/showthread.php?t=1707177
But i had some issues. I tried CM9.1 as Base and one v rom as port rom (extracted ruu and copyed over some folders)
-> didn't boot... i had no problems while flashing... but then there just came a stock android bootscreen logo but nothing happend.
I wasn't sure about which device would fit the best for porting and how to get started the best.
Would be nice to get some help!
Thanks!
Click to expand...
Click to collapse
I think i can help you here
If you were stuck at bootscreen, then replace the android_servers.so in system/lib of the ported rom with the android_servers.so file of original rom(i.e. rom made for xperia s)
Let me know if its working or not and if possible can you send me a link of your ported rom..
Sent from my iPhone 6 using Android 5.0
I can help with testing, as long as you send me it after December 11th.
Sent from my LT26i using Tapatalk
ap030993 said:
I think i can help you here
If you were stuck at bootscreen, then replace the android_servers.so in system/lib of the ported rom with the android_servers.so file of original rom(i.e. rom made for xperia s)
Let me know if its working or not and if possible can you send me a link of your ported rom..
Sent from my iPhone 6 using Android 5.0
Click to expand...
Click to collapse
Thanks! I'll try it soon, but it will take a few days... i'm having some issues with my PC and also busy with school.
Sorry!
Anyway.. I stay active here!
I will upload the Rom if it boots sometime and I really hope to get this work with your help.
Sent from my Xperia S using xda app-developers app
Try reporting vipera rom of sensation. Ask M0narx and then try, maybe it work, because same hardware
Sent from my HTC Sensation Z710e using xda premium
PopaStefanx said:
Try reporting vipera rom of sensation. Ask M0narx and then try, maybe it work, because same hardware
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I wrote him a message
Sent from my Xperia S using xda app-developers app
I need help with the kernel.
Always when i try to extract boot.img it says "ANDROID MAGIC not found in boot.img. giving up" or Magic header not found or s.th like that.
I tried to extract with cygwin and dsixda kitchen and other tools. Always same Problem
any suggestions?
Hey Guys i no i might seem like a noob but i want to compile cm10.1 for the play ive got a pc with pretty decent specs
i7 2600 3.4GHz And 4GB Of Ram and ubuntu 12.04 LTS 64BIT the questions is can it be done since fxp hasnt done this yet would i have to compile my own kernel and such
extremetempz said:
Hey Guys i no i might seem like a noob but i want to compile cm10.1 for the play ive got a pc with pretty decent specs
i7 2600 3.4GHz And 4GB Of Ram and ubuntu 12.04 LTS 64BIT the questions is can it be done since fxp hasnt done this yet would i have to compile my own kernel and such
Click to expand...
Click to collapse
Firstly, This should go in the questions sub forum, that's what its there for. Secondly, FXP has a working build for the Xperia Play. So you could use there ROM as a base. Compile everything normally and CM10 should and when you build your ROM should work with CM10 ROMs. If not, you either heavily modified the ROM and you most likely will need a custom ROM(Unlikley) or you made a mistake. Reply if you need links to the got source. Happy building! :beer:
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Firstly, This should go in the questions sub forum, that's what its there for. Secondly, FXP has a working build for the Xperia Play. So you could use there ROM as a base. Compile everything normally and CM10 should and when you build your ROM should work with CM10 ROMs. If not, you either heavily modified the ROM and you most likely will need a custom ROM(Unlikley) or you made a mistake. Reply if you need links to the got source. Happy building! :beer:
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
What i Dont Think They Have CM10.1 Built Yet?? Link If They Do
Official FXP development thread.
http://forum.xda-developers.com/showthread.php?t=1780322
Sent from my Xperia Play using xda app-developers app
JunDavis said:
Official FXP development thread.
http://forum.xda-developers.com/showthread.php?t=1780322
Sent from my Xperia Play using xda app-developers app
Click to expand...
Click to collapse
Thats CM10 i Need 10.1 I Want To Make Android 4.2
extremetempz said:
Thats CM10 i Need 10.1 I Want To Make Android 4.2
Click to expand...
Click to collapse
Oh OK! Didn't see the .1. Yes get it from source and try to port? You might have to make some kernel adjustments. I recommend trying to port a similar device or ROM using 4.2. Sorry for the misunderstanding.
Glad to see someone actually noticed 4.2
••••••••••••••••••••••
If I helped you. Please click the thanks button!
Seems that with the actual sources they put on github you can't achieve that,we need either fxp to push their source or to debug it ourselves, I just made a build this morning but it doesn't go past the kernel logo, and can't seem to be able to logcat, the strange thing is that adb doesn't recognize the phone but I was able to use flashtool to reboot it in flashmode via adb, any suggestions?
Sent from my R800i using xda app-developers app
sasukekun67 said:
Seems that with the actual sources they put on github you can't achieve that,we need either fxp to push their source or to debug it ourselves, I just made a build this morning but it doesn't go past the kernel logo, and can't seem to be able to logcat, the strange thing is that adb doesn't recognize the phone but I was able to use flashtool to reboot it in flashmode via adb, any suggestions?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Log cat should work. Pm me the ROM and I'll log cat it for you.
••••••••••••••••••••••
If I helped you. Please click the thanks button!
You may be able to port the Arc release while using a 4.1.2 kernel.
Sent from my Xperia Play using xda premium
I got a logcat thanks, will see what is wrong later, I'm very noob at this so don't expect anything from that try, it's just a way for me to start learning
Sent from my R800i using xda app-developers app
Leraeniesh said:
You may be able to port the Arc release while using a 4.1.2 kernel.
Sent from my Xperia Play using xda premium
Click to expand...
Click to collapse
He will need to make modifications to Ramdisk for the kernel to work fxp cm10 zImage is fine
Sent from my GT-I9300 On Official JB