Related
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?????
This is not my work this a reply i got from a guy when i posted in the sony developers forum ...I hope someone finds this useful:angel: .And since i m a new user i can post links for some stupid reasons...so i will get creative
by fzort
Kernel source for the Xperia E1 is available as a tarball on the "Xperia open source archives" site. I'm running a custom-built kernel on my Xperia E1 (D2114). I documented what I did here:
[https://
github.com
/mpersano
/xperia-e1-kernel-patches
/blob
/master
/README.md]
https://github.com/mpersano/xperia-e1-kernel-patches/blob/master/README.md
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Caio99BR said:
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Click to expand...
Click to collapse
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Kizoky said:
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Click to expand...
Click to collapse
Ok, but for now a kernel working in Stock is good, so how i can unpack boot.img?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Use this:
Zsenyka said:
Use this:
Click to expand...
Click to collapse
Edited: The Bootloader is locked, so the boot.img is "Encripted", and no way to unpack this, i will unlock this.
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------
https://github.com/Caio99BR/android_kernel_sony_falconss
Caio99BR said:
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
Click to expand...
Click to collapse
Hi! I'm the owner of the github repo mentioned at the top of this thread.
Getting a working ramdisk took me a while. I think that what finally worked was downloading an official firmware image with XperiFirm (you don't even need to wait for it to finish downloading the full image - one of the first files downloaded is the kernel one, containing boot.img), then I extracted boot.img with the unofficial XPERIA flash tool, then extracted the ramdisk. (The kernel command line I used is the same one in the official boot.img, by the way.) As for the device tree image, you can build it from the kernel sources.
Note that boot.img on this phone has a device tree blob appended to the end. I wrote a small script to unpack the official boot.img and compare it to the one that I built and check if I was doing everything right (can't post links as I'm a new user, but it's linked in the README.md file linked above).
I'll try to add more details to those instructions when I have some time (I didn't think anyone else would be interested in building a kernel for this cheap phone ). By the way, I use the E1 with a custom kernel as my main personal phone and it works fine (for a 512M phone), kudos to Sony for not compromising the quality of even their lowest end model.
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Kizoky said:
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Click to expand...
Click to collapse
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
fzort said:
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
Click to expand...
Click to collapse
I've been trying to get that script work like ages
Does it require Linux, or just Python?
EDIT: nvm, I figured it out
So is CM for E1 finally possible or just custom kernel?
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Caio99BR said:
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Click to expand...
Click to collapse
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Kizoky said:
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Click to expand...
Click to collapse
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Caio99BR said:
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Click to expand...
Click to collapse
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Kizoky said:
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Click to expand...
Click to collapse
We have a problem, the TV is not working anymore, idk why
I will check it, we need TV Support working, or i need it, since my father use it
EDIT: The problem is inside kernel or ramdisk.
it's amazing .. Very good work .. Congratulations friends??
racer.z said:
it's amazing .. Very good work .. Congratulations friends����
Click to expand...
Click to collapse
@Kizoky TV is fixed
Edit: THANKS, i forget ever
---------- Post added at 10:59 PM ---------- Previous post was at 10:19 PM ----------
I will try to release tomorrow, since i want to make a new banner, based on my old VeeKernel banner.
For CM i will need to redownload CAF Kernel MSM (since im stupid and overwrited .git in tests).
I will start building TWRP (V3), merging it to stock ramdisk and update to make cwm and twrp side-by-side.
So i have done this in two weeks for make a custom kernel, thanks @fzort
Enviado de meu E435 (L3 II Dual) usando Tapatalk
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.
Before i posting anything i need to say this recovery is exclusive from our greatest developer kumajaya. I'm just add theme to default one you just need to reflash nothing more. I'm not responsible for bricked devices. This is working well if you have any problem just leave comment on thread
It's enough, don't hide TWRP inside a ROM thread!
Built from source inside cm-13.0 source tree, always sync to upstream TWRP
Trusted, completely open (recovery changes, device tree, kernel, etc)
Currently use the new default TWRP theme
Qualcomm encryption support (untested, have no plan to encrypt my device)
Properly run AROMA Filemanager 2.00b7
Compatible to both old KitKat and new Lollipop bootloader (since 20160201 build, use updated kernel source but CM known not boot with the new bootloader)
Source Code:
Device tree: https://github.com/kumajaya/android_...e/cm-13.0-twrp
TWRP source: https://github.com/kumajaya/android_...y/tree/cm-13.0
Kernel source: https://github.com/kumajaya/android_...ss-2.1-wt88047
Click to expand...
Click to collapse
Download: https://mega.nz/#!zJZxwZKb!i
Credits: kumajaya
Have fun!
I can't download with this link
Hey guy, first, thanks for the recovery. You have uploaded in Mega, so, you need to share the link (that you shared) and the decrypt key. Please fix link asap, because anybody can't download it.
Seems the OP doesn't want to reupload the file
Thread closed
there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea
Well if your trying to build a device tree and kernel source and vendor start with downloading android source in linux there are many great guides for this then download the sources for the A600F/FN or any other current model of the A600 then there will be a file in the folder for whichever source you downloaded that will allow you to pull resources from your phone like kernel recovery device vendor files ect.. use that and then import it to the same folder than try to build TWRP and test it to see if you get a working build if not then go back and try again their are many sources for learning how to compile twrp for devices that dont have it read those and try again.
Sent from my [device_name] using XDA-Developers Legacy app
tmvkrpxl0 said:
there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea
Click to expand...
Click to collapse
I did find the kernel and source here: http://opensource.samsung.com/recep...menu_item=mobile&classification1=mobile_phone
(page 44 for SM-A605FN - A605FNXXU1ARD7)
I would like to build it myself, but my android development knowledge is limited (i do have a solid linux knowledge though).
Is this guide obsolete (https://forum.xda-developers.com/showthread.php?t=1943625)?
If yes, anyone knows where can i find an up-to-date one?
If not, any idea where BoardConfig.mk can be found?
Where can we find a guide on how to build a twrp? I would really like to learn how to do it