adeii

Members
  • Content count

    203
  • Joined

  • Last visited

  • Days Won

    15

adeii last won the day on March 22

adeii had the most liked content!

Community Reputation

59 Excellent

4 Followers

About adeii

  • Rank
    Enthusiast
  • Birthday 05/17/1979

Profile Information

  • Location
    Србија
  • Interests
    hakkkz! krakkkz! reverse-engineering

Previous Fields

  • Your Current Device(s)
    Huawei Y300 SlimKat 9.0

Recent Profile Visitors

4,633 profile views
  1. Brace yourselves, "make android 8.0 rom for y300/g510" requests are coming! http://www.androidcentral.com/android-o
  2. Also enable "intelli-plugin" and chose exp. "eco-performance".
  3. Yup, their server need few days to "pick a right moment" to finish "giving a code"... (dok se porodi).
  4. Is that app the same as "huawei y300 all-in-one" pack from: https://www.dropbox.com/s/rgguo3bswbtg3pd/Huawei.zip?dl=1 , cause it contain also dc-unlocker + fastboot commands for boot unlock (with code from Huawei) and recovery flash?
  5. Thank you Robert for support. Well, preferred roms are nougat (not available), marshmallow (become boring) and kitkat (excellent but old); lollipop is underestimated but in golden middle...
  6. microG + Xposed framework + FakeGapps module + This app will work without Google Play services module should work... and still much better performance than OpenGapps. maybe with older version of G+. Did you enabled GPfProxy? and Google cloud messaging period?
  7. March build is uploading! I hope it will be last one, if Google does not update 6.0.1 above r79. No new rom for march.
  8. Still not concrete solution. Maybe automatic brightness, often BS happen after finished call, maybe low CPU freq. is too low, maybe MultiProcessor decision, etc....
  9. No, - I can not find full legacy dev.tree, - SlimKat suggests to use CAF version for QCom devices, Legacy is for non-QCom, - android source just got update from 4.4.4_r2 to 4.4.4_r2.0.1 <-- thats all that can be updated.
  10. Yes, you right, again. Slim6 has not thread, chil360 starts testing Slim6 builds and find them interesting and put them on mega.nz. Slim6 (and LineageOS 13 with Slim6 device tree) have problem with speak-to-otherside, but CM-13 builds has not such a problem, cause chil360 use prebuilt "rild" and "radio" from CM commit by LGHackTeam. You can try to flash ril+audio+radio fix from https://mega.nz/#F!F1hmmICR!22r532OdQ_gwphqHy9kwCg or replace all files contain "ril", "audio" and "radio" from CM13 to Slim6 zip file.
  11. Yes, you are right. Xposed 2.7 don't work on SK, but 2.6.1 works very well. Should works on SK 9.1 CAF, also. Did you wipe cache and dalvik-cache after flashing sdk19 libraries?
  12. Thank you for trying. So, G510 can work on 1.3GHz, good to know. Ok, Synopsys kernel is better on DU.
  13. I can not try it, now work for Y300. Should work for G510 and G330 (OC by WBrambley is working for G300 for SlimKat)
  14. Since pure AOSP and F-AOSP and AOSPA (Paranoid Andoid) are "unbootable and full of errors", I give up from them. After that, march build of Lineage will be in next week, with CM dev.tree (fixed RIL) and android source 6.0.1_r79. UPDATE: And it worth it!
  15. My case: Y300 goes brick. No bootable system, no recovery, only download mode. Tried some stock roms via /sdcard/dload/update.app not working (fail at step 2/2). USB port seams to be something losing contact.... after many tries, PC (win10 x64) detect unknown device and finaly install some drivers. fastboot devices - gives empty, adb devices - give sometimes "recovery" ?! othertimes "fastboot" ?! but most of time - empty. All that I could do it to "adb push recovery.img /data/local/tmp" <--- push recovery image to rare 777 permission folder on phone :) And just one more thing has to be done (but phone can randomly reboot and "miss" from PC....) "adb shell" "su" "dd if=/data/local/tmp/rec.img of=/dev/block/mmcblk0p13" if you are lucky and got "fastboot mode"... but you can not use "fastboot flash recovery rec.img" cause you got "waiting on phone,.." if you are in "recovery mode", you can not use "adb shell" cause not access to /system/bin/sh.... so only things to do is "adb push rec.img /dev/block/mmcblk0p13" and if you are lucky, you got stock or custom recovery that works!!!!!!!! Now you can flash/format every partitions of phone.

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.