Hi,
I was trying to flash stock rom to my Moto E Indian version. It was running Cm 12 but suddenly it stopped detecting sim card. so I used this script to flash the stock firmware
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 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
pause
mfastboot.exe reboot
but flash wasnt successful and its now stuck at recovery loop. If I try to flash any custom rom from recovery it says unable to mound data and system. Tried everything I know but doesnt help.
when I flash the above script it shows CM boot logo and gets stuck there
Using this stock firmware RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC
C:\MotoTool\ADB>"Retail+lock.bat"
C:\MotoTool\ADB>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.089s]
finished. total time: 0.092s
C:\MotoTool\ADB>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.577s
C:\MotoTool\ADB>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.099s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.574s
C:\MotoTool\ADB>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.233s
C:\MotoTool\ADB>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.101s
C:\MotoTool\ADB>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 1.757s]
finished. total time: 2.161s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (243072 KB)...
OKAY [ 7.676s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.348s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257254 KB)...
OKAY [ 8.128s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.197s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (201709 KB)...
OKAY [ 6.381s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.447s
C:\MotoTool\ADB>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.507s]
writing 'modem'...
OKAY [ 4.589s]
finished. total time: 6.101s
C:\MotoTool\ADB>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\MotoTool\ADB>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.025s
C:\MotoTool\ADB>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.106s]
writing 'fsg'...
OKAY [ 0.127s]
finished. total time: 0.237s
C:\MotoTool\ADB>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.369s
C:\MotoTool\ADB>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.415s]
finished. total time: 1.419s
C:\MotoTool\ADB>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.043s]
finished. total time: 0.046s
C:\MotoTool\ADB>pause
Press any key to continue . . .
C:\MotoTool\ADB>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
C:\MotoTool\ADB>
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
rizzee said:
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
Click to expand...
Click to collapse
Try the 5.1 factory images
please provide me the link of 5.1 if you have.
Here you go : Link
rizzee said:
please provide me the link of 5.1 if you have.
Click to expand...
Click to collapse
Why u all gave lock command at first?
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
rizzee said:
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
Click to expand...
Click to collapse
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
nilanko said:
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
Click to expand...
Click to collapse
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
rizzee said:
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
Click to expand...
Click to collapse
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
nilanko said:
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
Click to expand...
Click to collapse
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Click to expand...
Click to collapse
I'm confused which one to download and install, there are many different versions available.
rizzee said:
I'm confused which one to download and install, there are many different versions available.
Click to expand...
Click to collapse
I made a correctin to the previous post
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
nilanko said:
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
Click to expand...
Click to collapse
Maybe you're right... He does have the 5.0.2 bootloader... So, flashing the 5.1 gpt.bin won't do any harm.
At least that is what I think
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Click to expand...
Click to collapse
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
rizzee said:
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
Click to expand...
Click to collapse
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Rohitagni said:
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Click to expand...
Click to collapse
failed bootloader preflash validation failed
rizzee said:
failed bootloader preflash validation failed
Click to expand...
Click to collapse
It won't work unless you unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2753110
Related
Xt910 RSD faild to flash, ap fastboot ( flash failure) or stuck on logo solution.
Dear Friends,
a customer brought to me a bricked razr maxx xt910 which he has been rooted and bricked . i have tried many time to flash it with RSD but it failed to be flashed. i tried eveything but with no success. finally thanx to doub01 who had the problem in this thread http://forum.xda-developers.com/showthread.php?t=1796712 and fixed his mobile.i tried his way and bingo, it works. i'll explain the way he used to help others fixing their xt910.
1. go here http://sbf.droid-developers.org/umts_spyder/list.php and download 01.6.5.1-73 for your country.
2. download also 01.6.7.2-180 for your country.
3. extract both of them.
4. copy webtop_signed from 01.6.5.1-73 and all the files from 01.6.7.2-180 and paste them in c:\fastboot ( if you dont have it google for moto fastboot )
5. start cmd and write these commands (but you have to wait each command to finish then write the next one.)
cd c:\fastboot
moto-fastboot flash webtop webtop_signed
moto-fastboot flash cdt.bin cdt.bin_signed
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash ebr ebr_signed
moto-fastboot flash mbr mbr_signed
moto-fastboot flash devtree devtree_signed
moto-fastboot flash system system_signed
moto-fastboot flash boot boot_signed
moto-fastboot flash recovery recovery_signed
moto-fastboot flash cdrom cdrom_signed
moto-fastboot flash radio radio.img
fastboot reboot
thats it. Good Luck and wish that will help you as it helped me.
P.s for those who has a battery problem while flashing, use a factory cable ( connect pin 1 to pin 4 )
Best Regards
Mazen
Nice work brother:thumbup:
My friend has a XT910 running 2.2.3 i am thinking of rooting it i dunno the procedure can you guide me and i am from india wt firmware should i download for XT910 is it possible to flash md5 files through odin and also can moto razr XT910 have cwm recovery???
Sent from my GT-I9505 using Tapatalk 2
Sorry man for being late. For rooting xt910 u can use droid utility. U cant install cwm cause the bootloader is locked. U can use an app called safestrap which works as the cwm. No you cant use odin for motorola while you can use RSD to flash sbf. I will guide you tomorrow on how to flash, root and cwm.
Sent from my GT-N7100 using Tapatalk 4 Beta
Sure brother waiting:thumbup:m very new to moto n hve a few issues will tell ya everything 2mrw
Sent from my GT-I9505 using Tapatalk 2
So, can anyone help here?
Flashing 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b 57374ab5a_p2b_S1FF_fb_CFC.xml via RSD Lite comes back with an error message "Failed flashing process. 6/19 flash cdt.bin cdt.bin_signed ->Phone returned FAIL"
Flashing via Fastboot comes with these messages:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
0A3C0B8219013011 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) fastboot oem lock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.008s
C:\Program Files\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.012s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery-0.99.
3
target reported max download size of 1056964608 bytes
error: cannot load 'recovery-0.99.3': No error
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery_signe
d
target reported max download size of 1056964608 bytes
sending 'recovery' (9216 KB)...
OKAY [ 0.448s]
writing 'recovery'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.929s
C:\Program Files\Minimal ADB and Fastboot>fastboot erase boot
erasing 'boot'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot_signed
target reported max download size of 1056964608 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.399s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.872s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>
Is there any way at all to recover from this issue?
Help please.
which one is for germany pls
i hang in fastboot flash failure
Same issue
Lincoln357 said:
So, can anyone help here?
Flashing 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b 57374ab5a_p2b_S1FF_fb_CFC.xml via RSD Lite comes back with an error message "Failed flashing process. 6/19 flash cdt.bin cdt.bin_signed ->Phone returned FAIL"
Flashing via Fastboot comes with these messages:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
0A3C0B8219013011 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) fastboot oem lock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.008s
C:\Program Files\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.012s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery-0.99.
3
target reported max download size of 1056964608 bytes
error: cannot load 'recovery-0.99.3': No error
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery_signe
d
target reported max download size of 1056964608 bytes
sending 'recovery' (9216 KB)...
OKAY [ 0.448s]
writing 'recovery'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.929s
C:\Program Files\Minimal ADB and Fastboot>fastboot erase boot
erasing 'boot'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot_signed
target reported max download size of 1056964608 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.399s]
writing 'boot'...
(bootloader) Preflash validation failure
FAILED (remote: )
finished. total time: 0.872s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.009s
C:\Program Files\Minimal ADB and Fastboot>
Is there any way at all to recover from this issue?
Help please.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I have the same issue. My phone was rooted and had custom rom(s). Yesterday I managed to brick it and since then can't figure out how to unbrick it. Keep having same problems as him..
Thanks
jdorfsman said:
I have the same issue. My phone was rooted and had custom rom(s). Yesterday I managed to brick it and since then can't figure out how to unbrick it. Keep having same problems as him..
Thanks
Click to expand...
Click to collapse
The only way I could manage to unbrick it is by deleting CID. After that, flashed stock rom via RSD Lite, first stock ICS 4.0.4 then upgraded to JB 4.1.2, installed Safestrap 3.65 and flashed few custom roms and everything worked like a charm. Before deleting CID, nothing, and I mean NOTHING worked, always aborting flashing process at step 6 (cdt.bin). Tried every known method and nothing worked. I was ready to sell the Razr for parts or something, but I had nothing to lose so I deleted CID and voila! Worked like a charm. Search my posts here, there is a step-by-step guide on how to do it.
another source for stock rom images?
mazen_al_ahmar said:
Xt910 RSD faild to flash, ap fastboot ( flash failure) or stuck on logo solution.
Dear Friends,
a customer brought to me a bricked razr maxx xt910 which he has been rooted and bricked . i have tried many time to flash it with RSD but it failed to be flashed. i tried eveything but with no success. finally thanx to doub01 who had the problem in this thread http://forum.xda-developers.com/showthread.php?t=1796712 and fixed his mobile.i tried his way and bingo, it works. i'll explain the way he used to help others fixing their xt910.
1. go here http://sbf.droid-developers.org/umts_spyder/list.php and download 01.6.5.1-73 for your country.
2. download also 01.6.7.2-180 for your country.
3. extract both of them.
4. copy webtop_signed from 01.6.5.1-73 and all the files from 01.6.7.2-180 and paste them in c:\fastboot ( if you dont have it google for moto fastboot )
5. start cmd and write these commands (but you have to wait each command to finish then write the next one.)
cd c:\fastboot
moto-fastboot flash webtop webtop_signed
moto-fastboot flash cdt.bin cdt.bin_signed
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash ebr ebr_signed
moto-fastboot flash mbr mbr_signed
moto-fastboot flash devtree devtree_signed
moto-fastboot flash system system_signed
moto-fastboot flash boot boot_signed
moto-fastboot flash recovery recovery_signed
moto-fastboot flash cdrom cdrom_signed
moto-fastboot flash radio radio.img
fastboot reboot
thats it. Good Luck and wish that will help you as it helped me.
P.s for those who has a battery problem while flashing, use a factory cable ( connect pin 1 to pin 4 )
Best Regards
Mazen
Click to expand...
Click to collapse
Is there another soruce for stock images?
I can't find mine there.. (Israel stock rom)
What's CID
Lincoln357 said:
The only way I could manage to unbrick it is by deleting CID. After that, flashed stock rom via RSD Lite, first stock ICS 4.0.4 then upgraded to JB 4.1.2, installed Safestrap 3.65 and flashed few custom roms and everything worked like a charm. Before deleting CID, nothing, and I mean NOTHING worked, always aborting flashing process at step 6 (cdt.bin). Tried every known method and nothing worked. I was ready to sell the Razr for parts or something, but I had nothing to lose so I deleted CID and voila! Worked like a charm. Search my posts here, there is a step-by-step guide on how to do it.
Click to expand...
Click to collapse
Sorry, don't understand what the CID is that you're deleting. Would you mind expanding the acronym?
Thanks,
Deepesh
deepesh_wig said:
Sorry, don't understand what the CID is that you're deleting. Would you mind expanding the acronym?
Thanks,
Deepesh
Click to expand...
Click to collapse
CID stands for Customer ID which is preventing you to flash other firmware than the one which is meant for your country/region. By deleting CID via Fastboot, your phone becomes "unlocked" to flash any firmware world wide. That's how I unbricked my phone.
Bricked Motorola XT910 indonesia version
Good day everyone..
I having a trouble about my motorola xt910 i'd rooted the devices using EPRJ easy root multi os, and i installed CWM via razzrtouchblack i followed the step by step process, then i enter the CWM mode with razzrtouchblack make a backup of my current rom. i intend to install cm 10.1 rom and follow the installation process instruction, and ended in black screen after M logo, i tried to enter cwm recovery mode by pressing power and vol - button but cant enter the recovery mode, im trying to enter fastboot mode hold power + Vol up/down for 10 sec but cant enter it neither. i browse many instruction but they all included fastboot rds and adb method which require a fastboot mode is on. this is my first time experience cant fix a boot stuck problem. i really need help from anyone who had fix a same problem like me.
thank you, Before and after.
Problem Solved
Kanisius said:
Good day everyone..
I having a trouble about my motorola xt910 i'd rooted the devices using EPRJ easy root multi os, and i installed CWM via razzrtouchblack i followed the step by step process, then i enter the CWM mode with razzrtouchblack make a backup of my current rom. i intend to install cm 10.1 rom and follow the installation process instruction, and ended in black screen after M logo, i tried to enter cwm recovery mode by pressing power and vol - button but cant enter the recovery mode, im trying to enter fastboot mode hold power + Vol up/down for 10 sec but cant enter it neither. i browse many instruction but they all included fastboot rds and adb method which require a fastboot mode is on. this is my first time experience cant fix a boot stuck problem. i really need help from anyone who had fix a same problem like me.
thank you, Before and after.
Click to expand...
Click to collapse
After an hours of observation and search all other probability via google and xda, i solved the problem... the boot loop is caused by unfinished installing cm 10.1 in my main system, and the clockworkmod recovery useless at all to help since it cant be booted to cwm recovery by any methods if the devices were boot loop while the battery are in minimal power so the Fastboot mode is unreachable to prevent me doing a uncompleted flashing roms via rsd lite. so i let the phone in boot loop show the M logo untill the battery drains out, iwhen it switched off cause of no more battery power i plugin the charger into the phone and let it charging for 10 hours +/- then the fastboot can be entered so i can flash the device with a stock rom. even there is no one who answer my question im grateful with xda and all the senior and developer thread who helped me to resurrect my device.
Viva XDA
Mazen
You are the KING I buy the beer from now on!!
Dear Friends,
a customer brought to me a bricked razr maxx xt910 which he has been rooted and bricked . i have tried many time to flash it with RSD but it failed to be flashed. i tried eveything but with no success. finally thanx to doub01 who had the problem in this thread http://forum.xda-developers.com/showthread.php?t=1796712 and fixed his mobile.i tried his way and bingo, it works. i'll explain the way he used to help others fixing their xt910.
1. go here http://sbf.droid-developers.org/umts_spyder/list.php and download 01.6.5.1-73 for your country.
2. download also 01.6.7.2-180 for your country.
3. extract both of them.
4. copy webtop_signed from 01.6.5.1-73 and all the files from 01.6.7.2-180 and paste them in c:\fastboot ( if you dont have it google for moto fastboot )
5. start cmd and write these commands (but you have to wait each command to finish then write the next one.)
cd c:\fastboot
moto-fastboot flash webtop webtop_signed
moto-fastboot flash cdt.bin cdt.bin_signed
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash ebr ebr_signed
moto-fastboot flash mbr mbr_signed
moto-fastboot flash devtree devtree_signed
moto-fastboot flash system system_signed
moto-fastboot flash boot boot_signed
moto-fastboot flash recovery recovery_signed
moto-fastboot flash cdrom cdrom_signed
moto-fastboot flash radio radio.img
fastboot reboot
thats it. Good Luck and wish that will help you as it helped me.
P.s for those who has a battery problem while flashing, use a factory cable ( connect pin 1 to pin 4 )
Best Regards
Mazen[/QUOTE]
Can't find the image from the link you have specified
Hi,
I also have similar problem(got the device bricked and battery dead due to wrong rooting steps), I even got the factory cable created and I can see AP fastboot OK to program.
the link (http://forum.xda-developers.com/showthread.php?t=1796712 ) you have given is showing 404 error
Can you please guide me towards right image
my phone is being purchased in india(I guess its Asian version)
Please let me know, If any other information is required.
Thank you very much in advance
mazen_al_ahmar said:
Xt910 RSD faild to flash, ap fastboot ( flash failure) or stuck on logo solution.
Dear Friends,
a customer brought to me a bricked razr maxx xt910 which he has been rooted and bricked . i have tried many time to flash it with RSD but it failed to be flashed. i tried eveything but with no success. finally thanx to doub01 who had the problem in this thread http://forum.xda-developers.com/showthread.php?t=1796712 and fixed his mobile.i tried his way and bingo, it works. i'll explain the way he used to help others fixing their xt910.
1. go here http://sbf.droid-developers.org/umts_spyder/list.php and download 01.6.5.1-73 for your country.
2. download also 01.6.7.2-180 for your country.
3. extract both of them.
4. copy webtop_signed from 01.6.5.1-73 and all the files from 01.6.7.2-180 and paste them in c:\fastboot ( if you dont have it google for moto fastboot )
5. start cmd and write these commands (but you have to wait each command to finish then write the next one.)
cd c:\fastboot
moto-fastboot flash webtop webtop_signed
moto-fastboot flash cdt.bin cdt.bin_signed
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash ebr ebr_signed
moto-fastboot flash mbr mbr_signed
moto-fastboot flash devtree devtree_signed
moto-fastboot flash system system_signed
moto-fastboot flash boot boot_signed
moto-fastboot flash recovery recovery_signed
moto-fastboot flash cdrom cdrom_signed
moto-fastboot flash radio radio.img
fastboot reboot
thats it. Good Luck and wish that will help you as it helped me.
P.s for those who has a battery problem while flashing, use a factory cable ( connect pin 1 to pin 4 )
Best Regards
Mazen
Click to expand...
Click to collapse
The links are dead, can someone upload the files, 01.6.5.1-73 and 01.6.7.2-180?
tttony said:
The links are dead, can someone upload the files, 01.6.5.1-73 and 01.6.7.2-180?
Click to expand...
Click to collapse
I have just 6.7.2-180
https://mega.co.nz/#!8E02RZwI!Md8-HLx3ha8ZBVRjoVcy_iCdCr8teBceTG09S_To31E
Sent from my Razr XT910
tttony said:
The links are dead, can someone upload the files, 01.6.5.1-73 and 01.6.7.2-180?
Click to expand...
Click to collapse
Did you look here http://motofirmware.center/files/category/10-spyder-umts/
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
or http://web.archive.org/web/20130817173904/http://sbf.droid-developers.org/umts_spyder/list.php
Thanks for the links
The links from archive.org works, but while downloading the file, the download fails, I tried like four times and always shows an error, that can't download the file
Then I downloaded this 6.5.1-167_SLC-M37_SIGNLATAM_USASPYDMVSGEB1B2B5B8B8LA030.0R_USASPYMOVVZ0LA_P009_c672bbd997_HWp2b_CFC_fastboot.xml firmware from motofirmware (the phone it's from Movistar Venezuela)
But like many others firmwares that I tried, RSD shows an error: cdt.bin_signed failed!
Now I'm trying to delete the cid like Lincoln357 did, but this phone it's locked, cant unlock the bootloader so cant delete cid
Code:
>mfastboot oem get_unlock_data
...
FAILED (remote: unsupported command)
finished. total time: 0.007s
Code:
> mfastboot erase cid
erasing 'cid'...
Command restricted
FAILED (remote: )
finished. total time: 0.011s
At the end of this story.. this phone it's dead, cant unbrick...
Several more Flashing options posted in
http://forum.xda-developers.com/showthread.php?t=3023837
[INDEX] Motorola Droid Razr Development (2015)
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
M fastboot
House of moto....
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
I made a bootlogo with Moto Boot Logo Maker (http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667).
But when I tried to install the bootlogo via fastboot, I did the mistake of try to flash 'boot' instead of 'logo'.
I tried to flash bootlogo in 'boot' partition 3 times, and now I don't know what to do.
Please help, what to do now?
I don't know if I can turn off my phone or try to restart, I don't know if it'll start again or if it'll hard brick because I tried to flash 'boot' partition.
What can I do? Will I need to download original firmware and flash boot with its correct image?
Computer Logs
Code:
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.047s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.062s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot logo.bin
target reported max download size of 299892736
sending 'boot' (421 KB)...
OKAY [0.078s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
Phone Logs
Code:
Fastboot Reason: Reboot mode set to fastboot
USB connected
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000696e8
cmd: flash:boot
Mismatched partition size (boot)
Phone Info
Code:
Model: XT1025 Dual Sim w/ TV - Brazillian Retail
Updated to first 5.1 Official OTA on July 23rd
Then installed Resurrection Remix
So is your phone booting now?
It wouldn't have done any harm imo.
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
neo.ank said:
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
Click to expand...
Click to collapse
I thought boot partition was important as motoboot's bootloader partition or gpt, forgot 'boot' is kernel.
fastboot formatted my boot partition, phone was stuck at bootlogo.
Downloaded official XT1025 firmware and flashed only boot partition.
Went to TWRP, installed my old custom kernel and now the phone is fine.
Thanks
Glad u solved it..
Tapped from my Moto X
The custom logo's doesn't flash on the boot partition, flash on the logo partition
Example: mfastboot flash logo nameoflogo.bin
Hi guys, a friend of mine had a problem with his Moto E XT1021 and I'm trying to help him. I'm stuck on this screen and i don't know what to do:
AP Fastboot Flash Mode (S)
...
Battery OK
Devis is LOCKED. Status Code: 0
Connect USB Data Cable
...
failet to validate system image
Fastboot Reason: Fall-through from not charger-boot mode
He told me that he started to have problems after updating his phone. Whatever I do, I get:
failed to validate system image
Boot up failed
I tried to unlock the bootloader, but when I type fastboot oem get_unlock_data I get this error:
(bootloader) Could not get unlock data! OKAY [ 0.166s] finished. total time: 0.173s
...any suggestions? Thanks.
Anyone who can help me?
Here's the link of stock firmware, flash it (guide included) :
http://forum.xda-developers.com/showthread.php?t=2755857
It doesn't require unlocked bootloader.
I tried but I get this error when i type the flash boot command:
C:\...\XT1021_CONDOR_RETEU_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.398s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.463s
The smartphone shows: "hab check failed for boot"
...it is possible that I downloaded the wrong version ?
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Yes, they returned okay. When I type mfastboot flash boot boot.img, I get "failed".
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Why are you assuming that I'm using the Indian version ? The phone was purchased from Amazon in Italy and I was trying to flash the stock retail EU 5.1
I tried the 4. KitKat but i got some error about downgrading.
What you actually did, before this problem was caused?
Were you using the same rom(that you're trying flash) ??
It's not my phone, but he said that after an updating (was a normal update. I suppose it was the 5.1 update) he started receiving this problem.
Can you help me?
Okay skip the boot.img step and execute the rest of the commands.
Okay I will try
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
rafapp said:
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
Click to expand...
Click to collapse
That's not done dude.
It shouldn't have fixed your device the main part was this
mfastboot.exe flash system system.img_sparsechunk*
and that returned Failed too. Since the bootloader isn't unlocked so flashing custom recovery isn't possible too.
There's no other way I can see but device is bricked.
So is it impossibile to unbrick it?
rafapp said:
So is it impossibile to unbrick it?
Click to expand...
Click to collapse
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
-z3r0- said:
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
Click to expand...
Click to collapse
I tried and it didn't work. All the commands failed.
hello,
i follwd the procedure u said but all are unsuccssfull and even i tried by skipping the boot.img step and executed the rest of the commands.
but i found
prevalidtion failed for
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
-z3r0- said:
Okay skip the boot.img step and execute the rest of the commands.
Click to expand...
Click to collapse
Hi, did this get resolved? I have the same problem. My XT1021 (UK Tesco variant) had been switched off for some time. When I turned back on it was looping in fastboot. Could not even turn it off. I tried flashing with a number of stock ROMs using usb to PC and mfastboot commands. Many stock ROMS caused errors on various commands, the 5.1 UK Tesco variant seemed to work perfectly - no errors displayed on phone or PC. But hone now boots too fastboot and shows the failed to validate system image error. Battery is apparently OK .. is something else likely to be toasted?
Its an old phone but would be good for my son as he starts senior school until he has proved he won't lose it
Similar Problem with Moto XT1225
Hi there, I've similar problem with XT1225.
I tried to lock the oem and it is locked with status code 2. I forgot to enable OEM unlocking from the Developer options and now I have no way to boot my device it always end up loading into fastboot mode.
Any help would be appreciated.
This is made for the XT1900-02 which is the 64gb/4gb dual sim variant sold internationally
Please do not flash this on any other variant you risk bricking your device
Install instructions:
Download Moto X4 Stock Firmware from below.
Make sure you have adb/fastboot drivers on your pc
Now extract stock firmware into a folder
Now, turn off your device and boot into bootloader by pressing volume down button and power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
Downloads:
PAYTON_PPWS29.69-26-4_9_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
https://www.androidfilehost.com/?fid=11410963190603915881
PAYTON_OPWS27.57-40-3-5_XT1900-2-DS_8.0.0_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
https://www.androidfilehost.com/?fid=1322778262903985819
Credits to @lohanbarth for the install instructions
Thanks, i was waiting for this.
Is this is signed Motorola official firmware or custom firmware??
No, it is not.
viswaA5 said:
Is this is signed Motorola official firmware or custom firmware??
Click to expand...
Click to collapse
This is not an official Motorola Recovery Image, you will have a warning that this is a wrong software when you boot up with your re-lock bootloader. And also no future OTA update.
khanhlinh said:
This is not an official Motorola Recovery Image, you will have a warning that this is a wrong software when you boot up with your re-lock bootloader. And also no future OTA update.
Click to expand...
Click to collapse
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
ding17 said:
Is there any way around this?
Click to expand...
Click to collapse
No unless Motorola releases their signed images which will most likely never happen. This has been said many times throughout these forums and it's in the FAQs thread.
ding17 said:
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
Click to expand...
Click to collapse
Hello give your Moto Rom link pls
Battery faulty
ding17 said:
Is there any way around this?
I'd happily install an old version of android that was Official, just to get rid of this warning. I'm pretty sure the battery is faulty in my phone (or something else is that drains it super fast), so I'd like to return it for repair. I tried Android 7 and AOSP-roms (without google services) just in case it was Moto firmware killing the battery, but no luck. Now I'm left with the firmware warning even after I put the Moto ROM back in and get OTA security updates.
Click to expand...
Click to collapse
I am sure Moto behind this, my phone stuck at 50%, but it's show 100%, that's why it drain super fast.
Anyone know how to changes fonts on stock firmware pls help or guide me how to do that
mujju85 said:
Anyone know how to changes fonts on stock firmware pls help or guide me how to do that
Click to expand...
Click to collapse
Not without rooting your phone. If you do not plan on rooting your stock install, the only thing you really can do is change the font display size.
Magisk has several modules that will allow you to change your system default font. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
**EDIT**
Found my issue. Been a while since I've been in the rooting game... mfastboot is the actual command. Once I got mfastboot everything worked perfectly
**EDIT**
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
fastboot flash fsg fsg.mbn
Sending 'fsg__a' (5508 KB) OKAY [ 0.154s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
Finished. Total time: 0.161s
pantoner said:
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
Click to expand...
Click to collapse
I had this problem when I used the latest android SDK tools. If you use the linux-fastboot or mfastboot (Windows) Motorola utility it will just work. Alternatively, try and find an older version of the ADB/Fastboot tools.
There is nothing wrong with the downloaded ROM.
Update :
It is compatible as per the posts in other threads
.....................................
My device is XT1900-2 6GB Ram variant. Is this firmware compatible with my device?
Software channel is Retin and below are current firmware software parameters.
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-3-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.306.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M660_7036.16.01.69.02R PAYTON_APACDSDS
(bootloader) version-baseband[1]: _CUST
Any Solution for such kind of issue?
Facing the same issue with my mobile any solution for this?
pantoner said:
**EDIT**
Found my issue. Been a while since I've been in the rooting game... mfastboot is the actual command. Once I got mfastboot everything worked perfectly
**EDIT**
Most of my pushes are failing. Says invalid partition. Anyone else having this issue? Device is an XT1900-2
fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (95999 KB) OKAY [ 2.627s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 2.635s
fastboot flash fsg fsg.mbn
Sending 'fsg__a' (5508 KB) OKAY [ 0.154s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
Finished. Total time: 0.161s
Click to expand...
Click to collapse
Sir i locked the oem after all commands and now i am in a boot loop....moto logo....what to do
Can you provide Android Pie Firmware for XT1900-02? I have unlocked bootloader so there is no other way to update!
I have added the Pie firmware to the OP
PAYTON_PPWS29.69-26-4_9_subsidy-DEFAULT_regulatory-XT1900-2_CFC.xml.zip
Thanks for this. This might be a noob question, but how can i check if i have pie firmware on mine? I flashed a pie ROM the first day i got the phone but i didn't flash any firmware on it.. Everything works fine as far as i can say.... (Battery drains super fast tho)
Hello,
I have XT1900-02 (stock rom unrooted and bootloader locked) I only want to flash the modem or baseband file instead of the entire rom as i am having issues with Volte(No incoming calls) service center flashed my device but it didn't help.
Please help me with the steps or commands that i need to use to do
Unlocking Bootloader, Rooting, Etc
Hi, I have recently purchased the XT1900-2, 6GB, 64 GB model and have updated to 9.0 using the procedure in this thread. I would like to know what are the possibilities of rooting, unlocking bootloader without losing warranty?