Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.
Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.
So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud
vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports
It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.
free gee very fast
Use Flashify u n00b.
Related
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Use goomanager. It's by far the easiest since it's mostly automated.
mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD
Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app
theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP
you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Jexx11 said:
What is the advantage/difference in installing the SuperSU app you linked, in favor of the one included with the TWRP 4.4 recovery?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
alex94kumar said:
Probably nothing. The only reason I mentioned the one in the play store, is because TWRP never actually asked me to root in the first place. I thought it was strange, but I didn't really think much of it
Click to expand...
Click to collapse
That's odd, I used the TWRP version in Hashcodes thread, flashed with the Motorola Fastboot. When I went to restart from TWRP it asked me if I wanted to root and I let it. Now I'm rooted.
Sent from my XT1060 using Tapatalk
Stranger things have happened, I guess. Regardless of which method you use, you'll end up with root either way
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
chaoslimits said:
This doesn't seem to be working for me. I accidentally rebooted into Android (hit the power button) then tried the whole thing from scratch.
I get an image of andy with "no command" when I boot into recovery.
Edit: Seems like a low battery issue. Will try again after charging.
Click to expand...
Click to collapse
same here but i have 85% battery
so i guess we will have to re-flash and push the supersu
The only advice I can give to either of you is to try reflashing TWRP again
Actually i did it again and it worked, guess we can't just skip steps.
Sent from my Nexus 7 using Tapatalk 4
Well im glad it worked out for you in the end
It worked after I charged the phone.
Thanks
Sent from my XT1060 using Tapatalk 2
How do I return my phone to default in order to install OTA
I have already flashed the stock recovery but my phone is still rooted. Do I need to unroot? I tried installing the OTA and it said it failed.
This method should work on any version with with an unlocked bootloader such as Sprint and T-Mobile - not just the dev editions.
alex94kumar said:
https://www.youtube.com/watch?v=NP9WXLIzhTY
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, **do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this**.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)->
http://forum.xda-developers.com/showthread.php?t=2534850
________________________________________________________________
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
Anyone knows how to do UNROOT if I used this method to get root?
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
s0nic69 said:
1) let the system fully install the 4.4 Kitkat ota and reboot.**Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.**
Can someone explain this to me? i keep reading it, but not understanding what it means.
Click to expand...
Click to collapse
If we're already on 4.4, how do we know if we have the first OTA?
Thanks
chillmeow said:
I get a preflash validation failed because the file size is over the limit, but I've checked the file size is actually smaller than the limit.
Has anyone experience this?
Sorry this might be a noob question.
Click to expand...
Click to collapse
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------
doctor_evil said:
I'm getting it too, and I've tried both the mfastboot and regular fastboot and I've tried redownloading the file several times. I'm beyond annoyed at this point I need root so I can restore my apps using titanium backup
Click to expand...
Click to collapse
OK I feel like an idiot. I just noticed that in the fastboot screen it shows that it's locked. I thought developer phones were unlocked by default?
ok after unlocking it I was able to install twrp recovery with no problems
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
pphi said:
Ok, what am I doing wrong?
I've got an unlocked GSM DE with 4.4.
I used the mac mfastboot to flash twrp and then select recovery. After that it just boots to android telling me I have an unlocked bootloader. Help?
Click to expand...
Click to collapse
Are you selecting recovery with the power button or the volume up button? Volume up selects. If you use the power button, the phone just boots normally.
Hi,
I have an LG G2 D802 and already installed TWRP 2.6.3.4 for installing zip-files. But now there is an update (only browser, but 4.4 shouldn't be that far away), but without stock recovery it's impossible to install it I know the way how to get back to stock completely, but I don't want to go back to stock every time there is an update, installing all of them and then reinstall TWRP. I think on CWM the problem is the same, but i don't want to miss the camera tweak and splitwindow, so I need an custom recovery for the zip-files:crying: Is there any way to get the stock recovery back without installing complete stock or at least a possibility, to only "boot" the custom recovery when I'm back on stock, like on Nexus devices, and only use it for the flashing and then lose it on the next reboot?
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
simon_lefisch said:
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
most likely, but cannot confirm it, you ooen a stock kdz, and try flashing the kernel .img thats inside, I am not sure
anyone confirm it works that way
Sent from my LG-D802 using xda app-developers app
for all I know, the kernel doesn't contain any recovery... but I will test it tomorrow, when I downloaded the kdz if you could say me how to open a kdz-file.
Artim_96 said:
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
Click to expand...
Click to collapse
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
simon_lefisch said:
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
Click to expand...
Click to collapse
If it's not working, I have a backup of the current. but I will test it tomorrow, then I have more time. But thanks for the quick answers.
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Artim_96 said:
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Click to expand...
Click to collapse
I've had similar problem, i think I just installed the KDZ file trough the way they showing: http://forum.xda-developers.com/showthread.php?t=2432476
It just erased the rooy and TWRP, and all of the apps and settings did not change, its like a repach.
at least it should be. but I can't take the last step. "By turning off, Holding down power and Vol Down until it comes up on the screen." doesn't works, there only starts the normal software, and that's the old one. And unpacking the kdz file with 7zip or Peazip also don't work. Peazip can do ist, but I have to find out how to let it extract it. After installing it, there is another file with the same name, but it's an .cab file with password. If I boot over widgetsoid into recovery (I think this is what the manual means) there is only a little droid with a read sign. How to get further?
EDIT: found out how to come into that menu. It wants to make a hard reset so I make an backup first.
Finally I was able to install the complete new software version (D80210e-EUR-XX) over the LG PC Suite. The file downloaded from the manual seemed to be corrupted or so as it only caused an unpacking error in the programm.
Does anybody knows a way how to flash a zip without a custom rom? Flash Gordon seems to not work.
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 !!
Long story short: I want cm on the S4 after using it on the HD+, but CWM isn't booting up.
I've seen problems regarding simply accessing the recovery mode like needing to use the buttons twice after powering on, but the thing is that after getting to do this, for whatever reason, the phone boots up with the default recovery option (Android system recovery <3e>).
Some background on the phone would be that it is rooted, about one year ago when I bought it. I fear that I might have flashed something back then, but I don't have any of the files. To add, I sadly don't remember the method, but I can give some device info:
View attachment 2870784
The next and last thing would be that ROM manager says I have CWM installed and even with the reboot option of the app, it takes me to the default recovery.
View attachment 2870785
Any similar experiences on how to deal with this? I'd at least have a means to access CWM.
Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you sure you're still rooted? If you're not sure I would re-flash root using motochopper
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, yes. I do have things like tethering and su on the phone, plus root checking apps from the store say its rooted.
ROM Manager is crap. It says I have CWM 6.0.4.7 installed but when I boot into recovery it says 6.0.4.4.
I've been looking for a way to manually install the latest Touch version of CWM but so far I've come up with nothing. Maybe if you flash TWRP (via Goo Manager app) you'll then be able to flash CWM back over it. Sometimes it takes 2 or 3 tries for Goo Manager to successfully flash the recovery.
Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
https://github.com/djrbliss/loki
The readme was very helpful.
snakecharmer23 said:
Even better, I figured out how to flash CWM touch. The loki_tool downloaded here can patch any compatible img file and then flash your recovery directly.
The readme was very helpful.
Click to expand...
Click to collapse
Thanks for the link! It was really easy to follow.