starting from the Chinese ROM http://ui.nubia.cn/rom/detail/62
Download download necessary files https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase system
fastboot erase modem
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash dsp dspso.bin
fastboot flash parameter parameter.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img (if you failed, don't worry, try this step again and again.)
fastboot reboot
enter recovery, use a FAT32 pendrive format, add Chinese ROM, rename it (update.zip) to OTG flash.
Everything works again.
good luck.
emmegitony said:
Download download necessary files https://drive.google.com/drive/folde...Ym?usp=sharing
good luck.
Click to expand...
Click to collapse
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
nabbed said:
404. That’s an error.
The requested URL was not found on this server. That’s all we know.
Click to expand...
Click to collapse
modified link: https://drive.google.com/open?id=16in6Jnyi4s5aIIuQwapQ1KK1LjysSfYm
Related
http://motofirmware.com/files/file/949-retuglb-xt1063-444-kxb2185-23-cid9-cfcxmlzip/
Kobro said:
http://motofirmware.com/files/file/949-retuglb-xt1063-444-kxb2185-23-cid9-cfcxmlzip/
Click to expand...
Click to collapse
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69fastboot
now extract your .zip into the directory where your command window is open and start flashing
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
reboot device
doppelhelix said:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69fastboot
now extract your .zip into the directory where your command window is open and start flashing
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
reboot device
Click to expand...
Click to collapse
do i have to erase data at the end?
Kobro said:
do i have to erase data at the end?
Click to expand...
Click to collapse
Not necessarily. You can try without wiping userdata. I have my stuff, like pictures, music etc on the external sdcard and backed up my apps with Titanium Backup so I can always do a full wipe.
doppelhelix said:
Not necessarily. You can try without wiping userdata. I have my stuff, like pictures, music etc on the external sdcard and backed up my apps with Titanium Backup so I can always do a full wipe.
Click to expand...
Click to collapse
well, i tried without the wipe, and after boot i got a black screen so i did it again with wipe and it worked!
Hello guys
Today morning i was on cyanogenmod11 and after some time i decided to restore back to stock Lollipop so i restored a backup of Lollipop system image and suddenly a error poped up saying unable to mount /data /system
I thought this might me minor issue then i tried using fastboot to flash the stock lollipop images
When i started the flashing process i got some serious errors on my cmd
"Failed to erase partition"
"failed to write partition"
And for now only Fastboot Mode is working with UTAG "flashfail" error
i tried to flash recovery images and partition gpt file but no luck looks like my partitions are messed up bad
have a look at my attachments :crying:
any help would be appreciated
Hello ?anyone there?
Sent from my GT-S5830i using XDA Free mobile app
haytham.kenway said:
Hello ?anyone there?
Click to expand...
Click to collapse
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
doppelhelix said:
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
haytham.kenway said:
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
Click to expand...
Click to collapse
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
doppelhelix said:
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
Click to expand...
Click to collapse
dude i know how to flash these images,and i tried latest version of fastboot from google still problem persists
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Curious8 said:
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Click to expand...
Click to collapse
The fastboot commands you are executing are lacking the image file and have the incorrect partition target.
Code:
fastboot flash ramdisk "boot-image-filename.img"
fastboot flash recovery_ramdisk "recovery-image-filename.img"
fastboot flash system "system-image-filename.img"
fastboot flash vendor "vendor-image-filename.img"
@Curious8
If you will flash anything - it' a good idea you have FULL-Update from your Build on your PC !
Find FULL-Update with HuaweiFirmwareFinder and download.
Extract with HuaweiExtractor from Update.app (inside Update.zip) 3 img : ramdisk.img, recovery_ramdis.img, system.img
The Extractor do automatic 3 *.img.header. This 6 files copy to your ADB-Folder.
NOW you can flash any developer-rom. If this not work reset your phone to stock-rom with
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
this help for self-repair if
- bootloader unlocked
- FRP unlock
the commands you write is for Android older OREO ! With OREO we have new Partition-Names and new commands.
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.
For Linux, Mac, or Windows users with fastboot installed, those who have need of flashing an individual partition, those for whom Moto Flash Tool fails, those who'd rather use fastboot, etc...here are the fastboot commands translated from the cebu flashfile.xml. These can be used to recover a device when all else fails...usually. For cebu with unlocked bootloader only.
Lolinet firmware link: https://mirrors.lolinet.com/firmware/moto/cebu/
Boot to bootloader (hold power and volume down until bootloader screen), plug into computer, and navigate terminal to directory containing the extracted firmware files. Run the commands one at a time, in order, and watch for "Finished" before running the next:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
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 recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Now, didn't that feel good? Your phone sure liked it.
TIP: For Linux, commands can easily be made into a bash script and all run with one command.
1. Copy everything in #2, paste into a text file in the same directory as the extracted firmware, and save with a .sh extension (ie. flashfile.sh)
2.
#!/bin/bash
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
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 recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
3. Make file executable:
chmod +x flashfile.sh
4. Execute the script with:
./flashfile.sh
5. Reboot.
Please note these commands may be different from one version to another.
You should always refer to the flash_file.xml or service.xml
Getting flash commands from the .xml
Flashing Commands
Use a batch file for easier flashing
Online FlashFile Converter
sd_shadow said:
You should always refer to the flash_file.xml or service.xml
Click to expand...
Click to collapse
arkansawdave74 said:
translated from the cebu flashfile.xml.
Click to expand...
Click to collapse
I try to always include where I got it or what I made it from. Good lookin out. Thanks, Man!
Deleted
BTW @sd_shadow, my next device after the ocean was the Moto G Stylus (sofiap) and a script wouldn't work with it. I wrongly assumed scripts wouldn't work with devices that use a super partition. I hadn't even thought of trying a script on these more recent Powers with super partitions until you posted this. Sure enough, a script works, so thank you.