Database Develop

[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064

[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?

[GUIDE][HOW TO] Flashing with care & Surviving soft bricks with fastboot [CMD] [TIPS]

[GUIDE][HOW TO] Flashing with care & Surviving soft bricks with fastboot [CMD] [TIPS]
Hello guys, some of us are new to the A/B partitions. Flashing on wrong partition may end up in soft bricks. This is not a rooting guide, here I'm explaining how to handle flashing A/B partitions properly and survive soft bricks using fastboot . Always backup your data before flashing anything.
Those who still don't know about the A/B partitions, please take a look at this thread https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Prerequisites:
OnePlus 6T with unlocked or locked bootloader
A computer for running fastboot commands
You :laugh:
Rebooting
Rebooting your device via adb and fastboot
Code:
adb reboot //normal reboot
adb reboot recovery //reboot to recovery
adb reboot bootloader //reboot to fastboot (bootloader)
Code:
fastboot reboot //normal reboot
fastboot reboot bootloader //reboot to fastboot (bootloader)
Unlocking the Bootloader
Bootloader can be unlocked via fastboot
Code:
fastboot oem unlock
WARNING THIS WILL WIPE YOUR DATA
Working with A/B Partitions
There are two boot partitions on this device, named boot_a and boot_b respectively, they are not the “traditional” boot partitions. Both of these partitions contain a kernel and ramdisk like you are probably used to. The difference is that there is no recovery partition and the boot partition is new recovery partition. The A/B partitioning scheme can be quite confusing to users. There are actually two copies of many of the partitions. There is only one data (userdata) partition.
Slots
The concept of ‘slots’ comes into play to determine whether you are booting ‘slot A’ or ‘slot B’. We can determine which slot is ‘active’ or marked for booting via adb and fastboot:
Code:
adb shell getprop ro.boot.slot_suffix
Code:
fastboot getvar current-slot
Switching Slots
We can switch between slots via fastboot:
Code:
fastboot set_active other //switch to inactive slot
Code:
fastboot set_active (a or b) //switch to specified slot
Flashing/Booting
We can flash/boot (temporary flash) recovery/kernel via fastboot. To boot (what we call temporary flash) a kernel/recovery there is no need to switch/select any slot. Keep in mind that when we run the flash command instead of boot, it will wipe the specified partiton (you may lose your root & custom kernel)
Code:
fastboot boot boot.img or twrp_recovery.img
To flash permanently, first switch/select any slot you want or it will automatically flashed to the active slot. This may cause boot loop, always proceed with caution.
Code:
fastboot flash boot boot.img or twrp_recovery.img
Code:
fastboot flash recovery twrp_recovery.img
If your testing something, always use the inactive slot. Eg: if you want to test a custom rom, first back up your data then switch to the inactive slot and flash the custom rom, this will save your time (no need restore full backup only data).
Surviving Soft Bricks
Some possible simple solution we can try rather than using MSMTool or flashing the full rom.
When causing boot loops, try these:
Flash Magisk via recovery
Switch to the other slot via fastboot
Wipe data partiton via fastboot -w
When causing Bootloader crash, try these:
Turn off the phone by holding the power button (release after power off)
Hold both volume buttons
Now press power button
Phone will boot to fastboot
Now switch the other slot via fastboot
To be continued....

Just in case

This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?

Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it

patelparth120595 said:
This is my first A/B device so forgive my ignorance, I was wondering if its possible to flash two different roms on to different slots...like oxygen on one partition and lineage on other?
Also why twrp has two buttons 'slot a' and 'slot b' in reboot section?
The phone doesn't have recovery partition, so what happens on typing 'Fastboot flash recovery' command?
Click to expand...
Click to collapse
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.

geminium said:
Thanks again for this tutorials. That's really helpful in understanding of the new Android features.
What'd be your advice on instructions to get stock kernel back? I couldn't find an appropriate command on how to do it
Click to expand...
Click to collapse
Get stock boot.img file and flash using fastboot
Code:
fastboot flash boot boot.img

AnoopKumar said:
You can install any rom on both slot, there is no problem. There is only one userdata partiton. The two buttons are for switching between slots, if you press slot a button, the recovery will mark slot a as bootable or active partition. On next boot or reboot rom from slot a will boot, this same thing is applied for slot b too. There is no dedicated partition for recovery , files for recovery are stored in system_root.
Click to expand...
Click to collapse
Thanks for the reply. Cleared all my doubts.

So could we have two ROMs and switch back and forth between on one device in this case?

geminium said:
So could we have two ROMs and switch back and forth between on one device in this case?
Click to expand...
Click to collapse
Because of one userdata partition, there will be some issues. If wipe data when switching roms, no issues then.

Man i could use some help patched the file moved it to harddrive tried fastboot flash boot boot.img (the patched one) and all i get is
C:\Users\seang\OneDrive\Desktop\Moto G Stylus 2021>fastboot flash boot boot.img
error: cannot open 'boot.img' Could you please make a guide with some pics or at least a step by step cause nothing i have tried has gotten root yet. Thanks!

Thanks to the OP.

[GUIDE] How to convert to Wileyfox swift (crackling) from Android one 2gen (seed)

Code:
*
*Your warranty is now void.
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
How to convert to Wileyfox swift (crackling) from Android one 2gen (seed)
THIS ONLY WORK ON Qualcomm Snapdragon 410 (MSM8916)
Basic Requirements \/
1.Proper brain with Knowledge about ADB and flash.
2.Phone With Unlock bootloader.
3.Working Computer.
4.Reliable USB cable.
5.BACK UP YOUR DATA
(If your Phone is not Unlock bootloader) Go this from Wiki.lineageos[url]https://wiki.lineageos.org/devices/seed/install#unlocking-the-bootloader[/URL]
Get ADB from Wiki.Lineageos here [url]https://wiki.lineageos.org/adb_fastboot_guide.html#on-windows[/URL]
LET DO THIS.
Download the cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip here (no more link) [I had to remove the DL link BC of i am new user lol, due of xda rule, you can find via androidfilehost.com or search on Google.]
Then extract all files (without folder) and put directly in to platform-tools. Now open "Windows PowerShell" then type this command to run ADB and Fastboot
Code:
cd where you put the platfrom-tools
Ex. cd C:/user/download/platfrom-tools
hit enter on your keyboard to run.
Now Boot your phone to fastboot. To do this hold Volume down + Power Button now plug your phone to PC
Once the phone is in fastboot mode, verify your PC finds it by typing
Code:
fastboot devices
If you see your phone then proceed. (If not try different usb or reinstalling the ADB drivers and Fastboot Driver before you go.)
(Warning!!!! Follow carefully the command may ended up will break your phone if you don't follow and will erase all of your data. Just i warn you!!!!)
Type this all command
Code:
fastboot erase DDR
fastboot erase userdata
fastboot flash sbl1 sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash splash splash.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Wait to boot
And now setup your phone now........
Go back to fastboot then flash the TWRP
To flash TWRP go here [url]https://wiki.lineageos.org/devices/crackling/install#installing-a-custom-recovery-using-fastboot[/URL] this take you to wiki.lineageos
Now... FIND THE ROM YOU LIKE
(Note: only you install crackling rom not seed)
You're done.....
Need help? Just ask me here.
Special thanks (AKA Credits)
Lineageos and wiki.lineageos
@JominatorX
@m192
@SubwayChamp (for helping me)

Knowing Bugs........
1.Blue Screen flicker (all Phone )
2.Camera may or not working sometimes, Blue Screen occur will reboot your phone............. (Only on Foxy Kernel)
3.Battery may bug out (All of Them )
(To fix just discharge the battery/phone. To do this power off your phone and remove the battery then Holding Down the Power Buttons for Few 30sec then put it back your battery and power on your phone.)
4.GPS will be not super accuracy unlike the stock rom
(As of Ang 13 2019 lineage os developer they fix the GPS accuracy)
5.i-mobile iQ II 8150 poor RAM due of 1GB of ram
(To fix this Install Android Go enabler)
That it, i can find some more bugs but i need more testing
I have 4 phone to test (i own)
Cherry Mobile G1 (H220)
General Mobile 4G / 4G Dual (GM-113)
i-mobile iQ II (8150)

wifi and network not working after installing factory image

Hello,
I've rooted my pixel 5 and it was running without any issues. But I wanted to return back to stock. So installed the factory image from google and once booted up, I lost wifi and network completely. When I check the about phone in settings, wifi mac address shows as "unavailable" also in the imei number, I dont see my imei number, its just some default value starting with 0044991..
When I check the barcode in fastboot mode, it shows the correct imei etc.
Anyone has any suggestion on how to solve this?
Thanks in advance

matruck said:
Hello,
I've rooted my pixel 5 and it was running without any issues. But I wanted to return back to stock. So installed the factory image from google and once booted up, I lost wifi and network completely. When I check the about phone in settings, wifi mac address shows as "unavailable" also in the imei number, I dont see my imei number, its just some default value starting with 0044991..
When I check the barcode in fastboot mode, it shows the correct imei etc.
Anyone has any suggestion on how to solve this?
Thanks in advance
Click to expand...
Click to collapse
Did you use the right build for the right carrier? How did you flash it, did you sideload it via adb sideload xxx.zip? If not, try that as a next step.

Yes I had checked and its correct, I've used the RQ1A.201205.011 (the one for all carriers except AT&T and Verizon). I've also tried the OTA sideload method, it also didnt work out.
I already have a QCN backup which was taken with the method linked in the below. But the same method also no longer work now, the command diag_mdlog no longer hangs, it just continues to work in an endless loop, when I cancel, I can see the device in QPST but the port constantly drops and reconnects, so I cannot restore it (even if I could, not sure if it will fix)
How to add 5G configurations to your Pixel 5 (solved)
Hi all Similarly to the Oneplus 8 series, Pixel 5 does not support 5G in countries that it is not sold in. For Oneplus, configurations could be changed using the Qualcomm QPST file manager...
forum.xda-developers.com
I just tried to extract below partitions to have a look and seems like the fsg partition is empty which seems weird, the image file is completely filled with zeros, do you or any one has the unlocked version that can run the last command below and send me the fsg partition image?
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst1 of=/sdcard/modemst1
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst2 of=/sdcard/modemst2
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/fsg of=/sdcard/fsg

In below link, it mentions that fsg is a backup of modemst1. So what if I overwrite fsg (which is already filled with zeros as mentioned in above post) with the modemst1 image I have which already have data in it?
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
NOTE: I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources like this and many others. This information is according to best of...
forum.xda-developers.com

and one more question, I tried to erase the modemst1 and modemst2 as suggested in below link via ADB, it had no effect. So I erased them again and right after I erased have taken a backup to see if its all zeros in both partitions but no, they both has still data inside.
I'm trying to erase via fastboot but that also gives error and doesnt allow. Any idea why this might be?
Code:
fastboot erase modemst1
Erasing 'modemst1' FAILED (remote: 'Not allowed to erase (modemst1)')
fastboot: error: Command failed
How to Fix Empty IMEI, Corrupted EFS, No SIM, Unknown Baseband and WiFi/Bluetooth issues after restoring a TWRP Backup
While flashing things with TWRP is fun and games, it can sometimes also lead to serious issues on your device. If proper care is not taken or if the installed TWRP recovery on your device has bugs/…
nerdschalk.com

It sounds like there may be something wrong with the baseband; try reflashing the baseband image.
If that doesn't work, I would recommend a complete factory reflash. Use the Android Flash Tool, force flash all partitions and wipe data. You'll have to start over, but at least it should get the device working.

[Q] bootloop after insufficient space rooted

I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.

Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).