Database Develop

Any change to relock bootloader?

Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!

alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.

Why would you want to relock the bootloader just to get back to close as stock as possible?

I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.

nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!

TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.

alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.

edit:canceled

KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).

alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.

KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.

Thieves? How will having a locked bootloader protect you from thieves?

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291

AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?

pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request

AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)

Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???

I have a soft rocked Red Magic 3

Can anyone tell me what this (remote: Flashing is not allowed in Lock State).
What exactly is locked? Is my cell OEM unlocked?
I flashed the wrong TWRP (for the 2017 Red Magic-NX209J) and even though I have been able to unlock my cell via CMD commands; it remains permanently in fastboot mode?
If I send a CMD command to reboot it reboots straight back to fastboot mode.
No form of ADB connect seems to work an my windows PC cannot see/show the cell?
How the hell do I fix this? It's been in this state for a week.
Can anyone help?

Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.

xronaldx said:
Meaby try this?
Then, to unlock your bootloader, enter "fastboot oem nubia_unlock NUBIA_NX629J"
And meaby try the recovery backup instead of TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion. I have no recovery back up Is it possible to get past TWRP being locked and use CMD to flash the International or chinese ROM? Or recovery image?
Unless tools are developed to unbrick this device I am scared this problem might be permanent

Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444

Secretcow said:
Download this twrp, and then upload it to google drive or something so the rest of us can download it too .
Password is: 6i3i
https://pan.baidu.com/s/1ZdMPjm2fEwt...06770439204444
Click to expand...
Click to collapse
Thanks but what do i do with it? Its all in an asain language?

Link not open bro

The TWRP does not work
Sorry. That link to the twrp does not result in a bootable twrp recovery for me.
I am starting to think my cell is not fixable.
I did not do that much wrong I just flashed the twrp for 2 models of red magic earlier. It only has a fastboot mode. I either get a boot screen then fastboot mode or a warning about the bootloader being unlocked.
Whatever is wrong with my cell prevents ADB connect an the cell is not able to be seen by windows.
This $1100 New Zealand dollar cellphone may be permanently bricked by my mistake.
I might just need to bin it an buy another one.
Lesson learned.
It confusing....
My cell acts like it has a softbrick (can turn off an on an has fastboot options and I have erased it an OEm an bootloader unlocked it)
And also behaves like a hard brick (resists every method of repair).
I just do not understand it or Nubia products. I am unfamiliar with this phone.
Does anyone have any clue how I can see this cell on my windows pc or ADB connect it an boot into TWRP?
Are there any Nubia repair software tools?

I already share nubia red magic 3 twrp check my all post

sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Thanks for that. I'm talking about using CMD to totally wipe everything in the cell an reflash the Chinese ROM that came with it. Repair software. Might take months to develop software like that.

sandeepkhatri said:
I already share nubia red magic 3 twrp check my all post
Click to expand...
Click to collapse
Also it isn't a zip. It's some other kind of file. And does not boot into TWRP on my unit

So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Sent from my NX629J using Tapatalk

terrapin4 said:
So are you able to unlock your bootloader in its current state?
If you have an older TWRP installed maybe try changing the model on your bootloader command to match it:
fastboot oem nubia_unlock NUBIA_NX209J
If this works then flash the correct TWRP and the boot IMG from your original rom
fastboot flash recovery <new recovery>
fastboot reboot bootloader
Click to expand...
Click to collapse
Terrapin. Absolutely nothing worked. I am the 3rd person who has had this issue I know of. 2 other xda members had the same issue. One with TWRP like me an the other got stuck in fastboot mode after trying g to flash an apk of Gapps? I think these cells do not like tinkering. But your advice enabled me to be OEM and bootloader unlocked. But always.....straight back to fastboot mode no matter what I flash? My red magic 3 device is currently at a service center with a technician trying to solve the problem. I have 3 repayments left on my Xiaomi Mi9 that has zero flashing issues. O admit i.may be ignorant of the ways of Nubia ?

I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
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 system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.

emmegitony said:
I did it
I extracted the file system.img
this is what I did ....
starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm?usp=sharing
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
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 system system.img
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
Click to expand...
Click to collapse
Thank God. Maybe the Chinese service guy I'm paying will get on xda an try your idea. I'm being lazy saying that lol. Thanks very very much. I will show your post to the service guy who has my red magic 3 or try it myself.
There's no way your a junior member working all this out. I'm a junior member listed as a senior member who makes rookie flashing errors with Chinese cellphones lol.
I will share if I can implement your ideas successfully. Thanks buddy my missus really loved this phone I felt really bad when I incapacitated it.
Fingers crossed.....

I have no idea how did you managed to flash the system.img
C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
LE: After this error, somehow it manages to continue and flash all partitions of the system, but after above tutorial, the phone still reboots in fastboot mode and cannot access recovery

The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050

sakilxda said:
The solution is here:
https://forum.xda-developers.com/re...tboot-mode-t3937527/post79715050#post79715050
Click to expand...
Click to collapse
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner

Bryceicle1971 said:
Thanks for the help. I do not understand some of the commands an cannot seem to get them right? And I do not understand why the instructions say to cmd flash the image (IMG) via command prompt (which just errors like the strange NON-HLOS command?) Then the instructions say to flash the Chinese rom via otg?
Are you supposed to flash the ROM twice?
Can someone please give me some more detailed instructions as this cell has been non functional about 2 months now.
Planning to fix it an give it to my partner
Click to expand...
Click to collapse
Hane you fixed the phone or not?

JerryYin said:
Hane you fixed the phone or not?
Click to expand...
Click to collapse
No still not working. Might try again when I have spare time. Very hard cellphone to fix

Bryceicle1971 said:
No still not working. Might try again when I have spare time. Very hard cellphone to fix
Click to expand...
Click to collapse
My suggestions is, download a full sd card update package, unlock the bootloader temporarily,extract the update file and flash the vbmeta.img to vbmeta partion, then flash the recovery.img to recovery partition, after that, try to boot into recovery through bootloader. You have to make sure that you use all the same file from same package, if you are use a low version vbmeta file to boot a high version system (or recovery ) it will not boot. the vbmeta is very important on this phone.

Device is corrupt. It can't be trusted and will not boot

Can't even fastboot flash boot recovery system...and thats all folks...waste of money.

Failed attempt to unlock the bootloader and instal TWRP ?

Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9

roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.

Just flash the ROM again..It will be back lm

mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked

SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first

SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.

xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.

SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot

mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.

SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?

mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.

SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick

mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?

SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone

Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.

Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
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 system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.

SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
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 system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it

Hows your phone?..Did it work.

Mi A2 has not slot b

As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.

gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.

Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.

You need to flash stock through EDL

Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b

gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.