[Nubia Red Magic 3 Questions & Answers] kaizerv:
Im back

I was really busy with real life that I didn't even have the time to check this forum.

Yes, it is big. I think mine is around 5gb+ after all the compiling. I think I delete it after that because I was pretty sure about my backup :p. I mean its a waste of 5gb+. Orait, lets try to do this again and see if we got lucky~

First of all, get the RM3S ROM here. http://ui.nubia.cn/rom/detail/64. Extracted that ROM in one folder and I'm just gonna repeat what I did. If you be reeeallly careful, you can use the oldest version one, but hey, I used the latest one n go YOLO all the way.

1. Convert system.new.dat.br into system.new.dat using Brotli

-A quick google will reveal the command as "brotli.exe --decompress --in system.new.dat.br --out system.new.dat" using CMD

2. Uses "Tool Unpack Repack DAT IMG v3 x64" (can be searched easily with google, yes the Thai developer one), by placing the system.new.dat + system.transfer.list into Input_DAT, then open the program and pick 7

-The extract system.img will be at SYSTEM_REPACK_FINISH > IMG > system.img and yes it is large. Around 5.2gb on mine

3. Then, download the latest ADB , go google "latest adb 2019" or something, just to be sure it is the latest adb, look the date of the upload.

So when it upload a large file to your phone it supposedly won't crash. I did saw somewhere, by changing

"fastboot flash -S 100M system system.img" into a different number will also overcome this problem.

4. Used these command on CMD (The first part was to clear your phone but somehow I got a better chance by using the default clear data on stock recovery then do these command but you still need to go through this phase if you boot loop out of recovery)

fastboot oem nubia_unlock NUBIA_NX629J

Fastboot erase boot

Fastboot erase recovery

Fastboot erase system

Fastboot erase userdata

Fastboot erase cache

Fastboot erase data

fastboot erase system

fastboot erase modem

fastboot erase dsp

fastboot erase vbmeta

fastboot erase dtbo

fastboot flash parameter parameter.img

fastboot reboot bootloader

fastboot oem nubia_unlock NUBIA_NX629J

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash splash splash.img

fastboot flash modem NON-HLOS.bin

fastboot flash dtbo dtbo.img

fastboot flash dsp dspso.bin

fastboot flash vbmeta vbmeta.img

fastboot flash -S 100M system system.img

fastboot reboot

6.Now I'm still in the boot loop but pressing volume down + power, I can go to the bootloader and can flash and go inside twrp which previously I keep going into fastboot again and again.

The next part is just a copy of paste of my previous guide with extra steps which I dont even know if that what make it tick...

7. Apparently, I flash nubia recovery before going to TWRP. From there > Wipe Data > User Data > Wipe again > Cache. Then, flash twrp, n continue like usual.

fastboot oem nubia_unlock NUBIA_NX629J

fastboot flash recovery twrp.img

If you have 0mB in Internal Storage, you need to go to TWRP > Wipe > Format > yes (Will incur the loss of data). Then repeat step 4 again.

Idk, if it's needed, I use "Universal DM-Verify, ForceEncryption" after the ROM flash.

8.Enter the TWRP > Enable MTP or file transfer in the Mount data/otg/related folder> Put your "WhateverNameYourRom.zip" via OTG or PC into the phone. Probably need to unmount others except data & cache.

Install the .zip > clear Dalvik/Cache.

9.Reboot

Enter the TWRP > Enable MTP or file transfer in the Mount data/otg/related folder> Put your "WhateverNameYourRom.zip" via OTG or PC into the phone. Probably need to unmount others except data & cache.

Install the .zip > clear Dalvik/Cache.

5.Reboot

So, a wild guess from me, your error would be flashing the system.img file and the error while flashing it. That can mean either two. The first one is your adb is not the latest as you say it is and caused it to crash bcus of the file too large ( I didn't have a problem on this after updating my adb and I think, I tweaked the number on the 100M command). The second one would be u f-ed up earlier than that, and create the system.img incorrectly. I try my best to help but can you post what u done and a screenshot of the error ?