Installed the 2.7.0.0 version of TWRP using Autorec. Worked flawless on my D802.
Took me a little bit more time to figure out how to upgrade recovery to version 2.7.1.0.
So far I discovered 2 possible approaches and like to share it with you:
1. Following the instructions within the original TWRP thread (http://forum.xda-developers.com/showthread.php?t=2449679).
This requires the TWRP Manager app from the Play Store. Install TWRP Manager, open it and provide root permissions. Then hit Advanced->Install Recovery.
Downside of this approach is that the TWRP Manager app requires you to install Stericson BusyBox. Since I didn't want to mess with an other already installed Busybox version, I looked for another approach
2. Flash new version through TWRP recovery itself. This is probably the most simple/straight approach.
Download zip version of TWRP 2.7.1.0 (e.g. from http://techerrata.com/browse/twrp2/g2d802)
Save it in phone memory. Reboot in recovery and flash zip the usual way.
I did use the second approach, which worked flawless.
Related
So basicly I just want to upgrade my TWRP version (from 2.6.3.2 to 2.6.3.3+) in order to flash new kitkat roms.
But I have 2 issues:
1) I have rooted my device and installed TWRP 2.6.3.2 on my LG stock rom, then I wanted to change rom, so I wiped all but internal storage and flashed Beanstalk 4.4.2 + GAPPS. Now it looks like there's a problem with my root access (root checker says that there is a problem and superSU won't install binary updates). Recovery works fine. Do I need to root my phone again or what? Can I just do these steps: http://forum.xda-developers.com/showthread.php?t=2448887 all over again?
Edit: Ok, After flashing http://download.chainfire.eu/376/SuperSU/, I just needed to deativate supersu and reactivate it. Now it works just fine!
2) I wanted to upgrade my TWRP using FreeGee, but it looks like the app couldn't load without root access (Issue 1). So can I upgrade it with just doing these steps: http://forum.xda-developers.com/showthread.php?t=2449670 all over again?
Sorry for the long questions.
Thanks
Download the zip file for twrp. Boot into recovery and install the zip
Sent from my LG-D800 using Tapatalk
Hello,
sometimes I am reading that some users are installing TWRP via AutoRec.
But sometimes I am also reading that some users install Bump!ed versions of TWRP by simply flashing it directly via Flashify for example.
Are there any advantages/disadvantages comparing those methods?
Or would both give the same results?
What is currently considered the best way to install TWRP on the LG G2 when TWRP has not been installed yet?
Regards
wq0913562 said:
Hello,
sometimes I am reading that some users are installing TWRP via AutoRec.
But sometimes I am also reading that some users install Bump!ed versions of TWRP by simply flashing it directly via Flashify for example.
Are there any advantages/disadvantages comparing those methods?
Or would both give the same results?
What is currently considered the best way to install TWRP on the LG G2 when TWRP has not been installed yet?
Regards
Click to expand...
Click to collapse
It depends on the roms you will be using, if you're going to use a bumped ROM then using the latest stock base and flashing twrp though flashify is the cleanest method, but if the ROM you're using isn't bumped you need the jelly bean bootloader and thus should use autorec. Note that you can install bumped ROMs on the jelly bean bootloader but you CAN NOT install non bumped ROMs on the kitkat bootloader. If you are using a bumped setup and flash a non bumped ROM, it will boot loop. If you don't have a BUMPED ROM still on your storage, you will need to factory reset through download mode or fastboot (whichever you have, some flashable bootstacks purposefully break download mode to enable fastboot. I personally prefer download mode, if I can't get to an adb prompt I'd rather just flash a kdz).
wq0913562 said:
Hello,
sometimes I am reading that some users are installing TWRP via AutoRec.
But sometimes I am also reading that some users install Bump!ed versions of TWRP by simply flashing it directly via Flashify for example.
Are there any advantages/disadvantages comparing those methods?
Or would both give the same results?
What is currently considered the best way to install TWRP on the LG G2 when TWRP has not been installed yet?
Regards
Click to expand...
Click to collapse
Hey wq.
I very recently installed AutoRec on my D802, which has the latest 4.4.2 KK. It works flawlessly, and I recommend it. I believe the .apk installs TWRP 2.7.0.0, which has worked for me very well, and I have installed at least 15 different ROMs with it so far.
Hello,
thank you very much for your fast and detailed answers.
So, let's assume someone uses AutoRec to install TWRP for the first time on a LG G2, which only installs an old version of TWRP (version 2.7.0.0).
Which TWRP version should one then use to update to the latest version of TWRP?
Would you use the blastagator version from over there:
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Or would you use the official version from over there:
http://teamw.in/project/twrp2/197
And how would you install it?
By simply booting into TWRP 2.7.0.0 (provided by AutoRec) and then from there flashing the latest TWRP zip file?
Regards
wq0913562 said:
Hello,
thank you very much for your fast and detailed answers.
So, let's assume someone uses AutoRec to install TWRP for the first time on a LG G2, which only installs an old version of TWRP (version 2.7.0.0).
Which TWRP version should one then use to update to the latest version of TWRP?
Would you use the blastagator version from over there:
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Or would you use the official version from over there:
http://teamw.in/project/twrp2/197
And how would you install it?
By simply booting into TWRP 2.7.0.0 (provided by AutoRec) and then from there flashing the latest TWRP zip file?
Regards
Click to expand...
Click to collapse
I wanted to flash cloudy rom which is bumped.
So i straight away used flashify to flash bumped recovery and then flashed the rom..
No autorec needed.
I flashed blastgator's twrp with thermal control.
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
mundodroid said:
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
Click to expand...
Click to collapse
I aslo had that problem on two occasions.
The first was with the Stock ROM 7.0 and the resolution was simply reboot and wait with an app that needed SuperUser to run. After a while the SuperUser request flashed up. In my case I used Titanium BackUp as the app.
In the second instance I had loaded the Lineage 15 (Android Oreo ROM) and had to install Magisk to get the root. I may have been using the wrong SuperUser though.
Some ROM's, however have a setting that you can change to get the root if you want to.
mundodroid said:
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
Click to expand...
Click to collapse
Why don't you try Magisk instead of SuperSU. I also had a lot of problems with SuperSU like App Quarantine, Titanium backup not detecting root, or taking a long time for SuperSU prompt. I have no problems with Magisk.
Not sure it will help you because in my case, SuperSU did appear in the app drawer.
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?
I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?
jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.
please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager
@cssr any other input or suggestions?
jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(
@cssr should i try another version of magisk?
jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?
What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.
I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.