Develop Bugs

[Kernel] SEtweak

SEtweak kernel for Xperia S.
Intro:
I know I failed last time (with Play - it was stolen) and left development. But let's be serious this time.
Since it'll take a bit to set up everything again, I've taken DooM's ramdisk (hope you don't mind) for the first test.
Note: I don't have the device so I can't test it. If you want to, you can donate via Donate button on the left.
Sony finally published everything we need to build kernel.
Due to some possible bootloader problems, kernel might not work.
Features:
Codepage 852 (purely selfish reasons )
NLS UTF-8 (Native Language Support)
NTFS support
TUN/CIFS support
Default governor set to 'ondemand'
Prerooted
init.d support
Coming soon:
More governors
Recovery
Download: be patient
Best regards,
Blagus

Cool.
Ive unlocked my bootloader already so ill test it for you.
Im not rooted yet tho. I did have the rooted rom installed form another thread but i was having issues with app crashes so i flashed the stock .67

Hi there,
I hope the kernel wil be pre rooted and have some nice features....
I will try it

I need someone to send me kernel.sin of 6.0.A.3.62 firmware.

Hi there,
You can download it here : https://github.com/DooMLoRD/Xperia-2012-Official-Kernel-Sources and if its not there you can find it here http://eddy.uni-duisburg.de/bin4ry/L...1257-3921).ftf

Blagus said:
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Click to expand...
Click to collapse
Im uploading it now for you
Edit:
Done
https://rapidshare.com/files/1187401250/kernel.sin

Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.

deovferreira said:
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
Click to expand...
Click to collapse
Really? Any more info on that?

It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.

deovferreira said:
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
Click to expand...
Click to collapse
hi defer,
what is the bug exactly?
i faced some issues yesterday when testing out kernels on a users device...
whenever we tried hotbooting the kernel (fastboot boot kernel.elf) the bootloader always returned "Wrong range" even though i used exactly the same ranges as given by Sony....
the test kernels are posted here:
http://forum.xda-developers.com/showthread.php?p=23868276#post23868276
if anyone wants to try them

I don't know the specifics of the bug, but it's in the bootloader it might be anything really, no way to know. However, what happens is that the bootloader is able to boot signed kernel.sin files but not the unsigned kernel.elf

About the bootloader [Again]

I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?

Yesterday, motorola mobility rep. posted this on their Google+ page
Motorola ATRIX HD at AT&T will have a locked bootloader to meet requirements; our goal is still to provide a way to unlock the bootloaders on our devices to those who wish to do so, more details will be shared as soon as we can.
Click to expand...
Click to collapse
The question is, what that really means.

popcorp said:
Yesterday, motorola mobility rep. posted this on their Google+ page
The question is, what that really means.
Click to expand...
Click to collapse
Probably another lie from them.
Sent from my ICS Defy

NITRO_100 said:
Probably another lie from them.
Sent from my ICS Defy
Click to expand...
Click to collapse
I do not doubt. Motorola has a terrible historical. But i really enjoy the Defy and wouldn't like to have to change my device to update kernel/android. I'm really wanting to play the fool to believe in fairy tales at the time :laugh:

I want to believe in this fairy tale this time.

I have a RAZR and just got the official ICS on it. I like my defy more than my razr. I wish I could put ICS on here.

iolinux333 said:
I wish I could put ICS on here.
Click to expand...
Click to collapse
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654

Martijn1971 said:
Huh? Why not try ICS CM9 from devs Quarx and Epsylon3? Or even better, wait a few days and flash CM10 Jelly Bean...
OT: time to spam their Bootloader discussion forum again:
http://community.developer.motorola...ader-discussion-board/td-p/22108?pubid=987654
Click to expand...
Click to collapse
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.

Kazid said:
Martijn, you know...you can try Quarx end Epsylon3 ROMs. I'm doing this right now, and since we got the dualboot, i'm testing a lot of ROMs. But we have a great problem, our kernel. On Jelly Bean android will receive great improvement on the sdk and with the system, like App stack navigation or Network service. Much of the improvement are done on the system, but some of then could request new implements from the kernel. A example could be the use of the NFC ( Near Field Communications ). It's on the kernel how to initialize on care some IRQ from the hardware. You could build a module to load how to care with NFC from the Android OS, but if it would build on kernel (like it could be from new linux kernels). And things like Dynamic writeback throttling, performance on reading or size limit from file systems
Take a look on this: http://kernelnewbies.org/Linux_3.1
Much things i can do on CM7, using kernel 2.6, like the wiimote, so why this would be news on kernel 3.1? 'Cause there, isn't the OS that is caring the NFC or the wiimotes, but the kernel. A such difference is a example that could make a new version of the Android flow better on our device. And things like this we just get with a bootloader opened.
Quarx end Epsylon3 are doing a great, a extraordinary work! I salute them! But as the Android evolves, they work get even more hard if all that could be on kernel, they have to do with patches or modules on the OS. Praying for a open bootloader isn't just to ensure that we gonna have updates until or device could run it and be moneymaking for the developers, but is a way to ensure that this work will be more easy (and probably faster) to the developers too.
Click to expand...
Click to collapse
Opening the bootloader is not the only way to load a new kernel. Kexec was designed exactly for that. It's possible on android -- kholk have got that to work on RAZR already. There were some problem on defy, but I think it is not impossible to fix.

I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app

t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3

nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
I think it gets not burnt... it just crashes, panics and in consequence the defy(+) reboots.

nidhish91 said:
As far as what I've read, the radio is burnt completely if we try kexec.
S3nt fr0m my D3fy/w1u1 GB st4BL3
Click to expand...
Click to collapse
Thought we could exclude the Radio and use just USB/Audio =/
Didn't they used "burn" just as a expression?
Our Kernel can load modules, can't it reload them? We use a module called mod2 who kicks in after to add to the first module? Or to override the first one. It's a lot like kexec but with the modules, not the kernel.
Sent from my MB525 using xda app-developers app

Kazid said:
I had almost lost hope of getting unlocked bootloader when I saw a new hope with the launch of Galaxy S III.
How many of you know, the Verizon version of this device is locked with the bootloader, while others appear to be unlocked. Even knowing how bad this is, this may be an opportunity for many of the models with locked bootloader have a chance.
What I mean is that, like the S III, we have some defy's around the world with unlocked bootloader (most of them in china so observe here for the XDA). Would I be so foolish to believe that with a device such as the S III target, there is a possibility of unlocking the bootloader by developers? And this means of release could somehow help with the release of the Defy and many other devices with locked bootloader?
Click to expand...
Click to collapse
t0n0n said:
I may be wrong, but can we use the kexec to solve the actual problem with CM10? It won't work for Radio but we can use it for USB/Audio?
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Samsung's different. Nearly all Samsung devices have unlocked BL. Nearly all Motorola devices have locked BL.
They tried using oem fastboot on the Defy but it didn't work so well I don't think.

droid_<3er said:
I remember something called "Project Cheesecake" and "Operation MOSH" from like, a year ago.
Petitions did not save our Defy from a locked bootloader.
Click to expand...
Click to collapse
Here's the thread for cheesecake.

[S][DEV-ONLY]HTC Sense

This isn't another one of those 'can somebody port Sense' threads.​
Please note that this thread is for developer-oriented discussion. If you don't have anything to say to help development, please refrain from posting here.
Also note that ideas are welcome. Just check if the idea you're about to post has already been posted by somebody else.
Right now, it's just multiple people working on this. No team, just individuals.
As of the last edit of this post, there has been little to no progress:
I'm constantly working on builds. The current, and the only goal I'll be striving towards as of now is using a T-Mo HTC One X ROM in combination with RaymanFX's CM10.1 RC2 build.
XDA RC @abcdjdj has reported that he has fixed a lot of errors in his build, and is now stuck at the bootanimation. If you can help him in any way, here is what's wrong with his build. He's using FXP's CM9 as a base and a 4.0 HTC One X with Sense 4 ROM as a port.
The OP will constantly be updated with any progress anyone makes.
We're currently using this XDA thread to help us port the ROM.
--------------------------------
​Here's everything I have to share on my build:
PORT: HTC One X, T-Mobile Edition| Android 4.2.2
BASE: Sony Xperia S, nozomi | Android 4.2.2
------------------------
ITesters needed. If you can work through adb commands and can provide me with logcats, please leave a post about it in the thread.
And finally, a note to anyone that may be cursing me for working so very slow (because I admit, this is very slow):
Please understand that all this isn't easy for me. I have painfully slow internet, making each download at least one hour, and thus a pain. My time on this project is limited every day, so progress is slow.

Reserved.

someone755 said:
Okay, so this is the work that has already been done and some of the mysteries that puzzle me right now:
I've edited the CM9 kernel's ramdisk, like stated in the tutorial I'm using (see post 1). As of now, the kernel itself is broken and even if the ROM was complete, not even the booting would work. (Well, booting works as far as showing the boot logo (the green FXP one) goes. But the LED notification light for entering recovery doesn't light. Bootloop over and over...)
Many of the lib files intended to be copied from one lib folder to the other are missing on our Nozomis... My question is, what are the consequences...?
My main issue here is that the zip won't flash. The recovery (no matter which I choose) just returns an 'ERROR' and refuses to flash the file...
Another question would be how to repack an .elf kernel into a boot.img. Because now, I'm trying with letting the CM9 kernel in the zip (since it is an .img) and then flash the modified .elf kernel that I repacked with Flashtool. Inefficient, but at least there's a way.
So currently, the priority list would be:
1.Get zip to flash
2.Fix kernel
...Not necessarily in that order. We could fix the kernel first, but there isn't much gain to it if the ROM zip can't even be flashed to test if it truly works...
Click to expand...
Click to collapse
Bro, it may be possible to get Sense on our devices. Even I have been working on getting Sense booted on our device. My status:-
PORTED FROM - HTC ONE X
BASE - FXP 215 CM9
STATUS - Gets past kernel and even loads bootanimation. Fixed many errors in the logcat. Gets stuck at bootanimation and even displays a message saying that System is not responding, would you like to close it.
I couldn't manage to fix any more errors in the logcat so I gave up but you have rekindled my spirit to get Sense booting on out device. I will upload my rom soon along with the logcat.
Cheers,
abcdjdj

Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?

someone755 said:
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
Click to expand...
Click to collapse
Not fully booting but I think close to booting. I followed the guide mentioned by you in the OP and one by one eliminated all errors that I could eliminate. I had been working on Sense for around a month during my school holidays but now I am not getting any free time. And yes it is Sense 4 (Android 4.0.4).
Sent from my LT26i using xda app-developers app

But isn't the Tegra3 completely different than our FUJI board?
Especially the graphics, those must be out of control on your ROM...
If I were you, I'd at least take the AT&T version of the HOX.
Oh yeah, I forgot to ask: is it the same if I try and port from a MSM8260 board (the same as the Xperia) and the later S4 Qualcomm versions (used in the Xperia T, AT&T One X etc.)? Because porting from a CDMA phone (HTC Rezound) seems to make the work harder...
Thankfully, my summer holidays have just begun, so I have plenty of free time (that's also the reason I started my project).
P.S.
Yeah, maybe that's exactly what I should do. Ditch the CDMA phone and start with the Snapdragon S4 One X!
I would prefer Sense 3.x, but oh well, at least Sense4 is also Sense

http://www.xda-developers.com/android/sense-4-ported-to-sony-xperia-devices/
I just found this. It's not even that old...
Anyways, I've been thinking if the devs of this would be able to help us.
This development stuff gets boring pretty quick when you do it for the 10th time

@samuel2706, could you give these guys a little hand?

But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?

someone755 said:
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
Click to expand...
Click to collapse
Yes,, maybe, but he also could give a little help. Can't he?
Sent From my LT26i using Tapatalk 4

Contact the guy who did this http://forum.xda-developers.com/showthread.php?t=2184706

Well, I thought I'd make this thread so that devs could help each other to actually work together and create a working Sense ROM. So naturally, all help is welcome from anyone.
Anyways, I'm on my way to finishing yet another try, this time with the AT&T One X. Fingers crossed that it at least makes it to the bootanimation.
EDIT: I see that the easiest way to get Gapps is with including the default /data folder from the original HTC ROM (with vending, youtube etc.). But I have to add that to the updater-script. So, I want to ask, is /dev/block/mmcblk0p14 the data partition on the Nozomi?

What's happening?

samuel2706 said:
What's happening?
Click to expand...
Click to collapse
Hi,
I am porting [or trying to port] Sense 4 from HTC One X to Xperia S. I used FXP 214 CM9 as a base. I followed this guide - http://forum.xda-developers.com/showthread.php?t=2245786
Then I fixed as many errors as I could by checking the logcat and got it till the Bootanimation. But now I need help to get it to boot. So, I have attached the logcat from my latest build.
Thanks for your help,
abcdjdj

Maybe copying a few more files could help. Maybe act like your xperia is a HTC device? http://forum.xda-developers.com/showthread.php?t=1222746
Could be worth a try and play with this copying a bit...

Seems to be failing at dalvik; very strange, it doesn't show any major errors on first glance however I'll take a longer look at when I can, however I can link you to this thread that may help you in the meantime Porting

What about this one? http://forum.xda-developers.com/showthread.php?t=2276871
Nice and automated, but the question is, will it work?
I'm trying it with the HOX, just need to wait for it to copy to the phone...
All this seems like a big race -- who will get it working first? Hyped!

Kinda makes me wish I still had my xperia S I could have given this a real good go at; but instead I have a galaxy s4, so it's going to be mostly logcats and such I can help with, I don't like blind building things; made that mistake before.

A blind build is better than no build. Unless it makes bricks...
Thanks a lot for helping out.
Though I'll never understand how a pro HTC dev can go to Sony and then Samsung. ;P
I just hope THIS time my kernel will boot... Cause if it doesn't ... [censored]...
EDIT: Okay, [censored] is happening... Why can't I make this zip flash? I've done it a million times, but all I get is ERROR... ;-;

unfotunatly, i'm not a dev. but i really like the idea. specially if considering porting htc one sense version to our nozomi. i think it would fit like a glove

Android&Linux dual boot?

So ... I'd like to dual boot a normal linux on that tab.
My first problem is something like a boot loader that let me select wether to boot android or any other system (with touch capability and timeout ideally).
Some googling around didn't bring anything useful besides "it's highly dependent on the device".
Is there something like that out there? The alternative I thought of is to build something like the Ubuntu Phone boot app, but I have no idea how it works.
The next problem would be hardware support, but I will look at that issue later.
The chroot solution would be a fallback (I have to look deeper into, especially in terms of performance), but I'd prefer to have a real system.

hofmann.christian said:
So ... I'd like to dual boot a normal linux on that tab.
My first problem is something like a boot loader that let me select wether to boot android or any other system (with touch capability and timeout ideally).
Some googling around didn't bring anything useful besides "it's highly dependent on the device".
Is there something like that out there? The alternative I thought of is to build something like the Ubuntu Phone boot app, but I have no idea how it works.
The next problem would be hardware support, but I will look at that issue later.
The chroot solution would be a fallback (I have to look deeper into, especially in terms of performance), but I'd prefer to have a real system.
Click to expand...
Click to collapse
Just to clarify which exact tab s fo you have, you say also you will look into the issue of hardware support later....this is the wrong order im sorry to say and many people will agree its the first thing u shud look at.....for example it has to be taken into account that your using an arm processor and u cant just use any linux distro on any arm processor e.g arm v5 is different architecture to armv7...meaning a new kernal needed that runs your linux and android...you really are going into waters way above even my head...start with porting cynogenmod completely from scratch...look st compiling your first real rom and you will learn A LOT and MAY begin to comprehend what your asking here....not meaning to sound god almighty but honestly this involves a lot of factors.

Well, I am aiming at arch and afaik there should be ARM versions for any relevant CPUs, so this is not that a big deal. GPU and the likes could be way worse.
Also: 8.4", not sure if there are different versions of these besides the storage capacity

hofmann.christian said:
Well, I am aiming at arch and afaik there should be ARM versions for any relevant CPUs, so this is not that a big deal. GPU and the likes could be way worse.
Also: 8.4", not sure if there are different versions of these besides the storage capacity
Click to expand...
Click to collapse
Ok pal all you need to do then is create a kernal that will support both the android 4.4.2 and linux that youve custom built and taylored to your phones specs.
Heres a link to expanded info on linux and arm: http://www.reddit.com/r/linux/comments/2n21i2/can_arm_chip_linux_servers_run_all_software_or/
Heres a link to building kernals : https://source.android.com/source/building-kernels.html
And heres a link to your specs something you WILL need : http://m.gsmarena.com/samsung_galaxy_tab_s_8_4_lte-6435.php
Please keep me updated on this as if you put all the effort in needed then it would a nice self achievement...good luck m8.

pdolton2000 said:
Ok pal all you need to do then is create a kernal that will support both the android 4.4.2 and linux that youve custom built and taylored to your phones specs.
Click to expand...
Click to collapse
I thought about that, too. But that may be especially hard on arch due to regular updates. It still may be possible and I will have a look at it, but I'd prefer multiple kernels to choose from.
Also: Does having one single kernel in any way help with the boot choice problem?

hofmann.christian said:
I thought about that, too. But that may be especially hard on arch due to regular updates. It still may be possible and I will have a look at it, but I'd prefer multiple kernels to choose from.
Also: Does having one single kernel in any way help with the boot choice problem?
Click to expand...
Click to collapse
Well without one single kernal you cant boot anything...why go though making a bootloader to something when youve got nothing to boot yet? The bootloader is the easiest part its the rest thats the harder. Heres an example of bootloaders that shows its more than possible.
https://play.google.com/store/apps/...droid&pcampaignid=APPU_3DrCVJj1A8vW7AaIu4HQDQ
And the designer is a member of XDA so i say again you first need to build kernal and linux that are compatible with your hardware....then contact this bloke who made MultiBoot and when he sees all the hard work you put in he will be more than happy to help you i should imagine.
---------- Post added at 12:26 PM ---------- Previous post was at 12:18 PM ----------
pdolton2000 said:
Well without one single kernal you cant boot anything...why go though making a bootloader to something when youve got nothing to boot yet? The bootloader is the easiest part its the rest thats the harder. Heres an example of bootloaders that shows its more than possible.
https://play.google.com/store/apps/...droid&pcampaignid=APPU_3DrCVJj1A8vW7AaIu4HQDQ
And the designer is a member of XDA so i say again you first need to build kernal and linux that are compatible with your hardware....then contact this bloke who made MultiBoot and when he sees all the hard work you put in he will be more than happy to help you i should imagine.
Click to expand...
Click to collapse
EDIT
If you wanted a quick way out of all that i can only suggest emulating linux on android...find an example here:
https://play.google.com/store/apps/...droid&pcampaignid=APPU_FT3CVObxNIOa7gbxwYDACg
Good luck anyway pal hope it goes to plan

It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.

hofmann.christian said:
It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.
Click to expand...
Click to collapse
Haaa whats the chances, i only thought of that last minute, hope it works out man

pdolton2000 said:
Haaa whats the chances, i only thought of that last minute, hope it works out man
Click to expand...
Click to collapse
Well, so I am back at the "I need a boot manager" square just with the information that there is something like this which just doesn't work for now.

hofmann.christian said:
Well, so I am back at the "I need a boot manager" square just with the information that there is something like this which just doesn't work for now.
Click to expand...
Click to collapse
Sorry pal you want a boot manager to run this emulated version of linux? This works by emulating it inside android os? Or have i misunderstood?

pdolton2000 said:
Sorry pal you want a boot manager to run this emulated version of linux? This works by emulating it inside android os? Or have i misunderstood?
Click to expand...
Click to collapse
Who said something about an emulated Version? I want a real full fledged Linux to dual boot on a tablet.

hofmann.christian said:
It looks exactly like what I need. The screenshots are suggesting that regular linux distributions are running as well.
If this would be compatible with this device I'd stuff ALARM with an sshd on it and work my way from there.
Click to expand...
Click to collapse
Misunderstanding thought you were refuring to the edit i made just above this post im quoting in its original place.
Ok so you now no the idea of bootloaders exist and for them to work you need linux and a kernal ie an os otherwise theres nothing for it to boot, you need to compile a compatible kernal and lixux distro together thats going to work with your spec so then someone else can help you with the bootloader that will dual bot both it and android...otherwise your asking somebody to draw a design of a building and predict the levels of the foundations before the land itself exists which cannot be done.
Ive provided you research material in kernal design, the specs of your phone, about how linux and arm work together, ive provided you with a link to a bootloader exactly like what your after made by a member on xda whom u can see links to in the download of it to show that you have a place and a person to ask who specializes in the field once youve created what you want to dual boot with android.
Theres nothing more that can be done pal its all been made very clear.

Cm-13.0 - development/discussion thread

Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.

Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0

Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.

good luck you guys
i have really nothing to offer ..
but please make this happen ..

Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk

Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:

It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont

Cm we want... thank you for your interest!! ?

Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1

why is there not one custom rom for this device?

Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!

Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.

Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.

Yes we can! Yes we can! Yes we can!

Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.

gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?

Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.

gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.

droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.

No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.