IMAGE ATTACHMENTS:
i cudnt attach image pls mail at:[email protected]
One day while i was using my phone i kept it away for sme time wen i took it back i found that the phone is off and when i tried to switch it on i found the phone it stucked on the warning bootloader screen(i hav unlocked the bootloader and rooted the phone 1 month ago)i found that the phone is bricked i entered the bootloader and selected recovery(i hav been using twrp recovery)wen i tried to factory reset the phone in twrp it gives an error message:
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/persist'
E:Unable to mount '/firmware'
E:Unable to mount '/fsg'
E:Unable to mount '/pda'
E:Unable to mount '/storage'
(i hav attached an image regarding the error)
so i googled and found that i can use command prompt to flash stock rom i tried all the steps carefully.
i found that my device is detected by the CMD
wen i give mfastboot.exe devices the cmd shows my device name
but no other command is successfull each and every command fails except the one to display the devices and the command to reboot the phone works(the phone responds to every command pls check the attached images)
pls help me.
The commands that i hav used in Command promt are:
mfastboot.exe devices
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.bin
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 reboot
can you provide me some more info? Send me a pic of your bootloader screen, tell me your phone model no. , firmware/rom which you were using, latest logs, tweaks you had done on your phone like Xposed modules, apps with root access that you had installed, apps2sd or link2sd or similar memory affecting tweaks. I own a moto E xt1022 and i have flashed it a lot. I wld try to help to every possible extnt. Just give me the needed info. if you are unable to attach files, pm me
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.bin
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 reboot
Click to expand...
Click to collapse
what was the output in cmd after these commands?
sziraqui said:
can you provide me some more info? Send me a pic of your bootloader screen, tell me your phone model no. , firmware/rom which you were using, latest logs, tweaks you had done on your phone like Xposed modules, apps with root access that you had installed, apps2sd or link2sd or similar memory affecting tweaks. I own a moto E xt1022 and i have flashed it a lot. I wld try to help to every possible extnt. Just give me the needed info. if you are unable to attach files, pm me
Click to expand...
Click to collapse
xda is preventing me from attaching images as im a new user can u find some way so that i can send u those images,i hav rooted the phone but was not using any app that need root access,i hav been using twrp as my recovery pls mail me at [email protected] so that i can sent images personally
sziraqui said:
what was the output in cmd after these commands?
Click to expand...
Click to collapse
MY PHONE MODEL IS XT1022
OUTPUT IN CMD
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>stock.bat
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash partition gpt.bi
n
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.563s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash motoboot motoboo
t.bin
target max-sparse-size: 256MB
error: cannot load 'motoboot.bin': No error
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.063s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 10.012s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.354s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 6.031s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash recovery recover
y.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 6.028s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.0
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.1
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash system
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>system.img_sparsechunk.2
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash modem NON-HLOS.b
in
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.491s]
writing 'modem'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition modem
FAILED (remote failure)
finished. total time: 6.510s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.015s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.021s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.109s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.125s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.011s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.019s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>mfastboot.exe reboot
rebooting...
finished. total time: 0.003s
C:\Users\ANANTHU RAJ\Desktop\New folder (2)>
dont use stock.bat file
Download the factory images (5.1 rom files) from the below link
follow these instructions to flash stock 5.1 rom files (dont flash older 4.4.x, motoboot of old version may fail to flash)
FLASH IN THE GIVEN SEQUENCE, FIRST FLASH GPT.BIN, IF OUTPUT IS 'FAILED' FLASH THE GTP.BIN THREE MORE TIMES, IF YOU GET 'SUCCESS' MESSAGE IN CMD, FLASH THE OTHER FILE, DONT HURRY, GIVE EACH COMMAND AFTER YOU GET 'SUCCESS' MSG ON CMD FOR PREVIOUS FILES
sziraqui said:
Flash stock rom via fastboot: Ensure your phone's battery is atleast 50% charged. Just charge your phone for 45 mins,ead if yor phones seems dead. You DONT need to unlock bootloader for flashing official firmwares
1. Download and install Motorola device manager
2. Download and extract adb_fastboot.zip to any folder on your pc
3. Download XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip [thanks to lost101] and extract its contents to the same folder where you have adb_fastboot files
4. Reboot your phone to 'bootloader mode'. To do this turn of your phone completely. Hold volume down button and then press and hold power button. Release power button after 4-6 seconds and then release volume down button. Your phone is now in bootloader mode.
5. Connect your phone to pc via a reliable usb cable. Look at your phone screen. It should say 'USB connected'.
6. Now go to the folder where you have extracted all the files. Holding down shift key, Right click on any point on white screen. Then click on 'open command window here' from the menu that appears. Command Prompt will open now
7. On command prompt type
Code:
fastboot devices
and check if it is detecting your device.
8. Now run the following commands in the given sequence
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.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
fastboot reboot
proceed to each command after you get success message on command. If file name of system.img_sparsechunk is different then change the command accordingly. Just ensure to flash all system.img_sparsechunk files
Your phone may take 10-20 mins to turn on the first time. Dont panic this is normal. If it takes more time then power it off by holding power button till it turns off. Power it on after it cools down.
Click to expand...
Click to collapse
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
Also, flashing will fail if your battery is low
---------- Post added at 12:08 PM ---------- Previous post was at 11:52 AM ----------
email me a pic of your bootloader screen
sziraqui said:
dont use stock.bat file
Download the factory images (5.1 rom files) from the below link
follow these instructions to flash stock 5.1 rom files (dont flash older 4.4.x, motoboot of old version may fail to flash)
FLASH IN THE GIVEN SEQUENCE, FIRST FLASH GPT.BIN, IF OUTPUT IS 'FAILED' FLASH THE GTP.BIN THREE MORE TIMES, IF YOU GET 'SUCCESS' MESSAGE IN CMD, FLASH THE OTHER FILE, DONT HURRY, GIVE EACH COMMAND AFTER YOU GET 'SUCCESS' MSG ON CMD FOR PREVIOUS FILES
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
Also, flashing will fail if your battery is low
---------- Post added at 12:08 PM ---------- Previous post was at 11:52 AM ----------
email me a pic of your bootloader screen
Click to expand...
Click to collapse
bro as u said i was using 5.1 and wen my phone got bricked i tried to go back to stock 4.4 using cmd
now wen i tried to flash 5.1 using the above files the bootloader failed
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.480s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.044s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.559s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash partition gtp.bin
target max-sparse-size: 256MB
error: cannot load 'gtp.bin': No error
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>
try this
Code:
mfastboot erase system
mfastboot erase gpt
mfastboot flash gpt gpt.bin
if you get success msg after flashing gpt, proceed with my first post
sziraqui said:
try this
Code:
mfastboot erase system
mfastboot erase gpt
mfastboot flash gpt gpt.bin
if you get success msg after flashing gtp, proceed with my first post
Click to expand...
Click to collapse
i didnt get success message
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot erase gpt
erasing 'gpt'...
(bootloader) Invalid partition name gpt
FAILED (remote failure)
finished. total time: 0.016s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>mfastboot flash gpt gpt.bin
target max-sparse-size: 256MB
sending 'gpt' (32 KB)...
OKAY [ 0.018s]
writing 'gpt'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
C:\Users\ANANTHU RAJ\Desktop\5.1\extract>
just to get rid of the 'permission denied' and 'pre flash validation' errors, try this
Code:
fastboot oem lock begin
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.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
this should hopefully bring your phone back to 'out of the box' state
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
please clean your adb_fastboot folder. delete all flash files, and then copy the files from XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip TO ENSURE you are flashing the correct files, dont show laziness towards this
sziraqui said:
just to get rid of the 'permission denied' and 'pre flash validation' errors, try this
Code:
fastboot oem lock begin
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.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot oem lock
this should hopefully bring your phone back to 'out of the box' state
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
please clean your adb_fastboot folder. delete all flash files, and then copy the files from XT1022_CONDOR_RETAILDSDS_5.1_LPC23.13-34.8_cid7_CFC.xml.zip TO ENSURE you are flashing the correct files, dont show laziness towards this
Click to expand...
Click to collapse
again fail
C:\Users\ANANTHU RAJ\Desktop\5.1\new>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot oem lock begin
...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
try flashing philz recovery .img via fastboot
place CWM_PhilZ_Touch_6.57.9.img (do not rename it) in your fastboot folder and flash it with this command
fastboot flash recovery CWM_PhilZ_Touch_6.57.9.img
then reboot your phone to recovery mode. If it reboots to philz recovery, then your emmc is alright, but if it doesnt your emmc has become either 'read only' or it is corrupted.
if its read only, it can be reset using JTAG, (give your phone to a professional for doing this)
sziraqui said:
try flashing philz recovery .img via fastboot
place CWM_PhilZ_Touch_6.57.9.img (do not rename it) in your fastboot folder and flash it with this command
fastboot flash recovery CWM_PhilZ_Touch_6.57.9.img
then reboot your phone to recovery mode. If it reboots to philz recovery, then your emmc is alright, but if it doesnt your emmc has become either 'read only' or it is corrupted.
if its read only, it can be reset using JTAG, (give your phone to a professional for doing this)
Click to expand...
Click to collapse
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash revovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'revovery' (8824 KB)...
OKAY [ 0.313s]
writing 'revovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.313s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
ananthu0000 said:
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash revovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'revovery' (8824 KB)...
OKAY [ 0.313s]
writing 'revovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.313s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
Click to expand...
Click to collapse
dude its 'recovery' not 'revovery'
sziraqui said:
bro its 'recovery' not 'revovery'
Click to expand...
Click to collapse
bro again failed
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot flash recovery CWM_PhilZ_Touch_6.5
7.9.img
target reported max download size of 299892736 bytes
sending 'recovery' (8824 KB)...
OKAY [ 0.306s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.307s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
you need to send your phone for JTAG Flashing, just approach a local mobile repairer.
it seems you are not the only person facing emmc failure, your phone's emmc and dram are by 'micron' and 'elpida' respectively. I also have xt1022 but with 'hynix' emmc and dram and my phone is still working well after several flashes.
Just by searching 'micron elpida moto e' on google you will find many other people like you, i would conclude this brands emmc is faulty, thats why many moto e users are facing emmc failure
here are few guys like you-
http://forum.gsmhosting.com/vbb/f783/moto-e-xt1022-partition-error-possible-fix-2007708/
http://forum.gsmhosting.com/vbb/f78...2-jamesjerss-1965102/index6.html#post11215151
sziraqui said:
it seems you are not the only person facing emmc failure, your phone's emmc and dram are by 'micron' and 'elpida' respectively. I also have xt1022 but with 'hynix' emmc and dram and my phone is still working well after several flashes.
Just by searching 'micron elpida moto e' on google you will find many other people like you, i would conclude this brands emmc is faulty, thats why many moto e users are facing emmc failure
here are few guys like you-
http://forum.gsmhosting.com/vbb/f783/moto-e-xt1022-partition-error-possible-fix-2007708/
http://forum.gsmhosting.com/vbb/f78...2-jamesjerss-1965102/index6.html#post11215151
Click to expand...
Click to collapse
wat to do now..?? should i take it for jtag flashing.?? if so where should i take it to.?
look if ur emmc can be recovered by a reset (using jtag) then your phone would be fine otherwise its bricked forever. So i would say yes u should take it for jtag flashing, just give it to any reliable mobile repairer and tell him its not booting up, all mobile repairers generally flash using different boxes and not through fastboot. So you really dont need to mention what you have done on your phone.
Facing same problem
ananthu0000 said:
again fail
C:\Users\ANANTHU RAJ\Desktop\5.1\new>mfastboot devices
ZX1B34BRLF fastboot
C:\Users\ANANTHU RAJ\Desktop\5.1\new>fastboot oem lock begin
...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
C:\Users\ANANTHU RAJ\Desktop\5.1\new>
Click to expand...
Click to collapse
Someone please help, I'm facing the same problem
Related
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
I am also facing same problem any knows the solution?
shubhm said:
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
Click to expand...
Click to collapse
Are you trying to revert to 4.4.2 or 4.4.4?
Yeah
Sent from my MI PAD using Tapatalk
shubhm said:
Yeah
Sent from my MI PAD using Tapatalk
Click to expand...
Click to collapse
What yeah?
BTW you dont need to flash gpt.bin and motoboot.img.
nilanko said:
What yeah?
BTW you dont need to flash gpt.bin and motoboot.img.
Click to expand...
Click to collapse
People these days do not follow the quote "Look before you Leap"
Don't you feel the same @nilanko?
Rohitagni said:
People these days do not follow the quote "Look before you Leap"
Don't you feel the same @nilanko?
Click to expand...
Click to collapse
LOL yeah, I pheel the same
I tried flashing stock firmware without flashing these files.
But i was unable to flash it.
Since my phone was stuck at bootlogo.
So in the end i decided to flash whole firmware again along with these files.
Sent from my MI PAD using Tapatalk
I have the same problume Do you find any solution. Emmc corrupt may be
I have the same issue my Moto E 1st Gen stuck in AP fast boot mode and give same error like Failed to program partition table while flushing ROM. While i google I got to know that my EMMC is corrupt and there is no solution of this.
Moto Auto Flasher / Root Script By Jamesjerss
________________________________________________________________________________
Connect in Bootloader Mode (fastboot Mode)
FLASHING PARTITIONS...
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.088s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.622s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\motoboot.img': No error
FLASHING BOOTLOADER..
target max-sparse-size: 256MB
error: cannot load 'Firmware\bootloader.img': No error
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (247 KB)...
OKAY [ 0.094s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.114s
FLASHING BOOT...
target max-sparse-size: 256MB
error: cannot load 'Firmware\boot.img': No error
FLASHING RECOVERY...
target max-sparse-size: 256MB
error: cannot load 'Firmware\recovery.img': No error
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS...
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img': No error
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img_sparsechunk.0': No error
target max-sparse-size: 256MB
error: cannot load 'Firmware\system.img_sparsechunk.1': No error
thanks
hey manoj am facing out the sameissue i can get to bootloader nothing will flash what you have done to your device
It worked for me
shubhm said:
Hello everyone!!
Whenever i try to install stock firmware on my xt-1022, i get following error in cmd-
C:\Users\stock>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.484s
Click to expand...
Click to collapse
Start with the below commands then try from the first commands you are currently using:
Try with
mfastboot erase system
mfastboot erase gpt
Then start from
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.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Above commands has been worked for me.
vivektiwari said:
Start with the below commands then try from the first commands you are currently using:
Try with
mfastboot erase system
mfastboot erase gpt
Then start from
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.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Above commands has been worked for me.
Click to expand...
Click to collapse
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Daniel Nascimento said:
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Click to expand...
Click to collapse
Can you go to twrp??
Sent from my AO5510 using Tapatalk
Daniel Nascimento said:
Same issue - Im getting PERMISSION DENIED error to all of those commands.
oem_locked once rebooted - I cannot enter in system for there´s none bootable to unlock it in developer menu.
ADB menu for booting img files doesnt work either.
Any tips?
Click to expand...
Click to collapse
Try to install the LAST official firmware. It does where you downgrade gpt.bin
HeaDekBatHblu said:
Try to install the LAST official firmware. It does where you downgrade gpt.bin
Click to expand...
Click to collapse
You can flash gpt.bin via adb command only(not fastboot)
dd if=/sdcard/gpt.bin of=/dev/block/mmcblk0 bs=512 count=34
Sent from my AO5510 using Tapatalk
Rajendran Rasa said:
You can flash gpt.bin via adb command only(not fastboot)
dd if=/sdcard/gpt.bin of=/dev/block/mmcblk0 bs=512 count=34
Click to expand...
Click to collapse
No. mfastboot flash partition gpt.bin
HeaDekBatHblu said:
No. mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
If fastboot method failed then try ADB method
Rajendran Rasa said:
If fastboot method failed then try ADB method
Click to expand...
Click to collapse
Fastboot method failed only in case, if you flash gpt.bin from previous version frimvare. Eg frimvare 5.1.1 and you flash gpt from 4.4.4 or 5.1 previous build
Hey all, yesterday I only flashed 4.4.4 Kitkat in my phone (previously running custom 5.1.1).
(PS also received 3 5.0.2 updates as I was on soak test)
Anyways, the problem I am facing is that:
MY logo.bin is getting flashed, but still showing "Warning bootloader unlocked"
WHY?
I must mention here that I didnot flash gpt.bin and motoboot.img..... Do these files have anything to do with it?
Please help.
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
[/B]
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
UjRock said:
[/B]
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
Click to expand...
Click to collapse
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response Faiz, please find the screenshot of the errors when I try to flash from SD card and the mfastboot cmd.
These are the commands in the install ROM .bat file;
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
pause
mfastboot.exe reboot
This is what i get in mfastboot cm whe i run the istall ROM .bat file;
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.491s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash motoboot motobo
ot.img
target max-sparse-size: 256MB
error: cannot load 'motoboot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.077s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
error: cannot load 'boot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash recovery recove
ry.img
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
error: cannot load 'NON-HLOS.bin': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.039s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.028s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.094s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.135s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>pause
Press any key to continue . . .
Screenshot of SD card flash;
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Faiz Syed said:
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I tried, but it failed nevertheless.
This is what it returned:
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot devices
ZX1B33CH8Z fastboot
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>Fastboot erase system -w
'Fastboot' is not recognized as an internal or external command,
operable program or batch file.
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mFastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.930s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>
The problem is I do not have a proper service centre here and as per customer experiences, they have been asked to replace the motherboard. Now that is as goo as buying a new handset. Please Faiz, let me know if this is solvable or I have to simply shut down the handset and buy a new one?
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thank you very much Faiz, you were helpful in providing quick answers. I very much appreciate your time and effort. I'll buy a new phone as that seems to be a more doable option here.
You have a good day ahead!
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I'll try relocking.
Stuck in "Your device has been unlocked and can't be trusted. […] ID: bad key"
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
hackepeterbroetchen said:
I wanted to root the device but I now I have a device that doesn't boot anymore.
What I've done so far wasn't this much:
unlocked bootloader (fastboot oem get_unlock_data and fastboot oem unlock)
flashed TWRP (fastboot flash recovery twrp-3.0.2-0-griffin.img)
I bootet into the system, downloaded Magisk because I was going to root the device. I bootet into Recovery / TWRP and saw that I wasn't able to find the download folder where I downloaded Magisk. I rebootet and since then I can't boot into the system again.
Fastboot and recovery are possible tough. When I'm trying to boot regulary the device is stuck in:
Code:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
It looks pretty much like this except the ID ('N/A' in the image but 'bad key' on my mobile).
But it never boots. Before TWRP the screen appears as well but at least it is booting into TWRP.
Clearing cache didn't help neither.
Any idea what could help?
PS: I changed the clock in TWRP to 24h format but I guess this should brake anything — right?
PPS: I also tried to flash some official image (XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA) I found here somewhere but it failed with an error message that it won't downgrade security and therefore not flash. Perhaps because I upgraded to Android 7 when I got the mobile?
PPPS: I found a thread on another board with the same problem but no solution
Click to expand...
Click to collapse
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
hackepeterbroetchen said:
But I didn't flash another rom yet at all. I just flashed TWRP recovery image so far. Are you sure that you had the same issue?
Click to expand...
Click to collapse
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
doree said:
Had the same issue and figured it out:
https://forum.xda-developers.com/showpost.php?p=72005245&postcount=185
Click to expand...
Click to collapse
doree said:
I wouldn't reply if I wasn't.
You should have rebooted the device after unlocking the device, because it gets wiped after the process. Since you flashed TWRP right after unlocking it, you left the device wiped, therefore there's no system to gain access to. That's the reason you're stuck.
Click to expand...
Click to collapse
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
nighteeeeeY said:
Hm Im stuck at the same screen. My question is just, how can I flash the Rom if the phones not booting and I dont get the Zip on the phone? Recovery and Bootloader works, but no system start. And unfortunately your link only shows 404: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Thanks for you help!
(Found this link tho: https://mirrors.lolinet.com/firmware/moto/addison/official/RETBR/)
Click to expand...
Click to collapse
It shows 404 because the Site ran out of Traffic. The Info is on the frontpage. Do NOT flash the stuff you posted, because it's for a different model.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
Yep, you can't flash the Image, because you already updated your Bootloader to 7.0 Nougat. Therefore a flash attempt of the Image you mentioned will fail. It only works with a 6.0 Bootloader, since it's an 6.0 Stock Image.
nighteeeeeY said:
And if I want to sideload it says Invaild zip file Format in recovery and
Code:
C:\adb>adb sideload xt1635.zip
loading: 'xt1635.zip'
error: device '(null)' not found
C:\adb>adb sideload xt1635.zip
Total xfer: 0.00x
in cmd. :S
Click to expand...
Click to collapse
You need to Install ADB, boot into the Bootloader, unpack the Image I mentioned and execute the fastboot command I mentioned in the othet Post.
// Wait a sec. I will repack the stock image and will add the needed Stuff for you all.
hackepeterbroetchen said:
Ah, I think I understand. So now I should flash the stock image again and redo the things (but with rebooting between the steps) - is that correct?
In that case I just need a flashable image. As I wrote in the PS of the first post I tried to flash the original stock rom but I didn't work.
And I can't find an image for (the PHP script complaints about wrong parameters):
• Model: XT1650
• Software-Version: Blur_Version.25.221.12.griffin.re
• Carrier: reteu
Click to expand...
Click to collapse
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US". However, you have to submit the version that currently runs on your phone - and the server will give you the next update! For the version you provided, there is no update.
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
The nougat bootloader prevents downgrading itself and will cause that fastboot line to fail. Leave it in anyway. If the script breaks or anything, remove the line from the script and retry.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
directly boot into (stock) recovery, do not try to boot the system
press and hold down power, then press volume-up, release volume-up, then power.
select 'Apply update from ADB'
sideload nougat update from PC console: "fastboot sideload Blur_Version.25.11.14.griffin.retail.en.US.zip"
[*] Wipe data/factory reset, Wipe cache partition, Power off
[*] reboot
Please report back how it all worked out for you...
[a] XT1650-03_GRIFFIN_RETEU-EMEA_6.0.1_MPL24.246-17_cid50_subsidy-DEFAULT_regulatory-03_CFC_EMEA.xml.zip
OTA: Blur_Version.(24.21.46 --> 25.11.14).griffin.retail.en.US
Okay guys, do the following:
1) Download the Stock Image here and extract the archive to a folder of your choice: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://www.sendspace.com/file/1rm4cj
3) Shutdown your phone and then push the VOL- and Power-Button at the same time. You should now enter the Bootloader.
4) Connect your phone to the computer (USB)
5) Open up the command prompt and go the folder where you extracted the Stock Image and Fastboot files to
6) Type _FLASH.bat and ignore all error messages you will possibly see
7) Wait till the phone boots up with the Motorola Splashscreen
That's how I revived my device.
doree said:
2) Download the Fastboot and Batch-File archive from here and extract it into the Stock Image folder: https://mega.nz/fm/hqplTQJS
Click to expand...
Click to collapse
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
nighteeeeeY said:
It says "No Data". Do I do something wrong? Just created an account.
I have created this batch from your previous post on the other thread:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is this correct? Or the one @benzinerwin just posted?
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
REM fastboot erase carrier
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Use this link instead: https://www.sendspace.com/file/1rm4cj
My method is a different approach than benzinerwin's. Use the method you feel comfortable with.
Phew! Thanks. Worked out perfectly.
benzinerwin said:
You didn't account for the line break... It should read something like "Blur_Version.25.221.12.griffin.retail.en.US".
Click to expand...
Click to collapse
I really didn't see that
benzinerwin said:
You may want to try this:
backup everything you can via TWRP...
boot into bootloader (fastboot)
restore 6.0.1 image [a] via fastboot, see batch file below (the nougat bootloader doesn't let you boot it, but fastboot hopefully doesn't prevent flashing it..)
Click to expand...
Click to collapse
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
doree said:
Okay guys, do the following:
3) Shutdown your phone and then push the VOL+ and Power-Button at the same time. You should now enter the Bootloader.
Click to expand...
Click to collapse
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Click to expand...
Click to collapse
When rolling back the bootloader is not allowed, then also writing an older GPT will be prevented. Sorry, I missed that.
However, writing a retail image for a different country seems to work - the phone keepts its 'reteu' setting (I just tried it for a different reason).
That makes things a lot easier: just flash the RETxx nougat image as @doree discribed and you should be fine!
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Maybe that worked in the old days With current bootloader versions only VOL- & power works. But that only gets you into the fastboot mode, from which you can launch recovery...
hackepeterbroetchen said:
I really didn't see that
I'm getting errors with it (@benzinerwin method)
Code:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.142s
target reported max download size of 536870912 bytes
sending 'bootloader' (7076 KB)...
OKAY [ 0.030s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image hyp failed validation
(bootloader) Preflash validation failed
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.202s
VOL+ or VOL-? Somehow I entered a boot loop with VOL+…
Click to expand...
Click to collapse
Sorry, I meant VOL-. Typed it in a hurry!
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
hackepeterbroetchen said:
So I tried XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC now and it fails on different files:
Code:
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.048s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.061s
target reported max download size of 536870912 bytes
sending 'modem' (73570 KB)...
OKAY [ 0.269s]
writing 'modem'...
OKAY [ 1.035s]
finished. total time: 1.304s
target reported max download size of 536870912 bytes
sending 'fsg' (1976 KB)...
OKAY [ 0.051s]
writing 'fsg'...
OKAY [ 0.369s]
finished. total time: 0.420s
erasing 'modemst1'...
OKAY [ 0.193s]
finished. total time: 0.193s
erasing 'modemst2'...
OKAY [ 0.188s]
finished. total time: 0.188s
error: cannot load 'BTFM.bin'
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.075s]
writing 'dsp'...
OKAY [ 0.467s]
finished. total time: 0.542s
target reported max download size of 536870912 bytes
sending 'logo' (2533 KB)...
OKAY [ 0.054s]
writing 'logo'...
OKAY [ 0.377s]
finished. total time: 0.432s
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.094s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.467s]
finished. total time: 0.561s
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.083s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.468s]
finished. total time: 0.552s
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 2.764s]
finished. total time: 3.730s
target reported max download size of 536870912 bytes
sending 'system' (261378 KB)...
OKAY [ 1.035s]
writing 'system'...
OKAY [ 1.873s]
finished. total time: 2.908s
target reported max download size of 536870912 bytes
sending 'system' (251415 KB)...
OKAY [ 0.986s]
writing 'system'...
OKAY [ 1.867s]
finished. total time: 2.853s
target reported max download size of 536870912 bytes
sending 'system' (255815 KB)...
OKAY [ 0.959s]
writing 'system'...
OKAY [ 1.936s]
finished. total time: 2.895s
target reported max download size of 536870912 bytes
sending 'system' (255582 KB)...
OKAY [ 0.935s]
writing 'system'...
OKAY [ 1.938s]
finished. total time: 2.873s
target reported max download size of 536870912 bytes
sending 'system' (257857 KB)...
OKAY [ 0.966s]
writing 'system'...
OKAY [ 1.775s]
finished. total time: 2.741s
target reported max download size of 536870912 bytes
sending 'system' (260164 KB)...
OKAY [ 1.016s]
writing 'system'...
OKAY [ 1.750s]
finished. total time: 2.766s
target reported max download size of 536870912 bytes
sending 'system' (253309 KB)...
OKAY [ 0.992s]
writing 'system'...
OKAY [ 1.919s]
finished. total time: 2.911s
target reported max download size of 536870912 bytes
sending 'system' (256398 KB)...
OKAY [ 1.061s]
writing 'system'...
OKAY [ 1.805s]
finished. total time: 2.866s
target reported max download size of 536870912 bytes
sending 'system' (262140 KB)...
OKAY [ 1.066s]
writing 'system'...
OKAY [ 1.779s]
finished. total time: 2.845s
target reported max download size of 536870912 bytes
sending 'system' (147418 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 1.079s]
finished. total time: 1.706s
error: cannot load 'system.img_sparsechunk.11'
error: cannot load 'system.img_sparsechunk.12'
error: cannot load 'system.img_sparsechunk.13'
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 0.454s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.477s
erasing 'cache'...
OKAY [ 0.379s]
finished. total time: 0.379s
erasing 'userdata'...
OKAY [ 1.957s]
finished. total time: 1.957s
erasing 'customize'...
OKAY [ 0.365s]
finished. total time: 0.365s
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
erasing 'ddr'...
OKAY [ 0.312s]
finished. total time: 0.312s
rebooting...
finished. total time: 0.903s
These were the commands I ran (these are the ones @doree linked)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot erase ddr
fastboot reboot
Is it because the image is XT1635-02 instead XT1650-03?
EDIT:
I did flash it this way now anyway (I probably shouldn't have done this, sorry) but reboot failed now and moves directly to fastboot with the following error message:
Code:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
EDIT 2:
I tried ADDISON_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC with Android 7 now with the same effect. I guess I am missing something here?
PS: I absolutely appreciate your help and it's impressive how fast you answer. Thank you very much for this.
Click to expand...
Click to collapse
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
doree said:
Where are you getting this links from? My post cleary leads to:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You are trying to flash an Image for a whole different Device (Moto Z Play).
Moto Z Play = XT-1635 Addison
Moto Z = XT-1650 Griffin
Click to expand...
Click to collapse
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess I owe you a beer. Thank you so much!
I guess it isn't possible to go back to the EU rom again for now?
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
hackepeterbroetchen said:
Oh boy! I guess this happened because I skipped coffee today
@doree the mobile is booting again. I guess owe you a beer. Thank you so much!
Click to expand...
Click to collapse
Glad I could help
I guess it isn't possible to go back to the EU rom again for now?
Click to expand...
Click to collapse
RETBR is pretty much the same as the "regular" RETEU Rom, since it uses the same Softwarechannel (Settings/About/Softwarechannel). You'll get the same Updates as everyone else in Germany/Europe.
However, now TWRP and root!
Can you recommend any root system for using it with the stock rom?
Click to expand...
Click to collapse
What do you exactly mean with "root system"?
My model is XT1710-09 of Tim Italia with single sim, but it has also been tested in a dual sim model.
This tutorial explains how to get back from LineageOS to stock firmware without losing the IMEI. You should always make a copy of the IMEI in TWPR.
How does it work:
You have to be in a modified rom.
1- You have to download this firmware with the February 2018 patch: https://androidfilehost.com/?fid=962187416754466195
2- Install adb minimal fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3- After installing adb minimal fastboot, go to the location of the ADB installation and paste all the files extracted from the downloaded firmware there.
4- Copy all the commands of this thread in the cmd window, press enter and wait.
Commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
These are the results that I have obtained
For US variant XT1710-01 https://forum.xda-developers.com/showpost.php?p=76192627&postcount=18
That way is way i used to return to stockOS on another devices
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
What I'm anxious to know is if the phone will get the OTA´s
julesism said:
I just followed the steps above on my XT1710-01 unlocked US Retail and it appears to have worked. I got the normal blue/red splash screen and I have data/IMEI. I booted into bootloader and oem_locked + software status: official is there Thanks brother!
Click to expand...
Click to collapse
I was going to try this on my XT1710-01 (Canada retail) on the weekend. Thanks for confirming!
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Here's hoping this fixes my NFC issue
TravellingGuy said:
While this get me back to the stock Moto ROM, it did not lock my bootloader.
Got the dreaded "Image signed with key bad key" message during various times during using the fastboot commands and my bootloader remains unlocked.
XT1710-01 (Canada Retail)
Click to expand...
Click to collapse
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
julesism said:
I think you should try it again I went thru the process posted in another thread by rajatgupta1998 and ended up exactly where you are now. I manually flashed a modified boot.img via adb to get the blue/red splash screen back although some text was still visible including bad key message.
When this topic was created, I decided to give it one more try. I had so may files unzipped from previous zips/flashes etc., I decided to make a clean adb folder with nothing but this zip/files extracted in it. Low and behold, it worked for me. I believe once, maybe twice the process stopped and I had to manually copy/paste the next command. Maybe something was missed.
Click to expand...
Click to collapse
I actually did try it twice that evening and the same thing happened both times. That was also from a fresh folder.
Kacike27 said:
This happened to me because I did not install the latest firmware. It is because the bootloader is more recent than the firmware you are trying to install. When putting the firmware of February 2018 I have been able to close the bootloader three times, after returning several times to lineageOS.
Click to expand...
Click to collapse
So, I was on LineageOS when I followed your process. Your process includes steps to flash the bootloader and the firmware, which *should* mean the bootloader is the same version as the corresponding firmware (i.e. I didn't skip in any steps in the process that may have allowed a more recent bootloader to remain on my device).
I see from this post (a different, older device, but could very still be relevant), (s)he says
"Make sure you have a fastboot flashable official stock image signed to work with your carrier and region before re-locking the bootloader. Currently running the official firmware is not enough."
Click to expand...
Click to collapse
I wonder if it's also dependent on carrier and/or region. I'm in Canada, maybe there is a slightly modified bootlader for us Canucks or a different bootloader depending on the carrier or purchase location.
Use mfastboot to flash the files instead of fastboot ...check google for difference
I found many ROM for our Albus here:
https://firmware.center/firmware/Motorola/Moto Z2 Play/Stock/
But can't classify them.
My albus is XT 1710-09 in VietNam, so which file is of mine ?
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
HeltonMax said:
Can you block the bootloader but it did not get Official in the part software status, was Modified got how to make official again?
Click to expand...
Click to collapse
In my case, software status shows Official with bootloader unlocked.
method in this thread doesn't help me relock bootloader. I think I flash not correct fw for my local. But I cant find anywhere
Working very well in XT710-06 thanks bro.
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
ogabriel said:
Working fine on xt-710-07 also (Brazilian unlocked).
The only bug is the NFC is gone. Anyone has a workaround for this?
Click to expand...
Click to collapse
I just experienced this after returning to stock from LineageOS, and there was no way I was going to settle for it.
I followed the instructions only omitting the lock and reboot commands.
Flashed TWRP, (twice to be sure), rebooted into recovery, then restored my EFS, Data, and logo. (I think 'Data' is optional, I just didn't want to start over), NFC now works fine again.
I think you always need to restore your EFS.
However, the first time I tried just restoring EFS, after boot/setup, and that didn't work. so I think you have to do it prior to boot.
i imagine you could follow instructions completely, immediately booting into bootloader then use TWRP "Boot" instead of "flash", if your end game is to relock bootloader.
I successfully locked my US variant using following method
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
Here is the sequence I followed:
Phase-1 (Factory Flashing)
======
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash dsp adspso.bin
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash oem oem.img
mfastboot erase cache
mfastboot erase userdata
mfastboot erase carrier
mfastboot erase DDR
mfastboot reboot
<<Please note mfastboot erase modemst1 and mfastboot erase modemst2 commands are not being used in the above sequence>>
After reboot I wanted my phone to fully bootup upto "Welcome" screen to ensure I've LTE connectivity with my cellular provider and my IMEI is intact
Once verified, I rebooted the phone into the bootloader,
-While your phone is completely switched off, Hold <Power + Vol Down> button for few seconds to boot phone into the bootloader
Phase-2 (OEM Bootloader Locking)
======
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.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 boot boot.img
mfastboot oem lock
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
sevenstar75 said:
Hello,
I can confirm that using following sequence I was able to successfully lock my US variant without loosing IMEI (EFS Partition)
Here is the Stock file I used:
Retail US Stock (ALBUS_C) (ALBUS_NA_CUST) XT1710-01
https://androidfilehost.com/?fid=890129502657596522
Those on Retail channel can perhaps use following stock file
Retail Stock (ALBUS)
https://androidfilehost.com/?fid=890129502657596046
I used mfastbootv2 for my bootloader locking (Google it, easy to find)
<...snip...>
Following is the final message I got
mfastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.148s]
finished. total time: 0.152s
My phone automatically rebooted once the above sequence was completed
Give it a try at your risk - Best of Luck!!
Click to expand...
Click to collapse
I really do appreciate all you guys out there posting your steps to get back to stock and lock the bootloader.
I've literally tried every possible combination of fastboot, mfastboot, mfastbootv2, and all the different variants of ROMs posted. Haha, but it *always* fails for me.
Two things I notice, and I'm not sure if you guys see these or not.
One is that I always "get the (bootloader) Image signed with key bad key" message when I try to flash the boot.img. I'm not sure if that's something you guys get as well?
The other thing is I always see the "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer" message when I run the lock command. @sevenstar75, I notice in your final oem lock command, you don't see this. This makes me think that this is what is different for me. In my developer settings, the OEM Lock toggle is disabled, with a message to the effect of "Bootloader is already unlocked", and I can't change the toggle. This makes sense, as my bootloader IS unlocked, but why don't you see/get that message as well, I wonder?
Here is some sample output of what I'm doing and seeing:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
fastboot flash oem oem.img
target max-sparse-size: 256MB
sending 'oem' (232923 KB)...
OKAY [ 6.020s]
writing 'oem'...
OKAY [ 3.161s]
finished. total time: 9.181s
fastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262142 KB)...
OKAY [ 6.856s]
writing 'system'...
OKAY [ 4.225s]
sending sparse 'system' (259055 KB)...
OKAY [ 6.732s]
writing 'system'...
OKAY [ 3.632s]
finished. total time: 21.444s
fastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (245604 KB)...
OKAY [ 6.441s]
writing 'system'...
OKAY [ 3.479s]
sending sparse 'system' (240099 KB)...
OKAY [ 6.273s]
writing 'system'...
OKAY [ 3.105s]
sending sparse 'system' (30320 KB)...
OKAY [ 0.800s]
writing 'system'...
OKAY [ 0.414s]
finished. total time: 20.512s
fastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (255375 KB)...
OKAY [ 6.686s]
writing 'system'...
OKAY [ 3.752s]
sending sparse 'system' (258527 KB)...
OKAY [ 6.836s]
writing 'system'...
OKAY [ 4.416s]
finished. total time: 21.690s
fastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (262140 KB)...
OKAY [ 7.145s]
writing 'system'...
OKAY [ 3.449s]
sending sparse 'system' (258973 KB)...
OKAY [ 6.839s]
writing 'system'...
OKAY [ 3.405s]
finished. total time: 20.838s
fastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (261624 KB)...
OKAY [ 6.844s]
writing 'system'...
OKAY [ 3.589s]
sending sparse 'system' (258473 KB)...
OKAY [ 7.094s]
writing 'system'...
OKAY [ 3.587s]
finished. total time: 21.113s
fastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (253898 KB)...
OKAY [ 6.661s]
writing 'system'...
OKAY [ 3.451s]
sending sparse 'system' (262134 KB)...
OKAY [ 6.944s]
writing 'system'...
OKAY [ 4.081s]
sending sparse 'system' (8244 KB)...
OKAY [ 0.231s]
writing 'system'...
OKAY [ 0.160s]
finished. total time: 21.527s
fastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (252681 KB)...
OKAY [ 6.432s]
writing 'system'...
OKAY [ 3.292s]
finished. total time: 9.725s
fastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.448s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.458s]
finished. total time: 0.906s
fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.002s
Hi,
1) What is your variant? I mean XT1710-?? Is that RetUS software channel?
2) Did you toggle Allow OEM Unlocking to "ON" before unlocking your phone?
3) While that toggle currently grayed out, is the toggle - ON or OFF?
I tried to install TWRP
fastboot flash a twrp.img
Sending 'a' (39892 KB) OKAY [ 0.929s]
Writing 'a' FAILED (remote: '(a_a) No such partition')
fastboot: error: Command failed
astboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 1.057s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 1.063s
The phone is stuck in fastboot.
I tried this:
c:\TWRP>fastboot flash boot_b twrp.img
target reported max download size of 804261888 bytes
sending 'boot_b' (39892 KB)...
OKAY [ 0.931s]
writing 'boot_b'...
OKAY [ 0.215s]
finished. total time: 1.148s
fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
I press power Volume Up but the phone boot in Fastboot
you have flashed a bad boot image. if you are on a11 stock i dont think twrp work 100% safe. los recovery is recommended and work without problems