Database Users

Huawei Ascend XT2 Stock image Fix Brick With Unlocked Bootloader Access

OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521

Your first link for the userdata image says file not found when you go to that link.

UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse

Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.

aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either

FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs

The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse

the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?

one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?

HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!

mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse

divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw

If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse

divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.

Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.

Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS

same as above, i will even take the rooted system.img i have all other files needed.

I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it

littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2

Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
​My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.

[Root][Oreo][Guide] How to flash and root G5 with (opt. remove encryption)

Hello guys,
after testing around for days i thought it might be helpfull to post the honestly pretty easy procedure to install stock Oreo, root it and remove encryption if needed.
Disclaimer:
I am not responsible for bricked devices, dead SD-cards, lost data, etc.
Back up your data, app settings, be sure you remember your passwords, your device will be empty!​
Edit: It seems, theres a bug that, if you read this post on XDA labs, won't show you everything, it seems like it randomly skips some parts.
What you need:
Unlocked Bootloader
Motorola USB drivers
15 sec adb and fastboot uploaded by myself since the original links aren't working anymore https://multifilemirror.com/hgxxyrfyd7rx.
I originally got them from here (you may have to go into your device manager and select the adb drivers for your phone f.e. when you want to use adb push in recovery, see original xda site).
This will also install the google drivers.
TWRP 32bit (v.3.2.3-0)
TWRP 64bit (v.3.2.1-0)
Disable Dm-Verity & ForceEncrypt from here
Magisk and MagiskManager. Newest should probably work, i used Magisk-18.0 and MagiskManager-6.1.0
Most recent Oreo firmware (edit 08.19)
(I used this Oreo firmware found in this post)
Steps:
Be sure you backed up your data and app settings, your pictures, downloads, etc. It will all be lost!
Please read all steps before you begin.
Extract the firmware into your adb folder (where you installed adb, should contain 4 files), copy both twrp (32 & 64 bit) in there, too.
Boot into bootloader (hold power+vol down) and open a terminal inside your adb folder (shift+rightclick) and type in
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery (select recovery with vol buttons, then press power) and make a backup of EFS partition and persist folder (use file manager under advanced) and make another backup of system, boot and data and save both backups and persist to your SD-card or better your computer, too.
reboot into bootloader and check if your bootloader version is B.8.31 or above.
If it is B.8.31 or above DON'T FLASH BOOTLOADER!!! Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Also, unless youre sure your persist is absolutly ok (check here), please also omit the following lines:
Code:
fastboot erase modemst1
fastboot erase modemst2
They would reset your IMEI and usually it gets restored from your persist, but only if its not buggy.
Even if your persist is fine, as far as i know theres no harm in not using this commands (my persist is fine and i didnt use them).
Now paste following commands in your command promt in adb, in case you are BELOW B.8.31, add the bootloader commands from above between the first and second line:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Please make sure that it really flashed all sparsechunk 0-8.
Let your phone reboot itself after installation is done, then return to bootloader and flash twrp 64bit:
Code:
fastboot flash recovery name_of_twrp64bit_file.img
Boot into recovery, since your device is encrypted it will ask for a password, click cancel, then go to WIPE and click on FORMAT DATA and confirm with yes.
This will remove the encryption of your data partition.
Go back to twrp main page and click on REBOOT then RECOVERY.
Once back in twrp, either copy Disable Disable_Dm-Verity_ForceEncrypt.zip and Magisk-18.zip and MagiskManager-6.1.apk to your SD-card or use
Code:
adb push name_of_file /external_sd
or
adb push name_of_file /sdcard
to copy the files to your SD-card (external_sd) or Internal-Storage (sdcard). For this you may have to manually configure your adb drivers in device manager, see here under Notes.
In twrp go now to INSTALL and flash "disable-dm-verity&encrypt" an then REBOOT and SYSTEM.
Return to recovery and flash "Magisk-18.0.zip", wipe Cache/Dalvik at the end and reboot System
Once System has rebooted, install MagiskManager-6.1.0.apk from your SD-card.
MagiskManager should say that Magisk is installed and in settings under security, your phone should be decrypted.
Note: MagiskManager will only show full information when it has internet access, all you see without is if Magisk is installed.
If you want to encrypt your device again, do it but flash twrp 32bit, too, if it asks for a password, it should be your usual password which you also have to enter on every boot.
Some explanation:
Why twrp 64bit?
Because twrp 32bit is able to bypass encryption, however, it causes some problems:
In fact, probably every twrp without the bypass encryption feature would work f.e. older 32bit version 3.1.0. but 64bit offers some features as EFS backup.
If you flash 32bit directly it can bypass the standard encryption but formatting data fails every time when you booted System previously.
When you reboot recovery and format data again it works, but it needs to fail first, just rebooting into recovery 2 times doesnt work.
I dont know what would happen if you (after using your phone normally) reboot recovery and f.e. want to do a backup from data, though im sure i testet it out, but i probably forgot.
You need it later when you want to encrypt your phone again, for me it didnt decrypt data after i reencrypted my phone using my password.
Why reboot System between flashing Disable-encryption and Magisk?
If you do not, you get heavy lags in the first 2 minutes after rebooting System, MagiskManager will say that Magisk isnt installed and then your phone will crash and reboot. But after that 2. reboot everything works fine again, Magisk is back, no lags.
I remembered this post from Johny Cipeli, between flashing no-verity and magisk he wrote to reboot, so i tried and it worked without lags and crash.
You don't need to remove encryption:
You can root your phone without flashing Disable_dm-verity_and_force-encrypt, use then twrp 32bit, dont format data, just flash magisk.
I can say that it should work, because that was one of my first attempts (and it worked for me), however i didnt write down what i was doing so i cant tell you step by step.
Additional:
In case you're searching Viper4Arise for Oreo, the Aroma installer won't work, use the Magisk module and install in MagiskManager. You can download it here from Zackptg5
If youre also annoyed by that One-Nav vibration, you can try using ExKernelManager app and activate the powersave mode. Although i think its officially not for G5, the app works, maybe that only refers to the Kernel and not to the app.
I tried Flyhigh Kernel, it didnt boot after flashing it, if you know a working Kernel for G5 which can disable One-Nav vibration, please write an answer.
My device:
Rooted Stock Oreo 8.1.0: OPP28.85-16
Bootloader: B.8.31
Model: XT1676 reteu
Stock Kernel
Thanks to:
Snoop05 for 15 sec adb and fastboot.
TheFixItMan for twrp.
Zackptg5 for "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers".
topjohnwu for Magisk.
freeZbies for Official Oreo 8.1.0 OPP28.85-16 Fastboot Firmware.
Wolfcity, woozie.2007 and TheFixItMan for answering many of my questions!

- reserved -

ok friend, thank you for this. I think you dont need to flash twrp 64, i only flash official twrp 32, which indeed doesnt have the option for backup persist, but only efs. Maybe is someone else that will try your method to decrypt, I will try next time when I flash the stock, maybe to the next patch update. Good luck and A happy new year !!!
---------- Post added at 01:31 AM ---------- Previous post was at 01:26 AM ----------
LE: You cant root without format data partition, because flashing twrp, when twrp decrypt data you cant see anything on data partition, so you need to format it even if dont need to decrypt the phone

Nice guide @G5-User7080 .
For me everything seems to be correct, I can´t say anything device specific as I own a potter but there shouldn´t be big differences.
There´s one sentence I´m not sure about:
G5-User7080 said:
Because if you flash bootloader of the same version or below, it would hardbrick your device!
That also means if you f.e. want to downgrade to Nougat, just ignore following lines.....
Click to expand...
Click to collapse
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
I´m about to do that on a device of a friend of mine , he is rooted on 7.0 and wants to go the way to flash the firmware he´s on and after that take the OTA up to Oreo.
He could flash the Oreo firmware directly but he prefers to use the firmware from which he knows it´s working and is the correct one.
Very careful guy.
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.

Some screenshots from XDA Labs and Chrome mobile to show the differences.

Wolfcity said:
It´s clear that downgrading the bootloader can hardbrick your device but why should there be any risk in flashing the same bootloader?
If I flash the fastboot firmware I´m on shouldn´t it be ok? Where did you get that information from?
Click to expand...
Click to collapse
I read this more then one time, although i could just find one source for now: "Flashing bootloader of equal or minor version will hardbrick your device" from Oreo Fastboot firmware.
I dont know why flashing bootloader of the same version would do lead to a hardbrick, but didnt want to try it out myself, also i see no problem in not flashing the bootloader when you already have the same version.
Wolfcity said:
Edit: I just recognized that the part you called steps incl.the part I quoted isn't visible in XDA Labs, I'm only able to see it in mobile browser. Also some download links aren't there, on XDA Labs there is only the one for the 64bit recovery visible, not the one for 32bit. Maybe it's some kind of format problem, bb codes or else.
Click to expand...
Click to collapse
Thats weird, i dont have XDA labs (thats the mobile app, right?), i wrote it on XDA desktop version and only used the size, code, color and list tags, hmm maybe it has problems with the sorted list, for every other part i used the unsorted ones with dots instead of numbers.
Quick test:
Test One:
this is made
in an unordered
list, using
list tags
Test Two:
this is now made
in an ordered list
counting from one to four
using list=1 tags
Can you read both lists with each four points?
And thanks for mentioning the bootloader thing,.. i realized i forgot to paste the lines in to flash bootloader in case you are below b8.31 ehee..

Wolfcity said:
Some screenshots from XDA Labs and Chrome mobile to show the differences.
Click to expand...
Click to collapse
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow

To flash the same vers of bootloader is not a problem, only the below one will hardbrick the phone

G5-User7080 said:
wtf, it just skips random parts ?!!!
I have no idea what could cause this.. ill better add a note at the beginning of the post...wow
Click to expand...
Click to collapse
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...

Wolfcity said:
Your lists are both readable.
I took a look at the BB codes as it's known that some of them are not working on XDA Labs like SIZE or HIGHLIGHT. In that case the BB codes are shown in the text but there's nothing missing.
Maybe it has something to do with the use of
[*] in your text?
Edit: Have you changed something in your text now? It seems to be complete on XDA Labs now too...
Click to expand...
Click to collapse
the [*] just create new lines for a list, and yes, i edited it two times, first, i added that one should use the bootloader commands in case of being below b831 and then i added the info about missing things on xda labs, but i didnt change anything on the lists itself,...

[ZE550KL] Unbrick Experience, QCN recovered, working from 9006/9008

First of all, thanks for all the people here provide very useful message.
Acutally I encouter a lot of similar issues across the posts.
Please refer to the posts here:
Unbrick guide Z00l Ze550kl
Need QCN file for ZE550KL/Z00L (2GB Ram) Please.
[Solved]Stuck on logo when booting into custom ROM( Zenfone 2 laser ZE550KL Z00LD)
My model is ZE550KL 2GB/16GB version.
What need to be prepared (please look around from google)
1. CSCImage for recovery
2. QPST 2.7
3. Workable QCN, if you have no backup please make one from the other post. (you will need imei coverter and HxD)
4. Retail image WW_ZE550KL_1.17.40.1234-rel-user-20160304185904-secured-releaseAFT_QC
5. Offical latest image
6. TWRP
7. Minitool Partition Manager (I tried diskpart but not working, so please use this one)
8. Qualcomm Driver
Here are the procedures for reference (I do this for over 10 times and 3 nights)
Please make sure you have working QCN...otherwise you cannot recover the calling feature.
1. Erase aboot
fastboot_8916 erase aboot
use above command to erase the partition
you can unplug the battery and cable and replug them.
or simply use fastboot reboot command.
Result: Device enter into 9006 mode
2. Open Minitool Partition manager
Right click and Delete all partition.
Create one single partition using ext4 format
Once done, remove the battery and cable, replug them.
Result: Device enter into 9008 mode
3. If you installed QPST, you should have a program called QFIL
Please use it and extract the firmware from CSCImage, it should have all the items except emmc MBN, just copy it from the root folder.
If you do this correct (follow other post for more detail)
Replug the device will give you a fastboot screen
Result: Device with workable fastboot
4. Now you have a clean bootloader, but no other thing
Go to CSCImage and click flashall
Once it is done, all the partitions will be ok (sometimes I got /factory not mount, let's fix this later)
Result: you will have a engineering OS and bootloader unlocked, diag mode natively enabled.
5. Open Software Downloader from QPST, and recover the QCN, it will reboot the phone.
If you are not doing this correctly (and many issues here), you will get bootloop.
And you have to start over again.
My suggestion is do not touch any of the bootloader setting. (so do not try to use unofficial bootloader unlock guide)
Even you give a command like "fastboot oem adb_enable" it will cause a bootloop and have to start over.
So my suggestion is not touch any bootloader setting
Result: The phone calling and data should be recovered. You can test by making some call.
6. If you want to keep your bootloader unlocked, the retail image flashall you can search there is a "oem lock"
change to unlock and run it in fastboot mode.
Result: You will have a bootloader unlocked phone, with WW firmware.
You can start from here to do TWRP.
to fix /factory partition. you can install busybox and in adb shell, use mkfs.vfat for the partition.

What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)

christian.arvin said:
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
Click to expand...
Click to collapse
This means you didn't unlock your bootloader.
bootloader needs to be unlocked to flash the partition file, and then the partition will be recovered without data.

My bootloader was unlock.
I digged deeper in your method. And this is what i understand and let it be an information for those who will try.
Back up all partition before you delete all partitions. (Your serial and other sensitive data are stored in some of this partition)
Your method only restore 5 partition table that is inside the main0 gpt mbn.
Note: the whole partition table is listed in the both0 gpt mbn.
In my stupidity I renamed the both0 gpt to main0 gpt thinking that it would work. Instead I run into an unstoppable bootloader bootloop.
In an ending note my ZF2 Laser's only hope is a full eMMC reflash that requires external methods. Or let the official professionals handle it.

[UNBRICK] [WORKING AND TESTED 100%] Fix Hardbrick Meizu M2 easily without dongle

I thank Dinolek for creating this tool that allows the Unbrick of this device!
Hi, a few years ago, trying to change the logo partition of my Meizu M2 Mini I corrupted it and it went into HardBrick, I made threads where I asked how to do Unbrick and everyone told me that I had to use a dongle and other applications that were certainly expensive .
I tried with SP Flash Tool and gave authentication and bootrom errors. After a few years the developer Dinolek released a tool called Amonet.
I tried this tool and it brought my hardbricked phone back to life without problems.
This tool uses an exploit at startup that allows you to change the device's memory and, consequently, write the partitions, so if you corrupt the important partitions for booting such as: Logo, Boot or Preloader, you can use this tool for correct that otherwise you cannot access these partitions and the Bootrom.
The bootrom is a Read-Only memory and even if you remove the EMMC on the phone, the bootrom will continue to work.
Requirements:
PC With Linux (Tested) or Virtualbox with Linux (Not Tested)
Obviously the Meizu M2 Mini
Python3 and pyserial (on ubuntu/debian "sudo apt install python3 python3-serial")
And the zip file of the tool that I link to after.
1) Download the file that is in the link below
2) A very important step that, if not performed, does not allow you to use the tool (I had to do it several times)
Run the command "sudo systemctl stop ModemManager" and doing this causes the ModemManager to stop which can interrupt the Unbrick.
3) After extracting the zip of the tool enter the folder and start the terminal. Run the command "sudo ./main.sh -u"
4) At that point it will be looking for the phone bootrom. Switch off the phone press the VOLUME button - (WITHOUT PRESS THE POWER BUTTON! OTHERWISE DOES NOT RECOGNIZE THE DEVICE!) and connect the cable.
5) At that point the Unbrick process starts, at this moment the program is flashing the most important partitions of the device and can take some time. Do not disconnect the USB cable, you could corrupt important partitions, if you do you have to restart from step 3. Unplugging the cable does not corrupt the bootrom and the phone can still be unbrick but it is not recommended to do so and it is very dangerous.
If it happens that at the beginning the Tool does not recognize the device do not worry, turn off the device, run the command "sudo systemctl stop ModemManager",and try again at point 3.
After the procedure the phone will come back to life and it will restart in recovery, from there install the stock rom and your phone will return as before, if the bootloader was unlocked before the brick remains unlocked and you can also flash the TWRP and Custom ROMs without the need to unlock it again. If by chance the bootloader is locked then follow the guide in this link: https://forum.xda-developers.com/meizu-m2-mini/development/tool-amonet-meizu-m2-t3945812.
To download the tool go to this link: https://forum.xda-developers.com/devdb/project/?id=33492#downloads and download the zip file.
Thanks to Dinolek.

fgfdf

@XRed_CubeX Hello! maybe you still have amonet_mblu2.zip? the original link is invalid. I urgently need to get my brick back into operation. Thanks in advance)

WhiteDevil_ said:
@XRed_CubeX Hello! maybe you still have amonet_mblu2.zip? the original link is invalid. I urgently need to get my brick back into operation. Thanks in advance)
Click to expand...
Click to collapse
Amonet isn't supported anymore, use MTK Bypass Utility

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***

mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?

That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.

mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.

Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.

mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe

Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)

Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.

VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.

mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.

I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.

apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.

mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!

Okay I can't add anything special but daaamn this community is amazing. So much help I love you all

To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse

Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw

mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.

VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.