Database Info

Moto G4 Plus US XT1644 Stock Unmodified 6.0.1 TWRP Backup & Recovery/Logo Images

Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA

You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:

panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk

annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup

Does XT1644 have an OTA available now? I didn't think it was pushed yet.

pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again

Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk

you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!

Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.

bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.

where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .

panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.

Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/

didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out

TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk

getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk

bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?

dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk

bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.

vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .

New Update - QD1

According to the Verizon Galaxy S5 Update Page:
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip

what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!

knight194 said:
what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!
Click to expand...
Click to collapse
If you have a Developer Edition phone, the Stock one will remove the Developer status. The Developer Bootloader Friendly one won't.

Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!

sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?

nictabor said:
Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!
Click to expand...
Click to collapse
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
KazuDante said:
sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?
Click to expand...
Click to collapse
Normally the latest update provides the latest/best modem.

Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?

KazuDante said:
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?
Click to expand...
Click to collapse
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.

Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
I actually figured it out while waiting. Thank you for responding though!

nictabor said:
I actually figured it out while waiting. Thank you for responding though!
Click to expand...
Click to collapse
You're welcome.
On a side note, it seems like Verizon read the recent articles where the Galaxy S5 was still rated as the most popular smart phone being used on any network. Meaning, they are updating the phone monthly now, which is good news for us. We won't ever get Nougat but apparently we'll get Security Patches monthly now.

Dudash said:
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.
Click to expand...
Click to collapse
so can i take the modem.bin file from this update and replace it with the one from a 7.1.2 rom ? also i used to mess with porting roms but on mediatek platform , are the modem files still located in /system/etc/firmware directory?
because what i see is modem.b00-b27 ,modem.mdt
---------- Post added at 08:04 PM ---------- Previous post was at 07:08 PM ----------
i tried flashing the dev friendly one and the md5 check failed....am i missing something?

Dudash said:
According to the Verizon Galaxy S5 Update Page:
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???

how do we flash this update , odin fails on md5 check

Deleted

flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?

KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
I would not do it.

erw38 said:
I would not do it.
Click to expand...
Click to collapse
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.

KazuDante said:
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.
Click to expand...
Click to collapse
I didn't think a tutorial was necessary as I've never had to give one in the past. If your device is unlocked, you should know it. That's the only reason there is a Dev Friendly version of the update. It won't unlock your bootloader, but it won't lock it if it is unlocked. That's the only reason I make a Developer Bootloader Friendly version of updates.
If you want to update your modem but not the firmware, open either of the files in 7zip/WinZip, extract the modem.bin, then repackage it as a .tar file and flash it in Odin.
KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
In regard to your previous post, there is no problem with the MD5 for either file or any problem with the files themselves. I test them both before uploading them to prevent problems like this for people. I flashed the Dev Friendly version on both of my eMMc 15 S5's and experienced zero problems. The phone will hang on the "Verizon logo" for a minute or two at first boot but it will go past it and continue to "Optimizing" after that.
If you flash the Stock version, if your bootloader is unlocked, it will lock it and in order to re-unlock it, you'll have to use jrkruse's unlock method which requires you to go back to PB1. As of this post, he has not created a QD1 bootloader unlocker. The latest bootloader unlocker he has created is for QC2, which still requires you to have an unlocked bootloader prior to flashing it.
EDIT: Also, if you use an app like Package Disabler Pro to disable applications without root, it can cause updates to hang indefinitely at first boot if you don't re-enable all disabled applications and turn off/remove Admin rights for Package Disabler Pro prior to updating. I've experienced this in the past with both of my S5's and my S7. I'm not directing this at you KazuDante, this is just a warning to all.

21-Savage said:
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???
Click to expand...
Click to collapse
No. The Developer Bootloader Friendly version is just that, friendly to devices with a Developer Bootloader. Meaning it won't remove Developer Bootloader status/lock the bootloader.
If I had figured out a way to help all of the eMMc 11 people unlock their bootloader, I would've made a thread that clearly stated that.
I think the only way people with Toshiba eMMc's will get an unlocked bootloader is if either
A: Verizon provides an update to unlock the bootloaders on all S5's AFTER they stop putting out Security Updates, which is highly unlikely since it is Verizon, they've never done it before, and there's no end to Security Updates in sight.
B: Someone at Samsung or Verizon leaks an engineering bootloader. This is the most likely scenario since it's happened before. First, in my experience, with the VZW S3, and the latest being with the S7. There's still hope but it may rely on someone from within Verizon or Samsung feeling bad for us.
Sorry

@Dudash Any idea how to go from the Dev-friendly QD1 version you uploaded to a TWRP flashable zip file which resembles the jrkruse VZW_QA1_STOCK_ROOTED_DEODEXED.zip? I really like to debloat and root before flashing. Thanks!

New Update - QI2

According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.

so its safe to say that the new modem ql2 is pretty much the same sa the previous update?

Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.

Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse

For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse

I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.

You will also have to re-flash TWRP via Odon.

kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.

I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.

I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!

purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.

bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??

purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:

Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks

[STOCK][O] H850 30a OPEN EU ROM Flashable ZIPs + KDZ (Android 8.0 "Oreo")

Stock Firmware H850 V30a "Oreo" OPEN EU ROM
KDZ-File: H85030a_00_OPEN_EU_OP_0910.kdz (MD5)
Flashable ZIP Complete: LG-H85030a-Flashable.COMPLETE.zip (MD5)
Flashable ZIP Boot: LG-H85030a-Flashable.Boot.zip (MD5)
Flashable ZIP Bootloader: LG-H85030a-Flashable.Bootloader.zip (MD5)
Flashable ZIP Modem: LG-H85030a-Flashable.Modem.zip (MD5)
Android 8.0.0
Patch level: 1 September 2018
Baseband: MPSS.TH.2.0.c1.4-00070-M8996FAAAANAZM-1.163432.2a.168009.1
Kernel: 3.18.71
Build: OPR1.170623.032
Software version: V30a-EUR-XX
Changes:
- Android Oreo
Instructions:
Upgrade from Android 7 and root using TWRP and Magisk
Do backups! Expect to lose your apps and settings!
Get the required imgages:
H85030a_00_OPEN_EU_OP_0910.kdz from above --> store it on your HDD.
twrp-3.2.3-2-h850.img --> HDD
Magisk 17.1 ZIP file. Copy it to your G5's SD card.
the LG-H85030a-Flashable.COMPLETE.zip from above --> SD-Card.
Optional: You can additionally download the MD5 file which is being used by TWRP to verify the ZIP file (simply place it in the same folder like the ZIP).
As a safety measure, I'd clean upgrade with the stock KDZ first using LG UP. This will replace also recovery to stock. If successful, you can continue.
Unlock the bootloader (if not already unlocked) as described here with the official bootloader unlock and flash TWRP. TWRP 3.2.3-2 worked for me. Boot into TWRP as described.
Optional: Do a backup in TWRP.
Format Data: "Wipe" > "Format Data" > type "yes". Wipe slider wipe is not enough!
Go back until you see the TWRP main screen. Then Reboot into Recovery. Don't start into System!
Flash / Install the LG-H85030a-Flashable.COMPLETE.zip and Magisk-v17.1.zip without reboot inbetween.
Reboot to System
enjoy!
To build the ZIPs I used parts of autoprime's previous files. Thx again!
Disclaimer: This is not an official post by LG to update the firmware! Don't blame me if you destroy your phone. If you use these files and instructions you do it at your own risk!

Is the Oreo firmware backward compatible with Nougat?
Sent from my LG-H850 using Tapatalk

Why does it come with the Vodafone app?

Flashable ZIP Bootloader: LG-H85020v-Flashable.Bootloader.zip (MD5)
Flashable ZIP Modem: LG-H85020v-Flashable.Modem.zip (MD5)
Click to expand...
Click to collapse
Just curious if above should be in the OP as they are Nougat files unless I'm mistaken.

I've had it with these stock firmware files and images, I'm waiting until a debloated stable custom rom hits. The KDZ hung on boot even after factory resetting and this stock rom wipes twrp every time I reboot causing me to endlessly reflash twrp.

ezzony said:
Just curious if above should be in the OP as they are Nougat files unless I'm mistaken.
Click to expand...
Click to collapse
Thank you! My bad, the links were correct but the texts were wrong. Corrected.

VortexHD said:
Why does it come with the Vodafone app?
Click to expand...
Click to collapse
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?

Ok, just for information (and it may be useful to others with the same scenario):
I'm on lineage Oreo, with magisk and twrp 3.2.3.2, can I flash the COMPLETE zip => then twrp => then magisk and get the rom installed keeping twrp and root? I can't access any Windows machine (only Mac) to flash the kdz file, would it work as well if i flash all that stuff in twrp?
Thanks!

xlxcrossing said:
Is the Oreo firmware backward compatible with Nougat?
Click to expand...
Click to collapse
What do you mean? Downgrading back to Nougat? Honestly I never tried this.
xlxcrossing said:
I've had it with these stock firmware files and images, I'm waiting until a debloated stable custom rom hits. The KDZ hung on boot even after factory resetting and this stock rom wipes twrp every time I reboot causing me to endlessly reflash twrp.
Click to expand...
Click to collapse
The first boot after KDZ installation took 5-10 minutes on my device while showing the LG symbol and flashing LED... But it continued. The firmware appears stable on my device. TWRP runs persistent.

karma0321 said:
I'm on lineage Oreo, with magisk and twrp 3.2.3.2, can I flash the COMPLETE zip => then twrp => then magisk and get the rom installed keeping twrp and root? I can't access any Windows machine (only Mac) to flash the kdz file, would it work as well if i flash all that stuff in twrp?
Thanks!
Click to expand...
Click to collapse
I'd give a try but don't blame me if it is not working. Flashing the KDZ was a safety measure to me as I was not entirely sure if flashing COMPLETE alone is enough. But you are already running an Oreo OS, so I'd try it. As long as you have access to TWRP or Bootloader you can flash your working Lineage image and TWRP. However, flashing TWRP after COMPLETE makes no sense in my eyes as COMPLETE does not contain stock recovery.

DavidFlint said:
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?
Click to expand...
Click to collapse
i also see 2 vodafone apps and some french thing "jeau" or something similar that keeps asking for permissions.
im on EE, but the previous firmware was non branded.
everything seems to be working smoothly

Anyone got any other link than Mediafire? Takes 4 hours to download and would like it faster?

DavidFlint said:
...However, flashing TWRP after COMPLETE makes no sense in my eyes as COMPLETE does not contain stock recovery.
Click to expand...
Click to collapse
Thank you so much, I didn't know COMPLETE has no recovery inside. So (sorry for bothering) what does COMPLETE contain? My guess is Rom+boot+modem+bootloader but now I'm not sure anymore

Hi
So is good rom to install from TWRP recovery. Any one fund any issue?

DavidFlint said:
Shouldn't. I tested it and there is no Vodafone app on my device. Where did you see this? Are you Vodafone customer?
Click to expand...
Click to collapse
The Vodafone app is called "Start" and the phone is unlocked and I'm not a Vodafone customer.

Rom is from Vodafone or only app?

Flashed today, have been running it for about 5 hours...
Gotta say I'm in love, and btw, no bloatware apps nothing. Just clean stock LG Oreo. Beautiful.

bmwtomas said:
Flashed today, have been running it for about 5 hours...
Gotta say I'm in love, and btw, no bloatware apps nothing. Just clean stock LG Oreo. Beautiful.
Click to expand...
Click to collapse
I flashed yesterday coming from Lineage OS 15, wiped System, Data and Caches, installed Rom and Magisk. It works.
But I do have the bloatware from LG like Facebook App and a lot of others, that I can not entirely uninstall.
And my phone keeps presenting me a software update, that I would only see, when I agree in using my personal data for...
Btw. no Vodafone App. Why do we have these different experiences? What's going on?

Oevi said:
I flashed yesterday coming from Lineage OS 15, wiped System, Data and Caches, installed Rom and Magisk. It works.
But I do have the bloatware from LG like Facebook App and a lot of others, that I can not entirely uninstall.
And my phone keeps presenting me a software update, that I would only see, when I agree in using my personal data for...
Btw. no Vodafone App. Why do we have these different experiences? What's going on?
Click to expand...
Click to collapse
Use system app remover

Flashed Oreo on two LG G5
One got no bloatware and one came with Vodafone and Orange app
The one without bloatware has the Software Version: V30a-EUR-XX
and the one with bloatware has the Software Version: V30a-214-07
I used the same files for flashing
But the bad thing is on both phones the light doesn't work?!
Someone with the same issue?
---------- Post added at 01:27 AM ---------- Previous post was at 01:21 AM ----------
VortexHD said:
Why does it come with the Vodafone app?
Click to expand...
Click to collapse
You don't have software version: V30a-EUR-XX right?
Works the light for you?

OTA (Flashing via Fastboot) Cheetah

Ok I downloaded the May ota payload zip and flashed via fastboot in stock recovery
(adb sideload otamay.zip) renamed zip of course.
Absolutely no problems . i didn't have to update any platform tools or anything.
I read platform 33.0 instead of 34.0 ...I haven't updated any adb drivers since 2000.
Note my bootloader is locked no root.
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
After i flashed the ota.zip my performance got better. Seems the carrier factory software is slower. Even on my Motorola phones i would flash the retail software and remove the carrier software version.
Always a cleaner android experience imo..
Loving my Pixel 7 Pro on Stock no issues...

jhjhjhjhjhjh said:
So in case anyone is not aware us non-rooted pixels can update firmware using adb sideload command in stock recovery.
Click to expand...
Click to collapse
Every Android can be updated via adb sideload using the correct OTA file. That's quite normal. And a full firmware flash would require an unlocked bootloader and not root.

jhjhjhjhjhjh said:
Seems the carrier factory software is slower.
Click to expand...
Click to collapse
you still have the same firmware installed on your device. it's only updated.

WoKoschekk said:
you still have the same firmware installed on your device. it's only updated.
Click to expand...
Click to collapse
True just wasnt clear on pixel devices thought these devices had a different method of things.
Anyways thanks for clearing it up
I guess all pixels share one firmware across all carriers and regions..

jhjhjhjhjhjh said:
I guess all pixels share one firmware across all carriers and regions..
Click to expand...
Click to collapse
No, they have different builds for other carriers/regions. See here. But it's not possible to change the region/carrier version via OTA. You would need a full firmware for that, but it's not recommended and won't have any benefits for you.

Since you are locked and not rooted, why don't you just update from Settings/System/System update?