Jump to content

adeii

Members
  • Content Count

    418
  • Joined

  • Last visited

  • Days Won

    5

adeii last won the day on September 10

adeii had the most liked content!

Community Reputation

94 Excellent

5 Followers

About adeii

  • Rank
    Diehard
  • Birthday 05/17/1979

Profile Information

  • Location
    Србија
  • Interests
    hacks, cracks, ports, compilings, reverse-engineering
  • Your Current Device(s)
    Huawei Y300 SlimKat 9.1 Legacy

Recent Profile Visitors

12,099 profile views
  1. - 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).
  2. Since May of 2018. Huawei stops to give bootloader unlocking codes for free, but it can be done for 4$.
  3. 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 :)
  4. 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.
  5. 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
  6. 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.
  7. 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?
  8. 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).
  9. 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
  10. Well, all camera apps should turn on Max.brightess is there is a option. Snap Camera for CM-13 has it coded: https://github.com/CM13-Y300/android_device_huawei_msm7x27a-common/blob/cm-13.0/overlay/packages/apps/Snap/res/values/cm_strings.xml
  11. New version, 3.2.3.0 is ready! Now Android 9 Pie is supported... for flashing :) TWRP-3.2.3.0-u8833 image, no problems (adb and sideload are working, in few tries). TWRP-3.2.3.0 flashable.
  12. Comfirmed! Used same drivers (wifi and wlan, lp5.1 branch; wifi is disabled with mm6.0 branch) and CM-12.1 - default: chil360-kernel-LP 3.4.109 + toolchain Uber-4.9 = kernel panic and restart; - upgraded: chil360-kernel-MM 3.4.110 + toolchain Uber-4.9 = kernel panic and restart on CM-12.1 (works fine on CM-13, but updated drivers); - fixed: chil360-kernel-MM 3.4.110 + toolchain GCC 4.8 = no kernel panic, wifi upload works fine!
  13. 1 - Back up all data from you phone, cause it will be ALL ERASED, twice! Be ready for No More Warranty for your phone!!! 2 - Unlock bootloader: https://www.modaco.com/forums/topic/362034-unlock-your-bootloader/?tab=comments#comment-2115119 3 - Install custom recovery while you already in bootloader mode, you can flash other or newer recovery over and over that one: https://www.modaco.com/forums/topic/364071-recoveryall-cwm-6035-08082013/ -- or -- https://www.modaco.com/forums/topic/362074-recoveryall-official-twrp-2710-root-01082014/ 4 - In recovery mode (CWM 6.0.x.x or TWRP 2.8.6.x+) flash particulary 5.x.x rom and reboot after completed flash. 5 - Reboot to system and wait for loooong to see "android is starting" after looong bootanimation.
  14. Sorry, but NO on all answers. Random restarts, short battery life, no BS on calls only if use proximity sensor patch/disabler, normal lags for LP/MM roms, only sw decoders.
  15. No, just LS-LP...zip and save services-spoofed.jar to overwrite original in framework, in zip or via TWRP, if you want to use microG instead of OpenGApps. and/or Xposed instraller (install package v89 directly and reboot).
×

Important Information

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