I have the Verizon version of the LG G2 and when I received the device, it was already loaded with 12B firmware. I was able to root the device with ioroot16, install SuperSU, all that jazz... I'm under the impression that I need to use loki flash to flash TWRP onto my device, but when I try to do this through ADB, I get an error saying that my device has a Read-only filesystem. Is there some step that I'm missing in this process? Is loki flash the only way to get TWRP onto my device? or is there some other way?
You can use freegee from the playstore to install a supported recovery easily.
http://forum.xda-developers.com/showthread.php?p=48969786
Shelnutt2 said:
You can use freegee from the playstore to install a supported recovery easily.
Click to expand...
Click to collapse
Thanks! Worked flawlessly :good:
Same here worked perfectly
Related
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.
Could use some help/advice.
I restored the kdz using the lg flashtool to jellybean. I didn't update directly kitkat. Instead, I used towelroot to root, then I used autorec to install twrp 2.7.0.0 (or whatever it was). I then flashed twrp 2.8.5.1 and I flashed CM12. CM12 doesn't boot at all.--stuck at LG logo. If I try to use download mode to reflash kdz, it doesn't detect the phone. I can access phone in TWRP via ADB. and it detects it. Is there a way to restore the download mode to detect the phone.? I think this mess happened b/c I didn't update to kitkat and the partitions didn't get updated, but I'm not sure.
Any advice to either get download mode working again from within TWRP, or get CM12 working would be appreciated.
Thank You
zipeee2 said:
Could use some help/advice.
I restored the kdz using the lg flashtool to jellybean. I didn't update directly kitkat. Instead, I used towelroot to root, then I used autorec to install twrp 2.7.0.0 (or whatever it was). I then flashed twrp 2.8.5.1 and I flashed CM12. CM12 doesn't boot at all.--stuck at LG logo. If I try to use download mode to reflash kdz, it doesn't detect the phone. I can access phone in TWRP via ADB. and it detects it. Is there a way to restore the download mode to detect the phone.? I think this mess happened b/c I didn't update to kitkat and the partitions didn't get updated, but I'm not sure.
Any advice to either get download mode working again from within TWRP, or get CM12 working would be appreciated.
Thank You
Click to expand...
Click to collapse
You need to install the kk bootstack for your device and wipe data.
Sent from my LG-VS980 using XDA Free mobile app
How to Root a G2 which has TWRP installed?
Hi there!
I'm a beginner and I would be grateful if you could help me with this.
While trying to install CyanogenMod, I rooted my G2 using ioroot and then install Autorec. At this point I made a mistake and recover KitKat stock with Autorec, loosing root privileges. Now when I try to root using ioroot, the device shows me the TWRP menu.
I am stuck here. How could I root and install CyanogenMod????
Thanks a lot!!! Please let me know if this is not the right place for asking this in the forum.
Hi,
I think you can download flashable SuperSu and flash it via TWRP.
http://forum.xda-developers.com/showthread.php?t=1538053
TwinHeadedEagle said:
Hi,
I think you can download flashable SuperSu and flash it via TWRP.
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hi @TwinHeadedEagle, thanks a lot for your reply. I installed SuperSu through GooglePlay, after being installed it requested to make some modifications through TWRP, which it successfully did. At this point I was wondering wether I actually had root access or not to my device, so I decided to install Root Checker. This last one says that 'Root access is properly installed on this device'.
So I guess that I am root and I can with 'Installing CyanogenMod from recovery' as it is showed at https://wiki.cyanogenmod.org/w/Install_CM_for_d802.
Am I right?
Root is not required to install CM, only a custom recovery.
I have a d802. It was running stock Lollipop with no root. I installed a custom recovery (TWRP) and was able to flash CM12.1, Cloudy, and Orion.
audit13 said:
Root is not required to install CM, only a custom recovery.
I have a d802. It was running stock Lollipop with no root. I installed a custom recovery (TWRP) and was able to flash CM12.1, Cloudy, and Orion.
Click to expand...
Click to collapse
Hi @audit13!
Thanks! I have installed CM! :laugh::laugh::laugh:
BW
Congratulations! Right now, I am using Inazuma on a d802 and it's great.
audit13 said:
Congratulations! Right now, I am using Inazuma on a d802 and it's great.
Click to expand...
Click to collapse
Thanks @audit13! At first I was exceptional about using customs roms, but It certainly has given new life into my D802. I find very sad that companies do not work for keeping our devices updated, It is a way of planned obsolescence. My D802 has more than enough hardware for what I use it and now that I have managed to update it (without the help of LG) it is like having a brand new phone!
Thanks to all the xda-developers community!
KR
I was trying to root my v20 and its not working correctly and would like to start from scratch. i seen some stock tmobile v20 tots. It says something that you cant flash them. Is that correct? no way to return to stock? using the tots
Right now there is no way to flash a tot. We are missing the V20 specific dll file for the flash tool called LGUP.
Do you know anyway to remove all the root files, exploit stuff so I can restart the process
What part did you get stuck on?
Somehow during the last part where recovery is installed. Then the no encryption and installing supersu. I got twrp installed. But I flash both the no encryption and special su and root does not take. It says along the lines using to installer too can't reinstall the exploit or something like that
Idk if this helps but I thought the same thing until I installed nova. For some reason the LG launcher did not show supersu
Hope it helps
Have you tried running the commands manually in ADB?
No I haven't yet. Would restoring the LG recovery help?
I tried manual adb command it just says waiting for device
Although TWRP is *supposed* to be lokied, it turns out that all the 3.x versions are not properly lokied. This has been reported in the last couple of pages of this thread, and it's been reported in their bug tracker (although they seem to be ignoring it for now).
One of the users in that xda thread was kind enough to loki a few TWRP releases, but the latest one he did was v3.1.1.0, and he hasn't done any more since.
Can someone else be kind enough to Loki the latest version of TWRP for jflteatt, located here? (Preferably both IMG and TAR, so people can use it with whichever installation method they prefer/need)
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you. However, the method described requires root.
I had root on CyanogenMod 11, but ever since I flashed LineageOS 14.1, I haven't been able to root my phone without bricking it - so this method won't work for me.
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, safe root, CF auto root, or kingo root to root it. If all else fails you might have to ODIN back to stock, then root, then install the latest TWRP then Loki it using my guide then install lineage OS.
StoneyJSG said:
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, or kingo root to root it.
Click to expand...
Click to collapse
No, my phone is definitely not rooted. It *previously* had root under CyanogenMod 11. That's how I had a custom recovery installed. So I was able to use TWRP to flash LineageOS 14.1 just fine. However, here are the results of my trying to root this phone under LOS 14.1:
1. Magisk: Bricked on Samsung Logo.
2. SuperSU (normal systemless): Not installed properly. Seems to fail on patching the boot image.
3. SuperSU (system mode): Bricked on Lineage boot screen.
4. LineageOS addonsu: Installs fine, but doesn't seem to do anything. I still don't have root.
I've tried posting about this in a few places on xda, but so far, I haven't had any luck.
So *maybe* if I revert back to an older version of Android, I might be able to get a working root. But in order to be recent, it's looking like I have little choice but to finally retire this phone and get something newer. Which is unfortunate, because there's nothing wrong with the phone hardware-wise.
Perhaps I'll try one of the other root options you mentioned and hope it doesn't brick my phone as well.
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
StoneyJSG said:
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
Click to expand...
Click to collapse
I have a Lokied version of TWRP (3.1.1.0), which is working fine. But with all of the problems I've been having trying to get root, I was wondering if perhaps a newer version of TWRP might make the difference. That's why I was trying to get a Lokied version of the latest TWRP.
Ah so you're trying to gain root by flashing TWRP. No idea why lineage OS removed root, unless the people who made it built it that way. The only thing I can think of is either try all the root apps I mentioned before and if that doesn't work then ODIN back to MDL stock and use towel root to root. If lineage OS is anything like Oct OS, you will have to root using a root .zip file.
I wish I could be more help, but I haven't ever used lineage OS before due to liking touchwiz. I run golden eye ROM on my at&t Loki phone.
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
jabulon said:
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
Thanks for trying it! It's now confirmed my guide is only for CWM recovery.
Not sure if you've already searched it out, but HERE is my thread with the latest Loki patched twrp. I lokied jfltexx 3.2.3-0 which works on the i337 (ATT) s4.
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
StoneyJSG said:
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
Click to expand...
Click to collapse
Your link IS my link from the post directly above yours
Oh crap haha so it is. Oops brain fart there, my fault.
StoneyJSG said:
Oh crap haha so it is. Oops brain fart there, my fault.
Click to expand...
Click to collapse
You're good ? I had it in a separate post, and I just created that thread the other day to give it a permanent home more easily found.