Develop Bugs

[Q] D851, BUMP, TWRP, and Stock Lollipop Questions

Hello, I have the T-Mobile LG G3 D851 and I've been trying to find the best configuration. I came from a Nexus 5 that I would either run stock 5.x or CM 12. The CM12 for LG G3 is great but it doesn't have a good camera.
Anyway, I've come to enjoy the stock firmware that LG puts on these phones. So here's what I want to accomplish, however I feel I cannot find enough information to do it confidently.
I would like the have TWRP installed with Stock Lollipop 20b, with root.
Can I just bump a TWRP image and use flashify or something to flash it? or dd?
I installed the 20b KDZ and rooted using the one click method, and that's how my phone sits currently.
From what I understand I need to downgrade to do something with the boot.img so that I can manually flash 20b with a bumped recovery? I'm not sure what bump really is entirely. Do I need to bump all TWRP images that I install? If bump is required for the G3, do they not come pre bumped?
I know that my first go around, I had flashed TWRP with flashify, then installed CM12 without any issues. So I'm wondering if this is just for stock ROMs or did they do something to the boot in 20b that would stop anything from installing without being bump'd?
I also noticed most of the bump'd threads don't list the d851 so I'm wondering if T-Mobile doesn't require this?
Keep in mind I've searched and read extensively and cannot come up with a clear picture of what to do. I've become too used to Nexus devices it seems :-\

Revert to stock KK > root > install TWRP > flash ROM
Find everything here : http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298

Thot Ctrl said:
Revert to stock KK > root > install TWRP > flash ROM
Find everything here : http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
Click to expand...
Click to collapse
Thanks, and finally, do I need to bump the TWRP images from their site? or are they good to go?

troy` said:
Thanks, and finally, do I need to bump the TWRP images from their site? or are they good to go?
Click to expand...
Click to collapse
Autorec for d851 coming soon. See here: forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
@bender_007 is making autorec version for D851 to install twrp and bump boot

troy` said:
Thanks, and finally, do I need to bump the TWRP images from their site? or are they good to go?
Click to expand...
Click to collapse
D851 has unlocked bootloader. You don't need bump. Just flash twrp via trwo manager or get the inage and use flashify.

Swizzle82 said:
D851 has unlocked bootloader. You don't need bump. Just flash twrp via trwo manager or get the inage and use flashify.
Click to expand...
Click to collapse
Great to know! Just used flashify and it worked like a charm

Best upgrade path to lollipop

I'm currently rooted and bumped, twrp 2.8.5.0 and android 4.4.2
I was waiting for xposed to be available before upgrading, and am now thinking about using a newer 5.1 based ROM
What's the best upgrade method ? (Preferably giving me an option to switch back if I need to )
I like the idea of multirom, but I've got the 16gb version so space is at a premium

mjb152 said:
I'm currently rooted and bumped, twrp 2.8.5.0 and android 4.4.2
I was waiting for xposed to be available before upgrading, and am now thinking about using a newer 5.1 based ROM
What's the best upgrade method ? (Preferably giving me an option to switch back if I need to )
I like the idea of multirom, but I've got the 16gb version so space is at a premium
Click to expand...
Click to collapse
Depends on what you want? Do you want AOSP or Stock ROM

Aosp is fine, but what would be the difference between the two v methods ?

mjb152 said:
Aosp is fine, but what would be the difference between the two v methods ?
Click to expand...
Click to collapse
Nothing too significant
AOSP you would install from KitKat and then install most of the lollipop system partitions after if necessary
Stock Rom you would just OTA or Flash Lollipop KDZ and then root

Thanks, I'll look at this today.

easiest way to get to LP is by getting your current firmware from here: http://lg-firmware-rom.com/
then upgrade to that kdz from with lg flash tool 2014, from here: http://forum.xda-developers.com/showthread.php?t=2797190
then root with this tool: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
then, use an appropriate method correlating to your model number. try imageprep.
I'd suggest restoring, not upgrading to LP.
to roll back, you can of course create a nandroid before all this. move it to your ext_sd card before any flashing, too.
as for xposed, it says it's in alpha, but i haven't encountered a single issue with it and i've been running it for a good month+. tweaksbox works like a charm too.
as for multirom, i've never tried it, so can't speak for it.

How Autorec works

Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.

Simone98RC said:
Hi guys,
I've planned to do a CSE flash (means "with data loss") of latest official rom and then switch from the obsolete CloudyG3 to the FulmicsRom.
So I'll need TWRP recovery, but according to my experience it need to be "bumped", otherwise I get a Secure Boot error.
Autorec is considered the best solution, now I want to know:
1) How Autorec works to prevent this?
2) I'll get latest 2.8.7.0 TWRP recovery or the 2.8.6.0 instead?
3) I'll definitely solve bootloader issues, also when in future I'll manually flash "non-bumped" recoveries?
Ps i would appreciate more a better method to obtain the same result (the freedom of use non-bumped recovery).
The only I know is the "oem-unlock", but it's irreversible so I dislike it.
Click to expand...
Click to collapse
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have

RapHaeL_4_4_4_ said:
1) Autorec flash the "bumped" kitkat bootloader.
2) I have the 2.8.7.0, but its up to you really.
3) If you flash a not bumped rom or recovery, you will get a secure boot error. But, everything is bumped because its the only bootloader unlock that we have
Click to expand...
Click to collapse
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?

Simone98RC said:
So Autorec is useless, if I obtain the same result and limitations of a manual bumped recovery flash.
Why make useless bootloader changes if same result without mess up other partitions?
So, if I understand well, Autorec make exactly what I manually do by flashing of a "signed" boot/recovery partition.
I'm wrong?
Click to expand...
Click to collapse
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.

If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone

ypsmav said:
If you are on the cloudy Rom, you already have TWRP installed.
You don't need to go back to stock.
Just boot to recovery: turn off, press vol.down+power, when you see the LG logo release the buttons and press then again units you see the recovery the factory reset. Say yes both questions and then you are in TWRP.
Copy the new ROM on the SD card and flash it.
Brgds
Sent from my phone
Click to expand...
Click to collapse
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
RapHaeL_4_4_4_ said:
Its useless if you are still on kitkat, but if you're on lollipop and you want to install a custom rom or recovery, you don't need to downgrade with tot, loose everything, flash bump, and go on... it make things easier in that case.
In fact,
Bump make believe to the phone that what you try to boot is legit,
While Autorec install the bumped kitkat boot partition if you are on lollipop.
And the bootloader change is not useless if you're on lollipop because bump don't work on lollipop.
Click to expand...
Click to collapse
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Simone98RC said:
So you're saying that FulmicsRom, based on 21A, will works greaceful even under 20H system (bootloader, etc.)?
The CloudyG3 developer suggest to flash latest official rom before its latest custom one.
I think it's true for FulmicsRom too.
Regarding the rom, I never needed to look for bumped releases.
On my device I flashed both Resurrection Remix (CM-based) and CloudyG3 without any problem: as requirements only the root access and a TWRP bumped recovery.
Probably the cited roms are signed by default, so the scenario described by you may happens only in other systems like MIUI or Ubuntu Touch... given that they are unsigned, I'm doing only an example.
I continue to be confused regarding the aim of Autorec.
So, why if I flash a non-bumped recovery I continue to get Secure Boot errors? The bootloader may be modified to prevent this behaviour, but Autorec won't do that.
So what it does?
Click to expand...
Click to collapse
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone

ypsmav said:
Yes, you can flash on top of the cloudy no need to go back to stock.
The only thing you have to do is wipe all partitions except the sd before flashing.
Both ROMs are stock based.
If you decide to flash a KDZ or TOT to go back to stock you will have to root first and then use Autorec.
Brgds
Sent from my phone
Click to expand...
Click to collapse
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
RapHaeL_4_4_4_ said:
If you flash a non-bumped recovery, its normal that you get "Secure Boot Error" because bump is the "unlock". Everything on the g3 must be bumped to boot.
Autorec flash the kitkat bootloader if you are on lollipop (to make bump work) and after it flash a bumped twrp (recovery), that's all.
And if you read through the thread you will understand what autorec does: http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
Click to expand...
Click to collapse
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.

Simone98RC said:
Ok, thanks for the clarification.
I was afraid regarding the compatibility of the actual 20H bootloader with custom 21A rom, CloudyG3 is based on 20H but works under the same bootloader.
But you're telling me it's not existing any kind of problem with that.
So I can flash rom in the easier way (from zip file with TWRP recovery).
So we can say that Autorec is useful only when I work with TWRP on official (obviously rooted) firmware.
But since the cited rom is only "based" on official, I'm not needing to use Autorec, if I directly flash bumped version of TWRP.
Click to expand...
Click to collapse
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.

NatusVincere said:
Listen... Lollipop bootloader DOES NOT accept BUMP.
So what autorec app by Bender does is flash a kitkat bootloader which ACCEPTS BUMP.
Autorec also flashes the bumped TWRP to recovery partition.
So... if you have TWRP you are on kitkat bootloader and you can flash whatever you want that is bumped. All images based on whichever version of ROM 21A, 20H or any of the other ones you find will work on that bootloader.
To finalize, yes you can flash it the easy way with TWRP.
Click to expand...
Click to collapse
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid who won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).

Simone98RC said:
Clearful, thank you so much... even if uppercases may seem offensive (like you talk to a stupid which won't understand)
So if I start from an official 21A firmware, I need to:
1) Root device;
2) Install and execute Autorec;
3) Flash anything from the bumped TWRP (automatically installed by Autorec alongside the KitKat bootloader).
Click to expand...
Click to collapse
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one

bender_007 said:
1. root
2. install autorec for v20t or 20u
3. install rom (you already have bumped recovery because of step 2)
4. yes, you can now upgrade recovery if you find a more recent one
Click to expand...
Click to collapse
Thanks much for the specification: since I want to flash a firmware newer than 20H, I need latest Autorec to work with that [emoji106]
https://www.androidfilehost.com/?fid=24052804347817962
After all you are the official Autorec developer

^ yap, flash safely, after that flash fulmics
That's how I was using it
Plus thx to all people involved in here for answering and helping out
Poslano sa mog LG-H815 koristeći Tapatalk

Bought new LG3. How should I go about rooting? Update first?

So I bought a new G3. It'll be there today, and I don't know if I should update to MM first then root, or just root, twrp and then load a custom ROM.
There isn't any need to update to MM right? Since we're all here doing custom Roms, I can always just flash a rooted stock MM ROM right?

mroneeyedboh said:
So I bought a new G3. It'll be there today, and I don't know if I should update to MM first then root, or just root, twrp and then load a custom ROM.
There isn't any need to update to MM right? Since we're all here doing custom Roms, I can always just flash a rooted stock MM ROM right?
Click to expand...
Click to collapse
Its easiest to root LP and install TWRP then just flash a rom

Which model? Anyways, on my D850, I updated to the latest version (had to keep forwarding date after each update so get the following update, because the AT&T version wants you to wait a day between updates), which I believe was the Lollipop LRX21Y. After that, I used this guide for rooting:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Note that the distribution did not have a "reboot" script, even though it was mentioned in the docs. Create an empty text file called "reboot" without an extension and type one word LEAVE in it, then it should work. Or simply pull the battery out after rooting to exit download mode.
And use this guide for TWRP (make sure you download the correct version of autorec from that page):
http://forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

Sorry, can't believe I forgot the model. Its a vs985 and it was OK 10b. So I used stump and twrp manager. All is well now. Thanks all!

mroneeyedboh said:
Sorry, can't believe I forgot the model. Its a vs985 and it was OK 10b. So I used stump and twrp manager. All is well now. Thanks all!
Click to expand...
Click to collapse
You are perfectly fine to do so on 10(which is kitkat), on lollipop or mm you can´t go down the same routine

How to re-root a LG G Pad 8.3 (V500) already on Marshmallow 6.0.1

I rooted my LG G Pad 8.3 (V500) and I installed the AOSP 6.0.1 (MOB30J). It works fine, but for some reasons (?), I lost the root. Does someone know how to re-root the G Pad 8.3, already on Marshmallow 6.0.1 ? The root guides for Android 4.4 do not work and I do not find a guide for the 6.0 version. Thanks for your help.

Hi, you flash SuperSU 2.52 in recovery to root your Device? If still not have SuperSu after boot, you install it from playstore. It's will OK.

hptnhan said:
Hi, you flash SuperSU 2.52 in recovery to root your Device? If still not have SuperSu after boot, you install it from playstore. It's will OK.
Click to expand...
Click to collapse
Hi. Many thanks for your answer. I have SuperSu, but it tells me that:
1- I have no binary installed
2- if I made an update to Android 5.0 (in my case, it's 6.0), I have to re-root my device manually.

As @hptnhan says, if you flash the latest SuperSU.zip from custom recovery then you should be set.

roirraW "edor" ehT said:
As @hptnhan says, if you flash the latest SuperSU.zip from custom recovery then you should be set.
Click to expand...
Click to collapse
OK. I understand. I'll do it. Thanks for your help.

I have the same problem. Lost root after AOSP 6.0.1
I tried to flash the latest supersu zip 2.76 and got secure booting error and stuck on LG logo. Please help.

Edaily7 said:
I have the same problem. Lost root after AOSP 6.0.1
I tried to flash the latest supersu zip 2.76 and got secure booting error and stuck on LG logo. Please help.
Click to expand...
Click to collapse
Restore to a 100% stock unrooted ROM using a KDZ or TOT made for your variant (V500). Flashing a TOT or flashing a KDZ with the CSE option will wipe everything including internal storage. If you flash the same version of the stock ROM that you were previously successfully running, you could try flashing a KDZ with the Normal option which won't wipe Data. If the tablet won't finish booting after that, try wiping Cache or a Factory Reset which will be the same as flashing the KDZ with the CSE option.

Thanks for your help. I was able to flash the stock rom. I installed ASOP 6.01 again and i lost root again. How do I gain root again on ASOP 6.01? Flashing the supersu.zip doesnt work for me. Is there another way to regain root on ASOP 6.01? Thank you.

I will ask the same question: How do i root my LG G Pad 8.3, running Android 6.0.1?
I've tried SuperSU 2.52, but got stuck on the secure boot error.
Bump bump...

Edaily7 said:
Thanks for your help. I was able to flash the stock rom. I installed ASOP 6.01 again and i lost root again. How do I gain root again on ASOP 6.01? Flashing the supersu.zip doesnt work for me. Is there another way to regain root on ASOP 6.01? Thank you.
Click to expand...
Click to collapse
AOSP or CM 13? I haven't fooled with CM for any device in over a year but last I checked it includes it's own SuperUser app that you could enable. It might've been in the Developer Options section of Settings. You could also optionally try flashing an old version of SuperSU that's not Marshmallow-aware such as v2.46 or 2.5x (I think 2.5x was still not Marshmallow aware). Don't blame me for bricks though.
When I had tried CM 12.1 (for a different device, I don't have what you have) you could opt for flashing SuperSU.zip instead of enabling the built-in SuperUser app. I don't know if that's still an option under CM 13.

Sounds like you fellas are running wrong base ^^ (original firmware that V500 came with?)
Could be wrong as I've been out of the game a while o_0
Try a new base and then root, recovery and custom ROM it.