Database Info

Help with my Huawei Mate 9 MHA-L09. Oem Unlock

Hey guys, i tried to install a new rom and i deleted my OS. i unlocked the bootloader but when i tried to flash TWRP said me:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (26982 KB)...
OKAY [ 0.767s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>
If i try to flash anything else Said me ''Command not allowed'' and i think it's cause i did not turn on the Oem Unlock in development options (cause i don't have OS, obviously)
Anybody can help here please? is urgent and i'm dying :crying: :crying: :crying:

Failed remote command not allowed custom Rom (twrp)

Hi.
I've been trying to flash twrp my Huawai Mate 8 for a couple of weeks. I keep getting the error I mentioned in the title. The bootloader is unlooked, frp is looked. USB debugging is enabled. OEM is grey.
Android version 7.0, emui version 5.0.1. I've been using the official twrp and used adb files and fastboot from other sources as well as official files. The phone is NOT rooted.
Here is the full message:
fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (22142 KB)...
OKAY [ 0.470s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.477s
I would appreciate any help as this problem has bugged me for so long by now. Thanks!!

Stuck in bootloader nothing loads

Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s

Coolpente said:
Update: Of course... bad abd files quick update and everything went smooth.
Tried to root with magisk and got stuck in bootloop so I tried to install factory image and just be done with it and now its stuck in bootloader. trying to boot recovery just reboots into bootloader trying to use deuces script doesnt work and the flash-all script just fails its bootloader .0059 and its in boot-slot B and wont change to slot a. Havent had the phone long so im desperate to try and fix it if at all possible.
example of the flash-all
Code:
< waiting for any device >
target didn't report max-download-size
sending 'bootloader' (38728 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: -0.000s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (32 MB) to disk... took 0.153s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
tried flashing twrp and got
Code:
C:\Users\coolp\Downloads>fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
Click to expand...
Click to collapse
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.

enzyne said:
Try new platform tools. Then try different computer and usb cable. Preferably the usb c to c cable.
Click to expand...
Click to collapse
I did the new platform tools and it worked. I was not capable of using another cable since I dont have an adapter for the c to c.

How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot

dattaway said:
How odd. Latest platform tools from google. Two computers. Two pixel2 phones. Yes, TWO phones! Four cables. All the exact same result. The deuces script wiped twrp and I'm beginning to believe it installed a borked bootloader:
fastboot flash recovery twrp-3.2.1-0-walleye.img
target reported max download size of 536870912 bytes
sending 'recovery' (32768 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
fastboot --version
fastboot version 0.0.1-4500957
Installed as /usr/bin/fastboot
Click to expand...
Click to collapse
Are you flashing the proper factory image? Have you tried re downloading?

enzyne said:
Are you flashing the proper factory image? Have you tried re downloading?
Click to expand...
Click to collapse
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.

dattaway said:
How do I tell which is the proper factory image? There are 15 listed for the Pixel 2. Since I bought my two Pixel phones directly from Google, there appears to be 5 that might work, so I tried each one with identical results. SHA-256 Checksums match.
Click to expand...
Click to collapse
I just wanted to make sure there wasn't any data corruption. The most recent one which was .19 should do the trick if that's not working and you've tried everything else it may be time to do an RMA.

Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?

Rookx said:
Sorry to piggyback on a thread, but I seem to be having the same problem (I think). All I did was update Magisk to 16.0, then reboot my phone now I'm stuck in bootloader, none of the options do anything except make the screen go black for a minute then go back to the bootloader screen (assuming the bootloader screen is the one with the Android laying on it's back).
Is the main fix to re-flash a google factory image? OP said something about bad abd files, but I haven't even tried to push anything with adb since I rooted my phone last month. Or should i use the fix bootloop script in the other thread?
Click to expand...
Click to collapse
What your talking about is the android stock recovery not the bootloader.

Can't boot anymore on TWRP

Hello everyone !
I was trying to put a LineageOS on my OP7P with this rom.
I unlocked the bootloader, boot onto the TWRP image (this one), flashed the ROM and then I got into troubles.
When I flashed the ROM, I didn't see any "go back" button, so I just pressed the "reboot system" one.
I came back to recovery, only of course to see that I have the "basic" recovery menu. So I got into the bootloader mode and tried to fix this, nothing I did fixed it...
I tried and got :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrpop7pro.img
downloading 'boot.img'...
OKAY [ 0.692s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.692s
I have no idea why is it not working. I tried the fastboot oem unlock, but it tells me it's already unlocked.
Then, by seaching, I tried but got this :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-74-guacamole-unified-installer-mauronofrio.zip
target reported max download size of 805306368 bytes
sending 'recovery' (17872 KB)...
OKAY [ 0.389s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.405s
Which seemed logical to me as the OP7P has 2 slots, but when I searched alternative to this answer it only brought me back to the first answer.
So now I don't know what to do to boot again on a TWRP and fix all this. Thankfully, I can boot on my main system and my LineageOS is working. But I still want to root it with Magisk and use the NanoDroid installer.
Anyway, if anyone here has any idea to help me, I would be very grateful

Google pixel 1 stuck in fastboot!

Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...

SAMPPLE said:
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.

Homeboy76 said:
What do you mean the device is locked?
If the bootloader is locked you can not manually flash a factory image.
If the IMEI starts with 35 it is a verizon Pixel XL with a locked boot loader.
Go to this thread and try to unlock the bootloader.
If you are successful.
Download this Fastory image: 10.0.0 (QP1A.191005.007.A3, Dec 2019) from Prerequisites b.
in the guide below.
Download the latest SDK platform-tools r29.0.5 from Prerequisites c. in the guide below.
Use this guide to update to android 10 (Q). Do #4 'wipe data' then do #9 if you want to root.
Click to expand...
Click to collapse
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.

SAMPPLE said:
Thank you so much for your reply but the devices will not exit fastboot whatever I do and yes bootloader is locked.
Click to expand...
Click to collapse
What did you try to exit fastboot?

Homeboy76 said:
What did you try to exit fastboot?
Click to expand...
Click to collapse
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...

SAMPPLE said:
Cmd command fastboot reboot and let it drain until 0% and nothing... because power button is working like a volume button...
Click to expand...
Click to collapse
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.

Homeboy76 said:
How To Turn ON And OFF Pixel And Pixel XL With Broken Power Button
Google is your friend don't be afraid to use it.
Click to expand...
Click to collapse
I know I tried a lot of things to make it work... but nothing... Anyway thank you for helping me

put it in the freezer for an hour and tell me what happens, mine booted up with that, just put it in properly (all phone holes covered)