Search results

  1. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    My tool won't help you for non-standard samsung boot images. You need something custom like degas-unpackbootimg or other made specific for those images. If you search the xda you will find them.
  2. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    This was already discussed on some posts in this thread. It matters where you get the kitchen from, how you unpacked it and what windows you use. Anyway your problem is at your end.
  3. bluefirebird

    Post AUTO Materialised TWRP Maker [TOOL][New-Build]

    So, you ask for donations and thanks, also you claim you can do whatever you want with "your" tool's download links but you don't have the minimal common sense to give credit to the people that actually created the tools you use. I see in your tools folder a lot of executables from osmosis and...
  4. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    This is just a short break. Things are not well yet. I don't know if I will return here again. Take care ... all of you!
  5. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    All sources are on my github (still named carliv).
  6. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    If you still build with partial source repo, then you're missing /system/vold folder: this one.
  7. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    That looks like the bin folder can't be added in PATH for that session as it suppose to be, and how it works for all other people. That is a problem with your windows but I'm not an windows expert to tell you how to fix it.
  8. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    Just copy-paste this "How to remove the mtk header " in google or here in the search field (top right corner).
  9. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    That Config.in should be generated by a script but maybe the permissions are messed up in your cloned version. Anyway if you want to add it manually use this: https://github.com/omnirom/android_external_busybox/blob/android-6.0/Config.in.
  10. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    Your images aren't regular, they have mtk header but isn't a regular mtk header. You need to split the image manually and to remove the header manually with dd commands, or try michfood's tool.
  11. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Hi. I guess you downloaded a zip from github. Don't do that. Do a clone repo and the problem will be solved.
  12. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    No, it is in QCOMM section with no differentiate lollipop or marshmallow because there are only two devices.
  13. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    I personally didn't tried that way - I'm using full repo sources, but I'm sure it will work (this is the way mtk leaked sources work, because they don't use repo). Only thing that has to be taken carefully is the method to unpack since this can break some symlinks and permissions (try to use tar...
  14. bluefirebird

    Post TWRP Flags for BoardConfig.mk

    Are you sure it needs the mtk header? If the BoardConfig is right then this it is a qualcomm device and the mtk header is out of place. BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom... Also I never saw a mtk device with dt.img. My advice: get rid of mtk stuffs for this device...
  15. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Well, it is something I wanted to do for a long time but only now I thought it's the right time. I know there will be some adjusting time for those that know me as carliv but in the end I think it will be ok. When I was a kid I saw an animation movie (japanese) "Phoenix 2772" and I liked that...
  16. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    No need to check the ramdisk or kernel, I said drivers (windows) or udev rules (linux)... in your PC to be more clear.
  17. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Here's your problem: TARGET_RECOVERY_LCD_BACKLIGHT_PATH := /sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightnes for older recoveries this should be: TARGET_RECOVERY_LCD_BACKLIGHT_PATH := \"/sys/devices/platform/leds-mt65xx/leds/lcd-backlight/brightnes\" escaping quotes...
  18. bluefirebird

    Post Carliv Touch Recovery v6.5

    Ok, all done and links updated on download section. I changed the names a bit, now the version with adopted storage support has "-AS" in name, the other one doesn't. I updated the lun file path for the non-adopted storage recovery, as my friend yuweng told me it will work for usb mass storage...
  19. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    update CHANGELOG 14-07-2016: - add adopted storage support for marshmallow; - fix zip and wipe menu; - fix backup to internal sdcard - other improvements.
  20. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Yes, but that device is not on the list. Being a Mediatek powered one isn't a surprise. No problem my friend, :) it happens to all of us. ;)
  21. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    :laugh: No problem at all! Anyone who can help is welcome! That post you read was about twrp. In my recovery touch works but is screwed up (touch up and the response is down). It seems that the swap touch recovery flags couldn't help and as someone posted on the other page a link, that was a...
  22. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Well, he wants to turn off the touch completely and so it has to be a device that produce ABS events (touch) not only keys.
  23. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    No, you need the name, like this: TOUCH_INPUT_BLACKLIST := "mtk-tpd"
  24. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    That isn't a complete kmsg log it's just a part of it. You should use [ adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log ] and then to look for a line like this:[ 42.865263]<0> (0)[147:mtk-tpd]<<-GTP-DEBUG->> [3081]pre_touch:00, finger:81, pre_key = 0x00, last_key = 0x00 In device I...
  25. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Well, if you can find the exact name of your touch input device you can blacklist it and there will be no more touch. Try to see with dmesg wich is it. Or you can try to blacklist more than one, just use in BoardConfig something like thisTOUCH_INPUT_BLACKLIST :=...
  26. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    For kk you have to change more things to make it work not just mountpoints: first all selinux related files then if still doesn't work ueventd (with some other files from a kitkat recovery). But I didn't tried ever that. For vibration you have to check in dmesg why it's not working in recovery...
  27. bluefirebird

    Post Carliv Touch Recovery v6.5

    Since here was the most requested feature, I can announce you that I managed to add support for adopted storage too. I have to review the code and to check other functions for it, but I attached a preview with recovery booted and adopted storage mounted as /datadata. I used /datadata because...
  28. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    The problem is not in your setup. It is correct as you formated the ctr.fstab assuming that the internal storage is linked to /data/media. There is a bug in recovery when you backup on internal storage. I fixed that but couldn't find time to push the fix on github. Stay tuned, maybe tomorrow I...
  29. bluefirebird

    Post Carliv Touch Recovery v6.5

    The one with nas is for those that don't use adopted storage for sdcard. All written in post #4.
  30. bluefirebird

    Post Carliv Touch Recovery v6.5

    Even if my friend yuweng posted some info on how to report a bug, and I told you on last post to learn how to report problems you still don't want to do it right. Saying that doesn't work or I can't do this or that brings zero informations. Provide logs, dmesg, give all details (what version of...
  31. bluefirebird

    Post Carliv Touch Recovery v6.5

    You can flash a SuperSU zip to root from this recovery. The download links are in download page (on black menu bar) but if you enter from mobile they may not be visible. Change the site to desktop view or enter from a browser not mobile app.
  32. bluefirebird

    Post Carliv Touch Recovery v6.5

    Are you sure you didn't flash it on boot partition? If you say you flashed it twice... Try to flash again your boot image.
  33. bluefirebird

    Post Carliv Touch Recovery v6.5

    You have to give more details. What did you do in recovery before the issue? Did you tried to wipe cache and reboot the recovery then reboot to android or reboot to bootloader and reboot to android with fastboot command [fastboot reboot], and so on... I don't have this phone but maybe some of...
  34. bluefirebird

    Post Carliv Touch Recovery v6.5

    Sorry but that's not possible. Too much work to do and I worked alone for this for last three - four months in my free time. I won't start it from begining again. There is not much support for this.
  35. bluefirebird

    Post Carliv Touch Recovery v6.5

    This is not in a competition with twrp. I created this recovery as an alternative for those that liked cwm and wanted to use it post kitkat. Also, this one works even without touch and that could be in handy for those devices without touch in recovery (twrp can't be used without touch).
  36. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Well, good for you :) I noticed in your BoardConfig the flag Board has type B protocol. Your device has a synaptic touch panel and you saw in source code that flag defined? Because if it is not the case then that can cause the off touch issue. That flag shouldn't be used just "in case".
  37. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    I already told you to focus on building a functional twrp and after that you will be able to build this too. The huawei kiwi(qcomm) was having before a device tree that could build a functional twrp and I just added few things to build my recovery too. If you can't build a functional twrp then...
  38. bluefirebird

    Post Carliv Touch Recovery v6.5

    If you don't use adopted storage download the recovery-ctr-65-kiwi-nas.img and you will see the external sdcard too. For adopted storage I don't have yet a solution and therefore only the internal memory and usb-otg is supported (recovery-ctr-65-kiwi.img - this is for adopted storage). I rebuilt...
  39. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    On my github there is a device tree for huawei kiwi which is also a qcomm device. It builds and boots with graphics UI so you should take a look what I changed for that in my commits, you don't have to remove any parts from recovery just to use some flags (like USE_NEW_ION_HEAP to get rid of...
  40. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Update CHANGELOG 05-07-2016: - fix loading the graphical ui for qcomm devices; - added cancel backup feature (use power button or select from virtual keys); - fix display of progress while backup, restore or install; - some other small fixes and improvements (you can check the github commits).
  41. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    I think for touch accuracy I explained everything on building instructions. If the device has a low lcd density the value should be lower. The precision is not that fine to make a difference if you use 5 or 7, so the value on system.prop can be set once or twice until it's found the right one...
  42. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    Well, your device has an old CPU layout and it doesn't have a 32bit framebuffer. You have to use either this flag TARGET_RECOVERY_FORCE_PIXEL_FORMAT := "RGB_565" or to not use a pixel flag at all and let the recovery detect it. For partitions you have to define them as they are in your phone...
  43. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    You have to ask for help in sony's threads. I never had a sony device or even touched one and so I can't help you with something I don't know.
  44. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    For sony images you need a special tool, which you should find it if you have searched the forum.
  45. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    For ctr.fstab you need to change the device blocks probably. They are like in my device but this is a 64bit platform and yours is an old 32bit one. I told you before, that you need to change these [/dev/block/platform/mtk-msdc.0/by-name/cache] with something more like this [/dev/block/mmcblk0px]...
  46. bluefirebird

    Post [Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11

    Since I don't have a device with qualcomm I don't know. Maybe someone with knowledges will test and tell me if it does. That's the reason I told you to focus on twrp first. For twrp there are many developers with qualcomm devices and they can help you to solve the boot. After that if you came...
  47. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    update 2016-06-30 Update to version 1.3 stable Changelog: - detect mtk header during unpacking (hopefully it will find it in first 4096 bytes); - removed grep method; Maybe this will fix that grep error since there is no grep anymore.
  48. bluefirebird

    Post [RECOVERY] Carliv Touch Recovery v5.7 and v6.6

    I think it will be better to use cm-12.1, I didn't tested it in cm-12.0. And if your stock kernel is a lollipop 5.0 that doesn't matter it will work with cm-12.1. The error is easy to solve, just don't delete the stock recovery replacing it with my recovery or other recovery. Add the custom...
  49. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    Please read the red text of the error and do what it says. Hint: provide the image doesn't mean to post a picture here.
  50. bluefirebird

    Post [TOOL][UTILITY] Carliv Image Kitchen for Android - unpack/repack boot-recovery

    No, if you check my script you can see the command is passed like this [ grep -obUaPc "\x88\x16\x88\x58" ]. The problem is with his computer. Nobody else has this problem.