Related
I read couples of threads and realize that if a CM mod is wanted, MS2 must have its bootloader unlock.
Since most work is done in /system partition, why do a bootloader modify is needed?
According to the update.zip, we can modify /system partition already, so why do we need bootloader unlock?
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
momus87 said:
CyanogenMod needs its own kernel.
I guess that, since cyanogen is based on gingerbread now,
it runs with a more up-to-date kernel than the milestone's.
The locked bootloader and the efuse thing prevents updating the kernel.
It's possible that someone, using Cyanogen source, makes a backport running on our kernel, but I think it's a huge work...
However, the clever guys from freemymoto.com have created a hack that is capable of launching an other kernel after the legit one starts.
If salvation comes (Cyanogen alleluia ), it will certainly come from this project.
Actually, the hack works on DroidX, and Droid2. So it is 99.9% sure that with some work, it may run on milestone 2 as well.
So, to get Cyanogen work on MM2, we need :
- A very good developer, with android (of course !), linux kernel and kinit knowledge, able to port freemymoto's hack, and Cyanogen
- Hardware drivers for the Milestone (bluetooth, lan, gsm, 3g, touchscreen...)
If we find the golden dev, I personnally think that CyanogenMod could be out for milestone2 sooner than what most people think...
Click to expand...
Click to collapse
I LOVE YOUR REPLY!
Well, this is the first reply to me in this forum.Ya...nobody reply me before...so bad..
Milestone has also a locked bootloader, but a CM7 port running on it. That is what makes me want to do something on my MS2.
I'm a C++ programmer, so I learn everything about this these days.
Thank you, really.
And I think I'd read all the freemymoto.com site RIGHT NOW~~
Well, if you think you can be the golden dev, you just made my day...
If you try this, I (and almost everybody here) will at least help providing the hardware drivers.
But the first step is to make the hack work on MM2...
Edit : For the milestone1, the bootloader security has been compromised using a leaked unofficial rom build,
which lead to custom kernels, without needing a hack like freemymoto's.
In fact, freemymoto's hack is based on a milestone1 project, which was abandoned after the rom leak.
It circumvents both bootloader lock and efuse by starting a second kernel after the first one.
(What I couldn't figure out is what happens of the first one... Still in memory? Still using some ressources?)
I read the site yesterday, however sadly, I don't have any experience about writing drivers of cell phone.
So I just sent a e-mail to them to ask if I can provide any help and what to do.
Hope I can help. I'll try my best.
For about the second kernel...I guess I have to read source to know what happened to them...
Anyway, thank you for your reply. At least I get a way to help^^
I didn't mean that we will have to write the drivers from scratch. But we will have to find them.
Hopefully, most of them are open-source. Wifi/bluetooth per example, is handled by a wl1271 chip. Drivers are available on texas instruments website...
You should get in touch with Pizzaroll, who is also trying to make the hack work on milestone2
It's really good news that there maybe a hack bootloader, i like my mm2 but it is really a pity that no much ROM.
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
I don't think that distributed computing is the solution...
Even if the boinc project lets us find the signing key, we will have to do the same for the efuse thing.
The freemymoto's hack is a solution to circumvent both of these protections, and doesn't need any computing.
We only need someone to modify some parts of the code to make it work on Milestone2.
Tomszyn said:
liuyanghejerry...
Polish team try to broke bootloader with Boinc (many computers calculate 1 thing), maybe You and Yours friends can join to project?
In China lives maaaaany peoples, this can be speed up calculations
Click to expand...
Click to collapse
Currently I'm studying kexec method now, thanks to PizzaRoll and momus87's help^^
Well, in fact, I like to program and burn my brain. However, the Boinc method seems not really interesting...
Well Boinc is the best solution if you want to use bruteforce.
But even with a whole army of core i7, bruteforcing a 1024bits key is unthinkable actually...
Is this eFuse thing harder to break than the one used in iPhone? If it is then Mr Jobs should adopt a similar approach.
I would really like to get the OS updated on this device, I'm sure I'm not alone.
I've been following many of the guides on this forum, or youtube videos, but with no luck.
Is there anyone who can help me to figure this out better?
Building AOSP or Porting Cyanogen mod would be ideal, is this possible?
I have had the original a7 since it was released and the major hangup has always been, the kernel. The kernel source for 2.2 froyo has been released, but, no one has made or ported a kernel past that. Dexter the great did a lot with only that kernel, CM7 and Honeycomb, but limited because the old kernel. We need a 3.0 kernel for CM9/10 to really move. There are similar tegra devices that have Honeycomb and beyond, but swapping kernels has been reported to only partially work. I hope that it will happen one day, this baby is powerful.
So beyond my ranting we need, device tree, drivers, and a kernel.
I have been trying myself to push all sorts of Linux for Tegra (ubuntu, gentoo, and geexbox) as well as trying to figure out how dexter had started running ICS on his before he dropped the project.
What is known: this is an abnormal Harmony tegra 2.
What you need to know for APX: A7+ uses hsmmc interface, so all nvflash designed for nand or emmc will inherently fail (or at least has been the case thus far)
I dont know how exactly this is, but due to its odd nature most prepackaged or script made bootloaders will fail. I'd love to see ICS or JB on this device for sure, but making an APX backup would need a new bootloader, or at least a new boot.img for sure.
I'm a tinkerer, with very little programming skill. I can google as good as anybody though lol.
Somebody needs to design an uber cross-compiler that can just transform the kernel to 3+ so we can stop wishing for new firmware and just have it lol
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
What about use a base of stock roms and make the things work??? I know Cm its for armv, but all its adaptable,
Enviado desde mi XT890 usando Tapatalk 2
as for MIUI (there already is a MIUI port on the razr i, not complet I think, but it exist). MIUI is mostly a framework mod.. this is platerform independant AFAIK.
I don't think CM & Cie are so dependant of the SoC architecture. There's lot of différences between some ARM SoC .. maybe more than you can imagine. If CM can be adapt to so many device with so many ARM SoC witch a so différent, why not for a x86 Soc ?
I think you're a little bit pessimist here...
I didn't say it's impossible but it's more complex then a normal port for an ARM device. The issue is it requires more knowledge on the issue and will eat far more time. A CM port to x86 is a very unlikely goal for a single dev , and I'm saying this because a few months ago I discussed this issue with the people behind Android x86.
So a talented DEV will be able to achieve this but it will take time and a bigger struggle , that's why to start of developing for this device it would be more reasonable to look at Android code already ported to x86.
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
Sure there is some ARM dependent code in the repos but most of android doesn't really depend on the arch (like apps using the sdk dont need to be recompiled for working on the I, see play store apps). I have worked with o1 and android-x86 and there isn't really that much change from CM and android-x86, just some extra optimizations for x86 which can be added in later.
There are plenty of device on where even custom rom seems to be impossible. mostly because of a locked bootloader.
Look at the Motorola Defy. At the beginning, the development of a custom rom like CM was pretty impossible.... but they did it. They did it so far that the Defy became one of must used device with Cyanogenmod. And you now the most astonishing? It's thanks to only 2 devs.
I think bypassing a locked bootloader like the Moto one is far more tricky than adapting a CM ROM to a x86 SoC (while the device is natively unlocked).
AFAIK, android-x86 project is not so close to the Android we have on our phone.
When you develop a custom rom you can either take the AOSP source and try to put it on your phone : the tricky way. Mainly when you don't have access to the source of the drivers (ARM or x86 .. same fight)
Or you can take the official rom and mod it to reach the AOSP/CM/MUI/etc level. And I think on most device it's the way to go (unless the manufacturer release all the source code of the device.... something that never appends).
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
You really know what you are talking about? As others already mentioned above CM is in most a framework - porting android to x86 seems to be not such a big gap as motorola did it already and for sure you can run android on your pc - do you own an arm pc (in this case i think an rasperry pi...). The toolchain remains the same so why you make such a story out of it? Are you a razr i owner or do you just want to frighten all razr i devs and owners awaiting a CM port??
ARM architecture is different in some points but most of the work will do the compiler and to be honest i think there will be some more x86 phones in the future, intel never developed it for one or two phones....
So what is your intention with this topic??
kind regards.
lord0815 said:
So what is your intention with this topic??
Click to expand...
Click to collapse
That's what I'm wondering. Any dev that's taking on this task obviously knows it's going to take a bit of extra work. It would have been different had the OP offered some help and advice, but he just posted the obvious while making it seem like a bigger deal than it is (at least I'm guessing it's not as big a deal as he makes it seem, considering the other posts in this thread). Nothing but fear mongering and pessimism at this point. Sure, we will have to wait a bit for the devs to figure things out, but I know enough of them picked up this phone that something will eventually come. Plus, there seems to be a bit of dev interest in the Intel Yolo as well.
I don't know much about porting or developing and getting cm to run with all the necesary source and drivers is probably not easy but I do know that one of the basic options when running the build/make command for AOSP and CM is an x86 build for emulation. So basic x86 infrastructure exists does that ensure compatibility with this phone maybe not but it might help and certainly it would still require SOC and device optimization drivers but its probably the better place to start then tackling trying to port ARM based code and drivers.
However in the meantime my thinking is maybe a CM style rom could be achieved by first stripping down the rom making it "blurless" and then porting CM features especially since the latest Moto ROM's are comparatively closer to stock then sense or touchwiz. Of course I don't have the phone yet its in England waiting to be brought to me.
Hi buddies, i create a petition to Xiaomi for release the kernel source.
You can sign here, it's free : https://www.change.org/p/xiaomi-inc...source=share_for_starters&utm_medium=copyLink
Signed
I guess its useless since it isnt a responsability of Xiaomi but Mediatek
Signed ?
I really don't think that releasing kernel source is up to mediatek right now. Simple example is the HTC's One E9, same SoC. On HTCdev site the kernel source is available for free and for everyone. How is that possible?
adaltavo said:
I guess its useless since it isnt a responsability of Xiaomi but Mediatek
Click to expand...
Click to collapse
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
+1 signed
Gesendet von meinem Redmi Note 2 mit Tapatalk
+1 signed
~ Xiaomi Redmi Note 2 Prime ~
Deic said:
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
Click to expand...
Click to collapse
Of course they have it, but Im pretty sure that its illegal for them to release it, since the owner is Mediatek not Xiaomi. Its like if you buy a software for comercial purpouse, it doesnt mean that youre the owner of it and you cant resell it. Here is the same, Xiaomi bought Helio X10 SoC to include it in their phones, and obviously they have source code and permissions to use it, but that doesnt mean they can resell it, or release it to people, they would get involved in serious legal problems.
adaltavo said:
Of course they have it, but Im pretty sure that its illegal for them to release it, since the owner is Mediatek not Xiaomi. Its like if you buy a software for comercial purpouse, it doesnt mean that youre the owner of it and you cant resell it. Here is the same, Xiaomi bought Helio X10 SoC to include it in their phones, and obviously they have source code and permissions to use it, but that doesnt mean they can resell it, or release it to people, they would get involved in serious legal problems.
Click to expand...
Click to collapse
Linux Kernel is under GNU GPL license so no legal problems... Mediatek are a very stupid people... Too the code is modified by Xiaomi, so isn't the original/genuine code of MTK...
Deic said:
As said @nasko_spasko. How to Xiaomi did can build the kernel without source??
Is responsability of Xiaomi, not Mediatek.
Click to expand...
Click to collapse
Deic said:
Linux Kernel is under GNU GPL license so no legal problems... Mediatek are a very stupid people... Too the code is modified by Xiaomi, so isn't the original/genuine code of MTK...
Click to expand...
Click to collapse
Yep, but Mediatek isnt the only one, Samsung also keeps their Exynos code in secret, Huawei with Kirin SoC too, etc. And yep, Linux is free, but... there so many things included in a kernel, it includes system programs that manage an OS, but also includes drivers to comunicate the OS with the hardware (SoC for example), AND are those drivers wich doesnt belong to Linux kernel nor Android OS, that code depends of the hardware manufacturer and they doesnt have any obligation of borrowing it, so if you dont have code drivers you just have an incomplete kernel, AND thats the problem everyone faces with Mediatek
adaltavo said:
Yep, but Mediatek isnt the only one, Samsung also keeps their Exynos code in secret, Huawei with Kirin SoC too, etc. And yep, Linux is free, but... there so many things included in a kernel, it includes system programs that manage an OS, but also includes drivers to comunicate the OS with the hardware (SoC for example), AND are those drivers wich doesnt belong to Linux kernel nor Android OS, that code depends of the hardware manufacturer and they doesnt have any obligation of borrowing it, so if you dont have code drivers you just have an incomplete kernel, AND thats the problem everyone faces with Mediatek
Click to expand...
Click to collapse
Mediatek release the kernel source for helio x10 buddy.
We need the Xiaomi kernel source because we need their drivers from display, touchscreen, etc...
X-Genji said:
Mediatek release the kernel source for helio x10 buddy.
Xiaomi will release their kernel source because we need the drivers from display, touchscreen,etc...
Click to expand...
Click to collapse
wut?
#tapatalknięte
Someone can share it on 4pda and chinese forums?
signed
Mediatek didn't release nothing, the code was leaked but it wasn't useful because it wasn't customised by Xiaomi with drivers.
So Xiaomi have to pay Mediatek in order to get the permission to publish the code
Mediatek must be doing something illegal, violating Qualcomm or some other patents without paying them. That's why they don't want to share their code.
Signed +1
adaltavo said:
is it necesary to be agresive? or are you just a kid :silly:?... And as I said some post ago... Xiaomi doesnt have any responsability of doing that, and maybe they dont have enough rights to release it, and if what you say is true, then those codes must work on ours RN2 since is exactly the same SoC (System on a Chip), this means they must be using same drivers even if they are different phones, since everything is included in the SoC (modem, wifi, display driver, etc.). Maybe Xiaomi uses its own code for MIUI, but thats not necesary for building an AOSP ROM or a CM ROM.
Im not a developer, and Im sure you neither, Im just saying what is obvious for me but I accept I might be wrong.
Click to expand...
Click to collapse
And screen, buttons, camera, IR blaster? There are other components with others drivers
~ Xiaomi Redmi Note 2 Prime ~
SkiFire13 said:
And screen, buttons, camera, IR blaster? There are other components with others drivers
~ Xiaomi Redmi Note 2 Prime ~
Click to expand...
Click to collapse
as I said, screen is included in a SoC (must be), buttons are all the same in Android, just camera and IR blaster might be a problem, but not big enough to not build a ROM. Anyways, an IR blaster isnt such a big problem to handle with, I have worked with them, you dont need special drivers or something like that . And camera... Xiaomi didnt build it, so I guess its a problem of the SoC... So, the problem is from Mediatek, like everything we are talking about here, and if its true that theres codes already released of Helio X10, then all this shouldn´t be a problem, even this post wouldnt have any sense.
Im using Infocus M530 [MT6595] i saw lots of that for MT65xx but only few is worked on MT6595. There is no specific guides for MT6595 for development etc and Mtkdroid,SP flash tool both also not work on my device. Only found "How To Root".Please Respective MTK devs do anything for MT6595 also n help others..
Thank You !
Sorry for my RIP english.
Hello Sahil Sir,
Lenovo vibe x2 is based on same procesor mt6595 and they just rolled out Android L update for their device, is it possible to port that rom on infocus m530 its also shares the same specs.
if it is possible kindly guide me i'll be highly thankfull for ur support.
snandan.gupta said:
Hello Sahil Sir,
Lenovo vibe x2 is based on same procesor mt6595 and they just rolled out Android L update for their device, is it possible to port that rom on infocus m530 its also shares the same specs.
if it is possible kindly guide me i'll be highly thankfull for ur support.
Click to expand...
Click to collapse
Hi,
Lenovo Vibe X2 is having same specifications as you said. I think it is possible to port that rom in Infocus M530 but, before that I want to say that the lenovo X2's L update is having some serious bugs. Please check it. And one more thing, in order to port you need custom recovery. Did ported any custom recovery into your M530. If yes, please let me know. Because I tried lot times & failed to port CWM & as well as TWRP.
No update for our device yet?
No custom rom,No recovery..... Is infocus m530 support dead?
shra1 said:
No custom rom,No recovery..... Is infocus m530 support dead?
Click to expand...
Click to collapse
Nope. Since it is rooted you can directly write to the raw partitions for "flashing" a rom, thus no need for a recovery. But it is too dangerous. One tiny error would brick the device.
Jamesits said:
Nope. Since it is rooted you can directly write to the raw partitions for "flashing" a rom, thus no need for a recovery. But it is too dangerous. One tiny error would brick the device.
Click to expand...
Click to collapse
so better to buy a new phone than waiting for a os update...
I have a zopo zp999 (with a shattered screen so I'm back on ol' faithful - Galaxy Note 2 n7100)
The whole MT6595 I think suffered from being relatively closed source. Even though there was an ubuntu version of the mi3 I think and its source code released, other manufacturers didn't come to the party - like zopo.
Manufacturers are really their own worst enemy for slitting their own throats by being so restrictive with source.
It also might be partly associated with the MT6595 containing a PowerVR GPU.
Non-Mali (ARM) gpus tend to be more closed with their drivers too.
Whereas ARM have been releasing the drivers for their mali gpus for years now.
the MT6595 was the targeted at being a super-mid SoC. The top of its time. I think the last 32-bit CPU, and once the 64-bit MT697x cortex A57 & A53 based product well everyone lost interest really.
It's a good modem. They have a pretty good engineering mode - eg ability to choose LTE/HSPA frequencies.
beyond that... eh...