Related
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Click to expand...
Click to collapse
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
It should be. I flashed it using Philz recovery.
feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
I had the same problem, TWRP did not take the OTA file properly. Every time it wanted to boot after the install started, it started TWRP and if I restarded the device it went into a bootloop.
So I installed Philz and everything went fine!
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Is it OK to flash this if I'm already on 4.4.4?
Quark^2 said:
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Click to expand...
Click to collapse
You´ve restored wrong kernel. It may be working for you, but it is different from stock. The error says that there is something that is not supposed to be there in the kernel partition.
Nicolae-Daniel said:
Is it OK to flash this if I'm already on 4.4.4?
Click to expand...
Click to collapse
You´re kidding, right?
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Nicolae-Daniel said:
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Click to expand...
Click to collapse
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
knizmi said:
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
Click to expand...
Click to collapse
By connectivity I meant signal strength.
My US-Global XT1032 still waiting...
tonyleeloveyou said:
My US-Global XT1032 still waiting...
Click to expand...
Click to collapse
US Global already has 4.4.3. The new kernel and dialer are already there, so don´t expect any improvements besides security patches when we get 4.4.4.
I received the OTA today. Updated without problems. Stock XT1032 8GB Moto G.
drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're still on Stock Recovery and don't want to use Philz, you can try to update the OTA by following the steps in the OP of this Post. I tried a lot of flashing, but in the end only this worked:
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Phone is unlocked, rooted and had xposed modules on it
Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Click to expand...
Click to collapse
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
So why don´t you revert your build.prop to stock?
dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
Knizmi is right. You modified your build.prop file, and an OTA update requires unmodified system files. You can add files to /system without problems however, so the su binary for example isn't an issue.
Sent from my Moto G using Tapatalk
OK, and where do i find a stock build.prop?
i don't know what modifications i have, but can i replace the stock one with my current after flashing? (and do i need to?)
HI! Firstly thanks for share the zip.
I´m using cwm recovery, superSU and xposed. Can I flash the zip directly from the recovery without any change? Will I lose the recovery (coming back to stock recovery) if I succed?
I tried to install the OTA after uninstall xposed and checking the ota survival mode on superSU, but it didn´t work (bootloop).
Thanks in advance.
http://shield.nvidia.com/tablet-release-notes/2.2/
now to figure out how to get this to update on my rooted LTE Tablet.....
I'm rooted and just got the update. But haven't completed the update yet as I'm too lazy to reroot.
I tried using the nvidia updater, which failed since it rebooted and CWM had no idea what to do. I made a CWM backup so I am going to see how well it flashes in CWM manually.
I managed to find the OTA download location and have superSU at the ready in my downloads folder in case I have to reflash. the OTA saved as:
/data/data/com.nvidia.ota/files/ROM/shield_tablet_software_upgrade_2.2_-_lte__5.0.1.zip
Someone please report the steps on how to do this for Rooted 2.1.
CWM install zip failed. build fingerprint mismatched, its probably CWM. Will try sideloading stock recovery then installing the zip afterward, I think I remember seeing somewhere here that's how people upgraded rooted devices from 2.0 to 2.1
Omg things seem to be more snappy! The dreaded lag may be gone! I'm not rooted so I did the ota install
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Iorkca said:
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Click to expand...
Click to collapse
currently working on it right now, need about a few to upload all files and then get everything setup....
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Awsome sounds good. Quick question to get stock recovery back all id have to do is extract the recovery.img file from the ota 2.1 file i downloaded off nvidia's site and load it like i did the CWM recovery from the root thread right?
Or (if you've got root) wait until the full 2.2 .zip is available, then download it and flash it through your custom recovery, followed by the latest SuperSU. (just like the last Lollipop update).
Interestingly, the OTA update tool has an option for "Check full update" (under the top right menu), but it doesn't seem to return anything...yet...
Sent from my SHIELD Tablet using XDA Free mobile app
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
NaminatoR1254jaime.sier said:
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
Click to expand...
Click to collapse
Yeah, if you have the stock recovery file....
mcord11758 said:
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Click to expand...
Click to collapse
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
masterchiefb117 said:
Yeah, if you have the stock recovery file....
Click to expand...
Click to collapse
I dont
But Im downloading the 2.1 update stock images. Funny how I deleted the 2 gb zip yesterday and now I need it.
masterchiefb117 said:
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Click to expand...
Click to collapse
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
ok, here's what I dug up. If you are rooted and want it NOW, get to it, otherwise wait for someone to clean up the process:
get the OTA from here: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
get your latest SuperSU flashable zip: http://download.chainfire.eu/396/SuperSU/
get your recovery ready for reflashing, the OTA will install the stock recovery again. I went with: http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90
boot into recovery and install zip from sideload. then choose either: adb sideload productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip or adb sideload productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
reboot and let the upgrade happen, you've lost root and recovery, but you still are unlocked so you just have to reflash them. get into fastboot with power and volume down, then flash recovery: fastboot flash recovery openrecovery-twrp-2.8.5.0-shieldtablet.img
load up recovery and flash the superSU zip and you're back in business.
ShrekOpher said:
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Wiped cache and davlik then just in case flashed supersu after rom
An Droid said:
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
That means a rooted lollipop user with custom recovery, can download the full ota, and dirty flash it, right?
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
Introduction
Due to popular demand I have created a flashable zip from the official firmware released on 2016 July 12th (Version MM 30G)
Pre-requisite
If you haven't root/bump/TWRP already, read the tutorial here.
Disclaimer
I will not be responsible if you brick your phone. Use this tutorial at your own risk. Read the entire tutorial before proceeding.
How to use
To do a clean install:
Go into TWRP -> Wipe system/data -> Format system -> Flash the ROM zip.
To do an update without losing data/apps
Go into TWRP -> Flash the zip.
To get root
Flash my rooted boot.img -> Flash SuperSU V2.79.
If you an boot error, just flash the rooted boot.img again.
Only flash SuperSU V2.79 or above.
The only partitions that will be touched are the system and boot partitions. Bootloader and recoveries will not be touched, so after flashing to new ROM you can go back to TWRP and flash any custom zips!
I also provided a bumped boot.img on the side for those who want to use it with other Marshmallow custom ROMs like Fulmics.
If you want to get root for the stock ROM, you have to flash the rooted boot.img, then install SuperSU from play store. This is currently the only way to get root on official Marshmallow.
I don't have time to remove the bloatwares yet. So if you removed the LG bloatwares previously, they will be back.
Download
D852 Telus/Koodo MM 30G Stock ROM
D852 Telus/Koodo MM Bumped boot.img (no root, use this to unroot)
Rooted boot.img (Flash this to root #Rooted version 2.79)
SuperSU V2.79
Visit my blog for more G3 tutorials
Thanks, just wondering what the bump.img is for and why it is needed to flash another ROM.
powerserge1 said:
Thanks, just wondering what the bump.img is for and why it is needed to flash another ROM.
Click to expand...
Click to collapse
Read this and you'll know everything about rooting G3
hdlineage said:
Read this and you'll know everything about rooting G3
Click to expand...
Click to collapse
Perfect. Can the boot.img be flashed with TWRP instead of Imageprep? Say I flash Fulmics at some point or any other ROM (that has root), then immediately after flash your boot.img within recovery to overwrite the Rogers kernel that most ROMs come with. Just making sure. This extra step is for those with a Telus/Koodo variant of the G3
powerserge1 said:
Perfect. Can the boot.img be flashed with TWRP instead of Imageprep? Say I flash Fulmics at some point or any other ROM (that has root), then immediately after flash your boot.img within recovery to overwrite the Rogers kernel that most ROMs come with. Just making sure. This extra step is for those with a Telus/Koodo variant of the G3
Click to expand...
Click to collapse
Yep, as long as the ROM is based on stock you shouldn't have problem flashing stock kernel.
Would this boot.img work on rogers?
Octane70 said:
Would this boot.img work on rogers?
Click to expand...
Click to collapse
It seems LG released the same MM kernel for all variants in Canada. Theoretically it should work for Rogers too.
You can try it out to see if there's any bugs. If it doesn't work you can just flash back your original boot image (make sure to back up boot partition first!).
Let us know if it works.
Thanks you.
Does anybody have a success story to share about updating without wiping ?
hdlineage said:
It seems LG released the same MM kernel for all variants in Canada. Theoretically it should work for Rogers too.
You can try it out to see if there's any bugs. If it doesn't work you can just flash back your original boot image (make sure to back up boot partition first!).
Let us know if it works.
Click to expand...
Click to collapse
Thanks hdlineage,
If you dont mind i would like to confirm some steps?
I am on rogers MM OTA so i am complete stock.
So i download the kitkat-aboot.img, kitkat-laf.img and twrp
Use your imgprep program to install the img's and twrp.
then back up the current boot.img in twrp, then flash the modified you provided, correct.
Then i could either flash a super user.zip or install super user from the playstore?
Thanks for your work
Octane70 said:
Thanks hdlineage,
If you dont mind i would like to confirm some steps?
I am on rogers MM OTA so i am complete stock.
So i download the kitkat-aboot.img, kitkat-laf.img and twrp
Use your imgprep program to install the img's and twrp.
then back up the current boot.img in twrp, then flash the modified you provided, correct.
Then i could either flash a super user.zip or install super user from the playstore?
Thanks for your work
Click to expand...
Click to collapse
For imageprep to work you will need to downgrade to lollipop first.
It won't work with MM. Currently you need custom recovery to root MM.
Octane70 said:
Would this boot.img work on rogers?
Click to expand...
Click to collapse
Octane70 said:
Thanks hdlineage,
If you dont mind i would like to confirm some steps?
I am on rogers MM OTA so i am complete stock.
So i download the kitkat-aboot.img, kitkat-laf.img and twrp
Use your imgprep program to install the img's and twrp.
then back up the current boot.img in twrp, then flash the modified you provided, correct.
Then i could either flash a super user.zip or install super user from the playstore?
Thanks for your work
Click to expand...
Click to collapse
In order to root using the method described in this thread, you must already been rooted with a bumped TWRP when you were on Lollipop. Refer to OP and the "Requirement" section if you need more information.
If you were not rooted with bumped TWRP previously, then you have two options:
1) Downgrade to LP by using LGUP, root/bump using ImagePrep, then flash according to instructions on this thread
2) Wait for ImagePrep to be updated for MM compatibility and then root (and/or install bumped TWRP).
Your propose method may fail since you are on MM already and ImagePrep is currently compatible with either KK or LP only. If your method works, please let this community know.
There are other root methods available such as the one-click method http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197, but I am unable to validate them since I used ImagePrep method on LP only.
hdlineage said:
It seems LG released the same MM kernel for all variants in Canada. Theoretically it should work for Rogers too.
You can try it out to see if there's any bugs. If it doesn't work you can just flash back your original boot image (make sure to back up boot partition first!).
Let us know if it works.
Click to expand...
Click to collapse
bb709394 said:
In order to root using the method described in this thread, you must already been rooted with a bumped TWRP when you were on Lollipop. Refer to OP and the "Requirement" section if you need more information.
If you were not rooted with bumped TWRP previously, then you have two options:
1) Downgrade to LP by using LGUP, root/bump using ImagePrep, then flash according to instructions on this thread
2) Wait for ImagePrep to be updated for MM compatibility and then root (and/or install bumped TWRP).
Your propose method may fail since you are on MM already and ImagePrep is currently compatible with either KK or LP only. If your method works, please let this community know.
There are other root methods available such as the one-click method http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197, but I am unable to validate them since I used ImagePrep method on LP only.
Click to expand...
Click to collapse
Thanks for the clarification guys. i used http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 method to root LP
Thanks to op for releasing this but your dropbox is now suspended...an alternate mirror would be helpful please.
Paulicat said:
Thanks to op for releasing this but your dropbox is now suspended...an alternate mirror would be helpful please.
Click to expand...
Click to collapse
Updated with google drive, hopefully this one will stay up.
hdlineage said:
Updated with google drive, hopefully this one will stay up.
Click to expand...
Click to collapse
Cheers downloading now!
Surprised there is no modem.img in the update?
Did the baseband version change?
Mine is a Rogers D852 but is unlocked and was not OTA updated past Lollipop.
The baseband version showing is: MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1
Can anyone confirm a change in baseband?
Is there any flashable file available for fido users.?
delete, Rogers should be the same as Fido but can't confirm
Paulicat said:
Cheers downloading now!
Surprised there is no modem.img in the update?
Did the baseband version change?
Mine is a Rogers D852 but is unlocked and was not OTA updated past Lollipop.
The baseband version showing is: MPSS.DI.2.0.1.c1.13-00053-M8974AAAAANPZM-1
Can anyone confirm a change in baseband?
Click to expand...
Click to collapse
No baseband update. Mine is the same as above.
---------- Post added at 02:21 PM ---------- Previous post was at 02:18 PM ----------
patelsavan said:
Is there any flashable file available for fido users.?
Click to expand...
Click to collapse
It is the same (use bumped zip) from this thread. I have a Koodo G3 unlocked on the FIdo network configured with Fido APN and it works. No issues yet, have not tested GPS or Bluetooth. Since there is no baseband update, I don't think there will be any issues.
My Fulmics install failed to boot and was stuck on LG logo with flashing green & blue led. Stock MM bumped zip install works just fine.
Which boot image should I have used and what about installing SuperSU?
Current root methods in OP fails. Tried both boot images and tried bumped boot image. Supersu failed on version 2.65, 2.67, 2.68, 2.70.
hdlineage: keep getting the error message it is failing to patch the boot.img since Supersu detects boot is already patched. Any ideas?
Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much
Born<ICs said:
Was rooted on stock 7.0 and SuperSu, TWRP.
Flashed latest april factory image 7.1.2 using Flashfire which went Great. Rebooted to twrp recovery and flashed pixel mod, great.
Noticed I'm still on bootloader 3.62 and radio 3.72. ? So I guess flashfire doesn't update those.
I'm on Verizon.
Do I need to update to latest bl 3.67 and radio 3.81?
By what method? Fastboot, Flashfire, TWRP
Thanks much
Click to expand...
Click to collapse
Hello,
Reboot to bootloader,
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Done... :good:
Cheers...
Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks
Born<ICs said:
Figured fastboot works but..
Phone seems to function fine so...
Do I actually want/need to flash the latest BL & Radio?
Curious why flashfire skips over these and if it's possible to add these images separately in the flashfire sequence.
Thanks
Click to expand...
Click to collapse
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see infos regarding radio though.
Cheers...
5.1 said:
Hello,
I keep my bootloader up to date. Because it's part of the system, maybe security flaws have been patched... If it was useless, they wouldn't release a new one.
The radio? Well, maybe it will improve your reception or maybe not. It could even be worse. Radio version doesn't matter. If you want, you can flash the new one and if you don't see an improvement, you can flash your current one back. It's up to you...
Check this: https://flashfire.chainfire.eu/settings/#flash_bootloaders
The part about flashing bootloader. Didn't see info's regarding radio though.
Cheers...
Click to expand...
Click to collapse
Oh, OK thanks for the link. Fastboot it is then.
There's actually someone on XDA who created a flashable zip that can be used to update the bootloader and radio through TWRP. Not being great at command lines on the computer I usually use that and have never had a problem.
OK thanks I found the post. Took a chance and downloaded the latest bootloader radio combo zip and flashed via twrp.
All good