Database Develop

[DEV][ICS+SENSE][Mar.20.2012]HTC One V development[Source+RUU]

Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download

Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.

I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595

PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..

Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot

When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.

Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v

Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^

PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?

orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★

PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!

I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium

2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.

Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5

I'll upload the ROM port I just made a few days back. It has most of what I thought might work..

Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.

I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..

Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5

Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.

I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!

[KERNEL][CM11][4.4.2][MultiROM] MultiROM Port for the Sprint HTC One [m7spr]

Hey guys!
I got a Sprint HTC One, and I was psyched to see MultiROM ported to the One...unfortunetly it's not for the m7spr, only the m7/att/ul/tmo/gpe
I got to work trying to port the kernel mods not just to the Sprint eddtion, but the newest version of CyanogeMod (CM-11.0)
A big thanks to all the devs behind this ( @kushdeck @oblikas and @Tasssadar to name a few)
I'll be uploading a build once it actually completes (Shouldn't have any errors, as it seems to already have built the kernel) (LETS HOPE IT BOOTS)
P.s. I'll be uploading my modified version of Cyanogenmod/android_kernel_htc_msm8960 at some point (I think that's the repo)
The only reason I' doing a full build is to negate the need for a ramdisk and so it's built automatically to a .img for us S-On devices (Anyone got S-Off via CM? That'd be nice...but I think I have to be on a Sense ROM to do it (MultiROM anyone?))
XDA:DevDB Information
CM11.0 Hardboot Enabled, Kernel for the Sprint HTC One
Contributors
ajbiz11, kushdeck, oblikas, Tasssadar
Kernel Special Features: kexec hardboot
Version Information
Status: Alpha
Created 2014-05-28
Last Updated 2014-05-28

Mine

and mine

Thread closed.
We do not allow "placeholder" threads at XDA, please contact a Moderator or report your thread when you have something to upload and we can re-open it.
Thanks.

Kernel Source for HTC DESIRE 510

If you need kernel source for whatever reason it can be downloaded from here
http://www.htcdev.com/devcenter/downloads/P00
In filtered by select Desire 510 and hit Find Files
And download kernel source that you need

Still waiting on source code for the US Cricket variant. I have contacted HTC twice thus far with no results, Hopefully if i can get a backing of follows to message them about it they will finally release it.

Can you give link for EU stock kernel? (I have got bootloop and cant boot my phone xd)

shinru2004 said:
Still waiting on source code for the US Cricket variant. I have contacted HTC twice thus far with no results, Hopefully if i can get a backing of follows to message them about it they will finally release it.
Click to expand...
Click to collapse
Any luck?
Sent from my SM-P600 using XDA Free mobile app

i need kernel for 64bit eu version?? but the one for eu is not correct one??

Inside 4ndroid said:
i need kernel for 64bit eu version?? but the one for eu is not correct one??
Click to expand...
Click to collapse
Its not that the source isn't correct so much as we have no way to root or build recovery. Once you guys have root then we can pull the stock kernel and recovery to make TWRP.
tylerholbrook said:
Any luck?
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Actually yes i have a working/booting Cricket kernel with write protection removed, its posted on a different site but i will try to make a thread here with the link

wolfaas12345 said:
If you need kernel source for whatever reason it can be downloaded from here
http://www.htcdev.com/devcenter/downloads/P00
In filtered by select Desire 510 and hit Find Files
And download kernel source that you need
Click to expand...
Click to collapse
a general question, are these "source" files also namely RUU files? and can be used in HBoot mode or something?
still learning, thanks,

DX///M said:
a general question, are these "source" files also namely RUU files? and can be used in HBoot mode or something?
still learning, thanks,
Click to expand...
Click to collapse
No, they have to be compiled into an img file, and then can be flashed through HBoot using the Android Debug Bridge (adb), or packaged in an RUU by the manufacturer. Source code is what you use to make/modify binary code. It's of no use to you unless you're a super duper computer geek lol
Sent from my HTC Desire 510

shinru2004 said:
Its not that the source isn't correct so much as we have no way to root or build recovery. Once you guys have root then we can pull the stock kernel and recovery to make TWRP.
Click to expand...
Click to collapse
righto so i finally got the 64bit eu version rooted now as to building twrp i have my linux environment setup and ready to go now i am stuck here
Device Tree:
git clone *URL TO DEVICE TREE* -b kitkat device/*VENDOR*/*CODENAME*
Kernel:
git clone *URL TO KERNEL* -b kitkat kernel/*VENDOR*/*BOARD*
i have a url to device tree which i got from rbhheromax but what do i do for the kernel?????

TheDreamer Kernel Only 64bit

Warning: Use this on you Own Risk
Features:
S2W D2W
Stereo Call Record
GPU Tweak
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
How to:
Load boot.img into fastboot folder
run this command:
"fastboot boot thedreamer-Desire510-64bit.img"
When the Device Boot UP and is Stable
Flash the boot.img with:
"Fastboot flash boot thedreamer-Desire510-64bit.img​
Download:
http://forum.xda-developers.com/devdb/project/?id=8179#downloads
Source:
GitHub
I Give no Support i make this Kernels Only for me and post it for other 64bit MSM8919 User to Use.
I Integrate only my Wishes
XDA:DevDB Information
TheDreamer, Kernel for the HTC Desire 510
Contributors
Thestealth2, thestealth2, RBHeromax
Source Code: https://github.com/thestealth131205/HTC_Desire_510_64bit
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2015-02-10
Created 2015-02-10
Last Updated 2015-02-10

I'd love to try it. Is there a link to download it please?

Burtrum57 said:
I'd love to try it. Is there a link to download it please?
Click to expand...
Click to collapse
thanks for the source it coould prove useful in compiling a custom rom for the 64bit i may have to re sync the cm11 repo and give it a shot..
could you also provide a link to the boot.img so we dont have compile the kernel lol.. cheers..

excuse me if i sound stupid,but what is "AWB LCD Custom Color for .Rec 709 Profile" actually? is it actual modified screen colors or is it just the custom kcal driver?

Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app

Thestealth2 said:
Kcal driver. For Rec. 709 Calibration. My display is calibrated with a Colorimeter.
Download is in First Post
Sent from my HTC Desire 510 using XDA Free mobile app
Click to expand...
Click to collapse
do you remember which file you modified for the calibration? i would like to apply it to my kernel,i dont wanna bug you :silly:

See source and merge with youre source

Thestealth2 said:
See source and merge with youre source
Click to expand...
Click to collapse
i build for the 32bit,i cant merge a 3.10 kernel with a 3.4 one :silly:

I write you next days a pn. Have no time at the moment.
You can push a 64 bit stock kernel to git an the push my source than can you see all changes. ?

Just a question...
Exactly which toolchain you use to compile??

I'm about ready to flash your kernel - thestealth131205 I'll update after i get my flash on.

Thestealth2 said:
Features:
NO Write Protection for System Partition
AWB LCD Custom Color for .Rec 709 Profile
Few little Code Changes
Download:
http://www.dhm-server.de/thedreamer-Desire510-64bit.img
Source:
GitHub
Click to expand...
Click to collapse
Thank you for your kernel, have been using it for a month (on my EU) and it works very well!
However, could you make some progress please...
As it is seen on this forum your work is the only one for 64bit. So, could you consider some suggestions?
Namely in their 32 verisons of modded kernels developpers write here about improving screen touch responsiveness and removing HTC's backdoor "debugging" access... How about it?

download link unavailable

See first Post

RE: THEDREAMER 64 bit
Thestealth2 said:
See first Post
Click to expand...
Click to collapse
Last I touched base/read with you and RBHEROMAX, if I understood correctly, you were going to be changing something so I've been trying to remain patient and wanted to inquire about this. I picked up a Samsung Galaxy S5 Sport (sprint) all stock to entertain myself with. LOL. I have the utmost respect for you and Rbheromax, I'd like to thank you again for your dedication and time put into this project and the respect and patience you give to everyone that asks you questions on any level. You are very special individuals giving the gift of knowledge to all that seek it.
All that came together to make the 64 bit HTC Desire 510 project. All that came to the rescue to make THEDREAMER possible. You are pioneers and not afraid of a challenge. I don't know if you have any sort of recognition for everyone that takes the time and puts fourth the effort to share the GIFT OF KNOWLEDGE. If not, I'd like to declare Tuesday, March 31, 2015 programmers appreciation day! And you both deserve the GOLDEN THUMBS UP AWARD just because I appreciate your patience, and you caring enough to share knowledge with individuals that otherwise wouldn't have the opportunity to delve into this field.
THANK YOU!
Hopefully I'm not breaking any rules by speaking up. But I. Believe it's time for some recognition with a simple shout out saying THANKS, YOU MADE A DIFFERENCE IN MY LIFE.
paying it forward....
:highfive:

Should the kernel name be "3.10.28-g36bd0f8-dirty (root @ speedstarlap)" after installing?
I'm trying to enable S2W and can't seem to get it working, was wondering if the kernel installed right, or if there were other versions - you said you have MSM8919, whereas my 510 shows up as MSM8916- a typo or actually different chips? (if possible, could you please tell me how to enable S2W if the kernel installed right?)
@edit - Managed to get it... "working" - if I lock the screen and swipe to right and left near the menu buttons within 2-3 seconds from locking, it works. otherwise it doesn't. D2W is fully dead though. I'll poke around it a bit more and see if I can get it to work properly...

Hi, which gcc are u using? and how to compile the dt.img?
I compiled a kernel for D820, only with stock dt.img could bootup. It boots into bootloader if I use the dt.img which I compiled from stock kernel source.
could u help me?

Kernel works great and great improvement in speeds! Thanks

I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.

Lonely_Boz said:
I've a problem. Sometimes the touchscreen doesn't react after waking up my phone. But the volume up and down and the power button work.
Can this be because of the kernel? I don't know. Please help.
Click to expand...
Click to collapse
I have the exact same problem I have to restart my device for screen to be back in action

[ROM][AOSP 6.0.1_r10]AOSP MM-MR1-RELEASE branch by khaon

Hello everyone,
I have successfully built a package for this device. While the factory images is android-6.0.1_r5, this package features android-6.0.1_r10 along with the optimization flags I use for my other devices.
Instructions:
You need to get a custom recovery, this recovery should work
Boot into twrp
flash the package
optional: factory reset.
I haven't tested this as I am at work currently, so if anyone want to try before I get home do it
LINK​
XDA:DevDB Information
AOSP for Pixel C, ROM for the Google Pixel C
Contributors
Khaon, Namastaz
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Alpha
Beta Release Date: 2016-01-12
Created 2016-01-12
Last Updated 2016-01-12

Sweet! Does this have root integrated, by chance?

oRAirwolf said:
Sweet! Does this have root integrated, by chance?
Click to expand...
Click to collapse
No it doesn't. I could tho, I will see how thing evolves. I had my nexus 10 ramdisk patched for SuperSU. But I think now the flashing package cheks your partitions.

Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.

cheep5k8 said:
Guys just a reminder: don't flash SuperSU ZIP directly. That goes for stock as well as builds like khaon's (just a heads up), but rather one of the existing root options. Flashing a ZIP that tries to modify the kernel, like SuperSU systemless will fail on the Pixel C and might semi-brick your tablet.
Click to expand...
Click to collapse
I read somewhere you were saying that the boot image is chromeos alike. Could you link me some source-code so I can see and understand the differences and how chromeos bootimage are built ? I looked at the chromeos's sources but i couldnt figure out where to look at.

Basically the kernel image is a depthcharge (the bootloader) payload that contains the Android kernel which then boots Android.
Depthcharge (bootloader source code with fastboot code): https://chromium.googlesource.com/chromiumos/platform/depthcharge/
Other relevant project there is also vboot_reference.
---------- Post added at 11:49 AM ---------- Previous post was at 11:37 AM ----------
It's not just ChromeOS-like... up to the point where the Android kernel boots Android it's completely like on a Chromebook.

But, sourse code?

So is this using the stock boot image?

Sorry for the late reply...
Martin_Devil said:
But, sourse code?
Click to expand...
Click to collapse
Ewww, I am using this android revision
This tag points to the marshmallow-mr1-release.
There are no sources as it was built with the default sources, however, this was the build platform
bill3508 said:
So is this using the stock boot image?
Click to expand...
Click to collapse
Yes it is using the stock boot image.

Thank you! Could someone please upload the build.prop file? TIA!

Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .

Sjflowerhorn said:
Thanks a ton man. I've heard this device is more difficult than other devices to build for. When my type C cables and adapters show up tomorrow I will be unlocking the bootloader, flashing TWRP, nand backup, and then I'm going to try your ROM and then the kernel that's available. So it's going to be a good day .
Click to expand...
Click to collapse
You may just want to root the stock ROM. This ROM has not been updated to the new base, which has fixes for the touchscreen issues.