Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this rom. You do so at your own risk and take responsibility upon yourself.
About:
The Stock ROMs posted here are extracted from official LG KDZ files for the T-Mobile LG G Pad X 8.0 | v521 | b3.
Only change made on ROM was to prevent stock recovery from restoring itself
ROM includes modem/radio, however you can also manually flash the modem/radio from here
root is NOT included. However feel free to flash your choice of root with Magisk, SuperSU, or any others at anytime to get root.
Info:
Android version: 7.0
Kernel version: 3.10.84
Build number: NRD90U
init.d support
forceencrypt disabled
Requirements:
Your device must be or have been on 20f or newer at one point or another. If your device has always been on Marshmallow and has never been updated to Nougat by kdz or OTA, you'll need to upgrade to Nougat and re-root first. (Thank to monkeyass408 for verifying)
You can follow this guide to do so: Guide to Update V521 LG GPAD X 8.0 to 7.0 and Root
You must have TWRP or another custom recovery already installed in order to flash this rom.
Instructions:
Download the version of your choice from below.
Boot into TWRP and make a backup. You may want to remove any lock screen security before doing this as restoring with lock screen may cause unexpected issues.
Optional: Wipe data and/or system. As of TWRP 3.1.1.0, you will want to reboot recovery after wiping data/system before flashing as TWRP may get stuck on a black screen during the flashing process without a reboot.
Flash ROM.
Optional: Flash the disable OTA zip to prevent and disable official LG OTA updates & notifications
Reboot and you should be all set.
Downloads: (Listed by Sofware version / Android security patch level)
Note: As of 2017-02-21, TWRP 3.0.2-0, will sometimes give the error "Failed to map file" when attempting to flash this rom. Rebooting TWRP will resolve it and allow you to flash the zip.
v52120n >> Apr 1, 2018
v52120m >> Feb 1, 2018
v52120l >> Dec 1, 2017
v52120k >> Oct 1, 2017
v52120j >> Aug 1, 2017
v52120i >> Jun 1, 2017
v52120h >> Apr 1, 2017
v52120g >> Feb 1, 2017
v52120f >> Dec 1, 2016
All Stock ROMs Folder
Disable Stock OTA
Note: This should prevent you from verifying and updating via OTA. The OTA notification may still pop up but it should go away when you attempt to update after flashing this. I haven't fully tested this so backup first and don't be surprised if it returns you to full stock.
Credits/Thanks:
tungkick for the initial root method
shabbypenguin for TWRP on the LG G Pad X
All other devs who make rom building possible
Reserved - Unlikely I'll need it but who knows?
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
channeledbymodem said:
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
Click to expand...
Click to collapse
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
supaet said:
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
Click to expand...
Click to collapse
Hmmm I haven't had any issues with my 5ghz on my tablet. The roms are ripped straight out of the kdz files so any changes between 20g and 20f are strictly from LG/T-Mobile. Although I do recommend keeping the modem version and the rom version the same, I am curious, would you be able to test and see if it still happens if you downgrade the modem version to 20f while you're on the 20g rom?
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
.fenrir said:
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
Click to expand...
Click to collapse
Appreciate the update Thanks!!!
A bit quicker this time around. 20k has been added.
Amd4life said:
Appreciate the update Thanks!!!
Click to expand...
Click to collapse
No problem.
.fenrir said:
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
Click to expand...
Click to collapse
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
monkeyass408 said:
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
Click to expand...
Click to collapse
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
.fenrir said:
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
Click to expand...
Click to collapse
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
monkeyass408 said:
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
Click to expand...
Click to collapse
Glad to hear it worked out for you. I stand corrected on it being flashed over Marshmallow so I've updated the first post to reflect that. Thanks for trying and verifying it.
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Char_Liu said:
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
Click to expand...
Click to collapse
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
channeledbymodem said:
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
Click to expand...
Click to collapse
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
Thank you for the update.!
Appreciate the update
Thx a lot
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
I have always had excellent battery life but after a dirty flash of v.l it is terrible. I am losing 30% overnight. Can I roll back to v.k? I am reluctant to clean flash v.l; it's a lot of work getting back to normal.
Related
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
technocrat7 said:
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
Click to expand...
Click to collapse
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
jeffsga88 said:
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
Click to expand...
Click to collapse
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
technocrat7 said:
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
Click to expand...
Click to collapse
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
jeffsga88 said:
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
Click to expand...
Click to collapse
Thanks!
That helps a ton.
What is dm-verity though?
technocrat7 said:
Thanks!
That helps a ton.
What is dm-verity though?
Click to expand...
Click to collapse
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
jeffsga88 said:
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
Click to expand...
Click to collapse
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
carnivalrejectq said:
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
Click to expand...
Click to collapse
Here's the link to chainfires thread which will always have the latest beta supersu versions:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Only system and kernel are being flashed, no Modem, BL, etc. You should already have updated to 20B before using.
Have not tested this myself, due to not owning the H850. edit: flashed it on T-Mobile 830 for fun with 20A 830 boot, no surprise, didn't work.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of H85020b_00_TIM_IT_OP_1123.kdz
Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Should be able to dirty flash over current 20B if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.-Again, haven't tested this one myself
Link: H850_20B_DeOdexed
MD5: 99c9667294d1227de91605b8958233e0
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji13]
Enjoy.
Optional: Adjust Screen Color
Credits: @Chainfire for supersu. @SuperR. for the kitchen. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP. @bullghost for Firmware Extractor
It's people like them that make Android great!
Finally, thanks to Google/LG & XDA.
...whew.
Reserved
Great work Bro, nice. :good:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
xlxcrossing said:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
Click to expand...
Click to collapse
1. Not 100% sure. 2. Just system and kernel are flashed. No M/BL, etc. 3. No idea really.
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Mr. Schnabel said:
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Click to expand...
Click to collapse
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
lordodin912 said:
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
Click to expand...
Click to collapse
Same error... Keep at it tho, something like this could be really useful
If anyone wants to try this themselves here's a quick guide.
You can take the system.img and boot.img from either the kdz with LG Firmware Extractor or from autoprime complete zip.
Then Google "superR kitchen xda", if your using windows there is a VM iso in the thread you can use with VirtualBox etc.
Once you have the kitchen working just remember, set_metadata for perm, use smali/baksmali for deodexing and don't sign the zip or let it remove the meta-inf folders from apps.
In my h850 doesn't finish to install, it remains on initial boot animation.
failax said:
In my h850 doesn't finish to install, it remains on initial boot animation.
Click to expand...
Click to collapse
Flashed ok but stuck on LG logo? May need to flash no verify or "format data" in TWRP. BACKUP everything if formatting.
Ok so I just clean flashed my 20a for h830 and got that error code 7, doesn't happen on dirty. Just restarted TWRP after wiping and then it flashed ok. Might be the same problem over here.
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? .
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 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?