Unable to unlock Lenovo Tablet TB- 7504x - Thinkpad Tablet General

I am trying to unlock Lenovo Tablet TB-7504x but with no success.
--
$ fastboot devices
8SSP69A6NLRAHA2287J00FM fastboot
$ fastboot flashing get_unlock_ability
...
FAILED (remote: unknown command)
finished. total time: 0.003s
$ fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.003s

Same issue.No success in unlocking bootloader
I have the same problem.
If you get how to do it please mail me at
[email protected]

Related

Unable to 'fastboot boot' / 'fastboot oem device-info' w/ unlocked bootloader

Lately I am trying to root my p8, when I came across this issue:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock 2104915622823317
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.140s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-2.8.7.1-p8.img
downloading 'boot.img'...
OKAY [ 0.556s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.559s
As seen above I am not being granted the permission to these commands even though I have a unlocked bootloader.
Because I can not think of any reason why this is happening I am asking for tipps I can try.
Thanks in advance
fastboot boot won't work........... i tried it too....... didn't try oem device-info though

Accidently rebooted with no os installed

Linux:
[email protected]:~/Android/Sdk/platform-tools$ fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel: OKAY [ 0.070s]
finished. total time: 0.070s
[email protected]:~/Android/Sdk/platform-tools$ fastboot devices
33b1ed900804 fastboot
[email protected]:~/Android/Sdk/platform-tools$ fastboot boot twrp-3.4.0-0-twrp.img
downloading 'boot.img'...
OKAY [ 0.158s]
booting...
FAILED (status read failed (No such device))
finished. total time: 5.292s
[email protected]:~/Android/Sdk/platform-tools$ fastboot boot twrp-3.2.1-0-twrp.img
downloading 'boot.img'...
OKAY [ 0.158s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.244s
Windows:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-twrp.img
downloading 'boot.img'...
OKAY [ 0.120s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.220s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.2.1-0-twrp.img
downloading 'boot.img'...
OKAY [ 0.121s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.264s

How to root ZTE Blade A7P (Z6252CA)?

I have tried to unlock my bootloader using fastboot flashing unlock and fastboot flashing unlock_critical, however I get the error message:
Code:
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
I have turned on OEM unlocking in developer settings, and the output of fastboot flashing get_unlock_ability is:
Code:
(bootloader) unlock_ability = 16777216
OKAY [ 0.002s]
Finished. Total time: 0.002s
From that output, the bootloader unlock should work, however, it does not. Please help me.

adt-3: fastboot get_unlock_ability 0

Hi All,
I am trying to flash Android TV 13 beta 4 ~ to the developer tools adt-3. After flash ... the adt-3 keep reboot. And cna't load the bootloader and OS. when I try to flash the device again ... adt-3 said that FAILED (remote: 'locked device').
I would like to know how to unlock adt-3 !?
ToTo
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.049s]
Finished. Total time: 0.050s
sudo ./flash-all.sh
[sudo] password for toto:
error: no devices/emulators found
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'data' FAILED (remote: 'locked device')
fastboot: error: Command failed
Sending 'bootloader' (1591 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
--------------------------------------------
Bootloader Version...: 01.01.220621.133524
Baseband Version.....: N/A
Serial Number........: ACHE0000xxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.015s]
Checking 'version-bootloader' OKAY [ 0.014s]
extracting boot.img (16 MB) to disk... took 0.031s
archive does not contain 'boot.sig'
Sending 'boot' (16384 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
OKAY [ 0.023s]
Finished. Total time: 0.023s
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.305s
Need help to unlock adt-3
fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock
Many thanks, I using adt-3. I think oem not working ... many thanks. Here is the result.
./fastboot oem 'setenv lock 10101000;save'
FAILED (remote: 'locked device')
fastboot: error: Command failed
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
That is the command that is within flash-all.sh for build adt3_gtv-stt1.211025.001.z3-factory-91f7efe7.
It was designed specifically to fix this particular issue/bug with the adt-3.
This problem started before android 12. Read article;
[Update: Fixed] Android TV 12 preview builds for ADT-3 can't be flashed
The first builds of Android TV 12 for Google's own ADT-3 developer device are completely broken, leaving developers unable to install them.
9to5google.com
Yes, I know ... I also go through that issue when I did Android TV 12. Right now I have the issue again. When I was doing Android TV 13 beta 4. Here flash-all.sh come with Android TV 13 beta 4.
if ! [ $($(which ./fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
./adb reboot bootloader || true
if ! ./fastboot flashing unlock ; then
./fastboot oem 'setenv lock 10101000;save' || true
./fastboot reboot bootloader; sleep 3
./fastboot flashing unlock || true
fi
./fastboot erase data
./fastboot flash bootloader bootloader-adt3_gtv-01.01.220621.133524.img
./fastboot reboot bootloader; sleep 3
./fastboot -w --skip-reboot update image-adt3_gtv-trb4.220715.005.zip
./fastboot reboot bootloader; sleep 3
./fastboot flashing lock
./fastboot reboot
But this time ... it is not working
Are you sure that your fastboot version/drivers are new/good?
Within a few days I will try to update mine, in order to see if there are any issues.
Are you familiar with worldcup burn mode?
Obtain worldcup drivers and command line "update" program for your OS.
Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;
update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"
Then reboot and see if fastboot works.
./fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/platform-tools/fastboot
I just upgrade it b4 I do the Android TV 13 Beta 4.
Sorry ... I have no idea of "worldcup burn mode"
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
ToToHayashi said:
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
Click to expand...
Click to collapse
Did you try the update method as suggested by "Deleted member 11959327" ?
To get the tool i recommend the Khadas Git (khadas/utils) then the aml-flash-tool/ is the folder with Amlogic tools
for the update tool its in tools/linux-x86/update

TWRP image doesn't start (remote: dtb not found)

Hi,
I would like to ask you about a support in programming my "old" Redmi 3s, becase I want to have a newer Android version on the device
The device has Android 6.0.1 MMB29M, MIUI10 Global 9.3.28 Beta, kernel: 3.18.20-g89abe5f.
When I enter fastboot mode, I do not see any version of fastboot, only "picrure of bunny" with FASTBOOT.
Bootloader is arelady unlocked (as in bellow logs).
After when I flashed TWRP and I tried boot twrp.img, I got info:
FAILED (remote: dtb not found)
I tried with available the oldest one as I found on page Redmi3s-Land is twrp-3.1.1-0-land.img , and also tried with the newest one twrp-3.6.2_9-0-land.img.
ISSUE:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.403s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.487s
BOOTLOADER:
I have unlocked bootloader:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
What I should do to fix this issue and to enter TWRP:
FAILED (remote: dtb not found)
?
Ahh.. I fouded solution. :/ :/
Commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
calls twrp.img file from above folder, not from Redmi 3s interal flash, where I copied a new twrp.img to programming.
So simply I moved "right" file of twpr inside to folder "Minimal ADB and Fastboot", and then commands works an issue FAILED (remote: dtb not found) doest apperas.

Categories

Resources