Database Develop

[Q] Clarification on OTA bug fix update for Pure Edition

I have read the threads on the latest OTA update for the Pure Edition and I am confused on how to proceed. I am running System Version 22.11.6 Build Number LXE22.39.-6 and have got an OTA for 22.21.11.en.US, but it has failed of course. I am rooted with CF-Auto Root, the version from the middle of November, and have stock recovery.
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
What is the correct procedure for updating? Thanks Guys!!

I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device

Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!

Do not use the instructions on Motorola factory images website
That website is missing a subtle command, that will make your OTA fail. I had that problem.
This line is missing.
fastboot flash modem NON-HLOS.bin
The OTA checks for the integrity of the modem and fails otherwise.
---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------
Matthewlawson3 said:
What I am seeking to do is update to 22.21.11.en.US and not lose my apps or data.
Click to expand...
Click to collapse
You can try ADB backup for backing up all your apps and restore after OTA. This way the restore process works even after unrooting.

nimper said:
Since you're rooted, just run Titanium backup, return to 4.4.4, then apply .6 update and .11 update. (The .11 we have so far is only a delta from .6 -- not the full OTA)
edit: Apparently the full kitkat->lollipop .11 OTA is out there... hooray!
Click to expand...
Click to collapse
Android.is.better94 said:
I was on the first soak test build for lollipop and when the .6 build came out (the one that your on) I couldn't update unless I downgraded to 4.4.4 then re upgraded to lollipop OTA but it took a day for the OTA to show on my phone .....im pretty sure you have to do the same from .6 to .11 so https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images follow the steps on Motorola's website here really simple process just a few commands, but it will wipe your device
Click to expand...
Click to collapse
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.

Questions and Requests
bradley26 said:
I was rooted on .6 and had to go to 4.4.4. I received the OTA to .11. It was a 576 MB or so update. So there are 2 update OTA depending on what version you are running.
Click to expand...
Click to collapse
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625

Another Approach?
And what about this approach to upgrading from .6. to .11? Could this work?
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074

Matthewlawson3 said:
Ok. I have a few questions and requests.
First, this would be my first downgrade I have ever done, do I have to relock the bootloader and/or unroot first?
Second, what are the exact steps and commands in order to downgrade. I know you said they are Motorola's website, but just to be safe, and with the modem command added in, I would feel much better and be appreciative if someone provided that for me.
Third, I am on the US pure edition, which version of 4.4.4. would I need to download from Motorola's website? I've forgotten which version it came with.
Fourth, I was never a soak tester and I am on .6. Why can't I do a direct upgrade to .11 such as what is discussed here?
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ 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
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.

bradley26 said:
For whatever reason you can never have been rooted to update your ROM. So i followed the steps below to get back to stock for the update.
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ 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
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
Click to expand...
Click to collapse
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.

mrvirginia said:
@Matthewlawson3
you can't downgrade the bootloader so omit that step. it won't make the OTA fail.
i'd recommend erasing userdata and cache.
once you do this, you should get the official full OTA that you can check for in the settings menu and apply. good luck.
Click to expand...
Click to collapse
So motoboot.img is the bootloader? That is the command you don't want me to enter?
I need to type in all the commands in that exact sequence, correct? Where does one enter the fastboot flash modem NON-HLOS.bin in the sequence of commands?
I would prefer not to lose my apps and data if it can be avoided. I do have Titanium Backup and could if need be, but what are the downsides to not erasing usercache and cache?
Thanks for your help on this!!!

Motorola Fastboot
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?

Matthewlawson3 said:
I've never used the Motorola Fastboot utility. How does one acquire it and how do you set it up? I've only use the Android fastboot in the platform-tools folder.
Also, which build of 4.4.4. do I choose from on graffinxnyc's website? 4.4.4 Build: KXE21.187-42 Full Restore Images?
Click to expand...
Click to collapse
fastboot flash partition gpt.bin
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache

mrvirginia said:
fastboot flash partition gpt.bin
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase userdata
fastboot erase cache
fastboot reboot
I got the images from motos site. had everything I needed.
not sure what, if any, errors you'd see due to not erasing userdata/cache
Click to expand...
Click to collapse
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.

Matthewlawson3 said:
I have got the image for 4.4.4 (TMO_21.21.42.victara_tmo.tmo.en.US) from Motorola for the US Pure Edition, through the request process. Can I run these commands using regular fastboot from the android SDK platform-tools folder or must I use fastboot found in the Motorola 4.4.4 image? If I must use Motorola fastboot, what is the process for getting that setup before I go into a command prompt and enter the commands?
If I use the Motorola fastboot can I just copy the needed files into the Windows folder found in the Motorola image folder and then open a command prompt there to enter the commands? Is it that easy? I do not have a mfastboot file in the Windows folder in the image.
Click to expand...
Click to collapse
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?

Matthewlawson3 said:
After doing some research, I have placed the fastboot.exe from the Motorola image in the Android-SDK platform-tools folder, but before I placed it in there, I renamed it mfastboot.exe, so as not to clash with the android fastboot.exe. When I type in the command prompt "mfastboot," I get a list of commands. Does this indicate everything is working correctly? And if so, when I type in the commands to perform the downgrade will I type in "mfastboot" instead of "fastboot" with every command?
Click to expand...
Click to collapse
yes and yes

Ok. Thanks! One last question regarding the commands. After I flash partition gpt.bin, I am suppose to reboot from fastboot back to fastboot (reboot-bootloader) before continuing the commands..correct?

Flashing 5.0.1

I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6

SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.

Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...

So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error

mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6

SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.

SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!

Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360

I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.

dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?

mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.

Awesome man, worked perfect, you sir rock!

Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:

stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.

Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse

Flash LMY47E and Preserve Data

I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.

Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery

From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up

y2whisper said:
From what I've read you may need to flash twrp again even though you didn't flash the stock recovery. Just a heads up
Click to expand...
Click to collapse
Only if you boot android before rooting. Install-recovery.sh is suppled with the ROM that upon boot will install stock recovery. However flashing SuperSU hijacks this script for its own purposes, removing its ability to flash recovery. So trick is flash the ROM, boot straight to recovery and flash SuperSU

Ah. Good to know

rootSU said:
Its exactly correct. alternative is flashing a rooted stock ROM. Zip from recovery
Click to expand...
Click to collapse
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
EDIT: See your post above (I took too long typing). Thanks for clarifying.

ManHands said:
Yeah, thought about going the rooted stock ROM route. Just feel more comfortable with the factory image. Any truth to @y2whisper comments? Doesn't make sense to me how TWRP would get overwritten by stock recovery if it's not flashed.
Click to expand...
Click to collapse
Have a look above.

I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot

Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed

moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
rootSU said:
Sorry my fault...I didn't notice it didn't say boot.img in OP. Yes kernel should be flashed
Click to expand...
Click to collapse
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.

ManHands said:
Interesting... do I need to flash boot.img from LMY47E factory image if I'm using latest franco.Kernel? Seems silly to flash factory boot.img if I'm going to use franco boot.img instead. Thanks for the help fellas.
Click to expand...
Click to collapse
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.

Look at the op on Franco's thread and you'll have your answer

holeindalip said:
Look at the op on Franco's thread and you'll have your answer
Click to expand...
Click to collapse
If he looks in the Franco thread, it will answer his question about having to flash a stock boot.img?

moporoco said:
I use this without losing data, but perhaps this is overkill? I assume you can skip the recovery to avoid losing TWRP, but I don't know about the kernel.
{replace with actual file name}
Enable USB Debugging and OEM Unlock
Reboot into bootloader (vol-down + power) or adb reboot bootloader
fastboot flash bootloader {bootloader-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash radio {radio-shamu-xxx.img}
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?

rootSU said:
You're best off using a kernel that fully supports 5.1. I have no idea about Franco.
Click to expand...
Click to collapse
Brain fart, for future reference Franco r1-r19 is 5.0,5.0.1,5.0.2 and r20+ is for 5.1

Thanks for the input everyone. To follow-up, I took the steps just as I planned in OP. No need to flash boot.img as frano-r20 is what I'm running and is compatible with 5.1 (despite the build # difference). I also didn't want to encrypt as the factory boot.img will force encrypt.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
And just as @rootSU pointed out, prior to booting system, go into TWRP from bootloader to install su.zip first (otherwise factory recovery will overwrite TWRP). Then boot system, and you're back in business. Just had to re-do a couple build.prop edits, but everything else was as it was before.

If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?

lamenting said:
If I'm stock 5.1 rooted LMY47D with the modified boot.img without forced encryption (from here), can I just..
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
then reboot into TWRP, flash SuperSU, reboot and go about my day?
Click to expand...
Click to collapse
That, or you can wait for 47E factory boot.img that's non-enforcable. But, from the sounds of it people are still able to use the 47D boot.img linked in the post you provided. I'd imagine there's not much difference between the two.

Forerunner326 said:
Why do you prefer to erase the cache then flash the new one? Does this really matter as long as userdata.img does not get flashed?
Click to expand...
Click to collapse
I have no idea honestly, I saw someone else post it that way. It is probably not necessary.

ManHands said:
I just recently started fresh by unlocking and flashing LMY47D image. I'd like to upgrade to LMY47E and preserve data. I know I can backup/restore via TIBU, but I'd rather avoid that if possible. Am I overlooking anything by performing only the following commands? Also worth noting is that I'd like to retain TWRP and franco.Kernel.
Code:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash cache cache.img
At this point I'd use the hardware buttons to reboot into TWRP, flash su.zip, and then boot system.
I'm definitely going to perform a nandroid prior to doing this. However, just curious if this is the best way to do this or is there a better method. Or if there are any risks involved that I'm overlooking.
EDIT: Success... everything went just as planned. Thanks for everyone's help.
Click to expand...
Click to collapse
After flashing the files in fastboot you said to use the hardware buttons to boot into TWRP. How exactly did you go from fastboot to TWRP? Did you just power off while in fastboot or something else?

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

[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?