[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Sorry for my bad english! I hope someone can help me!
Here I put the files I've already uploaded! USE AT YOUR OWN RISK!
https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw
USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER
How-to:
-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder
-Copy the TWRP Backup to your SD Card Backup's folder
Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and
"fastboot flash motoboot motoboot.img")
fastboot flash logo logo.bin <--- From Retail US Firmware
fastboot flash boot boot.img <--- From XT1064 Nextel México
fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link
-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.
-Power Off the Device and enter to Fastboot again.
fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware
fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México
fastboot erase cache
fastboot erase userdata
ejsmsupersoyelm said:
Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.
Click to expand...
Click to collapse
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
reefuge said:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.
'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up
You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.
motoboot.img is your bootloader IT IS NOT the same as boot.img
forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)
you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
Click to expand...
Click to collapse
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
ejsmsupersoyelm said:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
Click to expand...
Click to collapse
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.
So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.
ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.
Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb
again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.
but i will give you a idea how to do
using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else
rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )
then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.
this is a very simple idea, there are more steps so search for a guide on here
I just need the motoboot.img file, would provide for me?
I accidentally flashed the radio image over the modem partition, and now my Turbo won't boot. I can't find the img after a quick google. Can someone with more time to look please give me a link?
BTW I tried using a full stock image that I downloaded when I unlocked, and it doesn't seem to have included the modem image.
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
schwinn8 said:
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
Click to expand...
Click to collapse
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
radio = modem
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
Those packages do have the modem.img...
And as @ChazzMatt stated modem <=> radio
Do you have a TWRP backup where you can restore EVERYTHING?
This is not our Quark TWRP below, it's just an example to show there are several categories you probably backed up and could restore. Actually many more categories than shown here.
In our TWRP, we have:
System
Data
Cache
Modem
Logo
Boot
Recovery
You can restore the modem partition through TWRP as well as the boot partition, if you need that.
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
Well that's a bummer Pixel, I can upload a (hidden) TWRP backup of everything (no data, you can't have my data partition, lol) if that'll help you out.
iiWoodstocK said:
Those packages do have the modem.img...
And as @ChazzMatt stated modem <=> radio
Click to expand...
Click to collapse
ChazzMatt said:
Do you have a TWRP backup where you can restore EVERYTHING?
This is not our Quark TWRP below, it's just an example to show there are several categories you probably backed up and could restore. Actually many more categories than shown here.
In our TWRP, we have:
System
Data
Cache
Modem
Logo
Boot
Recovery
You can restore the modem partition through TWRP as well as the boot partition, if you need that.
Click to expand...
Click to collapse
NepoRood said:
Well that's a bummer Pixel, I can upload a (hidden) TWRP backup of everything (no data, you can't have my data partition, lol) if that'll help you out.
Click to expand...
Click to collapse
I also thought that modem == radio until I tried the fastboot command
Code:
fastboot flash modem radio.img
As it turns out, Modem and Radio are, in fact, separate partitions on the device. And if you flash the radio.img to the modem partition, ResRemix gets stuck in the boot animation and stock su4tl-44 only boots to recovery. Additionally, I can't mount /data or /cache in TWRP anymore... I even tried re-flashing gpt.bin.
If anyone could somehow pull all the contents of their modem partition and package it in something flashable via fastboot, that would be most helpful.
immadeofpixels27 said:
I also thought that modem == radio until I tried the fastboot command
Code:
fastboot flash modem radio.img
As it turns out, Modem and Radio are, in fact, separate partitions on the device. And if you flash the radio.img to the modem partition, ResRemix gets stuck in the boot animation and stock su4tl-44 only boots to recovery. Additionally, I can't mount /data or /cache in TWRP anymore... I even tried re-flashing gpt.bin.
Click to expand...
Click to collapse
The command is
fastboot flash radio radio.img
http://forums.androidcentral.com/sp...astboot-flash-radio-modem-using-fastboot.html
There is a separate modem partition you can flash -- but not an ".img" file for the "flash modem" command. According to all the recovery commands I can find, it's a .bin file you should be flashing for the fastboot flash modem ____.bin.
as in
mfastboot flash modem NON-HLOS.bin
How to Manually Flash Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
[GUIDE] Moto G - Restore stock firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Moto X - Return to Stock
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
How to Fix your Bricked Moto E and give it a New Life!
http://techylab.com/1576/fix-bricked-moto-e/
All three of those Motorola-based guides for Motorola phones show
mfastboot flash modem NON-HLOS.bin
ChazzMatt said:
The command is
fastboot flash radio radio.img
http://forums.androidcentral.com/sp...astboot-flash-radio-modem-using-fastboot.html
There is a separate modem partition you can flash -- but not an ".img" file for the "flash modem" command. According to all the recovery commands I can find, it's a .bin file you should be flashing for the fastboot flash modem ____.bin.
as in
mfastboot flash modem NON-HLOS.bin
[GUIDE] Moto G - Restore stock firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Moto X - Return to Stock
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
How to Fix your Bricked Moto E and give it a New Life!
http://techylab.com/1576/fix-bricked-moto-e/
All three of those Motorola-based guides for Motorola phones show
mfastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Yes, I know that now. The problem is that I thought modem and radio were synonymous when I flashed the radio.img onto the modem partition. I already know I screwed up, I just need that file that actually belongs in the modem partition. It's not in any stock firmware .zip I can find, including BHB27's AFH account and RootJunky website
immadeofpixels27 said:
I just need that file that actually belongs in the modem partition. It's not in any stock firmware .zip I can find, including BHB27's AFH account and RootJunky website
Click to expand...
Click to collapse
Sounds like it's the "NON-HLOS.bin"
______
If you can fastboot, you've tried this?
[ROM] SU4TL-49 100% Stock
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
Obviously the full non-TWRP version...
TheSt33v said:
SU4TL-49 Stock Image for XT1254: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
Flash with TWRP.
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
Click to expand...
Click to collapse
i have a .49 modem
https://www.androidfilehost.com/?fid=24732830915362860
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
oh, found .44
https://www.androidfilehost.com/?fid=24732872338309178
quantum tao said:
i have a .49 modem
https://www.androidfilehost.com/?fid=24732830915362860
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
oh, found .44
https://www.androidfilehost.com/?fid=24732872338309178
Click to expand...
Click to collapse
Those are TWRP backups, right? If that's the case, they're for the radio partition, despite being labelled modem... I already tried restoring a modem backup in TWRP...
Just want to chime in that radio contains the modem, and also contains fsg and modem storage 1 & 2.
You can use laginimaineb's unpack_motoboot.py script, found here:
https://github.com/laginimaineb/unpack_motoboot
to extract the individual partitions of both bootloader and radio images from fastboot packages.
Fyi, the modem partition has to be unsparsed with simg2img before it will flash properly in recovery.
Also noticed that at least with lra and vzw builds, the specific radio for the corresponding build is required for everything to function properly.
Note:
mdm1m9kefs1 = modem storage 1
mdm1m9kefs2 = modem storage 2
mdm1m9kefs3 = fsg
I have made flashable zips of all vzw and lra radios for my personal use; if there is any interest, I'll post them up
Q9Nap said:
Just want to chime in that radio contains the modem, and also contains fsg and modem storage 1 & 2.
You can use laginimaineb's unpack_motoboot.py script, found here:
https://github.com/laginimaineb/unpack_motoboot
to extract the individual partitions of both bootloader and radio images from fastboot packages.
Fyi, the modem partition has to be unsparsed with simg2img before it will flash properly in recovery.
Also noticed that at least with lra and vzw builds, the specific radio for the corresponding build is required for everything to function properly.
Note:
mdm1m9kefs1 = modem storage 1
mdm1m9kefs2 = modem storage 2
mdm1m9kefs3 = fsg
I have made flashable zips of all vzw and lra radios for my personal use; if there is any interest, I'll post them up
Click to expand...
Click to collapse
How is that script used? I have Python 3.5 installed, but dragging and dropping the file to be unpacked onto the .py didn't do anything.
Also, your premade zips would be very helpful
immadeofpixels27 said:
How is that script used? I have Python 3.5 installed, but dragging and dropping the file to be unpacked onto the .py didn't do anything.
Also, your premade zips would be very helpful
Click to expand...
Click to collapse
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Q9Nap said:
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Click to expand...
Click to collapse
Okay, I installed python 2.7, but didn't add the path variables because I already have 3.5 and don't want two things trying to run the same file. How do I run the script without the path variables? It's not playing nice...
Q9Nap said:
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Click to expand...
Click to collapse
Alright, I have the unpacked modem file, but simg2img doesn't work in Command prompt or Python 2.7 shell... is it a Linux command?
EDIT: also, isn't the file I need supposed to be a .bin, not a .raw?
immadeofpixels27 said:
Alright, I have the unpacked modem file, but simg2img doesn't work in Command prompt or Python 2.7 shell... is it a Linux command?
EDIT: also, isn't the file I need supposed to be a .bin, not a .raw?
Click to expand...
Click to collapse
Simg2img is available as an exe, but the Linux one is what I usually use as the windows one doesn't always work.
I recommend downloading superr's kitchen, which has a nice collection of tools for working with image files.
As for the extension type, it is arbitrary what you name the file, as long as your updater-script matches.
Hi all, I want to clean install stock rom via fastboot. I used to do this on my oneplus one a while back. I think that I need to install img files to five partitions (boot.img, recovery.img, system.img, userdata.img and cache.img). Are there any other files that need to installed (eg bin or mbn files)?
I think I should be able to get the img files by unzipping the stock rom files. Has anyone tried to get the img files from unzipped stock rom and install via fastboot?
Any help is greatly appreciated.
Thanks
Don't know exactly, but also interested to learn about this!
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Jo_Jo_2000 said:
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Click to expand...
Click to collapse
The system.new.dat format is not unique to oneplus, but the standard for flashable android zips since version 6 (aka marshmellow). The system.new.dat, system.patch.dat and system.transfare.list are build from system.img while building a rom (aka compile rom from source). This process is NOT unidirectional; you can easily revert it. I'm on linux, so you have to google, how this is accomblished on win or darwin. For linux users:
https://github.com/xpirt/sdat2img