Database Develop

KitKat Update Crashed My Moto X - Unrecoverable?

Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris

cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.

xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.

cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.

Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!

xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris

SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s

cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip

Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.

SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak

Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?

waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.

jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052

waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin

Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052

waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.

Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052

I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140

ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?

Phone not booting after OTA

So today I got an update for a new firmware, it was a small 125 mb patch, no big deal. I downloaded it and installed it a couple of hours later, I leave it to install and when I'm back my phone is frozen on the Motorola logo and the "Powered by android" text written below, but it won't get past that. I left it for almost an hour and it won't boot, I tried forcing a reboot and it gets me back to the same screen.
Is there any way I could fix it, preferably while keeping my data? Especially the what's app gallery.
Thanks a lot guys, I'm kinda panicking here.
Ps. I'm not rooted, everything is completely stock.

it's Stuck on Moto Boto logo ?

Yes. I tried doing a factory reset and that doesn't work either, it sends me right back to the boot logo.

Sorry to not have any solutions but my girlfriends phone has probably had the exact same thing happen. At about 10PM tonight she got an update notification and told it to install. almost two hours later she checked the phone again to see it stuck on the boot logo and incredibly hot. She restarted it and same thing, stuck on the boot logo. Same as you, completely stock phone. Never been modified in anyway.
I had her go into recovery and wipe cache, no change at all. I've now had her do a factory reset twice as some similar problems mentioned that as a solution. No change, still just gets stuck on the boot screen.
My assumption at this point is that this update has completely trashed the phone and it's completely unrecoverable on the device at least.

I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.

darthlawl said:
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
Click to expand...
Click to collapse
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want

vaisakmct said:
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
Click to expand...
Click to collapse
My warranty is already over, I just want stock because I like it.
Are you sure a rom installation would work?

Ps. I can't unlock the bootloader since I can't access the OS

Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms

vaisakmct said:
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
Click to expand...
Click to collapse
What do you mean?

I'm a total beginner when it comes to android, I'm more of a windows guy. Can you walk me through the steps?

It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/moto-g-2014/development/original-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!

Wolfcity said:
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Click to expand...
Click to collapse
Its good guide follow these steps

If you want to go stock, I recommend you to go with the mfastboot method . . .
because it doesn't even need unlocked bootloader or any recovery,
The following link is having a mfastboot folder, in which, Moto G 2014(XT1068) stock 5.0.2 factory firmware is stored and, you just have to extract the folder and open it then pressing & holding shift + RMB and select "Open Command Window Here".
(Now press Power + Volume Down simultaneously, and you should go to the bootloader mode, if you don't know that )
Now in the command window, check your phone is connected with USB and type below code and press Enter.
Code:
fastboot devices
if any code(like for eg. ZDMJK2312) is shown, you're connected,
if not, try reconnecting the USB and try again.
Once properly connected, now you can flash the follwing commands one by one, to get your device to life.
Code:
Moto G 2014 Stock 5.0.2 Restore Script
------------------------------------------------------------------|
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
BTW this happened to me 6 months back and the same helped me.
mfastboot
Note : The above method is for only the model XT1068, because the firmware in the folder is for that model only, so plz make sure your model before proceeding.
And plz follow each and every step properly.
Thanks . . .

Alright thanks people! I'll try ArtRahul's method since it's easier and i was quite satisfied with stock. If that doesn't work I'll try Wolfcity's method.

Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!

darthlawl said:
What do you mean?
Click to expand...
Click to collapse
if ur phone is going to fastboot mode u can install twrp, no os is needed for doing this

darthlawl said:
Ps. I can't unlock the bootloader since I can't access the OS
Click to expand...
Click to collapse
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
you don't have to access to os in order to unlock the bootloader, go to android development section on this forum for moto g 2014 & follow any thread that guides about unlocking bootloader.

darthlawl said:
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
Click to expand...
Click to collapse
did anything work?
my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop::crying:
---------- Post added at 03:17 AM ---------- Previous post was at 03:03 AM ----------
it is giving me failed to validate system image error after first command mfastboot.exe oem lock begin

My beloved MOTO X 2014 2nd need a little help

Hello guys ! I am very happy that I found you ! I am apologize for my poor english, but you are my last hope of help. . .
My Moto X 2014 2nd was Flawless and perfect before the last OTA update in 2015.... After I installed, my phone don`t reboot anymore and freezing with the first white logo image about 20 sec and after appear a black screen with the "dead" android robot with red exclamation on it said "NO COMAND". The injured android logo just repeatedly flashes on for an instant and then disappears. Nothing happens when I hold the power button and press volume up. Anything I choose from bootloader is giving me the same result. I read all the pages from here and I am still stuck...
-I install everything: adb (it recognize the device - TA99303EV4) but every comand failed with a "REMOTE FAILURE" message. Fastboot or mfastboot - the same..... I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". Yeah, right - but I can`t do it now with this black screen
-The RDS Lite doesn`t recognize my device (many restarts, different USB ports and computers, nothing works...)
-Motorola Device Manager said: "No updates for your phone. Current Version: 23.16.3.victara.retes.retesall.en.eu"
-In the Device manager (win 7 32bit) it appears ok: Motorola ADB Interface
My Bootloader screen looks like this:
AP Fastboot Flash Mode (S)
60.16 (sha-496ce05, 2015-04-02 10:55:00)
CPU: MSM8974AC ES1.1
eMMC: 16 Gb Sandisk RV=07 PV=01 TY=57
DRAM: 2048 MB Elpida S8 SDRAM DIE=4Gb
Battery OK (Charging)
Device is LOCKED. Status Code: 0
Software status: Official
Transfer Mode: USB Conected
Dates extracted from adb (fastboot get var all) screen:
date:11-19-2014
sku:XT1092
ro.build.fingerprint: motorola/victara_retes/victara:5.1/LPE23.32-25.3/3:user/release-keys
ro.build.version.full:Blur_Version.23.16.3.victara _retes.retesall.en.EU
sdi.git: git=MBM-NG-V60.16-0-g582b967
The firmware that I trying to flash is:
BUILD REQUEST INFO:
SW Version: victara_retes-user 5.1 LPE23.32-25.3 3, RMBM Version: 60.16
System Version: 23.16.3.victara_retes.retesall.en.EU, Model number: Moto XAndroid Version: 5.1
Baseband Version: MSM8974BP_4235210.110.09.13R, Build Number: LPE23.32-25.3
Build Date: Tue Aug 18 04:30:10 CDT 2015
Blur Version: Blur_Version.23.16.3.victara_retes.retesall.en.EU
Please, help me... In my country there is nobody who can repair my beloved phone, I went 4 times to diferent service centers and nothing... Maybe with your help, my beloved MOTO X will be back to life again. If, OMG, IF i knew before to check/enable that option in the developer option - USB debbuging......
I wish you all the best for all and thank you so much for every posible answer !

Please corect me if I am wrong:
I thing that once OTA was upgraded the partition table, then I can`t never go back. Maybe the bootloader (motoboot.img) (also system) would ONLY work with the correct partition table. Meaning that I can't mix and match at all.
I think that means that I am currently stuck with the latest GPT from the last OTA i received. Somehow maybe the bootloader was downgraded and won't work for flashing other partitions ?! ...
That means that if I flash the new bootloader version and reboot, maybe it will be back to life. So guys, what version do you thing I must try to flash ?
Please respond me, I don`t know where to ask anymore... If I only could pass that "Device is LOCKED . Status Code 0" will be so. . . blissful

I have so much expectations from the MASTERS of this forum and nobody give me a chance. . . an ideea. . . I simply don`t believe: Am I the only one who has this stupid problem ?!?!
So, because of your complete silence (and only views) I understand that I have to throw my phone on the trash because:
- nobody told me that I have to enable this stupid USB debugging option on the first day when I bought the phone.
- nobody told me that I have to unlock this bootloader on the second day when I bought this phone.
- nobody told me that I should NEVER trust the OTA updates that destroyed my phone who works flawless before. . .
I will still wait, maybe someone, SOMEONE will find a solution for this idiot situation.
With all my great respect,
Matrix.

Hi,
You should be able to flash stock images without USB debugging enabled.
Can you explain a bit more how you tried to flash the image ?
Hope we'll find a solution,
Best regards.

I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .

Matrix_MotoX_2nd said:
I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .
Click to expand...
Click to collapse
Make sure your battery is fully charged before trying to flash anything. Sometimes a low battery can be the reason for the failure messages.

My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .

Matrix_MotoX_2nd said:
My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .
Click to expand...
Click to collapse
You need the xt1092 reteu 5.1 firmware.
Sent from my XT1095 using Tapatalk

Thank you so much for your answers ! All of you !
Can you give me a correct link ? There is so many xt 1092 reteu 5.1 firmware, and I want to be 100% sure that I`ll do it like you told me.
Can I look here for the corect one ?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1092/
I will try today again with this xt1092 reteu 5.1 firmware. But if the phone blocked every attempt to flash or erase its partitions, does it matter which firmware I send it to flash ?. . .
I`ll post the result as soon as I`ll arrive at home. Hope you are right, so much !
I really don`t understand why the Motorola official site who send me the unlock bootloader code special for my phone doesn`t work . . . It was so simple if it works. . .:crying:

Youre bootloader isn,t unlocked because off status zero.
Follow this guide.
https://www.youtube.com/watch?v=nLNja2M6zc0

With all my respect sir, you didn`t read my posts. . . .
I already past this stupid step, like I said:
"I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". . . . . . I already attach the image that proves what I am talking about and about. . .

So. . .bad news. Is the same error message, over and over again, with this firmware xt1092 reteu 5.1 . . . The phone simple don`t want to be flashed, don`t wanna accept any comand . Is there any way to flash SOMETHING on this phone ? I should try another program to flash, or something like TWRP recovery, or . . . another firmware ?
I don`t know, SOMETHING, SOMEHOW ?
I am sad. Very sad.
I attached a picture.
p.s the firmware that I tried was from here: http://forum.xda-developers.com/moto-x-2014/general/ota-t3132045.
and a little movie, trying every combination of pressing. . .
https://www.youtube.com/watch?v=vDTSncEvscM

wherever I tried to flash the RETES or RETEU 5.1 firmware, the phone respond with " invalid PIV signed system image". I am choose the wrong variants ?!?

Nobody can help me ? . . .

Matrix_MotoX_2nd said:
Nobody can help me ? . . .
Click to expand...
Click to collapse
Why dont you try flashing KITKAT Bootloader and image... It'll remove that silly option of OEM Unlocking in Developer Options... And maybe you will have luck with this... If the phone is already sort of dead, its worth a shot...
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
Also I wonder why don't you go back to MOTO Care, if your bootloader isn't yet unlocked they may help you with it..

I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).

@hamzaalijoiyah
"Why dont you try flashing KITKAT Bootloader and image"
I`ve tried with the same silly message - Failed (remote failure).... !!!!!
@Kayjay0x
Thank you for this new idea/trying to resurect my beloved Moto X xt1092. At first glance, there`s another adb and fastboot based programs, but I`ll give it a try again.

Kayjay0x said:
I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).
Click to expand...
Click to collapse
Bro you saved my day, I tried your method and it worked ! I updated the thread I started

Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml

YassGo said:
Bro you saved my day, I tried your method and it worked ! I updated the thread I started
Click to expand...
Click to collapse
Glad to hear it worked out for you like it did for me!
Matrix_MotoX_2nd said:
Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml
Click to expand...
Click to collapse
I don't know what to suggest other than trying your luck with a non EU rom? Can't promise that'll work though.

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.

[Q]Stuck in fastboot mode did not check ub debugging

So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English

Have you tried changing back to global rom using recovery mode through OTG cable?

kelv55l said:
Have you tried changing back to global rom using recovery mode through OTG cable?
Click to expand...
Click to collapse
i have not tried that, can you linkme how to do it?

Sinuhejrz said:
i have not tried that, can you linkme how to do it?
Click to expand...
Click to collapse
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!

kelv55l said:
I went to this link https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527
So basically you want to go into fastboot mode either using command "adb reboot bootloader" while plugging the phone into the computer or by holding down the volume down - and power button until it goes into fastboot mode.
Once you are in fastboot mode you go to "reboot to recovery mode" navigate while using the volume buttons and select by using the power button.
Now in recovery mode navigate by using volume buttons and select by using power button again. Its optional, but you can "wipe data" by wiping userdata partition and cache partition. I wiped data when I booted like this. Download the global from here https://global.redmagic.gg/blogs/news/red-magic-3-global-rom-flash-instructions I downloaded the North America version because that was the only version that worked for me. Put the zip file you downloaded into a flash drive USB. then connect the usb to the OTG cable you can buy from ebay, amazon or a nearby tech store. Then connect all that to your phone and click "Choose Update Package" and then click "Choose From OTG Device" then select the rom that you put in the usb drive and then everything should take care of itself from there.
Hope this helps!
Click to expand...
Click to collapse
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?

Sinuhejrz said:
i cant go into recovery mode when i select that option the phone restarts and the same message appears "your device is corrupt. it cant be trusted and will not boot" , what can i do?
Click to expand...
Click to collapse
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
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
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
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 dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!

kelv55l said:
Damn that happened to me to when I tried rooting my phone. My recovery mode was corrupt too. You can try to use the instructions given on this page https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057/page2. Extract all img and bin files from the Global ROM and place them into the folder where the "cmd-here.exe" is. Also you need "system.img" you can download that here https://drive.google.com/drive/folders/16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm, but dont download the other files they might be the Chinese files.
After you extracted the img and bin files and placed them into the folder where the cmd is placed connect your phone to the computer, open the cmd exe and run the commands
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
After all that you should be able to go into recovery mode through fastboot mode if not then try and flash dtbo.img and vbmeta.img in the line of commands so for example "fastboot flash dtbo dtbo.img" and "fastboot flash vbmeta vbmeta.img" looking something like this...
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 dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash system system.img
fastboot reboot
This was the line of commands I used when my recovery mode was corrupt and somehow worked
I hope this helps and let me know if it worked or if the issue is still there. Also the forum has several posts on this matter and they might have the answer you are looking for as it helped me with this issue. Good Luck!
Click to expand...
Click to collapse
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:

Sinuhejrz said:
OMG OMG OMG it works thank you so much dude you are THE MAN now i have more than an expensive weight-paper, i really appreciate it dude, the second code lines also works for me the only problem i encounter was in this code line "fastboot flash system system.img" throw this message "C:\adb>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi"
but i keep with the rest of the lines and works perfectly after that.
again thank you so much dude for the help :good::crying:
Click to expand...
Click to collapse
Awesome! glad I could help you out

kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?

Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Sorry man I haven't tried changing my ROM to Chinese yet. Don't want to risk corrupting my phone again :crying:
But I'll let you know if I decide to change my rom.

Sinuhejrz said:
tnx man i really appreciate it, so could you change the ROM of you phone to the Chinese one?
Click to expand...
Click to collapse
Pretty simple to change the ROM to chinese. Download the chinese ROM, place it in an OTG or the phone's root directory. You can either do it via local update from the system.update feature in settings or use the stock recovery and install it via the OTG. Personally I would.prefer you install it via the OTG.

Please help me !!! I have same problem with my rm3
Sinuhejrz said:
So i tried to change the global rom of my red magic 3 to the Chinese rom, i put the Chinese rom zip in the phone and i proceed to update it manually so it can be load, but when it was installing for the first time this error appears "your device is corrupt. it cant be trusted and will not boot", as i sais this error appears since the first time i tried to install it so did not have the opportunity to activate the developer options and check usb debugging and OEM unlock, i can use the bootloader to unlock the phone by using the command "fastboot oem nubia_unlock NUBIA_NX629J" but when i try to flash it by using this command "fastboot flashing unlock" this error appears "FAILED: (remote: flashing Unlock is not allowed)" so im stuck here, what can i do to continue or to go back to factory settings, i hope some one can help me.
im sorry for my bad English
Click to expand...
Click to collapse
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
kelv55l said:
Awesome! glad I could help you out
Click to expand...
Click to collapse
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:

hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
Give me your address, I'll come to your house to fix the phone!

hanif9067 said:
Please help me !!! I have same problem with my rm3 :crying::crying::crying: PLEASE
---------- Post added at 09:57 PM ---------- Previous post was at 09:49 PM ----------
PLEASE HELP ME Bro !!! I have same problem :crying::crying::crying:
Click to expand...
Click to collapse
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.

kelv55l said:
What seems to be the problem are you able to go into recovery mode?
If not then flashing the appropriate img and bin files should allow you to go back to recovery mode as explained on previous posts on this thread.
Click to expand...
Click to collapse
Mine has the same problem and tried all the steps in this thread. Not able to go into recovery mode, can go into fastboot mode and flash everything but phone is still corrupt and can not boot. New phone now no good, OH well

re-flashed the phone using the first version of the Chinese ROM v2.12 now can use the OTG update option. just need to get a usb adapter now

I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.

Johnnio said:
I'm hoping someone can help me. I've followed the fix on earlier pages and used the files including system.img a user uploaded.
Now when booting my phone I get a device is corrupt and cannot be trusted message. I read somewhere else that the command 'Fastboot flashing unlock' may solve this but I get an error message.
Would really appreciate some help, maybe I've done something wrong but I've followed the instructions and used the files an xda user uploaded.
Many thanks.
Click to expand...
Click to collapse
Have you tried to erase and then reflash again?
try something like this according from this user
em90256 said:
try this
fastboot -w
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot
try your stock recovery image
Click to expand...
Click to collapse

leipnacht said:
Have you tried to erase and then reflash again?
try something like this according from this user
Click to expand...
Click to collapse
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.

Johnnio said:
Thanks but I managed to fix it yesterday, I had to flash the system image using 'fastboot flash -S 100M system system.img', turns out that although it reported flash as successful it wasn't actually sent correctly unless split into smaller chunks.
Click to expand...
Click to collapse
Oh new information. What does "-S 100M" on fastboot command do?