Database Develop

Lollipop 5.1 ROM From Android one MyPhone Uno Philippines

Someone please upload 5.1 lollipop stock ROM from Android one MyPhone Uno Philippines. This phone is similar to indian android one phones. Its internal memory is 4gb. Hence there will be no problem in moving apps to sd card.

Use this to take backup without rooting or unlocking boot loader
forum.xda-developers.com/crossdevice-dev/android-one-general/guidetutorialhow-to-backup-stock-rom-t2948442

Myphone Uno has just started sales in Philippines so i don't think someone will upload it till two weeks or more
Sent from my Micromax AQ4501

itsmuhammedmuneer said:
Someone please upload 5.1 lollipop stock ROM from Android one MyPhone Uno Philippines. This phone is similar to indian android one phones. Its internal memory is 4gb. Hence there will be no problem in moving apps to sd card.
Click to expand...
Click to collapse
Am I right in saying that, in terms of the Filipino Android One phones, the Cherry One has 8GB? I presume that the 5.1 mount point for the 4GB MyPhone Uno and the same-sized Indian Android One phones set to internal by default whereas the 5.1 mount point for the 8GB Cherry One and the same-sized Indonesian Android One phones is set to external by default ( http://forum.xda-developers.com/cro...framework-res-apk-boot-img-mount-fix-t3035598 ): I recall that Google Camera on the 5.0 4GB Android One phones in India won't save a photo unless a microSD card is inserted.

dabotsonline said:
Am I right in saying that, in terms of the Filipino Android One phones, the Cherry One has 8GB? I presume that the 5.1 mount point for the 4GB MyPhone Uno and the same-sized Indian Android One phones set to internal by default whereas the 5.1 mount point for the 8GB Cherry One and the same-sized Indonesian Android One phones is set to external by default ( http://forum.xda-developers.com/cro...framework-res-apk-boot-img-mount-fix-t3035598 ): I recall that Google Camera on the 5.0 4GB Android One phones in India won't save a photo unless a microSD card is inserted.
Click to expand...
Click to collapse
That is right sir.

Myphone uno stock rom backup available now in this forum

help!!
Kind Sir can you help me in my myphone uno. I want to go back in stock ROM. I've tried using the sp_flash tools.but it can't detect my phone. And I've used the stock ROM of micromax karbonn and spice hoping that it will be compatible with the device, but its not, can someone help me to go back to stock myphone ROM?

patymary said:
Kind Sir can you help me in my myphone uno. I want to go back in stock ROM. I've tried using the sp_flash tools.but it can't detect my phone. And I've used the stock ROM of micromax karbonn and spice hoping that it will be compatible with the device, but its not, can someone help me to go back to stock myphone ROM?
Click to expand...
Click to collapse
Copy all the image files from your stock firmware to the ADB folder ( I presume you know what it is) and connect your phone in fastboot mode. Press SHIFT and RIGHT CLICK and select Open Command Window and type "fastboot devices"(without quotes) to check whether your device is recognized or not. Then enter the following commands:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash secro secro.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
And you might be good to go. Remember that the system will take little time flash and after these steps.....
fastboot reboot
It will take some time for the first boot so be patient. And you have successfully flashed the ROM.:laugh::laugh:

Saurabh K said:
Copy all the image files from your stock firmware to the ADB folder ( I presume you know what it is) and connect your phone in fastboot mode. Press SHIFT and RIGHT CLICK and select Open Command Window and type "fastboot devices"(without quotes) to check whether your device is recognized or not. Then enter the following commands:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash secro secro.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
And you might be good to go. Remember that the system will take little time flash and after these steps.....
fastboot reboot
It will take some time for the first boot so be patient. And you have successfully flashed the ROM.:laugh::laugh:
Click to expand...
Click to collapse
sorry cant find the adb folder, can you guide me where? thanks

Adb or fastboot is the folder in which you have for example recovery.IMG to flash it on your phone. If you don't have it download the minimal adb which is very tiny in size, and try to flash..
Sent from my Sparkle V

Copy all the image files to this folder and follow the procedure I poster earlier....
Sent from my Sparkle V

Flashed Stock MM, now can't complete setup wizard

I was on 5.1, bootloader unlocked by sunshine. I rooted to enable tethering, and after did a full unroot. Once the OTA MM update came it couldn't install. Android on back and then rebooted. Instead of trying to fix the software, I decided to get MM from XDA. I flashed TWRP, updated bootloader from computerfreek's thread and flashed his rom for non-verizon.
Now once it turns on I can choose language. At the next page it says select wi-fi netowork, but no wifi networks show up and the Skip button is grayed out.
I followed the directions again and reflashed a few times, but the same result.
I then tried the Brazilian MM from iiwoodstock but with the same result. I flashed his with and without the linked kernal, but again, with the same results.
Any ideas? I was hoping to avoid flashing the stock images, but if that's my only option....

Well I got irritated enough and flashed stock. All is working now.
It was a pain because I only have Windows 10, so RSDLite was being irritating.
Here are the steps I wish someone had put together for me.
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Having ADB Everywhere helps. Just install this:
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Make sure your drivers are installed. I needed to go to motorola to download their software to get fastboot drivers to work:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/103535/p/30,6720,9277
Have a copy of fastboot.exe
(Google it or just do a search on your computer. You probably have a copy of it somewhere if you've ever done anything to a phone)
Here is a link to the .bat file I made that will flash it without needing RSD.
https://nofile.io/f/sh00er98rzM/servicefile.bat
In case someone finds this thread and the file is no longer hosted, here it the text of the .bat file (use Notepad++ or something):
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot erase clogo
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
(Have phone connected in fastboot mode - power plus volume down)
1. Extract the stock image into a folder
2. Put the .bat file in that folder
3. Put a copy of fastboot.exe into the folder as well
4. double click the .bat file
(wait for it to finish. If there's errors, don't worry, it should be fine. Worry when it's worth it. This is not a big deal)
done
I figured this out primarily because of RootJunky.com's youtube video.
https://www.youtube.com/watch?v=njXQYn53SPc

gr8hairy1 said:
This is for flashing this version (and only this version) of stock by using fastboot:
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334

ChazzMatt said:
any reason you wanted to flash an older version and the newest?
You flashed this:
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5 (January 2017)
But this is much newer (March 2017):
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
Click to expand...
Click to collapse
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed

gr8hairy1 said:
No reason. That was the first one I had come across. At the time I was out of state visiting family and their internet was extremely slow.
I didn't feel like waiting another 2+ hours downloading what seemed like a minor update.
....or does it fix anything? I haven't found anything showing the reason that update was pushed
Click to expand...
Click to collapse
Release notes here:
https://www.verizonwireless.com/support/droid-turbo-update/
Sent from my carrier unlocked LG V30+ US998

Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)

If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.

I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...

What is the reason for relocking the bootloader? You don't get the warranty back...

should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance

Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all

Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?

Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802

Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again

Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing

I think i did it without flashing the sparsechunk

I bricked my device after doing some stupid thing, what stock ROM do I get to fix it?

I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?

If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the January Patch Stock ROM

NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.

smyaknti said:
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
Click to expand...
Click to collapse
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?

NitrodiumSK said:
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
Click to expand...
Click to collapse
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.

smyaknti said:
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
Click to expand...
Click to collapse
Alright gotcha! Thanks a lot for your help

Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar

No issue downgrade
You can downgrade one power there is no issue of you downgrade it don't worry
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse

Any how can anybody provide stock rom oem fastboot mode with March update???

azhar63 said:
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
Click to expand...
Click to collapse
Yeah bro flash this room via fastboot commands

motorola one power
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:

aum25 said:
Yeah bro flash this room via fastboot commands
Click to expand...
Click to collapse
Did you flash that rom in 1942- 1 ??? I have the same model num and running oreo... Want to update pie??? Were you successful in doing that ? Because that firmware file was for 1942-2 ? Plz share experience.

rudranshrajput said:
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
Click to expand...
Click to collapse
Did you install any third party app or it happens by itself? I had the same problem but i was messing around with the moto app launcher. Anyhow, try flashing this stock rom with latest june security patch. Don't use TWRP, it is a full rom. Use Fastboot mode. Also backup your device, if you want your files back. This will do a clean install of the rom.
Here is the link: https://drive.google.com/file/d/1lLmDvX4R4o2Jqrhp1RQflap27jxe4hXS/view
Steps:
1) Boot your device into fastboot mode
2) Open flashall.bat and wait for flashing
3) Reboot

colorist said:
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
Click to expand...
Click to collapse
thanks by you my device just boot up in fastboot mod
thank you very much
best regard

Need help with phone bricked.
I was installing the Arrows OS in Motorola one power and after rebooting, the set is in the bricked mode now it's not responding to anything. Can anyone please guide how can I fix it?

I got similar problem.when I'm flashing arrows or others custom ROMs(1custom ROM,2twrp installer)and restart my phone no restarting only bricked.help only blankflash

Phone bricked after installing arrow is on p30 note xt1942-1
I tried the blankflash method but not working, I'm getting I/O error
Any ideas?

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

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

Failed attempt to unlock the bootloader and instal TWRP ?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hows your phone?..Did it work.