Database Develop

[Q] Unable to use fastboot

After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.

I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s

antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.

g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!

antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too

g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!

antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?

g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry

1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.

Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .

Root Assistance RP2 Android 9 pie, latest updates.

Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)

Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk

blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin

In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock

blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.

Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html

xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445

LOCKED BOOTLOADER No USB DEBUGGING STUCK IN FASTBOOT LOOP

Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP

try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.

No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help

thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.

Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.

JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.

JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,

thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"

JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED

thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this

JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.

Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work

Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME

Did you flash the files from global rom?

same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?

godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.

Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.

Switch off the device and turn back on the Try going to recovery manually with vol and power button

(solved) Can't either unlock OEM or install recovery (Preflash validation failed)

Hello
I just purchased a cheap new Moto G7 Plus, only to install LineageOS on it. The phone is brand new and I just upgraded it to the latest Android 10.
I followed all instructions so far, and I am stuck, can't unlock the bootloader and/or install a recovery.
To unlock the bootloader I carefully followed instructions on the LineageOS wiki
Then I followed instructions on Motorola website
I received an email from Motorola with the unlock code
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
Despite the fact that it says OKAY, when I reboot in fastboot flash mode, I still see the message "oem_locked". So I am not totally sure that the unlock succeeded.
Then whatever I try, I can't install TWRP, see below :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
Z*****F5RR fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock CODE_RECEIVED_IN_THE_MAIL
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp-3.4.0-0-lake.img
target reported max download size of 536870912 bytes
sending 'boot' (30080 KB)...
OKAY [ 0.686s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.708s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.4.0-0-lake.img
downloading 'boot.img'...
OKAY [ 0.686s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I obviously googled a few time but can't find any working solution. Some says its because my OEM is still locked, others because the USB port or cable might be problematic. I tried on 5 USB ports and a USB hub and I have the same issue, and my cable is brand new. I also restarted the whole unlocking procedure, received another mail from Motorola, with exactly the same unlock key, unlocked 10 times, nothing changes.
Any hint ?
Cheers

Ok forget it, its solved. I am an idiot I forgot to activate developer mode in the settings

Fastboot boot twrp 3.4 infinitely?
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!

same
Richard2707 said:
Unlocked my oem, adp whenever I fastboot boot twrp 3.4 it just gets stuck on downloading. No fail code just stays on downloading infinitely. Would love some help!
Click to expand...
Click to collapse
trying on my xt1965-2 and having this same issue, did you manage a workaround?

The twrp file needs to be in the correct location and the name needs to be exact.
I use linux so check up on which locations to use in windows.
But on linux I open a terminal in the folder where twrp is located.
So if the filename for twrp is for instance "twrp-3.3.1-0-lake.img", the command needs to be:
fastboot boot twrp-3.3.1-0-lake.img (NO spaces in the file name!)
Fastboot then pushes the file to the phone and boots it.

What to do with a fully cleansed phone?

My attempt to install a custom rom has failed horribly and I'm left with a wiped phone. Is there a way to reinstall EMUI? Or still somehow get a custom rom?
I flashed lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img on system, but although there was no error message it didn't seem to do anything.
It's a LLD-L31

hasl3r said:
Is there a way to reinstall EMUI?
Click to expand...
Click to collapse
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...

-Alf- said:
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.

hasl3r said:
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
hasl3r said:
The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
Do you have TWRP installed instead of Recovery or eRecovery?
hasl3r said:
It's a LLD-L31
Click to expand...
Click to collapse
What is your regional variant? (Cxxx)

-Alf- said:
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
Click to expand...
Click to collapse
That worked, I'm not around a PC at the moment, I'll run the commands as soon as possible
-Alf- said:
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
Do you have TWRP installed instead of Recovery or eRecovery?
Click to expand...
Click to collapse
That booted into TWRP as well, so I guess?
-Alf- said:
What is your regional variant? (Cxxx)
Click to expand...
Click to collapse
How to I find that out? I tried google but didn't find information.
All else I got are the IMEI and:
Serial number: FPM4C18622002338
Product ID: 71171281
Many thanks already for your help btw

hasl3r said:
How to I find that out?
Click to expand...
Click to collapse
through the mentioned fastboot commands.

-Alf- said:
through the mentioned fastboot commands.
Click to expand...
Click to collapse
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)

hasl3r said:
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
Click to expand...
Click to collapse
Okay, try the following:
1. Download Service ROM
Unpack it, there's a dload file in Software folder. Copy dload as it is to the SD Card (without unpacking it!)
2. Download TWRP 3.2.1 https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
and copy it to SD Card
3. also copy to SD stock Recovery_ramdisk-9.1.img , download here:
https://mega.nz/#!M0FHlYhb!4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
4. Boot into your TWRP, select storage - SD Card, select "Install image", find TWRP-9.1 file and mark eRecovery, swipe. Go back, find recovery_ramdisk-9.1 file , mark Recovery, swipe.
5.Turn off the phone, use option 'Power Off' in TWRP's menu.
6. Press and hold Power & both Volume buttons .

-Alf- said:
Okay, try the following:
Click to expand...
Click to collapse
Amazing, thank you so much!
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.

hasl3r said:
Amazing, thank you so much!
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
Click to expand...
Click to collapse
Glad to help

-Alf- said:
Glad to help
Click to expand...
Click to collapse
Sorry to bother you again, just wondering if you have any advice. I tried flashing LineageOS 17.1, but realised that the bootloader is locked again. My unlock code doesn't seem to work anymore (check password failed) and I figured it's because I have to downgrade EMUI 9.1 to 8.0. Took me a while, but turns out that was not the issue.
Do you happen to have any idea what to try? Do I have to buy another DC Unlocker license?
I don't know if it's related, but "adb reboot fastboot" just reboots the device and I have to use the volume down key to get there.

hasl3r said:
the bootloader is locked again.
Click to expand...
Click to collapse
it's normal after using dload method
hasl3r said:
My unlock code doesn't seem to work anymore
Click to expand...
Click to collapse
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)

-Alf- said:
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
Click to expand...
Click to collapse
Turns out the problem was copy/pasting the unlock code instead of hand typing it..
So I could flash it, but then the reset failed. Just realised that EMUI 9.1 is a requirement though, so I'll flash that first and try again.

Edit: Nvm fixed it. Sorry if you got a notification anyway.

-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s

hasl3r said:
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
Click to expand...
Click to collapse
1. be sure that your bootloader is unlocked, try to unlock it again
2. In fastboot mode run command
fastboot erase system
and try to flash GSI again
3. Install TWRP 3.2.1 gaguga edition, in TWRP select Mount - mark System, go back, select Wipe > Advanced > mark System > Repaire or etc. > Resize file system > confirm, reboot .
Then flash back stock recovery and try to install GSI.
4. Downgrade to the lower build number via dload method
5. idk...