Jump to content

[REQUEST] ANDROID 8.1 GO - HUAWEI Y300


Recommended Posts

Guest Scofield1990
Posted

Hi to all. Is it possible to create a porting of the new lightweight Android 8.1 GO on the Huawei Y300?

Guest Trapezio
Posted (edited)

The Y300 is dead.

Edited by Trapezio
  • 2 weeks later...
Guest Runjaun
Posted
On 3/12/2018 at 3:51 PM, adeii said:

If you give us 8.1-GO kernel for MSM8225, it could be possible.

Can you make sailfish os for y300

  • 2 weeks later...
Guest adeii
Posted (edited)

Sorry, no for now.

Edited by adeii
  • 4 weeks later...
Guest adeii
Posted (edited)
On 3/16/2018 at 6:32 AM, Runjaun said:

Can you make sailfish os for y300

hybris-boot.img is ready for now... making of hybris-system.img is abandon because of many errors (missing repo, no root user,  huge repos, etc..)

Maybe this porting guide could be easier to follow (even it is for Y6).

Does anybody has (un)official SailFish OS for Huawei C8813 / G525, I could try port it for Y300/G510 ?!

Edited by adeii
Guest madix-333
Posted (edited)

Hi Adeii, maybe this help for build 7.1

https://github.com/ghostrider-reborn/android_device_lge_vee7ds
https://github.com/nicknitewolf/device_lge_vee7-twrp

for SailFish

https://github.com/drgogeta86/droid-hal-c8813q
https://github.com/drgogeta86/droid-hal-version-c8813q
https://github.com/drgogeta86/droid-config-c8813q
https://github.com/drgogeta86/sfa-mer
https://github.com/drgogeta86/android_device_huawei_c8813q
https://github.com/drgogeta86/droid-hal-configs

and
http://www.modaco.com/forums/topic/375953-devrom231-sailfish-os-for-zte-open-c-kis-3/
https://forum.xda-developers.com/moto-e-2015/development/surnia-sailfishos-2-1-moto-e-2015-lte-t3623141

I did not find SailFish for g525-c8813

Edited by madix-333
Guest madix-333
Posted

Sailfish OS 2.0 for xperia 2011

maybe porting this

https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_2011_Xperias
https://4pda.ru/forum/index.php?showtopic=273696&st=31380#entry44670974

Guest madix-333
Posted (edited)

HI Adeii , what release sailfish you build, xperia hawe 2.0.1.11 and cm11
Try this
https://4pda.ru/forum/index.php?showtopic=843775

for y6

https://4pda.ru/forum/index.php?showtopic=793691

Edited by madix-333
Guest adeii
Posted (edited)

I use Jolla-latest i486 for tooling, Jolla-latest arm7hl for target, hybris-12.1 branch and SlimLP device tree.

UPDATE:

Kernel is from CM13. But hybris-boot.img is done, again. But I can not build packages for a few days. I'll try to port/repack it from given links or give up.

 

Edited by adeii
Guest madix-333
Posted (edited)

This is my cm11 sleep, ported from d9. In cm12.1-cm13 battery drain too fast.

http://s3.uploads.ru/t/WdusN.png

http://sh.uploads.ru/t/loGgT.png

http://s8.uploads.ru/t/P9qDG.png

For Sailfish OS.

Join #sailfishos-porters on irc.freenode.net

Edited by madix-333
Guest madix-333
Posted

Phone is in standby mode, some services are disable, i not use google services.
Disable multisim in build.prop, Kernel Adiutor cpu 61-1008 intellidemand, gpu 192 mg, io cfg. ksm disable, and arch power enable.

  • 1 month later...
  • 3 weeks later...
  • 1 month later...
Posted

Another tip: oreo add some linux requirements in android kernel, so 5MB chil360-MM kernel rised up to 11MB... boot.img will be 12-14MB and default /boot is 8MB.

At least, for Oreo, we need to resize partitions inside phone!!! I guess, best option is to sacrifice /cust for bigger /boot and /recovery (and /cache).

Guest Einsam Teufel
Posted (edited)

 Hello, Adeii, what do you think, in the near future is it possible to compile the kernel 8.1 go?

And..are you going to make it bootable?

Excuse me for being tactless, unfortunately I do not know English enough to understand technical vocabulary. google does not help (

Edited by Einsam Teufel
Mistake
Posted
9 hours ago, Einsam Teufel said:

 Hello, Adeii, what do you think, in the near future is it possible to compile the kernel 8.1 go?

And..are you going to make it bootable?

Excuse me for being tactless, unfortunately I do not know English enough to understand technical vocabulary. google does not help (

Look post before, boot.img with chil360-MM kernel is about 12MB. At least, we need to repartition (resize partitions of) internal memory to install oreo/pie. But will it be bootable, I do not know. 

  • 2 weeks later...
Guest phil2sat
Posted

Enable xz compression in kernel defconfig and save some extra mb ;)

Posted (edited)
On 9/27/2018 at 1:40 AM, phil2sat said:

Enable xz compression in kernel defconfig and save some extra mb ?

Thank you for tip, but still not enough.

Default LZ4 compression - kernel is 11.369.996 b, with XZ - is 11.351.452 b.

Boot image is 12.658.688 b, and  max size is 8.388.608 b. Removing various HID devices support, not helpful also.

Risky way is to resize /boot, but also /recovery, something, /cache and /cust in recovery terminal and flash boot and recovery again for current OS. Is it possible?!

If works, then we can flash oreo ?/ pie ?  boot.img and system.img in future.

I suggest:

/dev/block/mmcblk0p12 344064     360447      16384    8192K 48 Unknown/boot
/dev/block/mmcblk0p13 360448     401407      40960    20.0M 60 Unknown/recovery
/dev/block/mmcblk0p14 401408     409599       8192    4096K 6c Unknown
/dev/block/mmcblk0p15 409600     802815     393216     192M 83 Linux/cache
/dev/block/mmcblk0p16 802816     966655     163840    80.0M 83 Linux/cust

to

/dev/block/mmcblk0p12    344064     376832      32768   16384K 48 /boot x2
/dev/block/mmcblk0p13    376833     417793      40960    20.0M 60 /recovery
/dev/block/mmcblk0p14    417794     425986       8192    4096K 6c Unknown
/dev/block/mmcblk0p15    425987     925699     499712     244M 83 /cache = 196608k + 53248k = 249856k = 244M
/dev/block/mmcblk0p16    925700     966655      40955    20.0M 83 /cust = 81920K - 8192K(boot) - 53248K(cache) = 20.0M = 20480K - 5

 

Edited by adeii
Guest phil2sat
Posted (edited)

why kernel image is so huge, if i build kernel with xz its about 4mb !?

did you compress initrd also with xz or in standard gzip?

Edited by phil2sat
Guest phil2sat
Posted

btw its possible to change partition sizes, but youre unable to recover phone with stock roms!!!

problem is if you change boot and recovery you cant boot after all DANGER!!!

In theory you have to change ofset of recovery first, leave free space for boot, then reflash recovery, test if recovery does boot and then create boot partition

fdisk -H64 -S32 /dev/block/mmcblk0 is the correct ofset to change partitions, spended the whole night to get this working.

as long as you can adb either to recovery or to normal boot youre alive ?

 

Posted
18 hours ago, phil2sat said:

btw its possible to change partition sizes, but youre unable to recover phone with stock roms!!!

problem is if you change boot and recovery you cant boot after all DANGER!!!

In theory you have to change ofset of recovery first, leave free space for boot, then reflash recovery, test if recovery does boot and then create boot partition

fdisk -H64 -S32 /dev/block/mmcblk0 is the correct ofset to change partitions, spended the whole night to get this working.

as long as you can adb either to recovery or to normal boot youre alive ?

Thanks for reply! Seems like good tactic - from OS, to disable cache and move/resize /recovery, /cache and /cust, after from twrp to resize /boot. No need to restore to stock rom, ever.

Oreo adds something to "normal" kernel (MM kernel is 4,67 MB for lineage 13), compiled is 10,3MB for lineage 15.1.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.