Database Develop

help to unbrick

i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help

D3LTA-V said:
i have just rooted my tf701
but i messed up the bootanimation.zip
and want to revert the stock
i have downloaded WW_epaduser_10_14_1_47_UpdateLauncher
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot boo
tloader
< waiting for device >
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash boot
boot.img
< waiting for device >
target reported max download size of 643825664 bytes
sending 'boot' (5936 KB)...
OKAY [ 0.806s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 1.006s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.580s]
sending 'system' (1379 KB)...
OKAY [ 0.193s]
writing 'system'...
OKAY [ 0.057s]
finished. total time: 1.830s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash syst
em WW_epaduser_10_14_1_47_UpdateLauncher.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.108s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 348226856 is not a multiple of t
he block size 4096
OKAY [ 86.138s]
writing 'system'...
OKAY [ 17.136s]
sending sparse 'system' (340068 KB)...
OKAY [ 46.638s]
writing 'system'...
OKAY [ 9.278s]
finished. total time: 160.298s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.021s
C:\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
but i am still stuck in the asus logo
someone help
now fastboot wont even work someone help
Click to expand...
Click to collapse
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.

schmeggy929 said:
First I would retry >fastboot flash staging blob
also that updateLauncher.zip you have has to be extracted once more to get a UL-K00C-WW-10.14.1.47-user.zip then flash that. You will get the parse errors but let it finish. Gonna take awhile.
Click to expand...
Click to collapse
flash drgravy's recovery.img, the v47 blob, start recovery, sideload update 47 zip (this works without errors)

Well now I can't even go into fastboot.
I press and hold vol down and power button. My tf701 justremain stuck at the device is unlocked

so you can't enter the bootloader selection screen?
what does your pc detect when connecting it?

i can only get into APX mode thats all

what firmware version was it when you rooted? was it WW 47?

26 ww

D3LTA-V said:
26 ww
Click to expand...
Click to collapse
so you had root and a running V10.26.1.7
and did this?
WARNING: DO NOT FOLLOW THESE STEPS!
fastboot flash boot boot.img (of the 10_14_1_47)
fastboot flash system blob (of the 10_14_1_47)
fastboot flash system WW_epaduser_10_14_1_47_UpdateLauncher.zip
fastboot reboot
If you did, you bricked it at the point where you flashed the old boot.img (remember, 47 is the old one) and misflashed the blob to system (blob goes to staging...).
all I know can help here, is nvflash (apx), but I have not seen one supporting the TF701...

what can i do now?
i cant access fastboot
only can access apx

D3LTA-V said:
what can i do now?
i cant access fastboot
only can access apx
Click to expand...
Click to collapse
if that's what you did, I can't help you.

so the only thing i can do is to send to the service center?

D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
well it's "wait until someone leaks a newer nvflash", or "try sending it back". but I'm pretty sure they're going to charge you a fair amount of cash to fix it, as you voided the warranty (the unlocker app calls home, that's a fact). But I might be wrong. If I were you, I'd wait for a fix. But I'm rather patient. Maybe someone else has better idea...

D3LTA-V said:
so the only thing i can do is to send to the service center?
Click to expand...
Click to collapse
Well send it back in to a service center or Asus is the only thing you can do now.
Since you are rooted and unlocked (do you have some more experience with this?) it is possible to brick your device,
Especially when you make a mistake by flashing the wrong files.
Sad but **** happens.

Cant load phone to recovery mode

I was trying to install rom and something got wrong with phone it just keep restarting after huawei logo. I tryed to reinstall system through fastboot (FULL Huawei P7-L10C900B852)
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cust cust.img
target reported max download size of 536870912 bytes
sending 'cust' (400995 KB)...
OKAY [ 15.426s]
writing 'cust'...
OKAY [ 18.747s]
finished. total time: 34.176s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8072 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.970s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
sending 'cache' (8296 KB)...
OKAY [ 0.320s]
writing 'cache'...
OKAY [ 0.423s]
finished. total time: 0.745s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
sending 'userdata' (132497 KB)...
OKAY [ 5.089s]
writing 'userdata'...
OKAY [ 6.829s]
finished. total time: 11.921s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (523522 KB)...
OKAY [ 20.682s]
writing 'system'...
OKAY [ 24.469s]
sending sparse 'system' (523531 KB)...
OKAY [ 20.890s]
writing 'system'...
OKAY [ 24.489s]
sending sparse 'system' (454037 KB)...
OKAY [ 18.014s]
writing 'system'...
OKAY [ 21.367s]
finished. total time: 129.919s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13188 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 1.064s]
finished. total time: 1.577s
Now when i turn on phone it allways loads fastboot menu. When i try to load recovery menu it fails just keep restartint. Tryed curstom recovery like twrp and cwm, and also cant run.

danixlt said:
I was trying to install rom and something got wrong with phone it just keep restarting after huawei logo. I tryed to reinstall system through fastboot (FULL Huawei P7-L10C900B852)
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cust cust.img
target reported max download size of 536870912 bytes
sending 'cust' (400995 KB)...
OKAY [ 15.426s]
writing 'cust'...
OKAY [ 18.747s]
finished. total time: 34.176s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8072 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.970s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
sending 'cache' (8296 KB)...
OKAY [ 0.320s]
writing 'cache'...
OKAY [ 0.423s]
finished. total time: 0.745s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
sending 'userdata' (132497 KB)...
OKAY [ 5.089s]
writing 'userdata'...
OKAY [ 6.829s]
finished. total time: 11.921s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (523522 KB)...
OKAY [ 20.682s]
writing 'system'...
OKAY [ 24.469s]
sending sparse 'system' (523531 KB)...
OKAY [ 20.890s]
writing 'system'...
OKAY [ 24.489s]
sending sparse 'system' (454037 KB)...
OKAY [ 18.014s]
writing 'system'...
OKAY [ 21.367s]
finished. total time: 129.919s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13188 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 1.064s]
finished. total time: 1.577s
Now when i turn on phone it allways loads fastboot menu. When i try to load recovery menu it fails just keep restartint. Tryed curstom recovery like twrp and cwm, and also cant run.
Click to expand...
Click to collapse
Have you tried doing a force update? Just create a folder on your SD card called "dload" then copy the update.app to that folder and when your phone is turned off, hold down all three buttons to perform a forced update.

Need to go back to n6f26u to fix speakerphone.

Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.

bwquestion said:
Hey All,
I am attempting to install the n6f26u update to resolve the speakerphone issue, but my phone has already received a more recent (Oct 5, 2017) update from OTA. When I follow the instructions here
https://developers.google.com/android/images#instructions
the flash-all.bat sees that the bootloader is newer and stops, giving me an error.
I have looked all over this site and google, but do not see how to get around this. I do not know know if I am searching for the wrong thing or what, but any info on this would be great. I really need to go back to the previous version. I would love to be able to use this phone again.
Click to expand...
Click to collapse
Did you unlock the bootloader?

sd_shadow said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
I ran the command
fastboot flashing unlock
The result showed OK [0.000s]
The phone screen shows
Device is UNLOCKED. Status Code: 3

I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...

bwquestion said:
I jut ran it again, this time it made it further, but still stopped. Here is the last part. If the rest is needed let me know.
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8491 KB) OKAY [ 0.281s]
Writing 'boot' OKAY [ 0.262s]
Sending 'recovery' (13881 KB) OKAY [ 0.469s]
Writing 'recovery' OKAY [ 0.181s]
Sending sparse 'system' 1/4 (520563 KB) OKAY [ 17.749s]
Writing sparse 'system' 1/4 OKAY [ 7.980s]
Sending sparse 'system' 2/4 (523233 KB) OKAY [ 17.504s]
Writing sparse 'system' 2/4 OKAY [ 6.711s]
Sending sparse 'system' 3/4 (498449 KB) OKAY [ 16.863s]
Writing sparse 'system' 3/4 OKAY [ 10.087s]
Sending sparse 'system' 4/4 (32756 KB) OKAY [ 1.106s]
Writing sparse 'system' 4/4 OKAY [ 0.429s]
Erasing 'userdata' OKAY [ 11.269s]
Sending 'userdata' (4501 KB) OKAY [ 0.166s]
Writing 'userdata' OKAY [ 0.292s]
Erasing 'cache' OKAY [ 0.047s]
Sending 'cache' (120 KB) OKAY [ 0.022s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 103.359s
Press any key to exit...
Click to expand...
Click to collapse
Did it boot up?
Sent from my PH-1 using Tapatalk

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone was still showing the same screen. I did not want to mess anything up. When I read your reply I pressed the button on the right to "START".
The circle patterns are doing someting now. I will let you know when it is complete.

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The phone did boot. The set up ran and the settings show March 5 2017.
Thanks for you time.

sd_shadow said:
Did it boot up?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.

bwquestion said:
After a reboot of the phone, it only shows the word Google in while letters with an unlocked padlock on the screen. I can get to the original screen with the android and the status. Reloaded again, It boots up the first time, then reboot goes back to just Google with the unlocked padlock.
Click to expand...
Click to collapse
try a factory reset in recovery

As a general cautionary statement, when on a newer release and trying to go to an older release, don't use the flashall method. Fastboot flash system, boot and data separately. You don't want to run a chance that the bootloader downgrades. That might be one of the few ways to brick an N6.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

sd_shadow said:
try a factory reset in recovery
Click to expand...
Click to collapse
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.

bwquestion said:
Thanks, It is working now. Unfortunately it did not fix the speakerphone issue. I am now installing the February release and will sideload the OTA for n6f26u and see if it makes a difference.
Click to expand...
Click to collapse
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
If you are referring to the storage phone echo bug that occurred with the February 2017 OTA, Google addressed that in the March 2017 security patches
Click to expand...
Click to collapse
N6F26U is showing to be that release. I have loaded the factory image for March 2017, and also the factory image from February 2017 then side loaded the OTA for March 2017. Users still tell me there is an echo on the speakerphone when they talk to me. I can't figure out if I am doing something wrong or if it is just not working.

How to revert back to Stock Rom for Asus Max Pro M1 (and relocking the bootloader)

I owned an European version of Max Pro M1 (WW_X00TD) and I played with it with custom ROMs by unlocking the bootloader and install TWRP for flashing custom ROM.
When the trials done, I tried to flash back to the original international ROM (recovering the phone to original status including relocking the bootloader and re-installation of the stock recovery, etc.)
I searched the forum and also other web resources and I have tried an easier and more direct way to do this. Basically I used the Asus Fastboot flashing technique to directly overwrite the phone’s internal memory with stock data. So I guess this method can also be applied to a bricked phone
I think I should document the steps here so that in case other owners of this phone have the need to go back to stock, you can try the similar steps.
*Waning: I have only tried these steps on my own phone with the files suggested below. Proceed at your own risk.
1. Backup the important data in your phone
2. Get a Windows machine (7 or 8 or 10)
Install the Asus phone drivers for Windows
Visit this thread for downloading the rar file. One of the extracted files contains the drivers
This thread also contains the instruction to unlock your phone’s bootloader and install the TWRP
Download and install the adb setup files here in this thread
I used the one for Version 1.3 there
3. Connect your phone via usb cable to see if it can be properly connected to your Windows machine to make sure your drivers work.
4. Download the file [TuserHp.com]_WW_ZB601KL(ZB602KL)_14.2016.1802.247_20180419_AFT.zip in this thread
5. Extracted the zip file
6. Copy all the contents of the zip file to a folder under C: drive (in my case c:\asus )
7. Now reboot your phone into fastboot mode by pressing volume up + power on at the same time (make sure your phone has more than 80% power for the battery)
8. Connect your phone via usb connection to your Windows computer
9. Open the command Windows in your computer and navigate to the directory where you have extracted those files
10. At your command prompt, type flashall_AFT.bat to execute this batch file
11. Wait and watch the outputs while this batch file overwrites your phone internal storage with stock data
Here is the sample output:
c:\asus>flashall_AFT.bat
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is user
target reported max download size of 536870912 bytes
…………………………..<< truncated the outputs>>>>>
...
FAILED (remote: unknown command !)
finished. total time: 0.000s
...
FAILED (remote: unknown command !)
finished. total time: 0.033s
--------------------------------
begin to flash partition xbl
target reported max download size of 536870912 bytes
sending 'xbl' (2802 KB)...
OKAY [ 0.233s]
writing 'xbl'...
OKAY [ 0.021s]
finished. total time: 0.254s
done
--------------------------------
--------------------------------
begin to flash partition xblbak
target reported max download size of 536870912 bytes
sending 'xblbak' (2802 KB)...
OKAY [ 0.134s]
writing 'xblbak'...
OKAY [ 0.027s]
finished. total time: 0.161s
done
--------------------------------
--------------------------------
begin to flash partition tz
target reported max download size of 536870912 bytes
sending 'tz' (1916 KB)...
OKAY [ 0.165s]
writing 'tz'...
OKAY [ -0.000s]
finished. total time: 0.191s
done
--------------------------------
--------------------------------
begin to flash partition tzbak
target reported max download size of 536870912 bytes
sending 'tzbak' (1916 KB)...
OKAY [ 0.088s]
writing 'tzbak'...
OKAY [ 0.000s]
finished. total time: 0.111s
done
--------------------------------
--------------------------------
begin to flash partition rpm
target reported max download size of 536870912 bytes
sending 'rpm' (219 KB)...
OKAY [ 0.059s]
writing 'rpm'...
OKAY [ -0.000s]
finished. total time: 0.086s
done
--------------------------------
--------------------------------
begin to flash partition rpmbak
target reported max download size of 536870912 bytes
sending 'rpmbak' (219 KB)...
OKAY [ 0.023s]
writing 'rpmbak'...
OKAY [ 0.000s]
finished. total time: 0.073s
done
--------------------------------
--------------------------------
begin to flash partition hyp
target reported max download size of 536870912 bytes
sending 'hyp' (272 KB)...
OKAY [ 0.060s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.087s
done
--------------------------------
--------------------------------
begin to flash partition hypbak
target reported max download size of 536870912 bytes
sending 'hypbak' (272 KB)...
OKAY [ 0.027s]
writing 'hypbak'...
OKAY [ 0.000s]
finished. total time: 0.054s
…………………………..<< truncated the outputs>>>>>…………………………
done
--------------------------------
...
OKAY [ 0.081s]
finished. total time: 0.081s
...
OKAY [ 0.079s]
finished. total time: 0.079s
...
OKAY [ -0.000s]
finished. total time: 0.039s
All is download​
12. When everything done, the phone should reboot and you should have your phone restored to original stock Rom.
13. For my case, I can still normally get the OTAs so my phone can be updated to the latest updated Rom available from Asus

There is already a post with a very similar procedure, but already tested and approved by several people...
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Is there any difference or advantage in your procedure?

When i do this it show 1 was not expected at this time

Unbrick fastboot mode

After i i flash custom rom the i cant turn on the wifi so i decided to reset factory of my red magic 3 but after a rest i got stuck in FASTBOOT MODE no matter what i choice from reboot from recovery mode or reboot from system it will just restart and back again to FASTBOOT MODE can some one help me please is this permanent brick?
I USE ALL COMMANDS BUT DON'T WORK :
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ -0.000s]
writing 'vbmeta'...
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.819s]
writing 'dsp'...
OKAY [ 0.406s]
finished. total time: 2.230s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.219s]
writing 'splash'...
OKAY [ 0.031s]
finished. total time: 0.266s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144196 KB)...
OKAY [ 4.018s]
writing 'modem'...
OKAY [ 0.869s]
finished. total time: 4.888s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.780s]
writing 'boot'...
OKAY [ 0.469s]
finished. total time: 3.253s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.234s]
writing 'dtbo'...
OKAY [ 0.063s]
finished. total time: 0.297s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' (767446 KB)...
OKAY [ 24.161s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (786430 KB)...
OKAY [ 33.767s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (744616 KB)...
OKAY [ 30.043s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (786429 KB)...
OKAY [ 37.173s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (532404 KB)...
OKAY [ 26.319s]
writing 'system'...
OKAY [ 0.002s]
finished. total time: 151.675s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.800s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 3.339s

Instructions are everywhere. Follow them, or forever hold your peace.

after "fastboot flash recovery recovery.img"
write fastboot oem nubia_lock NUBIA_NX629J
and then fastboot reboot
u will get into recovery mode

Sir my Nubia red Magic 3 stuck on logo can any one help me please