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
Related
I did something apparently pretty stupid and let my ALE-UL00 update itself after having installed iRoot (yeah I didn't know what I was doing). I really just wanted to install an English version of the OS since changing the language in the settings only changed about half of it...
Anyway, now when I boot the phone, I get a screen with three options, roughly translated "clear cache", "restore factory settings", and "reboot". Selecting any of these leads to the phone booting right back to that screen again.
I've tried to flash two different ROMs using the SD card method. Neither from Huawei's website as I can't find my model anywhere on there, but both claiming to be for my phone. So I boot into recovery mode (vol up + vol down + power) while plugged in, I see the USB emblem, and it gets stuck at 5%. If I boot in recovery mode without plugging it in, it just plain fails at 5% and gives me a link to a website that has pictures of phones (none of them mine) and no download links.
I can boot the phone in fastboot/rescue mode (vol down + power), and fastboot does recognize it. So I extracted the UPDATE.APP using Worstenbrood's tool and tried to fastboot it manually. This fails, and here's what happens:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :ALE-UL00C00B569
OKAY [ 0.074s]
finished. total time: 0.079s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22918 KB)...
OKAY [ 0.647s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.674s
If anyone has any clue what I can try next, I'd greatly appreciate it!
mathguyjohn said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
Click to expand...
Click to collapse
In particular, can anyone say why lock-state info says it's locked, but get-bootinfo says it's unlocked? The fastboot screen on my phone says "PHONE Unlocked"
Update: I tried holding volume up to get to the eRecovery menu. I entered my Wi-Fi password, it looked for an update, and then got a red explanation mark along with a message Google translate tells me is "get package installation failure".
Update: I guess BOTH of the ROMs I'd tried to flash from the SD card were corrupted. I found a working copy elsewhere on this forum. Though nobody responded to this particular thread, this forum was immensely helpful nevertheless, so thanks guys!
For anyone that stumbles across this comment, follow this.
JpegXguy said:
For anyone that stumbles across this comment, follow this.
Click to expand...
Click to collapse
Dude, my entire problem was that the procedure outlined in this link was not working. It's the first two words of the post title...
I don't mean to be rude, but when I had this problem, I wasted countless hours sifting through people repeating the exact same solution. If it had worked for me, I wouldn't have needed to post here. I was clear about this.
Fastboot wasn't letting me flash any of the imgs, so the only thing I could do was but the correct update.app on a micro SD card and boot into recovery mode. The only reason that didn't work was because I kept finding corrupted ROMs. The one in the post you linked to wasn't for the right model of phone, so that link would have done nothing for me.
The entire problem was that the UL00 seems woefully undersupported in the English-speaking community, so I had a difficult time finding the correct one. I did find the right one on this forum, though, and it's here: https://forum.xda-developers.com/p8lite/general/emui-4-0-1-ale-ul00c00b569ota-t3467620
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]
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
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
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.