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
Would it be possible to list all OTA updates which are installable through TWRP? I am trying to find a way to update my P2 with TWRP to S244, and I find tutorials and ZIPs scattered around on the forum (except the one for S244), but it makes it a bit of a hassle when one buys this phone on MM, installs TWRP and finds out the OTA updates are not working (which makes sense).
I am on S233 now, but I can imagine I am not the only one using TWRP and looking for info whilst being even on an older firmware. I know it would be possible to reflash the stock recovery, but even these files are hard to find non-deodexed, non-TWRP.
same here
JayVerhofstadt said:
Would it be possible to list all OTA updates which are installable through TWRP? I am trying to find a way to update my P2 with TWRP to S244, and I find tutorials and ZIPs scattered around on the forum (except the one for S244), but it makes it a bit of a hassle when one buys this phone on MM, installs TWRP and finds out the OTA updates are not working (which makes sense).
I am on S233 now, but I can imagine I am not the only one using TWRP and looking for info whilst being even on an older firmware. I know it would be possible to reflash the stock recovery, but even these files are hard to find non-deodexed, non-TWRP.
Click to expand...
Click to collapse
same here bro. my phone is showing 125 mb update available which S244. i tired many times but it failed. im looking for this OTA update file which can be flash via TWRP.
please bro help me i dont want to flash whole stock rom. full updated ROM is available here.
https://forum.xda-developers.com/lenovo-p2/development/lenovo-p2-lenovo-p2a42-stock-nougat-t3661024.
please help me to find out only 125 mb TWRP update
Has anyone with systemless root, preferably Magisk, dared to try Flashfire? I looked in the official xda thread and there seem to be mixed experiences. Some get a black screen from which the phone doesn't wake up unless you use a hard reset. Others solved the black screen by booting into TWRP and flashing the Magisk uninstaller. Then doing a clean install before using Flashfire.
I guess the queue would look something like this:
1. Wipe cache
2. Flash OTA
3. EverRoot disabled
4 Flash Magisk
5. Normal reboot and preserve TWRP.
If unsuccessful
1. Flash stock boot.img
2. Flash OTA
3. EverRoot disabled
4 Flash Magisk
5. Normal reboot and preserve TWRP.
Hello everyone,
I have purchased my OnePlus 5T, and I absolutely love it! I was just wondering whether I could root while retaining the stock ROM and recovery and still get the OTA updates in the usual way? I don't mind staying with OxygenOS and stock recovery I would just really like root access while keeping updates!
Would appreciate a quick answer,
Thankyou in advance,
Nathan.
I would unlock the bootloader and backup the default recovery. Then flash twrp and boot in to it and flash Magisk for root. Then flash the default recovery back.
Why? If you root your phone, then incremental OTA updates will more than likely get broken. That means, once you root, you will just need to apply the full update for each OTA. If you have TWRP installed, then you just download the fill update.zip file, and flash the update.zip and root.zip packages and be on your way.
when an update comes out just dirty flash the full zip once released, i thought u could still install OTA even with TWRP, u just can't with root and a modified system, can't u just uninstall magisk, then do the update then reinstall magisk?
Exactly. As soon as you modify the system (whole point of root), incremental OTAs will not work. Just dirty flash the full OTA via TWRP and profit.
This question has been asked before. You can read through all the answers here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
I would like to get to the point where I'm able to OTAs instead of manually flashing factory images but I'm not passing safety net when I uninstall magisk and reinstall it when the update reaches step 2. I'm not sure what is causing the update to fail. I recently switched from system root via supersu (obviously wouldn't pass safety net) to systemless root with magisk. I'm running 8.1 feb. security update with the following apps installed: adaway, busybox, CF. Lumen, greenify, magisk manager, & titanium backup. (rootless substratum & andromeda as well).
I do not have TWRP installed, I only boot to it to flash magisk and kept TWRP systemless. The purpose for this post I guess is to try understand which of the installed apps listed may affect the /system files. I was under the impression that since i now root systemlessly I would be able to accept OTAs. What am I missing here?
As far as I know you cannot be rooted and/or have a custom recovery. You can have a unlocked bootloader but you have to be stock in order to receive OTAs.
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
......... you can flash full OTAs from TWRP?? I knew I was missing something.
So download the full OTA to internal storage. flash in TWRP. then magisk and if i choose not to install TWRP (i usually only boot to it), I'm done?
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
Wait, doesn't flashing the full OTA get rid of TWRP?
Do you have instructions how to install full images without TWRP being uninstalled?
Also... How do you get ota to install if the original bootloader is replaced by twrp? I thought installing twrp permanently voids the possibility to install ota...!
Can anyone provide a TWRP file for this tablet
We all gonna appreciate it
有人有twrp吗？我找了好久都没找到能正常使用的
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
PhotonIce said:
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
Click to expand...
Click to collapse
For example if you want to test a few Magisk modules and run into a boot loop ...
PhotonIce said:
why would you want twrp when there are no roms?
you could try flashing a gsi, or rooting the tab though..
gsi guide: https://forum.xda-developers.com/t/run-an-gsi-on-your-mi-pad-5.4352591/
root guide: https://forum.xda-developers.com/t/...p-by-step-pass-safetynet-widevine-l1.4412555/
apparently all GSIs have bugs with this device though, so maybe go for root.
Click to expand...
Click to collapse
Since when was TWRP specific to flashing ROM only? People use TWRP to perform nandroid backup or for flashing zip files for Magisk modules or whatever. Flashing ROM is just one of the things you can do.
And why would you stick with stock recovery anyway? Having custom recovery like TWRP or FOX is always a good thing, regardless of custom ROM availability or not. People should learn about the fundamentals of a recovery.
chaoscreater said:
Since when was TWRP specific to flashing ROM only? People use TWRP to perform nandroid backup or for flashing zip files for Magisk modules or whatever. Flashing ROM is just one of the things you can do.
And why would you stick with stock recovery anyway? Having custom recovery like TWRP or FOX is always a good thing, regardless of custom ROM availability or not. People should learn about the fundamentals of a recovery.
Click to expand...
Click to collapse
Sorry mate but I am aware of magisk modules and all, that's why I linked a root guide...
Also, on xiaomi devices unlocking the bootloader is a long and tedious process, and the Mi Pad 5 was relatively new when I made my reply, so I didn't want to:
(a) void someone's warranty
(b) encourage them to flash unofficial, untested TWRP (most likely bugged anyways)
(c) brick their device by flashing beta TWRP
Of course, I understand that custom recoveries have many advantages over stock, but at the time of writing my reply, there were no official custom recoveries for this device, and there were only a couple of beta/untested builds.
Cheers!
PS: No one would make a nandroid backup if they weren't going to make modifications to their device (adb/root/magisk), so really, all uses of custom roms stem off of device modifications, which are granted through root access.
EDIT: Sorry I just checked, there were no TWRP builds available at the time of my reply, hence why I provided none and also asked that sarcastic question. At the time, you had to manually patch the boot.img via adb.