Unlock Bootloader help

Ойбек said:

Hi everyone. I can't unlock my bootloader and get Ruth on my phone.
When you enter adb reboot bootloader and fastboot oem Unlock the volume up button does not work. And the volume down reacts perfectly. Please help me. Ruth's goal on the phone is to get.
Processor: MTK6735
Android: 6
Loader version: 0.1.00

Spoiler: fastboot getvar all

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 7d000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: TEK6735_35_M0
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.209s

please help...

Click to expand...

Ойбек said:

Yes, I read. I don’t have Alcatel .. I have a phone from China. Even there is no firmware anywhere .. Sorry for my English. I am writing through Translator.

Click to expand...

Ойбек said:

How can I solve the problem?
I can send a build file.prop..
and also I found the superboot folder inside the device and there were two su files inside and superboot.sh, but i don't run this file in adb shell

Spoiler: superboot.sh

mount -o remount rw/system
rm /system/xbin/su
rm /system/bin/su
mkdir /system/xbin
cat /superboot/su>/system/xbin/su
chmod 4755 /system/xbin/su
cat /superboot/su>/system/bin/su\
chown 0.0 /system/bin/su
chmod 6755 /system/bin/su

Click to expand...

Ойбек said:

No not rooted. I ordered a phone in China. Proves sells mobile phones of different brands, but all phones are the same firmware. I think this file is intended for Rooting, because looking at the instructions inside it rewires the volume and creates a superuser folder

Click to expand...

mikedt said:

Is this phone already rooted? And exactly what device have you got there? As for actually doing anything with build.props, not a clue. I'm not a dev. But I know if you mess up the build.prop, that can brick the device, possibly irreparably.

Click to expand...

MrJavi said:

Exellent advice mikedt,
Back in the days, I have soft-bricked my device many of times adding ,removing and/or replacing buildprops. Sometimes just tweeked one of them put my device in bootloops (soft-brick). Fashing a back up via custom recovery got my cellphone back in working order. I've learned to not mess around to much when it comes to the buildprops.

Click to expand...

Ойбек said:

They do not reply to messages at all. I’ve been writing to them for half a year already

Click to expand...

mikedt said:

Yeh I know. Been there, done it myself. But only with devices that I know I can get going again, specifically Samsung and Oppo.

Click to expand...