[Q] Trying to Flash CWM Recovery - G2 Q&A, Help & Troubleshooting

As far as I know and what i have research, the only rom recovery that can be flash to my LG G2 is TWRP and would have to use Loki to bypass the bootloader. Please correct me if I'm wrong in the information. I have the ATT version, software version is D80010o, and on 4.2.2 Android Version Stock Rom of cause.
Questions:
- Does the G2 have to have an unlocked bootloader to flash anything even if it is rooted?
- Is TWRP the only recovery that can be flashed to the G2? If so what is the "manger" for it similar to Rom manager with CWM.
- Is there any other way to backup your current rom without using any recovery, this is my main goal for the moment?
Note: I have check if it is compatible with CWM base on the website yet when i flash CWM with Rom Manager( not the touch support version) and try to reboot the Red Triangle pops up. I have tried with Flashify and download the recovery img to the sd and it comes up with secure booting error ( I'm not sure if this is because i flashed both CWM and CWM with touch at the same time with Flashify wasn't sure if i needed to flash both for touch to work or just CWM Touch)
Please inform me with the correct produces to follow or link me to a solution. Side note this is my first time with an Android device and my first Smartphone so I'm kinda new to this rooting roms, kernal, thing. Thank you in advance to anyone that can help. Feel free to message me through XDA. Thanks.

Kj97 said:
As far as I know and what i have research, the only rom recovery that can be flash to my LG G2 is TWRP and would have to use Loki to bypass the bootloader. Please correct me if I'm wrong in the information. I have the ATT version, software version is D80010o, and on 4.2.2 Android Version Stock Rom of cause.
Questions:
- Does the G2 have to have an unlocked bootloader to flash anything even if it is rooted?
- Is TWRP the only recovery that can be flashed to the G2? If so what is the "manger" for it similar to Rom manager with CWM.
- Is there any other way to backup your current rom without using any recovery, this is my main goal for the moment?
Note: I have check if it is compatible with CWM base on the website yet when i flash CWM with Rom Manager( not the touch support version) and try to reboot the Red Triangle pops up. I have tried with Flashify and download the recovery img to the sd and it comes up with secure booting error ( I'm not sure if this is because i flashed both CWM and CWM with touch at the same time with Flashify wasn't sure if i needed to flash both for touch to work or just CWM Touch)
Please inform me with the correct produces to follow or link me to a solution. Side note this is my first time with an Android device and my first Smartphone so I'm kinda new to this rooting roms, kernal, thing. Thank you in advance to anyone that can help. Feel free to message me through XDA. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2589950
loki is a bypass for the bootloader so we can install custom roms, recoveries, kernels

Related

[Q] Issue With Booting Into CWM (Manually/In-App)

After rooting my D80010q with ioRoot24 I decided to install ROM Manager and make a NANDroidBackup before I installed Xposed. The root works but an issue came up after I attempted to boot into recovery (CWM Touch 6.0.4.4). I simply got a dead android icon after the LG logo. After I Googled the issue and couldn't find any kind of solution besides attempting to boot into recovery manually by holding the volume buttons and the power button while turning on the device, which failed, I decided to come here.
Has anyone encountered this before and knows of any kind of solution to boot into recovery? I'm guessing it's because the bootloader is locked but I could be wrong. Didn't plan on installing a custom ROM though.
Info:
Carrier: AT&T
Device: D80010q
Android Version: 4.2.2
ROM Manager Version: 5.5.3.7
CWM Version: 6.0.4.4 Touch
Rooted with ioRoot24
Recovery flashed within the ROM Manager app
deggua said:
After rooting my D80010q with ioRoot24 I decided to install ROM Manager and make a NANDroidBackup before I installed Xposed. The root works but an issue came up after I attempted to boot into recovery (CWM Touch 6.0.4.4). I simply got a dead android icon after the LG logo. After I Googled the issue and couldn't find any kind of solution besides attempting to boot into recovery manually by holding the volume buttons and the power button while turning on the device, which failed, I decided to come here.
Has anyone encountered this before and knows of any kind of solution to boot into recovery? I'm guessing it's because the bootloader is locked but I could be wrong. Didn't plan on installing a custom ROM though.
Info:
Carrier: AT&T
Device: D80010q
Android Version: 4.2.2
ROM Manager Version: 5.5.3.7
CWM Version: 6.0.4.4 Touch
Rooted with ioRoot24
Recovery flashed within the ROM Manager app
Click to expand...
Click to collapse
ok so this is what we are gonna try first get on playstore download either freegee or flashify and instead install twrp and then report back
XxZombiePikachu said:
ok so this is what we are gonna try first get on playstore download either freegee or flashify and instead install twrp and then report back
Click to expand...
Click to collapse
Alright, I downloaded Flashify. Do you want me to download it from within the app because it said it can't find a compatible TWRP recovery within the app.
deggua said:
Alright, I downloaded Flashify. Do you want me to download it from within the app because it said it can't find a compatible TWRP recovery within the app.
Click to expand...
Click to collapse
well try freegee instead or just download twrp from here
XxZombiePikachu said:
well try freegee instead or just download twrp from here
Click to expand...
Click to collapse
FreeGee worked, 2.6.3.3 installed. Should I try and boot into it?
deggua said:
FreeGee worked, 2.6.3.3 installed. Should I try and boot into it?
Click to expand...
Click to collapse
yes it should not be a problem but others have reported trouble while trying to flash roms so be careful

[Q] Recovery boot error

I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?
I think I have the same problem. Could u solve the problem?
N12X93R said:
I used FreeGee to try to install a custom recovery after root. First TWRP, stuck at performing action. Then CWM. Then the older CWM. Always stuck at performing action. The old CWM worked. Reboot to recovery and get security boot error. Looked around on forums and found a CWM batch install that everyone says works for them. Still recovery boot error. Anyone know what's up? I'm on AT&T D800. Rooted by ioroot25
Also RomManager says I have both recoveries installed. Thinking this might be the issue. How do I delete one or both and get on the right track?
Click to expand...
Click to collapse
no you can't get recovery on kk because they patched our recovery/loki exploit on kk bootloader
not able to boot in recovery on Lg g2 802.. with stock 4.4. 2
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.
Purav786 said:
I have rooted my LG G2 using ioroot 25 and used Flashify tool to flash TWRp 2.7.0.0 however getting boot certification error.
I have 802 model updated on LG 4.4.2.
Please help want install CM11 snapshot build.
Click to expand...
Click to collapse
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok
Drachenminister said:
Safest way is to go back to stock 4.2.2 first, then root with IOroot then install recovery.lok
Click to expand...
Click to collapse
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?
Purav786 said:
Thanks Dranchenminister, but how can I return to stock 4.2.2 from stock 4.4.2?
Click to expand...
Click to collapse
There is a sticky thread in the general section of the forum
Drachenminister said:
There is a sticky thread in the general section of the forum
Click to expand...
Click to collapse
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?
Purav786 said:
Thanks again for quick help however I have checked the downgrade process and its too long plus I have to download stock 4.2.2 firmware which is 1GB plus in size..
So is there no easy method to install recovery on already rooted stock 4.4.2 firmware?
Click to expand...
Click to collapse
No, no easy one, and some might even say none at all, but you can read the rooting thread where they discuss recovery as well http://forum.xda-developers.com/showthread.php?t=2448887

LG G2 upgrade KitKat assistance

I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help
TheBull50 said:
I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help
Click to expand...
Click to collapse
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the
Merfy said:
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the
Click to expand...
Click to collapse
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2
TheBull50 said:
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2
Click to expand...
Click to collapse
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!
Merfy said:
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!
Click to expand...
Click to collapse
I'm using a Verizon LG G2 VS980 . I just downloaded TWRP 2.7 though so I am going to give that a go !!

Question: Flashify is able to successfully install a recovery ?

Flashify offers the possibility to download and then install one of these three recovery: TWRP, CWM and Philz.
Flashify allows backup of kernel and recovery, boasting the ability to restore the previous state in case of backup.
Those who have already used Flashify, may confirm the correct operation?
---
I have another question: is known (except error, or novelty unknown to me) that on KK to install a recovery different from that stock is need to downgrade the bootloader. Flashify, also deals this?
use autorec, it works 100%
kRel said:
Flashify offers the possibility to download and then install one of these three recovery: TWRP, CWM and Philz.
Flashify allows backup of kernel and recovery, boasting the ability to restore the previous state in case of backup.
Those who have already used Flashify, may confirm the correct operation?
---
I have another question: is known (except error, or novelty unknown to me) that on KK to install a recovery different from that stock is need to downgrade the bootloader. Flashify, also deals this?
Click to expand...
Click to collapse
Up, please....
kRel said:
Up, please....
Click to expand...
Click to collapse
Flashify does work and is the easiest way to flash a recovery.. if your on jellybean.
If your on kitkat though the loki exploit doesn't work and you have to use the autorec app which downgrades the bootloader for you.
Just be aware that knock code will be lost after you use it, because it also changes the kernel so your phone can boot back up. To get it back you have to flash a custom kernel like cloudy or dori.
Art Vanderlay said:
Flashify does work and is the easiest way to flash a recovery.. if your on jellybean.
If your on kitkat though the loki exploit doesn't work and you have to use the autorec app which downgrades the bootloader for you.
Just be aware that knock code will be lost after you use it, because it also changes the kernel so your phone can boot back up. To get it back you have to flash a custom kernel like cloudy or dori.
Click to expand...
Click to collapse
Hello and thank you,
sorry for delay
you've been very helpful
In G2 italian forum for restore Knock-on is provided this solution:
Code:
3845#*802# > HW Test Device> Touch Test> Touch Upgrade Firmware
and wait 10 seconds ..

[Q&A] [CM12] [Lollerpop] JFLTEATT Nightly Kangs

Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked

Categories

Resources