Develop Bugs

Multi boot with the SDE

Just an idea
I have a Gen9 (root+sde) and i would like to have on the same tablet
Archos rooted
Ubuntu
ICS by letama
Another...
Have you the possibility to create a multi-boot ?

cajl said:
Just an idea
I have a Gen9 (root+sde) and i would like to have on the same tablet
Archos rooted
Ubuntu
ICS by letama
Another...
Have you the possibility to create a multi-boot ?
Click to expand...
Click to collapse
Physically is possible .....remains to be implemented only ! If I had more free time and would not work ...I think I tried something....
Thanks @cajl ...is an ingenious idea !

Possible ? Well, yes and no.
OpenAOS guys wrote a nice boot menu that should work as is on gen9. However, the main problem is that the different OSes are sharing the same kernel.
My ICS kernel differs a bit from original one (touchscreen driver), but it could work with Honeycomb.
Plasma has its own kernel though.
Archos ICS kernel will be different, it's a 3.0 kernel.

Sorry Letama, BIG mistake. (I am sometimes a little bit out of memory with my brain) This was really a big, big mistake from me with my other thread to this.
But im interested, if someone has experiences with this boot menu from openaos which isnt declared es compatible with gen9.
What does it really does, is it able to boot different kernels and initramfs and images and of course - what are the caveeats?
The developers say it is really buggy, even for gen7 and 8, too, and so im "slow" before installing that. Dont even know how to install that and what to do if there is new official fw from archos then.
On the other side, buggy are nearly all bootloaders for pc, too, and there i dont mind so much.
Does someone know what buggy means in this context?

No problem...
Well, no, it doesn't allow multiple kernel/initramfs. What it does is let you choose between multiple rootfs images, that's all. This is ok if the multiple OS can work on the same kernel, but as I said most of the time they can't.
I don't know if it's buggy or not, I never tried it. To use it, you'd have to package a proper initramfs for gen9.

letama said:
Possible ? Well, yes and no.
OpenAOS guys wrote a nice boot menu that should work as is on gen9. However, the main problem is that the different OSes are sharing the same kernel.
My ICS kernel differs a bit from original one (touchscreen driver), but it could work with Honeycomb.
Plasma has its own kernel though.
Archos ICS kernel will be different, it's a 3.0 kernel.
Click to expand...
Click to collapse
What I'm thinking is what kernel does it use? because if it's the G8 kernel it won't do... in that case, how can I remove the G8 kernel in the boot menu and substitute it with a G9 Kernel?... thank you in advance

TjaXanK said:
What I'm thinking is what kernel does it use? because if it's the G8 kernel it won't do... in that case, how can I remove the G8 kernel in the boot menu and substitute it with a G9 Kernel?... thank you in advance
Click to expand...
Click to collapse
Well, when I meant as-is, I was talking about the menu command, not the zImage+initrd which are g8 only. You have to unpack g8 initrd, take command/scripts and port them back to g9 initrd. If you never played with initrds, it's a bit difficult to do.

letama said:
Well, when I meant as-is, I was talking about the menu command, not the zImage+initrd which are g8 only. You have to unpack g8 initrd, take command/scripts and port them back to g9 initrd. If you never played with initrds, it's a bit difficult to do.
Click to expand...
Click to collapse
ok, well thanks for the info... di do some work on my old Gen8, so I might be able to do something with the boot menu... will let you guys know... if it works I'll post back

http://www.youtube.com/watch?v=KZ07Ivmu9OM
What does this video mean? Knows so this guy? (my french is even after learning 6 years so worse ...)

he use this
http://dev.openaos.org/wiki/FBMenu

Yes, and the purpose of his work is to be able to have multiple data partition scheme. It's useful for instance if you want to have a stable environment with your trusted apps and a test one where you install stuff and check if they work properly.
It's not a multiple firmware boot. fbmenu can be used to do a multiple boot at the condition that the kernel remains identical though.

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.

[Q] Cyanogenmod 11 ?

So guys i read this post tonight by cyanogenmod http://www.cyanogenmod.org/blog/this-week-in-cm-nov-9-2013
And i saw this : First, and we’ve said this previously, just because KitKat is touted as being better for lower RAM devices doesn’t mean we will be bringing back support for devices that we’ve dropped in the past. , So i know that out device has 512 MB, but i wanted to ask did cyanogenmod droped support for out phone ???

Why 2 threads?

Xhemal1325 said:
So guys i read this post tonight by cyanogenmod http://www.cyanogenmod.org/blog/this-week-in-cm-nov-9-2013
And i saw this : First, and we’ve said this previously, just because KitKat is touted as being better for lower RAM devices doesn’t mean we will be bringing back support for devices that we’ve dropped in the past. , So i know that out device has 512 MB, but i wanted to ask did cyanogenmod droped support for out phone ???
Click to expand...
Click to collapse
For as far as I know, Ancora was never officially supported. So...nothing to drop.
And..yeah, please, stick to a single thread.

arsradu said:
For as far as I know, Ancora was never officially supported. So...nothing to drop.
And..yeah, please, stick to a single thread.
Click to expand...
Click to collapse
Yeah, i know, but however an unoffical version like cm10.1 will be good to , and yeah u are the guy who made cm 10.2 possible for out phone , meaby u can do something for CM11 , to
and yeah sorry about the second thread i dont know how that did happen , but now cant delete it :

Xhemal1325 said:
Yeah, i know, but however an unoffical version like cm10.1 will be good to
and yeah sorry about the second thread i dont know how that did happen , but now cant delete it :
Click to expand...
Click to collapse
We'll see about an unofficial version of cm11... Please, be patient. To delete that thread, I think you can use the report button on the top right corner of that first post and specify the reason for the deletion. A mod should do the rest.

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.

Huawei variants hardware PAR-LX9 and PAR-LX1M

hello guyz i'm glad to start the first thread of dev thinking about the Nova 3 device
here in middle east (Egypt/KSA) we've got Nova 3 with 4GB ram
i wonder what if we flashed the PAR-LX9 rom on PAR-LX1M device, is that may release the hidden ram to be 6 gb of ram
Huawei used to use the same hardware to all variants and hide/release spects as the marketing needs.

How?
Is it even possible!.. yeah i've been wondering why do we have the 4 gb variant while others have the 6 gb for the same money i guess!. And why would the company lower it's specs on the paper!

I actually own the chinese version (version PAR-AL00) 128GB + 6GB RAM, but I'm interested in enabling the NFC, since it's available for version PAR-LX1 (see official spec, section NFC).
If we find a way to unlock the bootloader (as of now I haven't found a way), then maybe we can somehow merge the firmware from PAR-LX1 (enable NFC) with firmware from PAR-AL00 (enable 6GB RAM)!
Any idea?

aymanshow said:
Huawei used to use the same hardware to all variants and hide/release spects as the marketing needs.
Click to expand...
Click to collapse
Wow. Are you sure about this?

krkuz said:
I actually own the chinese version (version PAR-AL00) 128GB + 6GB RAM, but I'm interested in enabling the NFC, since it's available for version PAR-LX1 (see official spec, section NFC).
If we find a way to unlock the bootloader (as of now I haven't found a way), then maybe we can somehow merge the firmware from PAR-LX1 (enable NFC) with firmware from PAR-AL00 (enable 6GB RAM)!
Any idea?
Click to expand...
Click to collapse
Can anyone confirm?

i think it's not possible because hardware cant be changed /upgraded or manipulated with software IMO

tarekh020 said:
i think it's not possible because hardware cant be changed /upgraded or manipulated with software IMO
Click to expand...
Click to collapse
I think OP's point is that a larger RAM is present in the device hardware, but it is being hidden by software?

Supersonic27543 said:
I think OP's point is that a larger RAM is present in the device hardware, but it is being hidden by software?
Click to expand...
Click to collapse
I don't believe so because its a big selling point

aymanshow said:
hello guyz i'm glad to start the first thread of dev thinking about the Nova 3 device
here in middle east (Egypt/KSA) we've got Nova 3 with 4GB ram
i wonder what if we flashed the PAR-LX9 rom on PAR-LX1M device, is that may release the hidden ram to be 6 gb of ram
Huawei used to use the same hardware to all variants and hide/release spects as the marketing needs.
Click to expand...
Click to collapse
How can flash PAR-LX9 rom on PAR-LX1M device. Please make a thread about how to flash PAR-LX9 to PAR-LX1M?