1. Download our Official Android App: Forums for Android!

Unlock Bootloader help

Discussion in 'Android Rooting' started by Ойбек, Dec 29, 2019.

  1. Ойбек

    Ойбек Lurker
    Thread Starter

    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
    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-size:eek:emkeystore: 200000
    (bootloader) partition-type:eek:emkeystore: 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-size:para: 80000
    (bootloader) partition-type:para: raw data
    (bootloader) partition-size:lk: 80000
    (bootloader) partition-type:lk: raw data
    (bootloader) partition-size:protect2: a00000
    (bootloader) partition-type:protect2: ext4
    (bootloader) partition-size:protect1: a00000
    (bootloader) partition-type:protect1: ext4
    (bootloader) partition-size:nvram: 500000
    (bootloader) partition-type:nvram: raw data
    (bootloader) partition-size:proinfo: 300000
    (bootloader) partition-type:proinfo: raw data
    (bootloader) partition-size:preloader: 40000
    (bootloader) partition-type:preloader: 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...
     

    Advertisement

  2. mikedt

    mikedt 你好

    Did you follow the instructions already posted in this thread and on XDA? Maybe Alcatel(TCL) updated their stuff to make unlocking impossible?
     
    MrJavi, Ойбек and ocnbrze like this.
  3. Ойбек

    Ойбек Lurker
    Thread Starter

    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.
     
  4. mikedt

    mikedt 你好

    Just so you know, this thread is about Alcatel phones, manufactured by TCL. But if you've got a phone from an unknown Chinese manufacturer, then good luck with it you're on your own, because there is nothing available or known, like fimware.

    no devs = no fun.
     
    #4 mikedt, Dec 30, 2019
    Last edited: Dec 30, 2019
    MrJavi likes this.
  5. Ойбек

    Ойбек Lurker
    Thread Starter

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

    Attached Files:

  6. mikedt

    mikedt 你好


    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.
     
    MrJavi likes this.
  7. Ойбек

    Ойбек Lurker
    Thread Starter

    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
     
  8. mikedt

    mikedt 你好

    Ok then, I think you need to go to your supplier in China, because he probably knows more about the devices he sells than anyone else out there.
     
    MrJavi likes this.
  9. Ойбек

    Ойбек Lurker
    Thread Starter

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

    MrJavi Android Enthusiast

    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.
     
    mikedt likes this.
  11. MrJavi

    MrJavi Android Enthusiast

    Welcome to Android Foroms Ойбек
     
    Ойбек and mikedt like this.
  12. mikedt

    mikedt 你好

    Yeh I know. Been there, done it myself. :) But only with devices that I know I can get going again, specifically Samsung and Oppo.
     
    MrJavi likes this.
  13. mikedt

    mikedt 你好

    I think you might be SOL, I'm a afraid. That's the difference between some unknown thing, and brand-name devices that have good information and community support, e.g. Samsung, Moto, Google Pixel, etc.
     
    MrJavi likes this.
  14. MrJavi

    MrJavi Android Enthusiast

    We have alot in common. I only wish my writing skills were even half as good as yours I'd be a very happy man. Wishing you and yours all the best.
     
Loading...

Share This Page

Loading...