Develop Bugs

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

How to root MM?

Hi! I have H815 EUR V20d, how can i root it? I can`t find anything specific

you can only do root with unlocked bootloader !!

Currently only if you unlock the bootloader, and flashing SuperSU with TWRP.

davebugyi said:
Currently only if you unlock the bootloader, and flashing SuperSU with TWRP.
Click to expand...
Click to collapse
Thanks, but i don`t have TWRP, do i have to downgrade to install it?

No, you must install TWRP in den Fastboot Mode.
https://twrp.me/devices/lgg4h815.html
Download the latest (SuperSU 2.67)
http://forum.xda-developers.com/showpost.php?p=64161125

Thanks guys, i now have root access!:good: Followed your advice and this guide: http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241

xxx

LG G4 Best root method?

Looking for the best available root for the lg g4 marshmallow international version, even a 1 click method

If you searched you'll realise there's no root for locked bootloader G4s on MM.

lambstone said:
If you searched you'll realise there's no root for locked bootloader G4s on MM.
Click to expand...
Click to collapse
He said international dude... The H815 which has unlocked boot loader. Very useful reply. But I too need to know the best method.

LightInDark said:
He said international dude... The H815 which has unlocked boot loader. Very useful reply. But I too need to know the best method.
Click to expand...
Click to collapse
Wait will the international version work in the US on ATT?

LightInDark said:
He said international dude... The H815 which has unlocked boot loader. Very useful reply. But I too need to know the best method.
Click to expand...
Click to collapse
What? H815SEA and H815EU are both international variants but only H815EU can be unlocked.

The best method is to flash boot.img unpacked from the custom kernel like SimpleGX via fastboot that will allow you to further flash TWRP in which you'll flash full kernel package to avoid software problems and lastly SuperSU

the method i followed was-
1. boot into twrp recovery with adb command(you need to have the twrp.img file in PC and also copy it in internal memory of your phone with SU)
2. flash systemless root with twrp
3. reboot
4. install flashify
5.flash twrp.img from your phone.
6. done
but there aren't as much benefits of rooting as any other phone. viper4android doesn't work. spirit fm doesn't work. xposed doesn't work properly.(these 3 were the main reasons for which i rooted)

Best way to root,unlock BL and install custom recovery

I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one

bolcna said:
I have Xperia z1 compact running stock non-rooted 14.6.A.1.236 rom. My bootloader is locked. I want to be able to install custom roms. What's the best way to root, unlock bl and install custom recovery? I've been searching forum for past few days but most of the download links redirect to d-h.st. and that breaks the chain of needed files.
Also i never used flashtool and i don't know should i use Sony flashtool or "original" one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6

levone1 said:
https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6
Click to expand...
Click to collapse
Do i have to be rooted to backup TA partition

bolcna said:
Do i have to be rooted to backup TA partition
Click to expand...
Click to collapse
I don't think so. Just need adb...

I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
You don't have to downgrade to flash NUT. It's been a while since I did it, but I'm pretty sure that flashing supersu won't totally remove Kingroot. Best thing to do once you're rooted, if you don't want to unlock bl, is probably to install recovery, then in recovery flash a prf, which will wipe your system and install new system with supersu instead of Kingroot.

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps

Raiyr said:
I guess I don't have to open a new thread for this: I've been reading a lot about this recently and trying to get my thoughts straight about this:
I found PhilZ Dual Recovery (https://forum.xda-developers.com/showthread.php?t=2647480) which works with locked bootloader. Some people wrote there they installed the recovery on 5.0.2, so it seems I have to downgrade first (I'm on 5.1.1), even though it doesn't say that in the manual..? - if you can't answer that I'll ask that later then in the linked thread.
Next thing: I rooted with Kingroot, but want to switch to SuperSU - cant switch because theres a problem with the binary, so I have to flash it anyway through custom recovery.
Can I now root with Kingroot, install PhilZ Dualrecovery and when it boots into Recovery Mode, can I just flash the SuperSu.zip?
OR would I need to boot normally first after custom recovery install, then uninstall Kingroot, to unroot, and THEN flash SuperSU in Recovery?
Ive been using root for years but never really got into flashing before so I'm quite new to that and appreciate your help. Thanks a bunch.
Click to expand...
Click to collapse
bolcna said:
I don't trust any universal rooting apps. Only way to legit root your phone is to downgrade to kitkat and then root using exploit, then flash prerooted lollipop (that is if you wan't to stay on stock rooted rom). If you don't plan on staying on stock room and only want quick root you have to use kingroot since that's only universal root that can root z1c. When it comes to recovery there you have two choices. To use xzdualrecovery or to unlock bootloader (you will loose drm keys which means you will lose stuff like x-reality) and flash normal recovery. I would go for dual recovery because if you ever wan't to get back to stock you can since stock recovery isn't getting overwritten with xzdr. But if you choose to unlock bootloader first backup TA (you have to be rooted) and then unlock.
Hope this helps
Click to expand...
Click to collapse
I would go with unlock bl method. You can restore TA after rooting so you done lose drm, and it's easy to root with unlocked bl - https://forum.xda-developers.com/showpost.php?p=72547776&postcount=6

Stock VS9862BA flashable zip

Hello!
I'm making a zip which contains stock 2ba software untouched, extracted from the original kdz
Includes:
Stock untouched System
Stock Boot (compatible with Magisk)
Stock MM modem
Install instructions:
- Reboot to TWRP
- Wipe data, cache, system
- Install zip
- Reboot
- Enjoy!
Link:
https://drive.google.com/open?id=1GaPfb_WNUW_4-kd_jk_80OWosbjdCLAv
Link updated! Feel free to upload some mirrors if you want
P.D: Sorry for my bad english

Hello. Thank you very much for the file. Installed everything works. At first I could not understand why there was no root, but then installed Magisk and everything turned out.

I am on a completely stock OTA upgrade version of 2BA, I have NO root, my boot loader is still locked,<as I have still not got around to flashing the UsU method, There for I currently do NOT have a custom recovery installed; such as TWRP; which is listed as a requirement(?) in the first step of following process (to flash a rooted Rom.)
I am curious as to how I will be able to complete these steps, or am I missing something? Is this,supposed a way to gain root on 2BA if you are on a non root version like me, or is this suppose to be a update of your on a previous version which you already have rooted, or is this just a different way to root AFTER you have had the UsU boot loader unlocked?

robles4242 said:
I am on a completely stock OTA upgrade version of 2BA, I have NO root, my boot loader is still locked,<as I have still not got around to flashing the UsU method, There for I currently do NOT have a custom recovery installed; such as TWRP; which is listed as a requirement(?) in the first step of following process (to flash a rooted Rom.)
I am curious as to how I will be able to complete these steps, or am I missing something? Is this,supposed a way to gain root on 2BA if you are on a non root version like me, or is this suppose to be a update of your on a previous version which you already have rooted, or is this just a different way to root AFTER you have had the UsU bootloader unlocked?
Click to expand...
Click to collapse
the only way to root your phone on 2BA is with UsU.
so after you do UsU you can flash TWRP and from there you can flash magisk for root. you don't have to flash this rom for root
here's a side note. when you do the UsU unlock do not flash the baseband package. it gave me problems with my SIM not being detected

ANDROID2468 said:
the only way to root your phone on 2BA is with UsU.
so after you do UsU you can flash TWRP and from there you can flash magisk for root. you don't have to flash this rom for root
here's a side note. when you do the UsU unlock do not flash the baseband package. it gave me problems with my SIM not being detected
Click to expand...
Click to collapse
I tested downgrading from Lineage 15.1 and this ROM Works and TWRP works too! Thanks!