Can somebody explain how freegee fits into the picture of 'freeing' the LG G2. Is it basicaly an alternative to adb for installing/pushing a custom recovery? How is it any different than Flashify? It seems some use a combination of the two... and recently, its use seems to be the only way of getting custom recoveries on recent OTAs. I just don't get it.
Related
I am rooted and have SU and Busybox installed. Installing recovery seems riskier than on my previous HTC devices with unlocked bootloaders. I am eager to flash but also don't want the angst of trying to resuscitate my G2 or rescue it from a bootloop. I am trying to get a feel for the most risk free recovery install method as it seems like they all have issues. Thanks in advance.
Im interested too.
Sent from my LG-D801 using xda premium
I used Flashify and it was quick and painless but it's probably a good idea to get familiar with the other methods in case you can't boot in Android. Just make sure you select the TWRP image that made for your variant before proceeding.
Im new to lg also. Came over from a galaxy s 3. I used flashify and installed malladus. Too scared to try adb
Sent from my vzw LG G2
ADB method is probably the least risky, also the suggested install method. Too many people have had issues with flashify which is why nobody recommends flashing recovery that way.
Sent from Verizon logo plastered G2 bastard
No best threads allowed, each has its advantages. Try them both and decide for yourself.
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
AlexRamallo said:
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
Click to expand...
Click to collapse
This might help;
http://forum.xda-developers.com/showthread.php?t=2451696
Hello,
I've rooted my phone but I cannot get twrp to work, I tried it through flashify with version 2.7.0 and on reboot it comes up with a security error message then I need to reboot and it'll start as normal
I downloaded ota update yesterday and it rooted fine after the update but refueses to install twrp, I also can't boot into stock recovery at all - I read update from LG has stopped this from working.
I rooted my HTC one m7 before which was a lot more difficult but I can't seem to get a custom recovery going on the LG g2 802 UK version
Edit: I Got into standard recovery for the hard reset using volume up and down, I've just read the new kit Kat update will not allow custom recovery is this correct ? So now I'm rooted thanks to chainfire, I'd still like custom recovery though
Why don't you use AutoRec ?
What's that ? I had cwm on my HTC one m7.
I've followed all the online instructions to install twrp but my phone doesn't like it and it throughs up a small error but luckily didn't harm the phone. It appears that after the update it won't let me install any recovery. I'm worried if I try cwm on the g2 it'll brick it or I'll need to hard reset
Edit : I read up about autorec, so is it a case that the new kit Kat update won't let me install a custom recovery ? If so I'm in no rush and can wait for some clever dev to fix this
After you've installed the rom it is 'safe' to install autorec apk on it , and you'll have custom recovery .
Kuoi said:
After you've installed the rom it is 'safe' to install autorec apk on it , and you'll have custom recovery .
Click to expand...
Click to collapse
+1
Skickat från min LG-D802 via Tapatalk
It wasn't a custom Rom it was the ota uodate, is autorec just like twrp? I tried using twrp and flashify with no success .
To be honest I like the new kit Kat but I like custom recovery, when I rooted it actually booted into what looked like a custom recovery
AutoRec will just install twrp to your device. Read through posts for more informations.
Thanks, I'll read more into it.
Rooting this phone was simple, just annoying the custom recover hasn't been so simple.
Do yous recommend sticking with the new kk Rom or is there something better out
Edit: thanks 007, autorec worked perfectly and surprisingly easy compared my past devices .
Thanks again for taking the time to reply
answering is the purpose of the forum m8 :highfive:
I might try cyanogenMod, I really like this knew knock password thing with the new update though, CyanogenMod seems the most popular so it must be best
Coming from a Nexus 5 I'm curious about LG's flashing/rooting methods.
With a nexus I had the option of easily unlocking the bootloader, installing a custom recovery, and rooting the device. All of this was done thru adb fastboot after installing the proper drivers. I'm reading a lot about LG's flash tool in g2 and g3 forums, Most zip files such as gapps or flashing a newer radio could be installed thru recovery or adb followed by a reboot on my nexus 5.
For those of you that have G2 T-Mobile devices or a G3 of any region is it as easy as a nexus device to root/install/unlock bootloader or is it more complex? I'm considering getting one in the coming weeks.
tarroyo said:
Coming from a Nexus 5 I'm curious about LG's flashing/rooting methods.
With a nexus I had the option of easily unlocking the bootloader, installing a custom recovery, and rooting the device. All of this was done thru adb fastboot after installing the proper drivers. I'm reading a lot about LG's flash tool in g2 and g3 forums, Most zip files such as gapps or flashing a newer radio could be installed thru recovery or adb followed by a reboot on my nexus 5.
For those of you that have G2 T-Mobile devices or a G3 of any region is it as easy as a nexus device to root/install/unlock bootloader or is it more complex? I'm considering getting one in the coming weeks.
Click to expand...
Click to collapse
g2:
root is simple just use ioroot(this roots using adb sideload and stock recovery) if on jb(also works on kk but not for t-mo g2) or towelroot(only way to root t-mo g2 on kk)
for recovery on kk we use autorec app while on jb we use adb
we don't have a way to fully unlock bootloader but we have loki patch so we can flash roms and kernels
flash gapps is only necessary when using aosp roms and basebands(radio/modem whatever you want to call it) can be flashed from recovery
g3:
root is simple with ioroot(this roots using adb sideload and stock recovery)
no way for custom recovery yet a few obstacles have to be overcome first(two boot partitions/locked bootloader/etc)
like mentioned above locked bootloader which means no custom kernels for now
no aosp roms and no recovery for flashing baseband
I do know with g3 there are custom roms like 2 or 3 and they use stock recovery to flash and other complicated stuff(have not looked into it)
I don't think it is as simple as doing stuff with nexus but I have never worked with one before so I can't compare
I got my spare G2 today and have run into a bit of a problem with rooting it. The root process seems to have gone fine. It says I am rooted and I can use Root Explorer to remove bloat and such, but something seems to have gone wrong with the recovery. If I try to boot into recovery, I get an error message that says something about Secure booting error. It has some other info, but the screen goes black so quickly that I can't make out what it is saying. If I hold the power button down, I can reboot the phone as normal so it's not bricked, but without a recovery I can't do any custom Roms. I've tried various methods to flash a new recovery and they all said they were successful, but I still can't get into recovery mode.
Does anyone know what I did wrong or how to get around this? The phone came with firmware 4.4.2 26a if that means anything to your advice.
Thanks a million for any help.
Looks like your recovery gone. Flash stock Lollipop Kdz then root and install TWRP with Autorec from Google Play.
Thank you. Just did the TOT method to flash back to stock 26a so thankfully all is back to normal. Now i'm afraid to try it again because I don't know what went wrong. The ioroot version I have is an older version for 24a or backwards. That's the one I used for my original G2. So I tried using a different method (one click) for this phone and it was a mistake. Could I use the flash tool to kdz back to 24a and then root using the method I know or do I have to stick to 26a for hardware reasons?