Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


adeii last won the day on June 1

adeii had the most liked content!

Community Reputation

90 Excellent


About adeii

  • Rank
  • 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

9,740 profile views
  1. If remove /misc from recovery.fstub, no more recovery loop nor freezing on splashscreen. Use with care: https://mega.nz/#!EkRhhBSB!J4pcOOm5pIfkfhl2zandlbx-jU1oQH7vCz8uUt2W0aI TWRP 3.2.1
  2. Tried to port it from d9 to u8951: no wifi with d9 kernel or got wifi but panic on upload with chil360 mm kernel.
  3. Update1: GenoTool changes splashscreen even it reports error about ADB. Partitions mmcblk5, 9 and 10 are changed after new splashscreen. I guess partition 5 (/dev/block/mmcblk0p5) is most important because its header is "oemlogo....", and so I can backup it and could flash it via recovery. Update2: There are, another way to make splash as png, 480x800, convert it to rgb565 format, compress it to oemlogo.mbn, upload to /system/media or make folder /data/cust/logo and put there oemlogo.mbn and execute load_oemlogo. !tested but not working! Update3: Let''s see GenoTools sourcecode, line 228, function changelogo(): https://github.com/genokolar/Genotools/blob/master/genotools.au3 Rooted + ADB! - it repack jpg to rgb565 format, rename it to oemlogo.mbn, push it to /data/cust/logo. - push load_oemlogo to /data/local/tmp and open shell (terminal on android or adb shell on pc) - chmod 0755 /data/local/tmp/load_oemlogo - chown 0.0 /data/local/tmp/load_oemlogo - /data/local/tmp/load_oemlogo and that's it. Update 4: Flash this via recovery, it do the trick! SplashScreenY300.zip
  4. Yes, you are right. There are no WebViewClassic support, only WebViewChromium and only chromium based browser could work.
  5. HI! I had tried with your kernel 3,5,7 for OctOS KK, both kernel and driver - still reboot. App is swiftp, adb via wifi works normal. files.zip Is CM11 from D9 to u8951d legacy or CAF?
  6. Thanks for tip, Madix. Still do not know cause of kernel panic. First time with new toolchain, upload works from both SD, with big files 20+ MB with no problem. Next day, do clean install rom+kernel and reboots started. Maybe some goverment/scheduler combination workaroung kernel panic. Also xposed framework cause bootloop (http://review.cyanogenmod.org/#/c/118800/). Maybe key is in vee3 device tree. Next time, LOS11 will be with display-legacy and see what will happen. update1: kernel 3.4.104 in slimkat9.1 legacy works fine, but kernel 3.4.104 to 3.4.110 in slimkat9.1 / LOS 11 display-caf cause reboots. Weritos' kernel 3.5.7 also reboots. On the other hand, kernel 3.4.104, ubertc 4.9, in slimkat9.1 legacy also cause boot but with "init" and "wifi" drivers from older kernel 3.4.104 solved rebooting.
  7. Update CAF: Kernel 3.4.110 is compiled with newer toolchain, wifi upload is not fixed yet, but SOMETIMES works, from /storage/sdcard1, no matter swapped internal or external. There are default version (48MB zRAM) and bigger swap version (128MB zRAM). Both working. Same zImage (with /wifi dir) could be repacked into kernels of other KK-CAF and LP roms that have common problem wih wifi uploading (SlimKat CAF, SlimLP, CM12.1, OctoOS-KK, DU8.2, AICP 7/10, RR 5.5.x). Update Legacy: Kernel is old 3.4.104, compiled with newer toolchain, seams little faster than CM11. Default zRAM is 128MB, new battery bar in status bar, wakelock blocker, FM Recording has now notification, call recording is enabled but can not record calls in amr-wb nor aac... Xposed Framework still don"t work!
  8. For Y300, maybe Croatia Deutsche Telekom do the trick: few Y300-0100 stock roms
  9. I guess, phone is rooted and adb is on. Maybe picture is not 480x800x24bit JPG? What OS (PC and phone) you has installed? Kill all adb.exe processes in TaskManager, GenoTools opens his hwadb.exe. 更换失败,请正确安装手机驱动并确认手机开启了ADB调试,然后将手机连接电脑 后重试 = The replacement failed. Please install the phone driver correctly and confirm that the phone has ADB debugging enabled. Then connect the phone to the computer and try again.
  10. LineageOS/ex-CyanogenMod 11.0 for G330/G510/Y300 Unofficial builds Introducion CyanogenMod 11.0 for our devices was built by Dazzozo. SlimKat and SlimKat CAF are built by chil360, using Dazzozo's device tree as base. Now LineageOS CAF is built, using chil360's CAF device tree as base. Also display-legacy added! Features * Should be the same as for CyanogenMod 11.0 by Dazzozo. Screenshots also, until newer will be made. * FM Radio, FDroid, getChromium, K9Mail are added. * ROM has signature spoofing. * chil360's kernel, Marshmallow compatible, compiled with UberTC 5.3 (instead of UberTC 4.9) --- NO MORE KERNEL PANIC (REBOOT) on WiFi uploading!!! (CAF build) * chil360"s kernel, good old SlimKat legacy kernel, compiled with UberTC 4.9 - NO kernel panic at all. Bugs - MAJOR bug, for now: apps using WebViewClassic are crashing (Browser, Opera mini, Via, etc...). Chromium and Dolphin browser are working. - MINOR bus, for now: Nanomod-microg 7.0 can not connect to Google Account, 7.1+ freezes "Sign in" and "Cancel" buttons. OpenGApps works fine. + WebviewClassic is enabled now. All browsers (both webviews) should work. + Legacy build has changable zRAM size (64/128/256/512 MB) from build.prop, also has WakeLock blocker in Settings>Performance. + Flash latest microG (currently 17.1) and flash microG-oldGPS from microG-7.0, reboot, enable all check-ins in microG settings, Sign-in for Play Store works. Sign-in to Google account, agree to contracts. But still can not connect to Play Store. Flash then latest microG again (since you signed in, restore latest GPS) and try again. It works now as it should or reboot again. Downloads ROM: LineageOS 11 (G330/G510/Y300, microG...) OpenGApps: Optimized GApps KK
  11. Thanks for review, Trapezio! Replace with newer PlayStore or adding FDroid could solve no.2 and no.4 even no.5 But no idea for WPS and QS Flashlight without using apktool, for now.
  12. If someone needs GenoTools... it would be nice to got translation or to know what partition is changed. The first option is for changing splashscreen, for others I do not know/read. This is my new splashscreen for U8833 (Y300), joking, of course.
  13. Ljudi, ne radi nijedan link. Da li moze re-upload? UPDATE: Nasao sam ova dva. Y300_firmware(Y300-0100,Android 4.1,Emotion_UI,V100R001C249B193,Serb-Telekom_Srbija,05011MEL).zip Y300_firmware(Y300-0100,Android 4.1,Emotion_UI,V100R001C242B195,Serb-Telekom,05011YLL).zip
  14. Thank you, Ceastel! Can not find patch for 2.8.5/6/7, but have found where are problems! 1 - "Reboot to ..." freezing is solved by adding init.recovery.service.rc for 5.0+ and init.recovery.hlthchrg.rc for 8.0+ to init.rc & adding "on property:sys.powerctl=* powerctl ${sys.powerctl}" and "service adbd /sbin/adbd --root_seclabel=u:r:su:s0 --device_banner=recovery" for the case of emergency :) "Reboot to system" now reboot to recovery, "Power off" now power down device. No more need for battery replace. Test image TWRP 3.2.1 is here. 2 - Since Android 7.0, system and recovery need to read /misc partition! So, in BoardConfig it should change "BOARD_HAS_NO_MISC_PARTITION" to false! After cleaning /misc partition in terminal, recovery finaly reboot to /system :) :) :) For now, it has to been to done manualy in terminal: dd if=/dev/zero of=/dev/block/mmcblk0p7 and reboot to system! Or as script misc.sh * Ignore partition is full, no space left, is just writes zeros to 4MB size partition! 3 - One of bugs left, mkdir /sideload didn't help, sideload can not be enabled. In 3.1.1, sideload disconnect device from PC, adb works normaly on recovery.

Important Information

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