KonstaT

Members
  • Content count

    3236
  • Joined

  • Last visited


Community Reputation

3259 Excellent

About KonstaT

  • Rank
    Hardcore
  • Birthday 11/02/82

Profile Information

  • Location Finland

Previous Fields

  • Your Current Device(s) Moto G, ZTE Open C
  • Your Twitter username konstatuomio

Recent Profile Visitors


7588 profile views

KonstaT's Activity

  1. KonstaT added a post in a topic Need help to compile dt img from kernel source of oneplus2   

    What's the point of uploading sources for something that might not work.
    Here's boot.img (with dt.img I built) for CM12.1 for someone to test. I used kernel/device sources from Grarak's github.
    http://www.mediafire.com/?7u3549t9h96yfp5
    • 0
  2. KonstaT added a post in a topic [Recovery] TWRP 2.8.7.0   

    recovery-stock-VDF-995NB01-IE02c.zip (Ireland)
    http://www.mediafire.com/?68f6sxadqqcpnmj
    md5:5a25bc3cea91e5a92fc3a9d566bb714e
    • 1
  3. KonstaT added a post in a topic Need help to compile dt img from kernel source of oneplus2   

    You're doing it wrong. :P
    dtbTool v3 does successfully create an image but only 3/12 of dtbs are accepted as unique. Resulting image is only ~850kb (vs. 3.4mb on stock).
    Start DT image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img Target dt image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img DTB combiner: Input directory: '/media/sda4/android/cm12.1/out/target/product/oneplus2/obj/KERNEL_OBJ/arch/arm64/boot/dts/' Output file: '/media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img' Found file: msm8994-v2.1-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v2.0-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v2.1-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v1-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v1-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v1-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v1-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v2.0-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v2.1-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped Found file: msm8994-v2.1-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 ... duplicate info, skipped => Found 3 unique DTB(s) Generating master DTB... completed Made DT image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.imgAfter hacking dtbTool to read qcom,hw-version none of the dtbs are skipped anymore.
    Start DT image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img Target dt image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img DTB combiner: Input directory: '/media/sda4/android/cm12.1/out/target/product/oneplus2/obj/KERNEL_OBJ/arch/arm64/boot/dts/' Output file: '/media/sda4/android/cm12.1/out/target/product/oneplus2/dt.img' Found file: msm8994-v2.1-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.1-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v1-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v1-mtp_14049_HW_14.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v1-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v1-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 65536, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.0-mtp_14049_HW_12.dtb ... Version:3 chipset: 207, rev: 131072, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.1-mtp_14049_HW_13.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 Found file: msm8994-v2.1-mtp_14049_HW_11.dtb ... Version:3 chipset: 207, rev: 131073, platform: 8, subtype: 0, pmic0: 65545, pmic1: 65546, pmic2: 0, pmic3: 0 => Found 12 unique DTB(s) Generating master DTB... completed Made DT image: /media/sda4/android/cm12.1/out/target/product/oneplus2/dt.imgSize of the image is slightly bigger than on stock (3,387,392 bytes vs. 3,354,624 bytes) but at least it's in the right ballpark. No idea if there's still other OnePlus strangeness that needs to be hacked or does this actually boot on a device. I can upload it if you have a device to test with.
    Edit. It's actually exactly the same size (3,387,392 bytes) as what's in stock OxygenOS 2.0.2 OTA that was released today.
    • 0
  4. KonstaT added a post in a topic Stock boot / recovery / system dump   

    Well, in that case you need to dump it from an unmodified device ('dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img').
    Or dump boot image ('dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img') and copy these recovery patch files so that it can be created.
    system/recovery-from-boot.p system/bin/install-recovery.sh system/etc/recovery-resource.dat
    • 0
  5. KonstaT added a post in a topic [Recovery] TWRP 2.8.7.0   

    You'd know if you'd bothered to read few posts above yours...
    • 0
  6. KonstaT added a post in a topic Need help to compile dt img from kernel source of oneplus2   

    Fails how?
    Quick guess would be that it needs dtbTool v3 (qcom,pmic-id support which CM's doesn't have). It's there on OP2's CAF tag (LA.BF64.1.2.1.c1-00810-8x94).
    https://www.codeaurora.org/cgit/quic/la/device/qcom/common/commit/?h=LA.BF64.1.2.1.c1_rb1.5&id=1b0556065535cee39dc77d26bee37a4561936827
    I think I already saw some OP2 specific patch in CM gerrit but can't remember what it was. BTW is there a stock boot.img somewhere I could have a look?
    • 0
  7. KonstaT added a post in a topic Stock boot / recovery / system dump   

    Like I already told you, please read the latest discussion in the TWRP thread. Upload the few needed files from the Irish stock firmware somewhere and I'll add Irish stock recovery.
    There's full firmware images available at ZTE support site. Dumping anything from the device is completely useless.
    • 2
  8. KonstaT added a post in a topic [HELP] Bricked my ZTE OPEN C (EU)   

    Well, that was a huge mistake. It's a small miracle your device still shows any signs of life after flashing bootloader and other low level firmware that is meant for a completely different device from a completely different manufacturer.
    If your device is recognized by the ZTE Windows flasher, you can use it flash correct firmware to your device. If you can boot to bootloader (volume down + power) you can try flashing images from Open C Windows flasher firmware with fastboot. Otherwise you'll have to resort to debricking guides you'll find on Russian forums.
    • 0
  9. KonstaT added a post in a topic Root lags my phone (?)   

    Where's that? There's zero reports of such issues in the TWRP thread and it's now been downloaded several hundred times. It would be the first time in history of all Android devices that custom recovery would cause such issues. It's not even technically possibly which makes this quite ridiculous.
    Maybe it's your shady rooting tool that causes the lag when it sends all your personal information to China. :P
    • 0
  10. KonstaT added a post in a topic Root lags my phone (?)   

    So you're using a task killer and have the nerve to complain that your device is not working properly...
    Recovery is a mini operating system of its own. You either boot to Android or you boot to recovery. This has nothing to do with TWRP and it seems you're the only one with this 'problem' anyway.
    • 0
  11. KonstaT added a post in a topic How to revert to stock recovery from TWRP   

    I was somehow under the impression ZTE had disabled flash_recovery service on the stock ROM (it will check, and if necessary restore, stock recovery on every reboot).
    You still shouldn't use mismatching recovery images to flash anything.
    • 0
  12. KonstaT added a post in a topic Root lags my phone (?)   

    LOL, that's the stupidest thing I've heard/read in a long time. You clearly have no idea what recovery mode even is. It's not even technically possible that it would cause any 'lag'. Android gives zero fscks what you have in your recovery partition.
    Your problem is more likely caused by Link2SD and or some other stupid thing (xposed) that you've done yourself. There's absolutely no reason for anyone to use Link2SD these days (it's not 2010 anymore) and this device has more than plenty of (fast) internal storage. If you move essential app data to your fake Chinese Kingston sdcard, no surprise if your device starts to lag...
    • 1
  13. KonstaT added a post in a topic How to revert to stock recovery from TWRP   

    Read the latest discussion in TWRP thread.
    No, none of that is true. Don't use mismatching recoveries and you won't have Irish recovery after the update...
    • 0
  14. KonstaT added a post in a topic [Recovery] TWRP 2.8.7.0   

     
    Here you go.
    recovery-stock-VDF-995NB01-ES02c.zip (Spain)
    http://www.mediafire.com/?h80bdgvh1agzc30
    md5:aa89dde0d4f6245522615d31cd40e668
    You could also dump the recovery partition ('dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img') but I much rather prefer creating it from the patch file as that is possible. This way you'll have a sha1 checksum to verify that the recovery image is exactly what it should be.
    • 1
  15. KonstaT added a post in a topic 1.0.0B03 to 1.0.0B13 (MR01b) OTA URL / details   

     
    AFAIK there's never been a ZTE device that had a locked bootloader and that allowed it to be unlocked somehow. Most ZTE devices (i.e. all that I've ever had) have bootloader left completely unlocked out-of-the-box. Bootloader isn't 'locked' in the traditional sense on this device either. ZTE has only crippled it so that the fastboot mode doesn't work. It doesn't verify the images it's booting so you can boot custom recoveries (TWRP) and custom kernels.
    • 0

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