Database Develop

TWRP and 4.4.2 Unlocked Bootloader

I am trying to install TWRP on my OTA updated XT1053 Moto X running 4.4.2, when I tried to push TWRP to my phone I got the following error,
HTML:
./fastboot flash recovery /Users/broopa/Desktop/twrp-2.6.3.1-ghost-4.4.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9854 KB)...
OKAY [ 0.872s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.152s
Anyone have any idea how I can go around and install TWRP to get root functioning? I tried to use ./mfastboot flash recovery but that command was not recognized.

broopa said:
I am trying to install TWRP on my OTA updated XT1053 Moto X running 4.4.2, when I tried to push TWRP to my phone I got the following error,
HTML:
./fastboot flash recovery /Users/broopa/Desktop/twrp-2.6.3.1-ghost-4.4.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9854 KB)...
OKAY [ 0.872s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.152s
Anyone have any idea how I can go around and install TWRP to get root functioning? I tried to use ./mfastboot flash recovery but that command was not recognized.
Click to expand...
Click to collapse
first issue is your battery is too low second did you download mfastboot and put it in the same directory as fastboot and adb

broopa said:
I am trying to install TWRP on my OTA updated XT1053 Moto X running 4.4.2, when I tried to push TWRP to my phone I got the following error,
HTML:
./fastboot flash recovery /Users/broopa/Desktop/twrp-2.6.3.1-ghost-4.4.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9854 KB)...
OKAY [ 0.872s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.152s
Anyone have any idea how I can go around and install TWRP to get root functioning? I tried to use ./mfastboot flash recovery but that command was not recognized.
Click to expand...
Click to collapse
The easy way is to put mfastboot into SDK platform tools folder as well as twrp recovery. From there hold shift and right click your mouse and you should see a window pop up asking open a cmd window here , click on it
mfastboot flash recovery twrp2.6.3.1-ghost-4.4.img
Sent on my Gummy running Lenoto X

Using a Mac I can't simply right click the file, I am trying to track it down to move it to an easier location to access but I don't see it any where in my SDK. Is there a separate file I can pull from Motorola?

broopa said:
Using a Mac I can't simply right click the file, I am trying to track it down to move it to an easier location to access but I don't see it any where in my SDK. Is there a separate file I can pull from Motorola?
Click to expand...
Click to collapse
Well I have a windows machine
Sent on my Gummy running Lenoto X
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
flashallthetime said:
Well I have a windows machine
You can try putting mfastboot in a folder on your desktop as well as twrp and see if it works, man I'm as anti Mac is it can get, nothing personnel
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Sent on my Gummy running Lenoto X

broopa said:
I am trying to install TWRP on my OTA updated XT1053 Moto X running 4.4.2, when I tried to push TWRP to my phone I got the following error,
HTML:
./fastboot flash recovery /Users/broopa/Desktop/twrp-2.6.3.1-ghost-4.4.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9854 KB)...
OKAY [ 0.872s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 1.152s
Anyone have any idea how I can go around and install TWRP to get root functioning? I tried to use ./mfastboot flash recovery but that command was not recognized.
Click to expand...
Click to collapse
Try renaming the twrp-2.6.3.1-ghost-4.4.img to recovery.img then try again but only type recovery.img when using the fastboot command to flash the recovery I had to rename for mine to flash properly
Sent from my XT1056 using Tapatalk

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Soft bricked OP3T

Hello my hope :3
actually i cannot access my recovery or the os, if i start the device, its just a bootloop.
Fastboot is possible, but bootloader is locked and im not able to tick something in the develeloper settings because there is no os anymore.
C:\adb>fastboot flash recovery recovery_OBT7.img
target reported max download size of 442499072 bytes
sending 'recovery' (22237 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.529s
Click to expand...
Click to collapse
i tried the Snapdragon tool(MsmDownloadTool) also but only get this error: FirehoseWriteData Failed, do you have any suggestions? :c

Huawei phone bricked. pls help me

i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u

Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is

Can you enter erecovery??

Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)

rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later

rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s

Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.

LOCKED BOOTLOADER No USB DEBUGGING STUCK IN FASTBOOT LOOP

Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP

try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.

No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help

thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.

Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.

JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.

JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,

thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"

JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED

thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this

JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.

Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work

Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME

Did you flash the files from global rom?

same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?

godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.

Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.

Switch off the device and turn back on the Try going to recovery manually with vol and power button