Recently I rooted my phone and flash the resurrection remix naught in moto g3 xt1550....
For some reason I start to flash firmware ROM .....but it is not flashing.... Shows " preflash validation failed " and on system image " invalid image" .......... I tried many times but it didn't flash......when I skip the partition gpt file then every image file start flashing and phone start..,..
But their is no network......
After that whenever I switch off or reboot or go to recovery rather than that it start boot loader....
Then I flashed the resurrection remix again..... When I press reboot after flashing then it goes to boot loader......
At boot loader I press power on then it start booting and there is no network in this ROM too......
What can I do now ...... Please help.........
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
yes U will get the error of "preflash validation failed" cause of the security update which motorola released for the month of October, January and recent April.... Do one thing again flash the appropriate stock rom according to ur mobile But skip these two steps/Files >>> 1) fastboot flash partition gpt.bin and 2) fastboot flash bootloader bootloader.img and enter the remaining command/or follow the whole procedure but skip these two file mentioned above U will succed:fingers-crossed::good:
For ur simplicity im providing u commands and plz CHECK UR SPARSECHUNK Files it varies according to mobile I have 7 thats y 7 sparsechunk files DO CHECK URs ok>>>>
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Do it ur own risk Im not responsible for any damage :laugh:
everything went well except my network .........i checked in about phone < status < imei no is " 0 ".......how to restore that...........i think thats why the network isn't showing.......................
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
heisenberg1546 said:
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
Click to expand...
Click to collapse
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
acejavelin said:
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
Click to expand...
Click to collapse
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
heisenberg1546 said:
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
Click to expand...
Click to collapse
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
acejavelin said:
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
Click to expand...
Click to collapse
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
heisenberg1546 said:
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
Click to expand...
Click to collapse
I don't know... There is a thread here specifically about it, you will have to look there.
I want to keep the custom rom (RR-O-v6.0.0-20180511-ospreyl) with all networks
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
Hey, I have installed RR-O-v6.0.0-20180511-osprey on Moto G(3rd Generation), and now the error is: "No sim Detected ", IMEI number is fine. I want to flash radio firmware in this custom Rom. Will flashing radio stack of stock rom 6.0.1 (Moto G3 x1550) work?
adb reboot bootloader
fastboot flash modem NON-HLOS.bin (That must of Moto G3?)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img (Is it to be of RR or of Moto?)
fastboot reboot
Is there any other option or solution then please mention.
You need to flash stock firmware first then your network problem solved then you can install custom roms?
Good Luck!
Related
Hi all,
Since Sunday I try to solve the hard brick of my Moto G XT1032. I was on a rom GPE in 4.4.4 (EU) and by making the MAJ Lollipop during the sunday, the tel reboot on the logo Motorola and nothing more.
I tested severals tutos on XDA and many french websites, as:
Http: // forum.xda-developers.com / showthread.php? T=2633272
http: // forum.xda-developers.com/moto-g/help/mo to-g-hard-brick-lollipop-t2998124
And a lot of the others...but nothing!
Well, I said myself it doesn't matter because mototool repair the tel with no problems, as usual. But not, many errors when I try of downgrade in 4.4.2 or in 4.4.4 with it. I tried to flash (cache/ system / data / Dalvik) with CWM and TWRP with one tens of versions all in all and impossible to make no anything to put back. I tried to install many rom's, always the same.
I have errors as " remote failure ", impossible of mount the partitions system/cache, hab check failed and more more more, i don't remember the other's errors...
I cannot copy files (like a rom) via ADB to the tel in mode bootloader and I don't know what to do anymore of the whole...
If you have an idea, I am interested because there I think that except the SAV ... i'am in bull***t. :silly:
Thanks to all of your help and good week!
(sorry for my poor english)
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
audit13 said:
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
Click to expand...
Click to collapse
I try but the problem it's adb, because it's impossible to synchronize my phone with it.
When i try "adb reboot-bootloader" in a shell, i have the error "device not found".
And it's impossible to continue the tutorial :
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
What is the solution for this?
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
audit13 said:
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
Click to expand...
Click to collapse
OK. I have a phone serial who appear on screen (with the command "fastboot devices"), but with the command "adb devices", i have no serial, so no devices attached...
EDIT : Into TWRP Recovery, i have the adb serial too
ok, now it's good I the phone turn on a retail rom 4.4.4.
For all those who have experienced the problem (a GPE 4.4.2 update to 4.4.4 and 5.0.1), the procedure is "simple".
Install adb+fastboot and copy the rom into the folder.
Fisrt, put your phone into bootloader mode and check the command 'fastboot devices"; you must have a serial into the shell. Boot on the TWRP recovery (2.7.1.1) and type the command into the shell "adb devices"; again, you must have a serial. If it's OK, format cache/system/data/dalvik and reboot the phone into the bootloader.
In my case, i use the rom RETAIL-FR_4.4.4 OTA.
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 erase cache
fastboot erase userdata
fastboot reboot
IF this does not work , it is still possible to achieve a different manipulation .
Take CWM recovery (Philz Touch for example) and try to push a rom with adb.
@+
You can't use adb commands when the phone is in fastboot mode. THis is why adb devices returns nothing.
Glad you got it working.
hello fellas
I just unlocked my bootloader, flashed aokp and used a little bit.
every Gapps i install stayed buggy, so I decided to install the original firmware than root it.
So I downloaded the original stuff
then:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Then it keep showing boot logo then android robot with deleting (something like that) on screen
and keep rebooting and doing this stuff for ever
Yes, I downloaded the right files for my phone
xt1544
I can still flash custom recovery and flash custom roms and boot them, but no stock roms
Could anyone help me?
Steps are looking correct... Is the file got currupted or what? I mean did u paused the file during downloads?
sagar27691 said:
Steps are looking correct... Is the file got currupted or what? I mean did u paused the file during downloads?
Click to expand...
Click to collapse
Nope :/
and it installs everything with no errors
OtavioMalzone said:
Nope :/
and it installs everything with no errors
Click to expand...
Click to collapse
Then u need to ask any dev. Or try steps again...
I've found my error. very stupid acctualy haha
my xt1544 has 6 system.img_sparsechunk parts, and all tutorials went only util .5
That's why it was not booting correclty!
anyway, tnx
Device: XT1031 converted to XT1028 for use on Page Plus. Bootloader unlocked. Rooted with SuperSU 2.46 Running Stock Verizon 5.1 ROM 221.26.7.falcon_cdma.Verizon.en.US
Recovery: TWRP 2.8.7.0
I accepted the new security update - http://forum.xda-developers.com/moto-g/general/moto-g-1st-gen-actually-security-update-t3362323
and when it tried to install the update, the phone just rebooted into TWRP Recovery.
So I flashed stock recovery from the Verizon 5.1 ROM and then tried the update again. This time it completed the update and rebooted but is now stuck at the Motorola bootlogo.
I'm able to reboot into fastboot.
I tried flashing system.img_sparsechunk.0, .1, .2, and .3, and rebooted but there is no change.
What can I try to get past this?
Before starting this I made a backup using TWRP Recovery, can I reinstall TWRP and restore that backup?
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
lost101 said:
it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
If the TWRP backup is still on phone, it might be worth transferring it to a PC / external OTG usb drive, as using the following fastboot command will erase it, along with everything else on internal storage:
fastboot command erase userdata
Click to expand...
Click to collapse
The TWRP backup was saved to an external OTG USB drive, so that's safe.
I was originally going to do the same as I did for the last update - http://forum.xda-developers.com/showpost.php?p=63976723&postcount=109 but tried it first and when it went straight to recovery, I figured I needed to flash stock recovery. I also figured I needed to flash system also, but it through me off when the sparsechunks were numbered 0 - 3 instead of 1 - 4.
I didn't see any errors when I did the flashes.
Right now my battery is drained all the way to 0%. Hopefully it charges back up.
I appreciate the response. Thanks.
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
lost101 said:
Do all fastboot commands including erase userdata. Change sparsechunk names to match the files in the firmware folder you have downloaded. Phone should charge on fastboot screen, but probably not if at a very low percentage.
Click to expand...
Click to collapse
I'm using this stock ROM: XT1028_FALCON_VERIZON_5.1_LPB23.13-33.7_cid2_CFC.xml.zip
The sparsechunk files in that zip are named:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
and I need to rename them:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Correct?
Then I would run the following commands one at a time and checking for an OK on each, correct?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
After that I can check that I can boot into the OS and then I can flash TWRP and restore my saved backup.
Does that sound right?
Thanks.
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Don't rename the sparsechunk files. I said change the name when doing the fastboot commands.
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
Edit: Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
OK, I got an error on the first one I tried:
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot devices
TA965000I5 fastboot
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.029s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Moto G Flashing\MotoG_Verizon_5.1_ROM>
And on the Moto G's screen:
cmd: getvar:max-sparse-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Is that a problem?
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
lost101 said:
Try flashing the latest available XT1028 Verizon 5.1 Factory Firmware Image:
XT1028_FALCON_VERIZON_5.1_LPBS23.13-33.7-2_cid2
Click to expand...
Click to collapse
OK, that worked. I was able to flash back to the stock ROM.
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Thanks for your help.
bw 1 said:
I'm wondering if there would be any issue if I were to flash TWRP recovery and restore my saved backup?
Click to expand...
Click to collapse
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
lost101 said:
I don't personally restore TWRP backups because of bad experiences, but as long as you are using the latest available TWRP you should be okay.
Click to expand...
Click to collapse
I decided to start over and not try to recover from the saved file. I don't think there was anything on there that I really needed anyway. All my pictures and stuff was synced to Google.
I'm guessing that I ran into a problem by not flashing the 4 system sparsechunks from the stock ROM to remove root and I wasn't able to flash the same 5.1 that I had on there since it was updated. Flashing the latest newer build Verizon ROM worked because it was the same as what was contained in the update.
I didn't receive another OTA update and system update shows my phone as up to date with:
Android version: 5.1
Android security patch level: 2016-03-01
System version: 221.201.2.falcon_cdma.Verizon.en.US
Build number: LPBS23.13-33.7-2
I'm back to having a working phone. Thanks for your help. Hopefully this will help others too.
Disclaimer: I am not responsible for anything that happens as a result of flashing these files.
Latest Build Nougat:NPJS25.93-14-18 Tested on: All retail variants: XT1621, XT1622, XT1640, XT1641, XT1642, XT1643, XT1644
Latest Build Oreo: OPJ28.111-22-1 Tested on: All retail variants: XT1621, XT1622, XT1640, XT1641, XT1642, XT1643, XT1644
Note: Motorola doesn't allow downgrading so once u flash O via OTA/Fastboot it isn't recommended to go back to N or any older build than OPJ28.111-22 .
Downloads:
Stock N: ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Stock O: ATHENE_OPJ28.111-22-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Note: If you're looking for a TWRP flashable version instead, please download that zip from the thread below, thanks to @Jleeblanch for providing this zip. Keep in mind that you can't take OTAs on this version as you'll be having TWRP and these zips don't upgrade your bootloader/gpt.
[ROM] TWRP Flashable Stock Firmware [7.0][8.1.0]
Procedure:
You must already have ADB and fastboot setup, check here if you haven't already as using adb/fastboot isn't within the scope of this thread.
How to Install ADB on Windows, macOS, and Linux
1. Download the file and extract the zip archive
2. Extract all the files to your fastboot folder. (Not needed if you have adb and fastboot added to the path, if you want to know how to do this, check this guide: How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC)
3. Restart the device in fastboot/bootloader mode and connect to your PC.
4. Make sure the system detects the device in fastboot mode, to verify this your command window/terminal shows a serial number when you type:
Code:
fastboot devices
5. Use the following commands now or you can use the flash scripts provided as attachments to this post:
NOTE: SKIP the oem lock begin and the oem lock commands if you dont want to lock your bootloader
Linux users will need to change the extension to .sh and add sudo before each command or directly run it as a root user .
To simply flash, run the "OEM Flash" file; to lock the bootloader, run "OEM Lock" file.
Manual method:
Code:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
Note: Many people have reported than flashing stock ROM after flashing a 64 bit Pie custom ROM leads to loss of IMEI. Just in case this happens to you, the fix has been made available by @Heeth21 . Also, some people suffer from having messed up Baseband, fingerprint detection or wrong IMEIs. Checkout both the threads here:
[Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue.
[Guide] [XT16XX] [Solve] G4+ Baseband/Network/Volte issue, Lost 1 IMEI & fingerprint
For someone who has hardbricked his device , please refer to the following thread to get the raw bootloader and partition table and then flash the ROM as mentioned above.
[GUIDE] Moto G4 Plus HardBrick SOLVED - ULTIMATE UNBRICKING GUIDE
Credits:
TeamReviver
Motorola Mobility LLC
Android File Host
XDA-Developers
Thanks OP, i have a question, i am right now using NPJ25.93-11 from november 2016 on my XT1641. Can i just enter those commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
without loose any data? thanks in advance.
was looking forward to this, thank you OP!
moonlightdrive said:
Thanks OP, i have a question, i am right now using NPJ25.93-11 from november 2016 on my XT1641. Can i just enter those commands:
without loose any data? thanks in advance.
Click to expand...
Click to collapse
Those commands look okay - as always, try to back up your data as much as you can before flashing, in case you have to factory reset your device. I personally would also include 'fastboot erase cache' as a command (without the quotes), to wipe your cache, which shouldn't affect your data. You may experience a longer initial boot time as your system rebuilds the cache.
It's up to you if you wish to flash and update your gpt and bootloader as well - I don't know if not updating to the latest bootloader and gpt may affect future updates.
echo92 said:
Those commands look okay - as always, try to back up your data as much as you can before flashing, in case you have to factory reset your device. I personally would also include 'fastboot erase cache' as a command (without the quotes), to wipe your cache, which shouldn't affect your data. You may experience a longer initial boot time as your system rebuilds the cache.
It's up to you if you wish to flash and update your gpt and bootloader as well - I don't know if not updating to the latest bootloader and gpt may affect future updates.
Click to expand...
Click to collapse
Thank you for your complete answer:good:. I will take your suggestion of wiping cache.
moonlightdrive said:
Thank you for your complete answer:good:. I will take your suggestion of wiping cache.
Click to expand...
Click to collapse
Good luck with flashing - also, might be worth flashing the logo.bin too, so your flashing list would look more like (if including the gpt and bootloader):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
moonlightdrive said:
Thanks OP, i have a question, i am right now using NPJ25.93-11 from november 2016 on my XT1641. Can i just enter those commands:
without loose any data? thanks in advance.
Click to expand...
Click to collapse
EDIT:
I report that it works perfectly (without loss of data).
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
echo92 said:
Good luck with flashing - also, might be worth flashing the logo.bin too, so your flashing list would look more like (if including the gpt and bootloader):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I just finished the flashing process, and it's all ok, everything works good now. thanks for helping me!
moonlightdrive said:
EDIT:
I report that it works perfectly (without loss of data).
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
Good luck with flashing - also, might be worth flashing the logo.bin too, so your flashing list would look more like (if including the gpt and bootloader):
I just finished the flashing process, and it's all ok, everything works good now. thanks for helping me!
Click to expand...
Click to collapse
Cool, will add it to the OP that it works fine on xt1641
How does one know which variants the referenced stock ROM applies to? I'm supposing it's any phone that lists NPJS25.93-14-4 under build number. Also, is this an official build direct from Motorola?
flroots said:
How does one know which variants the referenced stock ROM applies to? I'm supposing it's any phone that lists NPJS25.93-14-4 under build number. Also, is this an official build direct from Motorola?
Click to expand...
Click to collapse
Yes the ROM is officially signed by moto. Initial upload was done by the Moto Firmware team. It is confirmed to work on XT1641 and XT1643. Just like the Dec 1 Security firmware, this should probably work on the xt164* devices, as long they are retail versions. :good:
I will ask more people to try the same. :good:
A .bat file for commands would be really great..ease of use !
Thanks !
Sharp404 said:
A .bat file for commands would be really great..ease of use !
Thanks !
Click to expand...
Click to collapse
A zip containing the bat files has been attached to the OP. :good:
Great Job
I am now back to stock thanks for creating the fastboot rom i was eagerly waiting for it thank u
Anyone try it on xt1621?
Enviado desde donde estoy ahora. ¿Que esperabas?
tywinlannister7 said:
Yes the ROM is officially signed by moto. Initial upload was done by the Moto Firmware team. It is confirmed to work on XT1641 and XT1643. Just like the Dec 1 Security firmware, this should probably work on the xt164* devices, as long they are retail versions. :good:
I will ask more people to try the same. :good:
Click to expand...
Click to collapse
Can confirm it works on XT1640
Fede79 said:
Anyone try it on xt1621?
Enviado desde donde estoy ahora. ¿Que esperabas?
Click to expand...
Click to collapse
I dit, it works fine!
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
It is laggy, am i the only one?????
It only happens when i flash the firmware from PC!
When i install marshmallow and i updated to Nougat it worked so smooth. What could be the problem?
Is this rom compatible with XT1626? If yes: can anyone share a screenshot with system infos? Thanks in advance.
At first thanks to tywinlannister7.
Anyone tried the rom on the XT1622?
where is the files OEM Flash" file; "OEM Lock" file. ???????
diegomartinezlovey said:
where is the files OEM Flash" file; "OEM Lock" file. ???????
Click to expand...
Click to collapse
Check the attachment in the OP.
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Rasah97 said:
Hello everyone, i have big problem with my new motorola x force, i bought it with dead software. And i tried install new, (I'm doing it isnt first time). I get key for unlock from motorola service but is imposible. I get an error. This device can not be unlocked.
I guess first owner, forgot turn on develop mode.
Any idea? I'm tried flashing it with instructions from other thread https://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515.
I download soft from motorola, I'm tried first ver. android and new one. Everything without result.
Click to expand...
Click to collapse
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
TheFixItMan said:
You do not need to unlock the bootloader to flash original moto firmware
Just put it in bootloader mode and on your pc where you have fastboot and all the firmware files open a command/terminal prompt and type the following
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img (not all devices have this)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0 (flash all sparsechunks in number order - for example)
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Rasah97 said:
Sure, but When i done it phone starting with Motorola logo and restarting, I didn't have this file img with nr 1/4 I mean this fastboot flash system system.img_sparsechunk4
I download soft from Motorola, I don't remember version but it like 5.1? Middle one from list and in another one first vet same
Click to expand...
Click to collapse
Some phones may not have sparsechunks 0 & 4 - as long as you flash all the ones in the firmware in number order
I don't have your phone so I couldn't tell you what firmware to use
I have Motorola g5 so I can just tell you the process
And looking on that firmware thread it says you need to use mfastboot for system images - so see that thread for details
Long as everything is flashed successfully in the order I have written above including erasing user data
Sooo.... Could you tell me which comand i have to use ?
Related to no sim card issue?
I'm wondering if this is related to a problem I am having with mine phone. I flashed the official firmware (6.0) on my moto x force and everything works but the simcard. It says it's not loaded so I have no phone or cell data. My sim card works in other moto phones so its not that.