Hi, I am trying to root the droid maxx and I have an Idea but I need a custom either gpt.bin file from the droid maxx stock rom or a way to change my boot.img size from 7,476 to 10,240 .
So, could somebody teach me how to read/edit the gpt.bin file and resize the boot partition.
Or, teach me how to resize boot.img files.
Thank you for any help.
eeffeemorgan said:
Hi, I am trying to root the droid maxx and I have an Idea but I need a custom either gpt.bin file from the droid maxx stock rom or a way to change my boot.img size from 7,476 to 10,240 .
So, could somebody teach me how to read/edit the gpt.bin file and resize the boot partition.
Or, teach me how to resize boot.img files.
Thank you for any help.
Click to expand...
Click to collapse
the bootloader is unlocked?
Sent from my XT1254 using Tapatalk
No however I have found a way that I can flash boot.img and gpt.bin files to my phone (as long as they are the right ones for my device). When I open my boot.img files using carliv img kitchen the output file is less than it was when I put it in, and then when I flash it my phone says "invalid img size for partition boot."
eeffeemorgan said:
No however I have found a way that I can flash boot.img and gpt.bin files to my phone (as long as they are the right ones for my device). When I open my boot.img files using carliv img kitchen the output file is less than it was when I put it in, and then when I flash it my phone says "invalid img size for partition boot."
Click to expand...
Click to collapse
you cannot change partition sizes, with a locked bootloader
Sent from my XT1060 using XDA Labs
sd_shadow said:
you cannot change partition sizes, with a locked bootloader
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
I have been able to flash gpt.bin isn't that the partition?
Also what is motoboot.img and how would I edit it?
sd_shadow said:
you cannot change partition sizes, with a locked bootloader
Sent from my XT1060 using XDA Labs
Click to expand...
Click to collapse
I believe i may have found a way to flash gpt.bin without an unlocked bootloader. Also, is there a way to edit motoboot.img because I can't find one.
Thanks for the help!
eeffeemorgan said:
I believe i may have found a way to flash gpt.bin without an unlocked bootloader. Also, is there a way to edit motoboot.img because I can't find one.
Thanks for the help!
Click to expand...
Click to collapse
sure you might be able to flash a modified gpt.bin, but the device won't boot
sd_shadow said:
sure you might be able to flash a modified gpt.bin, but the device won't boot
Click to expand...
Click to collapse
Well that's okay I learn from trail and error, if all else fails I can factory reset with adb or rsd lite. Also you still haven't answered my original question how would I one change the partition or boot.img size.
Related
OK i'm going to flash with the Rogers ROM but I am unsure how to flash back to the factory Voda UK image if I dont like it.
I have rooted the device and have 2 backups on SD card of the current system. However when I download the Rogers ROM it is a zip file install but the backup is a bunch of image files. How would I install the default system back onto the device using these image files?
I just need to know how to get back before moving away
Thanks in advance
Mark
You update the rom with the ZIP-file named as update.zip.
If you want to revert back to your backup, power off the device, boot with BACK+POWER or VOLUME DOWN+POWER and type the following:
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Thanks, i'm guessing this is on my PC that I did the rooting on through cmd, is that correct?
Will those .img files need to be on the root of the SD card as well?
Cheers
Mark
Marko_1611 said:
Thanks, i'm guessing this is on my PC that I did the rooting on through cmd, is that correct?
Will those .img files need to be on the root of the SD card as well?
Cheers
Mark
Click to expand...
Click to collapse
Hello Mark
No. They are only on your SD-card in the folder Nandroid/HTxxxxxx/date and you need to copy/put them in the SDK/TOOLS on your PC.
OK thanks for the info, just flashing the Rogers ROM now, fingers crossed
Marko_1611 said:
OK i'm going to flash with the Rogers ROM but I am unsure how to flash back to the factory Voda UK image if I dont like it.
I have rooted the device and have 2 backups on SD card of the current system. However when I download the Rogers ROM it is a zip file install but the backup is a bunch of image files. How would I install the default system back onto the device using these image files?
I just need to know how to get back before moving away
Thanks in advance
Mark
Click to expand...
Click to collapse
Did you change the recovery image? You might need this too (link)
pdagenius said:
Did you change the recovery image? You might need this too (link)
Click to expand...
Click to collapse
How do you like the French rom? Compared to Rogers? It dosen´t have Exchange?
Joost39 said:
How do you like the French rom? Compared to Rogers? It dosen´t have Exchange?
Click to expand...
Click to collapse
Haven't looked at Rogers. French ROM is rooted, has inbuilt utilities such as wifi-tether, anetshare, PDF Viewer, Quickoffice, Meteo, Useful Switchers. All very easy and no problems.
Confused
pdagenius said:
Did you change the recovery image? You might need this too (link)
Click to expand...
Click to collapse
Ok are you saying that I need to reflash the origional image files using the info above and then run in this update to put the vodafone magic back to its origional state.
The update on the link re-roots the device is that correct?
Regards
Mark
Joost39 said:
How do you like the French rom? Compared to Rogers? It dosen´t have Exchange?
Click to expand...
Click to collapse
Missed your other point - it does not have Exchange. I on the other hand do not need it. Google sync works great for me.
Marko_1611 said:
Ok are you saying that I need to reflash the origional image files using the info above and then run in this update to put the vodafone magic back to its origional state.
The update on the link re-roots the device is that correct?
Regards
Mark
Click to expand...
Click to collapse
Am sorry but don't fully understand the ins and outs of Rooting and then Unrooting again. All I was offering was info on the original files that were presumably removed when you Rooted your phone.
There is also the original SPL now available - posted here
Is this right
OK
As i wont be the last to ask how to get back to a factory device, I have put all of your comments an suggestions into one file which is attached.
Hopefully this will become a guide for all future users to follow if they want to go back to the factory image on a UK Vodafone Magic.
Could you kindly read through the instructions and leave feedback for me.
Cheers
Mark
Marko_1611 said:
OK
As i wont be the last to ask how to get back to a factory device, I have put all of your comments an suggestions into one file which is attached.
Hopefully this will become a guide for all future users to follow if they want to go back to the factory image on a UK Vodafone Magic.
Could you kindly read through the instructions and leave feedback for me.
Cheers
Mark
Click to expand...
Click to collapse
I have had a quick look through your guide although not tried it out. It is good. Only a minor observation that the spelling of "origional" should be "original" all the way through the file.
Thaks for the pointer on the typo, copy and paste job, you got me on that one
Hi,
I followed your instructions and now my phone is stuck on the vodafone screen.
I get these errors in the process:
me$ ./fastboot erase system -w
ERROR: could not get pipe properties
erasing 'system'... OKAY
erasing 'userdata'... OKAY
have i bricked my phone?
any advice?!
It will boot to recovery and the fastboot screens.
Does that mean its fixable?
pdagenius said:
There is also the original SPL now available - posted here
Click to expand...
Click to collapse
Is not true..this is a modded SPL build for running OTA !!!
http://forum.xda-developers.com/showpost.php?p=3857151&postcount=10
http://forum.xda-developers.com/showpost.php?p=3923803&postcount=21
Crios said:
Is not true..this is a modded SPL build for running OTA !!!
http://forum.xda-developers.com/showpost.php?p=3857151&postcount=10
http://forum.xda-developers.com/showpost.php?p=3923803&postcount=21
Click to expand...
Click to collapse
Thank you for the correction
Joost39 said:
You update the rom with the ZIP-file named as update.zip.
If you want to revert back to your backup, power off the device, boot with BACK+POWER or VOLUME DOWN+POWER and type the following:
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Should I need to flash userdata partition?
The official rom should not include userdata, right?
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks
I put together a couple nice little Batch files for you guys. Tool is for windows only
This is what they can do for you
1. Relock a unlocked bootloader and complete wipe device back to android 4.4.2 along with fixing the Unlock logo
2. Full Restore to android version 4.4.2 including a full wipe
3. Full Restore to android version 4.4.2 NO WIPE
4. Flash Moto Logo to replace the unlock bootloader Logo
To run any of these scripts you must be in bootloader mode / Fastboot Mode
Power off Device
hold both volume up and down then power
hold all buttons for 3 seconds then release
this will put you in bootloader mode
Now run the script you want to run
check out this video of me using the scripts
Video
Link to the firmware tool can be found HERE
Link to Motorola Drivers needed are Here
Warning Use these at your own risk
Great job buddy
Sent from my XT1033 using Tapatalk
Doublepranks said:
Great job buddy
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Thanks. I thought someone could use this
XT1034??? Plz!
swirly05 said:
XT1034??? Plz!
Click to expand...
Click to collapse
Just download your firmware and replace the the firmware I have in the zip with the XT1034 the batch files should work the same.
sent from my Galaxy Note 3 running HyperDrive.
-edited- working links
just a simple question,if you locked the bootloader can you unlocked it again later? thanks
Sent from my XT1034 using XDA Premium 4 mobile app
ryuben2k said:
just a simple question,if you locked the bootloader can you unlocked it again later? thanks
Sent from my XT1034 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you can relock and unlock the bootloader with the same code you unlock it with the first time.
when you got the device the bootloader is status code 0 locked once unlocked it is status code 3 and relocked is status code 2.
now you can bounce between status code 2 and 3 locked and unlocked with the bootloader unlock code.
So if I wanted to completely restore my phone back to when I first got it out of the box, does this tool do that?
Would the "Restore US_retail_XT1032_KXB20.9-1.8-1.4_CFC" .bat work like this?
Because for some reason, all of my ringtones that came with the phone just disappeared and I wanted to get them back.
jman1234 said:
So if I wanted to completely restore my phone back to when I first got it out of the box, does this tool do that?
Would the "Restore US_retail_XT1032_KXB20.9-1.8-1.4_CFC" .bat work like this?
Because for some reason, all of my ringtones that came with the phone just disappeared and I wanted to get them back.
Click to expand...
Click to collapse
that bat file will restore and delete everything from the phone but you will keep the unlocked bootloader if you unlocked it
Tomsgt said:
Yes you can relock and unlock the bootloader with the same code you unlock it with the first time.
when you got the device the bootloader is status code 0 locked once unlocked it is status code 3 and relocked is status code 2.
now you can bounce between status code 2 and 3 locked and unlocked with the bootloader unlock code.
Click to expand...
Click to collapse
ok. so if i locked my phone back and turn on the phone, the unlocked bootloader warning will be gone? im planning to sell my phone to my friend. thank u
Sent from my XT1034 using XDA Premium 4 mobile app
Tomsgt said:
Just download your firmware and replace the the firmware I have in the zip with the XT1034 the batch files should work the same.
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
How would I do this (replace the firmware) for XT1032 GB Retail version? I would need VERY basic instructions!! I have downloaded it to my laptop running Windows 7, it is - RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.xml.zip -
1 question please
I have the moto g 1033 version can i download my phoe's factory file and replace with the US zip file in your tool to flash my 1033 stock system???
What's the point of Unlocking the bootloader againi if your warranty is already voided
even if as a means for selling to other person he will get phone the already without warranty..
harisaduelite said:
I have the moto g 1033 version can i download my phoe's factory file and replace with the US zip file in your tool to flash my 1033 stock system???
Click to expand...
Click to collapse
yes that should work just fine
akhil17kr said:
What's the point of Unlocking the bootloader againi if your warranty is already voided
even if as a means for selling to other person he will get phone the already without warranty..
Click to expand...
Click to collapse
some people just want to go to stock 100% the person you sell the device to doesnt normal get the warranty any way
Tomsgt said:
some people just want to go to stock 100% the person you sell the device to doesnt normal get the warranty any way
Click to expand...
Click to collapse
So the people here rooting there phones doesn't love warranty or what ??
as no one is working on exploit or something that will allows us to doesn't lose our warranty with unlocking bootloader?
In the Netherlands, the retailer is responsible for warranty by law. They cannot simply forward me to the manufacturer. Additionally, consumer law dictates warranty cannot be void for manufacturing errors by a mere software mod. Therefore I don't care for those intimidating "your warranty is now void" claims.
Sent from my XT1032 using Tapatalk
I always get a fastboot.exe error when i run any of the scripts and it crashes, but it loads back up and still goes through the install but I get alot of errors the whole time. what am i doing wrong?
Problem with your script and going to stock for example with GB tesco roms is that in your script:
Code:
%fastboot% flash system system.img_sparsechunk[B][U]1[/U][/B]
%fastboot% flash system system.img_sparsechunk[B][U]2[/U][/B]
%fastboot% flash system system.img_sparsechunk[B][U]3[/U][/B]
And in packages of GB rom there are system.img_sparsechunk0, system.img_sparsechunk1, system.img_sparsechunk2.
So people be careful.
---------- Post added at 04:21 PM ---------- Previous post was at 04:00 PM ----------
jamsh said:
How would I do this (replace the firmware) for XT1032 GB Retail version? I would need VERY basic instructions!! I have downloaded it to my laptop running Windows 7, it is - RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.xml.zip -
Click to expand...
Click to collapse
All credits to Tomsgt
Download this: Here
Unzip it on your desktop.
Open the "Firmware restore lock and more 4.4.2" folder and then delete this files:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
NON-HLOS.bin
fsg.mbn
Open the "Restore US_retail_XT1032_KXB20.9-1.8-1.4_CFC.bat" with notepad and change this lines:
Code:
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
to this:
Code:
%fastboot% flash system system.img_sparsechunk0
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
and save the file.
Download proper drivers and install them Here
Open "RETAIL-GB_4.4.2_KLB20.9-1.10-1.9_cid7_CFC_1FF_v5_SVC.xml.zip" and copy this files:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img_sparsechunk0
system.img_sparsechunk1
system.img_sparsechunk2
NON-HLOS.bin
fsg.mbn
to "Firmware restore lock and more 4.4.2"
Power off Device
hold both volume up and down then power
hold all buttons for 3 seconds then release
this will put you in bootloader mode
connect your phone to the pc
Now run "Restore US_retail_XT1032_KXB20.9-1.8-1.4_CFC.bat"
I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]
Did you do it with flashfire app? @parker.stephens
dzidexx said:
Did you do it with flashfire app? @parker.stephens
Click to expand...
Click to collapse
If you're taking about flashing the files no, I use fastboot. If you're taking about how I got the files, I used dd.
There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797
acejavelin said:
There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.
parker.stephens said:
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.
Click to expand...
Click to collapse
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos
acejavelin said:
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos
Click to expand...
Click to collapse
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2
parker.stephens said:
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2
Click to expand...
Click to collapse
Awesome! My concern was that in previous devices, extraction of the radio firmware with DD was protected, it would only output all zeros in the image, seems that isn't the case anymore!
I will try to look at the system thing this weekend, I'm out of town til Sunday so i am limited at the moment. Can you put the raw system img file on drive?
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.
Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
parker.stephens said:
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.
Click to expand...
Click to collapse
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.
acejavelin said:
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.
Click to expand...
Click to collapse
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.
annoyingduck said:
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/
parker.stephens said:
I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]
Click to expand...
Click to collapse
How did you get gpt.bin and bootloader.img?
yk1999 said:
How did you get gpt.bin and bootloader.img?
Click to expand...
Click to collapse
Tapa?
Post #3.
dzidexx said:
Tapa?
Post #3.
Click to expand...
Click to collapse
But there is no pertition called gpt(gpt is the partition table itself)
And bootloader.img contain pmic aboot tz etc i can get them separately using dd but can't get them in one bootloader.img
I didn't think,
Sorry. @yk1999
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
I didn't think,
Sorry.
@yk1999
is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??
abense said:
is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??
Click to expand...
Click to collapse
No, this is marshmallow.
Did anyone already perform a system restore after processing with sparse converter by any chance?
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Xdevillived666 said:
Hey all,
I am unlocked, rooted, etc. I have latest platform tools. i am trying to reflash a modem img using fastboot on windows 10 64 but am given "FAILED (remote: 'Not allowed to flash (modem_b)')"
Can someone point me in the right direction?
Click to expand...
Click to collapse
Is there a "modem.img" that you extracted from the factory image?
Badger50 said:
Is there a "modem.img" that you extracted from the factory image?
Click to expand...
Click to collapse
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Xdevillived666 said:
Yes. I've tried opening command window as admin, too. Seems to return this error noattwr what:-/
Click to expand...
Click to collapse
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Badger50 said:
Are you trying to use a different radio/baseband from a previous month? I've actually never seen anyone wanting to flash a modem.img for whatever reason. So now I'm curious.
Click to expand...
Click to collapse
Nope. Long story short I'm trying to use qpst and pdc tool. Getting a qmi error and read on a German thread that sometimes reflashing modem will fix it. Problem is that I can't flash individual images aside from radio or bootloader with fastboot -_-
Are your platform tools up to date?
jsauder2 said:
Are your platform tools up to date?
Click to expand...
Click to collapse
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Xdevillived666 said:
Yeah. Is this normal for a pixel 3 to be so locked down? I know my pixel one wasn't
Click to expand...
Click to collapse
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
jsauder2 said:
If it's a Verizon model, you can't unlock the bootloader. If it's from Google, you should be fine. I've not tried flashing a modem. If you can flash the factory images, just use the flash all script and remove the w. That will flash everything, including the modem, but will not wipe your data.
Click to expand...
Click to collapse
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
The factory image does flash the modem. It doesn't say so in the bat or sh files, but you'll also notice that it doesn't mention the boot, system, or vendor files either (along with many other things), even though those are most certainly flashed during an update. That's because those are all inside the image zip that is referenced in the last line of the bat or sh (where you remove the -w). It flashes everything inside of that, including the modem.
If a screwed up modem is your problem, flashing the factory image will fix it. If that doesn't fix it, then the modem is not your issue.
Xdevillived666 said:
I can use the script but opening it in notepad ++ , the flash all bat doesn't show anything about modem. I've tried everything from just fastboot flash modem modem.img to
Flash modem slot a, etc. Keeps giving remote error flash modem not allowed . I really think Google just locked this phone down that much more. Ridiculous.
Click to expand...
Click to collapse
I don't know if this will work. I also don't know what the fastboot update command does under the hood. But the flash-all batch file does flash the modem image using the fastboot update command. What if you created a zip file with your modem image in it and then tried to flash it with the update command, or possibly replace the modem.img in the zip in the factory image with your image?
Sent from my [device_name] using XDA-Developers Legacy app