Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


adeii last won the day on May 22

adeii had the most liked content!

Community Reputation

96 Excellent


About adeii

  • Rank
  • Birthday 05/17/1979

Profile Information

  • Location
  • Interests
    hacks, cracks, ports, compilings, reverse-engineering
  • Your Current Device(s)
    Huawei Y7 2018 EMUI 8.0

Recent Profile Visitors

13,014 profile views
  1. This kernel should works well with SlimKat 9.x CAF / SlimLP, at least fixes wifi upload and hotspot. Probably others KK CAF and LP roms could works, but maybe repacking needed. boot-LPmm-47 <-- MM kernel (chil360 3.4.110), for both KK,LP,MM roms, but compiled with GCC 4.7 got no problem with wifi upload. If you only change toolchain (GCC 4.8, 4.9, UberTC) you will had upload reboot. Maybe Linaro would work good like GCC 4.7 but not tested.
  2. I am not sure that 5.1 branch will boot. So mixed with 4.4 for more liked.
  3. Hello! New TWRP but not tested (no more Y300). If anyone what to try, beware - backup your phone, be ready to flash working recovery via download mode, if can not boot to system! TWRP- built with omni-5.1 branch, because missing omnirom/system/core 4.4 branch in repo. TWRP- build with omni-5.1 and mixed with omni-4.4.
  4. For any unrooted//bad rooted 4.4+ rom, you can also use Magisk 18+ (systemless) instead of SuperSU. Also particularly works on 4.2.x and 4.3.x roms! Not tested on KK/LP yet, but you can try it from GitHub. Installing could be done by patching boot.img in Magisk Manager or by flashing Magisk.zip from TWRP/CWM. More info.
  5. Hello, Micky007. I guess it would be boot-LOS12-mm or boot-CM12-mm-wifi last ones that are built.
  6. In theory, Treble project enables that phones with 8.0+ boot can run custom rom by just flashing generic system image (GSI). Example GSI of Lineage 15.1 is https://github.com/phhusson/treble_experimentations/releases/download/lineage-v21/system-arm-aonly-vanilla-nosu.img less that 900MB. Problem with old phones: is no compatible kernel, new kernel use much more space (linux part, some vendor drivers), all drivers (vendor files) must be added after GSI to /system partition or separate /vendor partition that our phones do not have. Maybe /cust can be used and rename as /vendor in fstab. But for kernel... I still do not see way to run oreo on Y300/G510.
  7. - Clean microUSB port from dust with plastic (toothpick, needle...). - Try cable with longer microUSB connector, without silicon phone case - Put some metal pin between connector and port, or even sold upper side of connector (for firmer GND junction betweem port and connector). - Try charger with different current (0.12A loosing connection, but 0.5A and 1.0A works).
  8. Since May of 2018. Huawei stops to give bootloader unlocking codes for free, but it can be done for 4$.
  9. End of Line for myself! - in next few months I can not compile ROM(s); - LineageOS 15.1 is above half compiled, but can not be finished this year ( I am not joking ) . Anyone can continue work on it and every other rom, current status (manifest, boot, patches, compiled files) is on MEGA.nz - I am do not have Y300 anymore , so no ROM testing :( [but still can build ROMs, in future, for known android versions (KK/LP/MM)], because Y300 is swapped for Y7 Prime 2018 :)
  10. 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.
  11. 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
  12. 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.
  13. I do not know, 2 weeks trying to compile LOS15.1 with LOS13 device tree, (app/lib/framework one by one) because of errors... And question is will it boot?
  14. 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).
  15. Made experiment with BrokenPop (ex-Broken roms, now Dysfunctional roms), 5.1.1 rom. MM kernel, GCC 4.8, audio-caf/libhardware for kitkat, fm radio from slimkat ... - FM Radio still not work, tuning station works but no output on speaker nor headset; - apk can not be installed from internal nor external sd memory - parse error! +apk can be installed from /data/local/tmp or /mnt/obb/apk (both folder and file mod to 777)... unknown cause! + wifi upload works normaly; most of stuff work. download rom . . . . . sourcecode
  • Create New...

Important Information

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