Related
Hi,
I have 4.2 on my LG G2 D802 and KitKat was just launched in my country. My phone is rooted and I got TWRP.
Can I download and install the KDZ-file (KitKat) without removing TWRP?
Do I have to remove any mods I have done to the system? Like G2 Xposed etc?
Please respond, before I do the update (don't want to brick it).
Thank you!
joq3 said:
Hi,
I have 4.2 on my LG G2 D802 and KitKat was just launched in my country. My phone is rooted and I got TWRP.
Can I download and install the KDZ-file (KitKat) without removing TWRP?
Do I have to remove any mods I have done to the system? Like G2 Xposed etc?
Please respond, before I do the update (don't want to brick it).
Thank you!
Click to expand...
Click to collapse
Do not make OTA update with TWRP on you phone ! you will be stuck at recovery !
You cannot flash a kdz without lossing root and twrp !
Flash this ROM and follow the thread so you get kitkat with root and you keep your custom reovery : http://forum.xda-developers.com/showthread.php?t=2661866
ahmed534 said:
Do not make OTA update with TWRP on you phone ! you will be stuck at recovery !
You cannot flash a kdz without lossing root and twrp !
Flash this ROM and follow the thread so you get kitkat with root and you keep your custom reovery : http://forum.xda-developers.com/showthread.php?t=2661866
Click to expand...
Click to collapse
I know not to make an OTA update.
And I don't care about loosing root and twrp. I'm wondering if it will work fine to install the KDZ-file and it will work like a original-phone. Or if I do have to remove TWRP and mods first?
Thank you!
joq3 said:
I know not to make an OTA update.
And I don't care about loosing root and twrp. I'm wondering if it will work fine to install the KDZ-file and it will work like a original-phone. Or if I do have to remove TWRP and mods first?
Thank you!
Click to expand...
Click to collapse
you can flash official KDZ no matter u have twrp or not ! but be aware that your bootloader will be updated and you will never get custom recovery again (till now)
I have searched a bit and from what I have found the phone will not be restored after a KDZ-flash? I want my phone completely wiped and restored to stock when I install KiKat. Can I restore my phone in settings before I install the KDZ-file?
Will this somehow be a problem when I have a rooted phone and TWRP?
Please help me restore my phone to stock and update to KitKat, I want it to be completely stock and with nothing left in it.
Thank you!
Back to stock: http://forum.xda-developers.com/showthread.php?t=2432476
Ota Problems!
Hi all my g2 stuck at recovery! Any1 help plz!
I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?
I think I have the same problem. Could u solve the problem?
N12X93R said:
I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?
Click to expand...
Click to collapse
no you can't get recovery on kk because they patched our recovery/loki exploit on kk bootloader
not able to boot in recovery on Lg g2 802.. with stock 4.4. 2
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.
Purav786 said:
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.
Click to expand...
Click to collapse
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok
Drachenminister said:
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok
Click to expand...
Click to collapse
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?
Purav786 said:
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?
Click to expand...
Click to collapse
There is a sticky thread in the general section of the forum
Drachenminister said:
There is a sticky thread in the general section of the forum
Click to expand...
Click to collapse
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?
Purav786 said:
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?
Click to expand...
Click to collapse
No, no easy one, and some might even say none at all, but you can read the rooting thread where they discuss recovery as well http://forum.xda-developers.com/showthread.php?t=2448887
Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked
Alright, currently im on cloudyg3. My twrp version is 2.7 i believe (the same one that comes with autorec). Can someone elaborate the instructions,
First, flash latest twrp via recovery. By this i just install it as i was installing a rom? Then reboot.
Back in recovery, now wipe sys/data/cache, then flash the lp bootloader, then finally flash the rom. Are these instructions correct?
Also if I want to revert back to my cloudyg3 backup do i need to change my bootloader again? If so which.
rasdabess said:
Alright, currently im on cloudyg3. My twrp version is 2.7 i believe (the same one that comes with autorec). Can someone elaborate the instructions,
First, flash latest twrp via recovery. By this i just install it as i was installing a rom? Then reboot.
Back in recovery, now wipe sys/data/cache, then flash the lp bootloader, then finally flash the rom. Are these instructions correct?
Also if I want to revert back to my cloudyg3 backup do i need to change my bootloader again? If so which.
Click to expand...
Click to collapse
Yes you flash a new twrp zip like a rom zip.
No, you flash the bootstack, not the bootloader. LP bootloader has no exploit available.
No idea, what bootloader did you have before? What exploit does the ROM require? If it's bump you need a kitkat bootloader, provided in the LP bootstack. If it's loki get a JB bootloader.
Choristav said:
Yes you flash a new twrp zip like a rom zip.
No, you flash the bootstack, not the bootloader. LP bootloader has no exploit available.
No idea, what bootloader did you have before? What exploit does the ROM require? If it's bump you need a kitkat bootloader, provided in the LP bootstack. If it's loki get a JB bootloader.
Click to expand...
Click to collapse
Ah, alright yea I meant bootstack. And, im not sure about what bootloader I had before, Im reading everything from my phone since i domr have a computer so finding info isnt that easy. I rooted my phone a while back, installed twrp via autorec and installed the cloudyg3 rom and havent done anything else for 8 months now. Would reverting to my backup return me to the bootstack i had before? Or would cloudyg3 still boot up on the lp bootstack.
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465
taywin13 said:
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465
Click to expand...
Click to collapse
I forgot to mention im on d802, though i guess id follow the same steps minus the last one. However ive read someone saying first you flash the bootstack before the rom, or does it not matter in what order?
rasdabess said:
I forgot to mention im on d802, though i guess id follow the same steps minus the last one. However ive read someone saying first you flash the bootstack before the rom, or does it not matter in what order?
Click to expand...
Click to collapse
You should flash the bootstack and reboot the recovery . Why? because it's got the KK bootloader and the necessary partitions for a smooth install
Choristav said:
You should flash the bootstack and reboot the recovery . Why? because it's got the KK bootloader and the necessary partitions for a smooth install
Click to expand...
Click to collapse
Alright, so wipe first and flash bootstack and reboot to recovery or flash bootstack then reboot then wipe then install the rom?
rasdabess said:
Alright, so wipe first and flash bootstack and reboot to recovery or flash bootstack then reboot then wipe then install the rom?
Click to expand...
Click to collapse
Doesn't make a difference so long you don't touch the internal storage.
Choristav said:
Doesn't make a difference so long you don't touch the internal storage.
Click to expand...
Click to collapse
Okay great. Btw would i be able to restore my backup or not? The backup being cloudyg3. Or would I have to change the bootstack again? Or you dont know?
rasdabess said:
Okay great. Btw would i be able to restore my backup or not? The backup being cloudyg3. Or would I have to change the bootstack again? Or you dont know?
Click to expand...
Click to collapse
I don't use stock so I could be wrong, but I'd say you will need an older bootloader. I can't find the thread for it, is it gone?
Choristav said:
I don't use stock so I could be wrong, but I'd say you will need an older bootloader. I can't find the thread for it, is it gone?
Click to expand...
Click to collapse
Ah it seems he renamed it. Its cloudyg2 2.2 although i have the 2.0 version. Its 4.4.2 kk
rasdabess said:
Ah it seems he renamed it. Its cloudyg2 2.2 although i have the 2.0 version. Its 4.4.2 kk
Click to expand...
Click to collapse
Well from a logical standpoint you'd need a jellybean bootloader to roll back t your backup since back then no one used the bump script in conjunction with the kitkat bootloader, and the autorec on kitkat installed a Jb bootloader.
what's your model by the way?
Choristav said:
Well from a logical standpoint you'd need a jellybean bootloader to roll back t your backup since back then no one used the bump script in conjunction with the kitkat bootloader, and the autorec on kitkat installed a Jb bootloader.
what's your model by the way?
Click to expand...
Click to collapse
D802. Im downloading the bootstack aroma changer zip just to be sure. Btw would this current rom be able to load up on the latest version of twrp?
A guy on reddit said the backup contains everything and id be able to go back to the backup but if i wanted to flash a kk rom id have to change the bootloader.
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?