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?
Related
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.
dansou901 said:
You flashed the firmware files of the 16 GB version, meaning you also flashed the partition table of the 16 GB version. If you got no backup, I think you'll have to wait for a dump of these files from a 64 GB phone to fix it for you or to manually edit the file containing the partition table. But be very careful with that... You can easily brick your device if you are not really knowing what you are doing.
Click to expand...
Click to collapse
Do you know which file define the partition table?
liujunwei4321 said:
Do you know which file define the partition table?
Click to expand...
Click to collapse
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.
dansou901 said:
As I don't have the phone yet, no. You'll have to ask the uploader of the files about it.
Click to expand...
Click to collapse
I'll try
Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!
liujunwei4321 said:
I have a China version OPO in hand, 64G storage. But after flashing the new CM11S, the storage reduced to 16G. I suspect it's CM11S re partitioned the storage, and didn't considering there are 64G version!
Is this mean I have to wait for the even newer CM to repair it?
I downloaded the firmware here: http://forum.xda-developers.com/showthread.php?t=2765455
Click to expand...
Click to collapse
http://forums.oneplus.net/threads/af...ge-12#post-231
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.
reply
LordKuroda said:
Any updates on this? Might be getting my hands-on a China 64GB OPO soon too!
Click to expand...
Click to collapse
No update up to now.
others
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.[/QUOTE]
I did. But the problem remains. He said next update will solve the problem.
liujunwei4321 said:
Check private msg over there. DavidS sent you info on how to flash the latest build of CM11S.
Click to expand...
Click to collapse
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.
Entropy512 said:
I did. But the problem remains. He said next update will solve the problem.
Click to expand...
Click to collapse
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.[/QUOTE]
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?
WenLei said:
Check the post I made in that thread. Go into TWRP and do a FULL userdata format. (You can "fastboot boot" TWRP without flashing it if you wish, or you can flash it.)
Wipe->Advanced Wipe->Data
(the standard factory reset will just remove all files outside of /data/media without reformatting the partition.)
Based on your description of what you did to flash it, I'm fairly certain that your partition table is OK (since it doesn't look like you altered that), but you flashed a premade 16GB userdata image to a 64GB partition.
Click to expand...
Click to collapse
[/QUOTE]Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?[/QUOTE]
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.[/QUOTE]
Thanks for the info, I will be receiving my 64GB tomorrow! :good:
ailai55 said:
Anyone successfully flashed the Build XNPH22Q on a Chinese 64GB OPO and could still use the full 64GB? I couldn't open the thread on the OPO forum. Does flashing each of the images image.zip work?
Click to expand...
Click to collapse
I've done what you said and my 64G OPO "turns" into 16G. I get information from OPO staff that CM will push an OTA this week to fix this issue.So just be patient.
Click to expand...
Click to collapse
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?
Entropy512 said:
What I said, or what he said?
Flashing a 16GB userdata.img is going to cause exactly this problem - have you tried the recovery reformat approach?
Click to expand...
Click to collapse
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
ailai55 said:
Sorry, I might mis-quoted your post.Actually I intended to reply his post.
I haven't done anything yet because I am waiting for CM's next update.
Click to expand...
Click to collapse
An update is not going to do anything unless they release a separate package with 64GB userdata, or force a complete format on OTA (generally this is something people don't do...)
If the update also has a 16GB userdata partition image, it'll have the exact same problem. Formatting userdata in recovery will resize it to use the entire partition.
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Key thing here: No flashing of userdata.img in fastboot - that's likely the ONLY thing you need to do (or more specifically in this case, NOT do) in order to avoid the issue of 64GB devices reporting 16GB userdata.
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?
ailai55 said:
Thank you. In your third step, could you make it more clear how did you do it? Did you flash the 467MB zip in recovery or followed the instructions in the original thread ( zip first and type commands)?
Click to expand...
Click to collapse
Flashing the zip rom is sufficient, no other command needed. Note you need to perform "Factory Reset" when you boot to recovery then apply zip rom. Cheers! :laugh:
reply to s
sasalove said:
Hello everyone, I got my one plus one today! I confirm CM11S rom works on 64GB. See Attached!
This is what I did with my phone and feel very excited now!
1. Unlock the phone by
fastboot oem unlock
2. Flash the recovery and modem with WCDMA
fastboot.exe flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
3. Flash XNPH22Q
Reboot to recovery, apply factory reset and install the XNPH22Q zip rom file
You can find the necessary files and instruction here if you know Chinese. Assume you have played with another phone before, it's easy!
[recovery and hacked modem] oneplusbbs.com/forum.php?mod=viewthread&tid=336574&extra=page%3D3%26filter%3Dtypeid%26typeid%3D25
[latest CM12s rom] oneplusbbs.com/forum.php?mod=viewthread&tid=351823&extra=page%3D1%26filter%3Dtypeid%26typeid%3D28
Cheers!
Click to expand...
Click to collapse
Could you post more detailed procedures? I couldn't get it work!
I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks
Rsd lite 6.1 to flash
hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci
hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
Rooted Verizon Pixel 2: "There's an internal problem with your device. Contact ..."
I rooted my Verizon Pixel 2 running 8.1 and whenever I boot it up and I'm on the lock screen, I get this error: ""There's an internal problem with your device. Contact your manufacturer for details" Anyone know how to get rid of it?
I found this for a Nexus6p, but I'm not sure it'd work for a Google Pixel 2 (Verizon): https://forum.xda-developers.com/showpost.php?p=64289509&postcount=8
You have to re flash the stock boot image and dtbo image.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
On both slots.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
---------- Post added at 01:30 AM ---------- Previous post was at 01:21 AM ----------
iamnotreallyhere said:
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
Click to expand...
Click to collapse
Also you may not have to reflash the stock boot image just dtbo. If you are using a custom kernel make sure to flash that dtbo.
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Lightn1ng said:
On both slots.
Click to expand...
Click to collapse
I did this. Curious though.. @Shadow/Walker doesn't mention doing it...is it important?
I downgraded to Magisk 15.1 because of this issue. 15.2 doesn't bring this error.
upperbladez said:
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Click to expand...
Click to collapse
Glad you figured it out! I was going to say it's in the second zip file within the first zip file. Also I don't think there is a way to brick unless you lock your boot loader. As long as you can fastboot and have an unlocked bootloader you should be able to recover from anything. Never ever ever lock your bootloader ever again
Just ignore the message, it's just a security warning because of what Magisk is patching to enable systemless mods on the vendor partition. I doesn't affect anything.
thanks to the other CODEFIRE members.. I'm able to provide these files.
this should help jumpstart public development for the G7 as well as ports for some of the other LG devices.
boot.img will help get TWRP going so those who are bootloader unlockable can actually do something with their device.
system.img and vendor.img will help with ports etc.
download:
http://downloads.codefi.re/autoprime/LG/LG_G7/LMG710EM/LMG710EM10B/
these zips are not "flashable".. just compressed files
md5:
c81aafbe1c1523ff5eb998104b62ebe2 | boot.img.zip
b28d23b289ab6ffaedf0abad17bebccf | modem.img.zip
1496207beed6e7735b40f1e94f1be12d | system.img.zip
a791f05b90099b818b257c47ddfe9cd5 | vendor.img.zip
have fun y'all :good:
Thanks for this!
Wow @autoprime... I remember you from that gnex script! Thanks again, btw.
thank you. would be possible to also get modem.img ?
VeixES said:
thank you. would be possible to also get modem.img ?
Click to expand...
Click to collapse
let me know what you need , since i have twrp i can dump anything from phone
I would need folder "mcfg_sw" and its contents(bunch of .mbn files). Its usually part of the the modem.img. Unfortunately i dont know where it sits on LG device. Maybe under /system/system or /system/vendor.
Thank you.
VeixES said:
I would need folder "mcfg_sw" and its contents(bunch of .mbn files). Its usually part of the the modem.img. Unfortunately i dont know where it sits on LG device. Maybe under /system/system or /system/vendor.
Thank you.
Click to expand...
Click to collapse
added modem.img.zip to the download folder linked in OP. :good:
autoprime said:
thanks to the other CODEFIRE members.. I'm able to provide these files.
this should help jumpstart public development for the G7 as well as ports for some of the other LG devices.
boot.img will help get TWRP going so those who are bootloader unlockable can actually do something with their device.
system.img and vendor.img will help with ports etc.
download:
http://downloads.codefi.re/autoprime/LG/LG_G7/LMG710EM/LMG710EM10B/
these zips are not "flashable".. just compressed files
md5:
c81aafbe1c1523ff5eb998104b62ebe2 | boot.img.zip
b28d23b289ab6ffaedf0abad17bebccf | modem.img.zip
1496207beed6e7735b40f1e94f1be12d | system.img.zip
a791f05b90099b818b257c47ddfe9cd5 | vendor.img.zip
have fun y'all :good:
Click to expand...
Click to collapse
Can you please explain how I can dump another version (10f or 10h) and/or how I can extract the boot.img from the kdz files?
I just need the boot.img for rooting.
Thank you in advance .
Is there any chance to have a system.img and vendor.img from international variant? Thanks in advance!
Astrako said:
Is there any chance to have a system.img and vendor.img from international variant? Thanks in advance!
Click to expand...
Click to collapse
What is the model of international variant If its lmg710eaw let me know the procedure i am getting G7+ lmg710eaw today here in india i will dump all the files
and wanna root my g7+ thanks
Sent from my SM-G965F using XDA-Developers Legacy app
I was hoping to find the preload folder with the preloaded music file Life's Good
@autoprime -always good to see you around. I'm hoping for magic with the vzw g7 [emoji3]
This is probably a really stupid question, but I soft bricked my phone and am looking to reset it back to initial factory settings, and I am wondering if I can do that flashing these images. I have flashed the boot.img using "fastboot flash boot boot.img" and have flashed the system.img using "fastboot flash system system.img", however that has not fixed my problem.
Also when I flash the system.img, I get an error saying "Invalid sparse file format at header magic". The system.img seems a little off when I extract it (7z says it is ~3 GB big but then extracts to 7 GB), and I have checked the md5 and it matches.
Another very stupid question, is what is the difference between the system.img and the vendor.img?
Sorry if this is the wrong place to post this, and thanks in advance for any help anyone can offer.
jdchristesen said:
This is probably a really stupid question, but I soft bricked my phone and am looking to reset it back to initial factory settings, and I am wondering if I can do that flashing these images. I have flashed the boot.img using "fastboot flash boot boot.img" and have flashed the system.img using "fastboot flash system system.img", however that has not fixed my problem.
Also when I flash the system.img, I get an error saying "Invalid sparse file format at header magic". The system.img seems a little off when I extract it (7z says it is ~3 GB big but then extracts to 7 GB), and I have checked the md5 and it matches.
Another very stupid question, is what is the difference between the system.img and the vendor.img?
Sorry if this is the wrong place to post this, and thanks in advance for any help anyone can offer.
Click to expand...
Click to collapse
You're better off with LG UP or LG Bridge and the difference between the system and the vendor is the system is Android and vendor is libraries that communicate with the hardware.
I would like to ask anyone you have a G710EM model with bootloader unlocked to make a dump with LGUP, without system and userdata.
Thanks in advance!
I bought a "factory unlocked" LM-G710EM on Amazon that has Claro phone company software. It works with AT&T and It has the 4g bands in the areas that I need so I'm keeping it. I have a question about the software and updates. Does anyone know if my updates are coming from LG or Claro? Is there a way I can find out? When I first used the phone it updated and added an extra Claro program .so it may be Claro or LG pushing the roms for Claro. Can I flash the rom in this post and convert my phone to a standard LM-G710EM? Is there anymore info that I can provide? Thank you in advance.
Here is the software info as of today.
https://i.imgur.com/ha14Hbn.png
khanfuze said:
I bought a "factory unlocked" LM-G710EM on Amazon that has Claro phone company software. It works with AT&T and It has the 4g bands in the areas that I need so I'm keeping it. I have a question about the software and updates. Does anyone know if my updates are coming from LG or Claro? Is there a way I can find out? When I first used the phone it updated and added an extra Claro program .so it may be Claro or LG pushing the roms for Claro. Can I flash the rom in this post and convert my phone to a standard LM-G710EM? Is there anymore info that I can provide? Thank you in advance.
Here is the software info as of today.
https://i.imgur.com/ha14Hbn.png
Click to expand...
Click to collapse
Your version EM is Global!
Could you make a full dump ( no userdata ) from your device with the bootloader already unlocked?
b8engl said:
Your version EM is Global!
Could you make a full dump ( no userdata ) from your device with the bootloader already unlocked?
Click to expand...
Click to collapse
Is there a difference between my rom and the one in the op? What method should I use to dump?
khanfuze said:
Is there a difference between my rom and the one in the op? What method should I use to dump?
Click to expand...
Click to collapse
I don't know which version number you have, but the O.P. just shared the system, vendor and boot for developer purpose. You could try LGUP patched... V30 link here can't say will work for you.
Any chance for uploading carrier image?
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