Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official. Officially supported device get automatic builds which are made available at dl.twrp.me/<device_codename> at each major release. Thank you.
Download : My Website
XDA:DevDB Information
TWRP for HOT 2, Tool/Utility for the Infinix HOT 2
Contributors
MSF Jarvis, Nonta72
Version Information
Status: Testing
Created 2016-04-13
Last Updated 2016-04-13
MSF Jarvis said:
Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official.
Click to expand...
Click to collapse
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Nonta72 said:
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Click to expand...
Click to collapse
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
MSF Jarvis said:
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
Click to expand...
Click to collapse
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Nonta72 said:
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Click to expand...
Click to collapse
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
MSF Jarvis said:
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
Click to expand...
Click to collapse
Sure
Let's make it work! :highfive:
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
In 15 minutes, there will be twrp-3.0.2-2 available there. If you're interested to see what I did to it, check the commits
This one has logcat enabled as well, so you may wanna help me that way. I don't do WhatsApp, so you may want to hop on to #team-redux on http://webchat.freenode.net rather.
Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
MSF Jarvis said:
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
Click to expand...
Click to collapse
Nonta72 said:
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Click to expand...
Click to collapse
Another test build is up : 3.0.2-2
MSF Jarvis said:
Another test build is up : 3.0.2-2
Click to expand...
Click to collapse
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Nonta72 said:
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Click to expand...
Click to collapse
Maybe I should, but where's the similarity?
MSF Jarvis said:
Maybe I should, but where's the similarity?
Click to expand...
Click to collapse
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Nonta72 said:
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Click to expand...
Click to collapse
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
RendyAK said:
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
Click to expand...
Click to collapse
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
MSF Jarvis said:
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Click to expand...
Click to collapse
Because MT6580 is a recent version of the MT6582. Forget the "2" that became "0" at the end. The MT6580 is even faster than the MT6582 and can match some MT6592 (with 1GB RAM). I saw a 33,000+ antutu on a MT6580 (with 2GB RAM) and overclocked (yes! overclocked, idk how but they said so).
MSF Jarvis said:
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
Click to expand...
Click to collapse
Sir, you're talking about the messed up ramdisk. In fact, there are many builds, the one you have seen have many bugs probably because of the messed up rcs.
The only recovery that works good for me is the one made by Ovatek. I made few commits to my github including the fstab file changes you suggested...
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Nonta72 said:
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Click to expand...
Click to collapse
Actually speaking, the OEM for the MT6582 device went with naming the device 'sprout', which I vehemently oppose, to avoid confusion. The stock boot.img's ramdisk also contains files according to the 'sprout' nomenclature. I took the sprout4 device tree, updated all *.rc's from the stock marshamallow boot.img and added in a bunch of TWRP flags.
One important thing you most probably already know, Infinix Hot 2 uses a standard MTK boot.img header, while the LAVA Pixelv1 uses an AOSP format, so it can be unpacked using standard tools, while yours requires Carliv's kitchen.
Related
Hello,
Developers, I really need help to get the ubuntu-touch port working again!
After the first release of Ubuntu-Touh I tried to port it again to our devices, but I don't get them booting. I only get a black screen. I have updated all sources on github and made the appropriate changes. You can find all relevant sources and information on my new website http://danwin.github.io/ubuntu-touch.html where I have uploaded the non-bootng builds for developers.
I still have the old builds available for those, who want a booting ubuntu-touch, but without any functionality: http://danwin.github.io/ubuntu-touch.html
it is so laggy on mini Dude :/
screenshot please
rod555 said:
screenshot please
Click to expand...
Click to collapse
there is already a video available, but I have made some Photos of my Neo V, sorry for bad quality: http://ubuntuone.com/6keWFpFBG0kEsVF7mBF54D
Can you add the screenshots in the op as pic
slimmer2 said:
Can you add the screenshots in the op as pic
Click to expand...
Click to collapse
I don't think this is really necessary, as I have a video from kakalko4 embedded there, which has a lot better quality than my screenshots. You can download the zip provided above and unzip the pictures inside, if you really want to see them.
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
MarioJerkovic said:
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
Click to expand...
Click to collapse
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
DanWin1210 said:
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
Click to expand...
Click to collapse
Yep done it and working ubuntu is working it lags a lot :/ but i dont care i am happy that we got Ubuntu on our old devices
I take it this a the same one as we already have? (crappy demo with no gsm)
replicant101 said:
I take it this a the same one as we already have? (crappy demo with no gsm)
Click to expand...
Click to collapse
For now yes, but hopefully officiallysonyrebel can make the kernel patches in one or two days available, so I can rebuild all images to make the daily builds of ubuntu booting, which have a lot of improvements.
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
emwno said:
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
Click to expand...
Click to collapse
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
DanWin1210 said:
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
Click to expand...
Click to collapse
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
With kernel patches, can performance be addressed?
emwno said:
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
Click to expand...
Click to collapse
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
replicant101 said:
With kernel patches, can performance be addressed?
Click to expand...
Click to collapse
Maybe, but the daily builds of ubuntu have a lot better performance and stability than the mwc-demo image, which is currently the only booting version.
DanWin1210 said:
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
Click to expand...
Click to collapse
Yes, others did have a blackscreen, even the n7100 users did. But some, including myself got it to boot.
This is what I did:
1. Wipe system / data / dalvik
2. install device part
3. install ubuntu image
NOTE: You made a new partition on the sdcard where ubuntu was to be installed. I recommend you to WIpe your sdcard, create a new partition and try again. Also try with try flashing with a different recovery / kernel then flashing the ubuntu kenrel in the end. Sometimes recoveries mess up.
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
d4k-pho3nix said:
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
Click to expand...
Click to collapse
Normally status 0 means success, can you go in CWM to advanced -> show log and enter the output of this here, maybe I can help you.
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
First thanks o.o
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Brawn_Sg said:
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Click to expand...
Click to collapse
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.
I will be trying a clean build 2day.
ashwin007 said:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
Click to expand...
Click to collapse
Which version of cwm recovery is in the build?
gud work
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
goutamniwas said:
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
Click to expand...
Click to collapse
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
EDIT:Well @ace312 its no more cwm in cm tree.its cyanogen recovery made by cm
ashwin007 said:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
Click to expand...
Click to collapse
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
goutamniwas said:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
Click to expand...
Click to collapse
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.
Hey,
Why don't you flash system.img and boot.img with fastboot?
ace312 said:
Which version of cwm recovery is in the build?
Click to expand...
Click to collapse
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
GeekyDroid said:
Hey,
Why don't you flash system.img and boot.img with fastboot?
Click to expand...
Click to collapse
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
okay. it's been months I left ROM development. Sorry about that.
ashwin007 said:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
Click to expand...
Click to collapse
Well, sorry I thought it is less than 215MB. I didn't think of it.
My last device was a motorola defy and developer @Quarx has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.
Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.
Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!!
•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•
see the attachment...
Lolipop is more closer...
This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.
http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1
I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:
Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.
If you have a question, SEARCH FIRST, per the Forum Rules
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
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
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
NeoPreacher said:
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
Click to expand...
Click to collapse
Finally!!!
Let's gooooooooooo!!!!!!!!!
It only took them a year and three months to release it.
Oh god...
NeoSDAP said:
It only took them a year and three months to release it.
Oh god...
Click to expand...
Click to collapse
lmao
Snapdragon_Mid_2020.SPF.1.0.1R_r00024.0
lol it makes even more sad.
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Zylam Marex said:
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Click to expand...
Click to collapse
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
nice. they can now close 1k issues regarding spes kernel. hahaha
pulsar said:
nice. they can now close 1k issues regarding spes kernel. hahaha
Click to expand...
Click to collapse
There are some people fixing the issues with source already!
NeoPreacher said:
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
Click to expand...
Click to collapse
Oh wow really, tape2wake works great in PA? I have tried almost all roms but PA. Thank you for letting me know, a shame the Kernel is missing drivers and such. I wonder why Xiaomi is trying to make sure the Note 11 is never developed for, it's such a good phone with a custom rom.
BerserkSlayer said:
There are some people fixing the issues with source already!
Click to expand...
Click to collapse
Haha I think Pulsar was referring to Xiaomi's github page where there would be like 10 posts a day asking for Spes kernel
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
aureljared said:
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
Click to expand...
Click to collapse
yes
Much easier to compile this kernel using Clang rather than GCC. Still getting used to it, it's been a good while since my last kernel compile, haha.
Does anyone know how to build a new boot image by hand? I have a working boot.img for PixelExperience and I'd like to replace the kernel with one that I built for testing, but I'm not sure if I should still use mkbootimg like with older Android devices as this is the first time I'll be dealing with a device that uses dtb/dtbo files. Any insights would be welcome.
aureljared said:
EDIT: board_id.h is present in the same directory, not in include/.
Click to expand...
Click to collapse
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
SAM209 said:
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
Click to expand...
Click to collapse
For one, it is theoretically easier to keep the device up to date without having to wait for Xiaomi's updates. Some changes that come with Android's monthly security patches are made to the kernel, for example, and having the kernel source code means we can apply those patches faster than if we were to wait for updated kernel builds from Xiaomi.
Some ROMs like LineageOS also require kernels to be built from source (i.e., not prebuilt) for a device to be granted official status.
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
jasmin811 said:
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
Click to expand...
Click to collapse
There's nothing to flash here. Only the link to the kernel source. There's still some work to do for a flashable kernel (compiling eg). Also there are drivers missing in the source it seems. What you tried was flashing the uncompiled kernel source package i guess and that.. doesn't work
Oh ok,I though it was finished already.