i mostly use this for hex compare but it has all kinds of compare, in a friendly gui
beyond compare 4.x (scooter software)
beyond compare 4.x (scooter software)

Found this from a post on XDA: (We don't want to use any of these commands based on their descriptions)I tried "fastboot flashing get_unlock_ability" and got result as in screenshot below. Can any one try below codes i have extracted them from lk.bin. Don't know what they do. Try at your own risk..
fastboot <below code one at a time>
oem p2u, oem reboot-recovery, oem append-cmdline, oem off-mode-charge, oem unlock, oem lock, oem key, oem lks.flashing unlock, flashing lock, flashing get_unlock_ability, oem usb2jtag
I tried the rest of the commands and here is what happened:
- oem p2u ("oem p2u <on|off>"; "printk to uart" - sends printk output to UART/serial port, neither relevant nor useful to the vast majority of people)
- oem reboot-recovery (will reboot into recovery)
- oem off-mode-charge ("oem off-mode-charge <0|1>"; enables/disables "off-mode charging", i.e. charging while the tablet is powered down). If you disable off-mode-charging ("off-mode-charge 0"), then the tablet will boot into Android when you connect it to USB while it is off.
- oem append-cmdline ("oem append-cmdline <option>"; Only supported by the new LK; appends option to the Linux kernel command line)
if we got success in unlocking bootloader and rooting............i will just port from my nubia n1 to k5 note.....simple things oly...so hurry up guyzzzzFound this from a post on XDA: (We don't want to use any of these commands based on their descriptions)
I tried the rest of the commands and here is what happened:
oem usb2jtag converts USB port to JTAG port. I have no idea what that means, but trying the command says: "FAILED (remote: not support on security)"
oem lock and flashing lock are supposed to be used for locking the bootloader but in our case it is already locked and we want to unlock it.
oem unlock does not work. It says "Unlock not allowed" on the phone and "(bootloader) Unsupportive project for unlock FAILED (remote: unknown command)" on the PC.
oem key says: "FAILED (remote: argument size is wrong)"
My assumption is that lks stands for lock state, which is shown as '1' (one) for me, even after trying the command oem lks.flashing unlock. For an unlocked bootloader, it should be '0' (zero).
flashing get_unlock_ability command does not work for me. It just shows me the fastboot command usage information.
On the page where I found the quoted post, the users have mentioned (for another Lenovo device) that patching the lk.bin is the only way to acquire root access or flash custom ROMs. I guess that's the only way for our device as well... (I'm still working on this)
Thanks for the suggestion though.
Try with Notepad++Does anyone know how to edit arm assembly code??
I have disassembled lk.bin to asm in IDA but dont know how to edit it.
I mean i can edit the values but don't know which values to edit.Try with Notepad++
Here You Go did as instructed by post.:fingers-crossed:https://forum.xda-developers.com/android/general/mtk-rooting-device-manually-t2976926
The tutorial is too lengthy...
can someone plz create a patched boot.img from this tutorial
I will flash it...m
I didn't follow first few steps as it is for users not having boot.img. We already have boot.img as well as scatter file in stock rom zip file inside target_bin folder so you can just extract that boot.img and edit it.kathanpatel1001,sir may I ask you which scatter file you used to create the boot image?Because I think the link to the tutorial he posted says that that method should not be used to create scatter file for devices with mtk67xx chipset.