Database Users

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

Stuck in Fastboot and Rescue Mode [hifi image error]

Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).

Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?

Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)

You can go to Twrpmeticulus?

Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.

[SOLVED] Fastboot fails, and SD flash stuck at 5%

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

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

I can't make TWRP on my Asus X00QD (ZE620KL)

Hello,
I can unlock my phone :
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KLXXXX
OKAY [ 0.008s]
finished. total time: 0.008s
but I don't make TWRP...
For flash it was "good" but it's recovery original with command line
and for boot in TWRP I have :
fastboot boot 'recovery.img'
downloading 'boot.img'...
OKAY [ 0.637s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.638s
I tested 3 TWRP different ones with the same result
Can you help me please ?

Please help me, I have no solution, and I want to put custom rom in my phone.
I have to put TWRP in my phone for custom rom

Ciao!
this error is common on my Asus x00QD when i use stock Android 10, you need to downgrade to 9 !
Please check on the Net for Q-P-UL-ASUS_X00QD-ASUS-16.0615.2002.120-1.1.33-user.zip and push it via SDcard or ADB, then retry with FastBoot

I can't make, when reboot, it was Android 10...
And Asus flash tool does not work, he can't find m'y phone in fastboot and recovery