have anyone have the stock firmware for the xt1072 me and can say how to flash it only the commands that i need to flash
Fix it
commands:
mfastboot 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 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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Firmware:
https://mega.nz/#F!JsRmRJgb!KOYbWf-p8bPlxNZ2svbN7g
I am using Moto X 2013, unlocked republic wireless.
Last night I wiped the OS with TWRP .
Now to install ROM when I connect to PC I cant mount drive.
Can someone help me the steps to copy & install appropriate ROM.
Appreciate your help.
Do you have Motorola drivers installed?
What OS do you have? If Windows "n" version you'll need to download Media Feature Pack for you Windows OS version in order for MTP to work.
Enviado desde mi Moto X mediante Tapatalk
pakve said:
I am using Moto X 2013, unlocked republic wireless.
Last night I wiped the OS with TWRP .
Now to install ROM when I connect to PC I cant mount drive.
Can someone help me the steps to copy & install appropriate ROM.
Appreciate your help.
Click to expand...
Click to collapse
So, I had this exact same problem a while back.
You would need to reset your phone to stock first. Get the requisite firmware first from here.
Next, you need to set up the Android SDK tools, mfastboot etc and do the following -
Code:
mfastboot devices
pause
mfastboot oem fb_mode_set
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot reboot-bootloader
pause
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
pause
mfastboot flash logo logo.bin
pause
mfastboot flash boot boot.img
pause
mfastboot flash recovery recovery.img
pause
mfastboot flash system system.img
pause
mfastboot flash modem NON-HLOS.bin
pause
mfastboot erase modemst1
mfastboot erase modemst2
pause
mfastboot flash fsg fsg.mbn
pause
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
pause
You would now be stock. Next, put the rom zip and gapps on the phone memory and use twrp to only do a factory reset. Next, you should be able to flash the rom zip file.
Hello everyone, firstly I want say sorry, because my english it's a ****...
My phone XT1097, stayed with "boot up failed", I already tried the many diverses formules to can resolve this problem, but always keep this errror, on the RSD the device don't is recognized, and with the ADB staying with the erro with da title of the post, that is "<bootloader> has-slot:boot: not found", I need help, I don't know what is I have to make.
Sorry again for my english, and I already say thank for everyone.
Obsv: my phone turn on in fastboot and my recovery it's normal,
img with the error:
-RSD: goo .gl/P0QynQ
-ADB: goo .gl/K2YHgK
-PHONE: goo .gl/yZW2r8
Hey, did you try to flash the files using mfastboot instead ? A bit longer but better than those tools....
You can find mfastboot here.
Just download it, extract it in a subfolder, copy your firmware files (all the files from the firmware archive), go to the extracted folder, paste them there, then I give you the following instructions (according to Motorola's official website):
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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.x
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase customize [leave that out if you have special customization from motomaker]
mfastboot erase clogo [leave that out if you have special customization from motomaker]
You also have the option to erase all the data on your device with:
mfastboot erase userdata
mfastboot erase cache
And finally:
mfastboot reboot
Everything should be okay, tell me if this worked.
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
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 dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
wedgehog said:
With unlocked bootloader, and with TWRP and magisk root installed, you currently can't install any of the motorola OTA:s.
Below have been tested on XT1965-3 while on RETEU, PPWS29.98-66 (security updates installed up until 1 january 2019), with TWRP 3.3.0 installed and rooted, to update to latest stock rom PPWS29.98-66-2 (security updates installed up until 1 april 2019), without wiping internal storage and /data (i.e. all files, apps and settings untouched).
I take no responsibility what so ever for using this guide. Below worked for me. Be prepared to lose all your files, hard brick your phone etc.
Get latest official stock firmware, I got it from https://forum.xda-developers.com/showpost.php?p=79653779&postcount=6 , unzip it
Connect your phone to your computer with usb-cable. Put your phone in flash mode (power button+volume down), open your terminal application (below tested on macOS and linux), get root
sudo -s
navigate in terminal to folder where you unzipped the full stock rom
check the below commands visavi the files from your downloaded stock rom (below works for version mentioned above - future updates may contain more or fewer for example sparse files).
fastboot getvar max-sparse-size
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 dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
Let your phone reboot and pray
After a hopefully successfull boot with everything still intact, then adb fastboot TWRP and from TWRP reinstall your root.
in flash mode once again
fastboot boot twrp-build-version-lake.img
Click to expand...
Click to collapse
with XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml at least for me dirty flash failed, rom didn't boot
did a backup of /data/ to external storage from TWRP with internal storage decrypted (had to boot TWRP from fastboot a couple of times before the decrypt password prompt were shown on boot of TWRP)
did also a backup of internal storage over MTP with TWRP to computer.
then flashed again with below commands, WHICH WILL ERASE INTERNAL STORAGE
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 dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Thereafter successfull boot, reboot to flash mode, boot TWRP again, restore internal storage over MTP from TWRP, restore of data from backup to external storage which were made above
all apps and settings back, and on latest moto firmware.
any chance of capturing the delta OTA's to make them twrp-flashable?
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
Would probably be doable as in almost all other devices in general and older motorola devices in particular have had that. I for one do not have the knowledge of how to do that (and not the time available even if I had that knowledge =) )
I can confirm that at least for me, a dirty flash like the one described in post 1 in this thread worked again with the latest OTA/firmware for RETEU - XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC, when written over the second latest (XT1965-3_LAKE_RETEU_9.0_PPW29.98-111_subsidy-DEFAULT_regulatory-DEFAULT_CFC)
I did however have trouble booting the latest twrp twrp-3.3.1-0-v5.1-lake-jlb from fastboot, phone rebooted after it was sent over adb boot instead of booting twrp it went straight back to fastboot. Tried many times with rebooting to phone home screen in between. But adb fastbooting the older twrp-3.3.0-lake worked straight away, and thereafter installing twrp-3.3.1-0-v5.1-lake-jlb with it's zip worked straight away.
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
SvenHee said:
I have tried to get the OTA file for my g7plus from a bugreport.
But it is only 100 Mb rather than the more than 1 Gb is see most roms.
Could it actually be an OTA update? Screenshot of the .zip contents attached.
Click to expand...
Click to collapse
Doesn't seem likely, date is 2009
For reference, here is the line where I found this url:
Code:
12-06 14:19:06.869 5831 14719 D OtaApp : UpdaterEngineHelper:applyPayload, applying payload with downloadUrl = https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/*lots-of-stuff*%3D offsetvalue = 9258 fileSize = 107713236
Lupask said:
any chance of capturing the delta OTA's to make them twrp-flashable?
Click to expand...
Click to collapse
It would be no problem to catch them and make them TWRP flashable. But it's strongly not recommended to do that!! Do an OTA-update only if your device is fully on stock! Otherwise the OTA-update will override incorrect blocks of your partitions and this could crash your entire system irreversible.
Edit: i just realized I put this in the wrong area, can a mod help me out
This took me hours to figure out honestly, and I have experience with this stuff. So, I want this to be as easy to find as possible for other folks.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware...iver/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. This also restored my OTA ability and I was able to get the Android 10 update without any issues.
fastboot oem lock begin
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 dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
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 oem oem.img
fastboot oem lock
Click to expand...
Click to collapse
idumych said:
Edit: i just realized I put this in the wrong area, can a mod help me out
Click to expand...
Click to collapse
[Using "Report" button] How to Report issues / Moderators assistance by TonyStark
https://forum.xda-developers.com/showthread.php?t=1718423
Sent from my ali using XDA Labs