Hi there! I rooted my LS990 on lollipop 5.0.1 a recently and I tried to use TWRP to get a ROM on it and when I tried to install TWRP it came back with the error right after the LG logo on reboot when I tried to boot to recovery. I looked through a few threads but they all led to other LG models and not the LS990 from what I saw. I'm not able to boot to recovery, update my phone or factory reset. My endgame would be able to factory reset my phone and not worry about rooting it because it's just caused problems for me.
If there's any help I can get it would be much appreciated!
What method did you use to install TWRP? Try either TWRP Manager or Flashify from the Play Store, or push the recovery *img via adb shell or a terminal emulator app. You can find the latest *img file for the LS990 here...
https://twrp.me/devices/lgg3sprint.html
Follow the "dd Install Method (Requires Root):" directions at the bottom of the page. And make sure to never take an OTA update or perform a factory reset w/ a custom recovery like CWM or TWRP installed.
redduc900 said:
What method did you use to install TWRP? Try either TWRP Manager or Flashify from the Play Store, or push the recovery *img via adb shell or a terminal emulator app. You can find the latest *img file for the LS990 here...
Follow the "dd Install Method (Requires Root):" directions at the bottom of the page. And make sure to never take an OTA update or perform a factory reset w/ a custom recovery like CWM or TWRP installed.
Click to expand...
Click to collapse
I had downloaded TWRP from the Play Store and used the instructions in the app to patch my SD card and then downloaded the latest img from TWRP and when I tried to install the img it came back unsuccessful and since then I have had my error(s).
Try using the Flashify app instead. Make sure the external SD has indeed been patched by running the "SDFix: KitKat Writable MicroSD" app (available from the Play Store) beforehand. The app also works w/ Lollipop, and can be uninstalled after the verification or installation of the fix.
redduc900 said:
Try using the Flashify app instead. Make sure the external SD has indeed been patched by running the "SDFix: KitKat Writable MicroSD" app (available from the Play Store) beforehand. The app also works w/ Lollipop, and can be uninstalled after the verification or installation of the fix.
Click to expand...
Click to collapse
I'll give Flashify a shot. Just to be sure on what I do, I am flashing a new recovery img correct or am I doing a boot img?
Yes, a recovery image.
redduc900 said:
Yes, a recovery image.
Click to expand...
Click to collapse
Does it matter which one I do? There is a choice of TWRP, Philz and CMM.
TWRP is the recovery of choice for the G3.
redduc900 said:
TWRP is the recovery of choice for the G3.
Click to expand...
Click to collapse
It told me the flash was successful but when I rebooted my phone when it prompted me to it rebooted back to the certificate verify and secure boot error.
I forgot about the locked bootloader for that model. You'll need to first download the LS990 BUMP *.img file to your phone from here...
http://downloads.codefi.re/thecubed/lg_g3/bump/
... then open Flashify, select Recovery Image -> Choose a file -> Downloads, and select the TWRP recovery image you downloaded.
redduc900 said:
I forgot about the locked bootloader for that model. You'll need to first download the LS990 BUMP *.img file to your phone from here...
... then open Flashify, select Recovery Image -> Choose a file -> Downloads, and select the TWRP recovery image you downloaded.
Click to expand...
Click to collapse
Do I need to restore my old recovery before I do this or can I just go ahead and flash this new recovery?
No, just flash the new recovery image.
redduc900 said:
No, just flash the new recovery image.
Click to expand...
Click to collapse
Okay, I flashed the signed img from that download and it still giving the the boot certificate verify error :/
See if this video is of any help to you...
http://www.xda-developers.com/lg-g3-locked-bootloader-bump-xdatv/
That's what I did and it still gave me an error :/
I'm out of ideas... sorry.
redduc900 said:
I'm out of ideas... sorry.
Click to expand...
Click to collapse
No worries, I appreciate all of your help!
Related
I'm new to Android and recently picked up an 2013 Nexus 7. I unlocked the device and flashed 4.4 Kitkat yesterday. Today I downloaded Clockworkmod Rom Manager so I could make a backup image.
After installing ROM Mgr version 5.5.3.0, I launched the app and received the message that I needed to install the custom recovery. I followed the steps given in the app below:
1) Identified device as Nexus 7
2) Selected "Install Recovery ClockworkMod Recovery"
3) Selected 'Flash Clockworkmod Recovery'
A download overlay appeared and the download completed. After doing this, I rebooted the device into recovery mode (power + Volume UP), but the stock recovery was still there. I tried the download again using the steps above, but still no luck. When I select "Reboot into Recovery", I receive the error message "An error occurred while attempting to run privileged commands".
Question:
1) Where are these Clockworkmod Recovery downloaded files going and how can I get rid of them? If I do a full wipe of the device to clear out these junk files that I may have downloaded?
Any input would be much appreciated. My goal is to set up my device, and take a base image that I can store off of the device on an external drive.
Thanks,
Rick
Cliffs: Installed Clockworkmod ROM Manager and am doing something wrong setting up Clockworkmod Custom Recovery
Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.
shane1 said:
Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.
Click to expand...
Click to collapse
Thanks Shane. I will check for the files. I basically flashed Kitkat and now just want to make a Nandroid backup. I assume since the device is unlocked that means I'm rooted.
In order to root you have to flash supersu in recovery.
shane1 said:
In order to root you have to flash supersu in recovery.
Click to expand...
Click to collapse
Thanks, I now think I may not be rooted but rather just unlocked which was required to flash Kirkpatrick from a command line.
After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.
shane1 said:
After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.
Click to expand...
Click to collapse
Thanks, it makes sense now. All I did really was unlock, and flash in the bootloader and then the 4.4 image file. So, I'm not rooted, but just unlocked.
Is it necessary to root the device to take a Nandroid backup?
Rick
I just read your new to android make sure you read directions of anything you plan on flashing. Also its good to read entire threads if you have any issues cause your probably not the first to have an issue. Enjoy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Not necessary to root but you do need to flash a recovery IMO tarp is the easiest
C5Longhorn said:
Is it necessary to root the device to take a Nandroid backup?
Rick
Click to expand...
Click to collapse
No, you do not need to root to make a nandroid.
meekrawb said:
No, you do not need to root to make a nandroid.
Click to expand...
Click to collapse
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.
C5Longhorn said:
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.
Click to expand...
Click to collapse
Nope. You need a custom recovery to root. And to make backups. You do not need to be rooted to make backups. That is how it is on the devices I own, anyways.
I installed the KK ROM wit the TOT method and then rooted the phone and installed the CWM recovery as an apk. Now when I go into SU, it says I am not rooted. I tried 2 methods to root but unsuccessful. It boots into CWM recovery and then nothing. Do I need to reinstall the OS with the TOT method again? Any ideas?
HD2FORNICK said:
I installed the KK ROM wit the TOT method and then rooted the phone and installed the CWM recovery as an apk. Now when I go into SU, it says I am not rooted. I tried 2 methods to root but unsuccessful. It boots into CWM recovery and then nothing. Do I need to reinstall the OS with the TOT method again? Any ideas?
Click to expand...
Click to collapse
This method works perfectly: http://forum.xda-developers.com/showpost.php?p=51480568&postcount=1
After root, use this to get the correct recovery: http://forum.xda-developers.com/showpost.php?p=52945705&postcount=1
Once the phone boots into the UI, use Freegee to install the latest recovery.
jdk2 said:
This method works perfectly: http://forum.xda-developers.com/showpost.php?p=51480568&postcount=1
After root, use this to get the correct recovery: http://forum.xda-developers.com/showpost.php?p=52945705&postcount=1
Once the phone boots into the UI, use Freegee to install the latest recovery.
Click to expand...
Click to collapse
Tries and doesn't work. It goes back to my CWM recovery and does nothing. Thanks.
HD2FORNICK said:
Tries and doesn't work. It goes back to my CWM recovery and does nothing. Thanks.
Click to expand...
Click to collapse
flash the hacked twrp. that gets me out of cwm bootloop.
Same problem here phone was rooted and then installed CWM and for some reason lost root. Its not a CWM bootloop.
When the root step requires "Apply Update from ADB" I cannot because CWM doesn't have that option.
mk3 said:
Same problem here phone was rooted and then installed CWM and for some reason lost root. Its not a CWM bootloop.
When the root step requires "Apply Update from ADB" I cannot because CWM doesn't have that option.
Click to expand...
Click to collapse
I got bad news bro. I had to re TOT the phone and start from scratch. There is a CWM 6.0.4.4 floating around causing this issue. The phone loses root but it constantly boots into CWM when trying to root.
ROOT achieved, now need recovery!
OK, so I had to re TOT and get the phone back to factory state with 4.4. Then I was able to root successfully and now I am wondering how and which recovery to use. Could someone please post a link to Philz recovery and can I flash it with the same root toll with ADB sideload? THanks.
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
mk3 said:
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
Click to expand...
Click to collapse
Ok so i need a custom recovery such one did you use. I need one that can read the external card.
HD2FORNICK said:
Ok so i need a custom recovery such one did you use. I need one that can read the external card.
Click to expand...
Click to collapse
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
jdk2 said:
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
Click to expand...
Click to collapse
The last time I did that and installed the CWM 6.0.4.4 I lost root and freegee couldn't install another recovery but I'll give it a shot again.
HD2FORNICK said:
The last time I did that and installed the CWM 6.0.4.4 I lost root and freegee couldn't install another recovery but I'll give it a shot again.
Click to expand...
Click to collapse
You'll loose root if you answer "Yes" to the disclaimer CWM throws when you try to reboot. Just answer "No" and you won't loose root.
jdk2 said:
You'll loose root if you answer "Yes" to the disclaimer CWM throws when you try to reboot. Just answer "No" and you won't loose root.
Click to expand...
Click to collapse
Thanks bro. Worked!
jdk2 said:
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
Click to expand...
Click to collapse
Can you please share the custom recovery that you flashed from 6.0.4.4 ?
Sent from my LG-E988 using Tapatalk
Akhileshjj said:
Can you please share the custom recovery that you flashed from 6.0.4.4 ?
Sent from my LG-E988 using Tapatalk
Click to expand...
Click to collapse
It was CWM 6.0.4.7 and included with Freegee.
jdk2 said:
It was CWM 6.0.4.7 and included with Freegee.
Click to expand...
Click to collapse
Can you be bit more specific on how did you download the 6.0.4.7 from freegee. As i see only install option available only in freegee but not download so that it can be installed from 6.0.4.4..
Sent from my LG-E988 using Tapatalk
Akhileshjj said:
Can you be bit more specific on how did you download the 6.0.4.7 from freegee. As i see only install option available only in freegee but not download so that it can be installed from 6.0.4.4..
Sent from my LG-E988 using Tapatalk
Click to expand...
Click to collapse
When I opened Freegee, it presented the option to install 6.0.4.7. It wasn't a stand alone version but part of Freegee.
mk3 said:
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
Click to expand...
Click to collapse
Thanks its works
I flashed paranoid ROM and gapps but after rebooting gapps failed to flash and now I have no way of getting into twrp to restore my backup. Tried using lg flashtool DLL and tot but get messagage saying lg USB port locked. I'm at a total loss as what to do. I've checked SD card from computer and twrp is still there along with my backed up restore. How can I get to it or how do I fix this issue with no way of getting into google apps? Someone please help!
dcm1200 said:
I flashed paranoid ROM and gapps but after rebooting gapps failed to flash and now I have no way of getting into twrp to restore my backup. Tried using lg flashtool DLL and tot but get messagage saying lg USB port locked. I'm at a total loss as what to do. I've checked SD card from computer and twrp is still there along with my backed up restore. How can I get to it or how do I fix this issue with no way of getting into google apps? Someone please help!
Click to expand...
Click to collapse
Can you still boot into download mode?
dcm1200 said:
I flashed paranoid ROM and gapps but after rebooting gapps failed to flash and now I have no way of getting into twrp to restore my backup. Tried using lg flashtool DLL and tot but get messagage saying lg USB port locked. I'm at a total loss as what to do. I've checked SD card from computer and twrp is still there along with my backed up restore. How can I get to it or how do I fix this issue with no way of getting into google apps? Someone please help!
Click to expand...
Click to collapse
Install Flashfy app, then reboot into recovery
yes
Yes. Can stillnget into download mode. It just says installing firmware update. Do not unplug USB.
itsbighead said:
Can you still boot into download mode?
Click to expand...
Click to collapse
can I install flashfly on my phone?
Will I be able to install flashfy onto phone without gapps?thanks for the help
toxin.tuhin said:
Install Flashfy app, then reboot into recovery
Click to expand...
Click to collapse
Did you manually try getting into twrp? Power off the phone, hold vol down + power at the same time until recovery screen pops up, choose factory reset option, select yes, and twrp should appear.
This is how it works on vs985...not sure on your model if it's different or not.
have tried that as well.
I've tried the factory reset and it boots into twrp for a quick second and then reboots back into the paranoid ROM. I've tried hitting the back button to stop the process in twrp so I can restore the backup but it will not let. I found a download for flashify that wasn't on google play and when I installed it I get the message that I do not have root/SuperSU which I'm pretty sure is because I'm a moron and don't have gapps installed. I know all the things I need to restore my phone are on SD card because they show up when plugged into my laptop I just can't get to it! I've also downloaded SDK studio to try opening a cmd recovery reboot but I can't find where in that huge studio where I can open a command prompt to give it a shot. Is there a smaller SDK I can download without having to get the whole studio? Thanks again to everyone who has any advice to give.
dcm1200 said:
Will I be able to install flashfy onto phone without gapps?thanks for the help
Click to expand...
Click to collapse
of course you can. flashify available on play store. If you are already rooted then you can install flasify app. and reboor to recovery mode. But I recommend a clean flash of stock kdz or tot then root install recovery amd reflash your favourite rom.
I don't have playstore. I have no gapps package
Use ADB Command from your computer.
Hi,
I get TWRP running on phone , but when I boot into recovery , I always get the Standard Recovery, only option being a factory reset. Have opted for this factory reset and that is exactly what I get, no TWRP :crying:
Thanks
Also if you reboot to recovery through TWRP itself, it won't stick? If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
MickyFoley said:
If not: Is rooting an option for you? If yes: Try Flashify and flash it through this nifty little app .
Click to expand...
Click to collapse
Thanks,
Yes rooting is where I want to go by means of TWRP and flashing these
Marshmallow custom kernel for root — Link | File: STOCK-20a-ROOTED.zip (16.5 MB)
Click to expand...
Click to collapse
I did have Twrp running on this phone but had to reinstall the full 6.00kdz to get out of a bootloop and since then TWRP won't sick.
thanks
More than one way to skin a cat. went HERE chainfire Systemless Root 2.61 using Running TWRP from PC
Update on getting TWRP to stick. ......... I had success using following
adb reboot bootloader
Click to expand...
Click to collapse
fastboot flash recovery twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
When done, execute “fastboot reboot”
Click to expand...
Click to collapse
This happened to me, too. Here is what i did:
Boot your device into fastboot mode via adb, straight up boot to recovery ("fastboot boot twrp-2.8.7.0-h815.img"), transfer the recovery image to your device, then flash it from within TWRP (there is an option for that within the normal install menu, its called "install image" or something like that). Hope this helps, it did for me.
Edit: Just realized you already found a solution. Never mind.
Ive the same problem. I unlocked the bootloader by the official procedure. Then i tried to flash twrp but it doesnt install truly. It always appear the stock recovery. I tried also clockrecovery but nothing. No recovery wants to get installed. Pls help me i want a custom rom on my g4
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery and then flash STOCK-20a-ROOTED
chester2011 said:
use twrp v2.8.7.0 on 20A mm....... adb reboot bootloader, fastboot boot twrp-2.8.7.0-h815.img, and to double check you have recovery,adb reboot recovery
Click to expand...
Click to collapse
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
setaf said:
Ok the one i tried is the newest. Ill gonna try the one u told me. But the line u wrote wont install twrp it will only boot it
Click to expand...
Click to collapse
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
chester2011 said:
sorry, fastboot flash recovery twrp-2.8.7.0-h815.img, instead of fastboot boot twrp-2.8.7.0-h815.img worked for me after hours and hours of boot loops and restoring
Click to expand...
Click to collapse
Also u had problem with the 3.0 ? Ill update you later
setaf said:
Also u had problem with the 3.0 ? Ill update you later
Click to expand...
Click to collapse
yep.. but currently running with xposed and g4 tweaksbox (paid version) nicely
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
flash twrp version 3.0.2.0
setaf said:
ok update:
finaly i got twrp 2.8.7.0 on my g4 (thanx chester) but i still cannot flash cyanogen.
when i try to do it by recovery i get the error message 7 then when i start the system im in damn bootloop
what i can do ?
Click to expand...
Click to collapse
you can upgrade twrp with the twrp manager from playstore (once youve got twrp and root of course)
I did the following
1. Downgraded to V30b-EUR-XXX with LGUP. Went smooth.
2. Rooted phone sucessfully with kingroot.
3. Got a shell with "adb shell"
4. "su"
5. Filled the recovery-partition with zeros from /dev/zero with dd
6. Installed twrp3.2.3-0 with dd on recovery-partition
When I boot into Marshmallow, all is fine. When I boot into recovery, I'm informed about a necessary factory reset. I say "Yes" both times, then the LG Logo and some tiny text is displayed and afterwards the screen goes dark. The LED is blinking blue and red; the only way out of this is to remove the battery.
If I do a factory reset from within marshmallow, the result is the same.
What can I do now? Should I flash a stock recovery with dd? But where to get it? Or should I flash an older version of twrp?
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
NetDog75 said:
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
Click to expand...
Click to collapse
Excuse me, but I'm not able to decipher that. What is flashify? What means "on the ROM of course"? Can you give more information please.
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
NetDog75 said:
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
Click to expand...
Click to collapse
Don't had to downgrade, because I was in V30b. Got root, installed flashify and flashed twrp - the first time 3.2.3, then 2.8.0. Same result as before.
From what version of android did you install what version of twrp?
Hi,
I use the twrp3.2.3 and no problem.
I'm not expert, I just can recommend some steps...
Maybe good idea to flash again the stock ROM. You can find here on the forum many step by step guide for this. ( tools and steps )
It seems your phone recovery partition is not OK....
I have no more idea...
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. Since you were connected via adb was it not possible to use fastboot? Flashing the recovery via that should(?) have also worked.
If the recovery partition is messed up you might have to start over. Not sure though as I haven't experienced that problem.
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. S
Click to expand...
Click to collapse
It's the same partition where I flashed twrp, so the zeros are already overwritten with something else ...
Seriously: Zeroing the partition before writing to it was mentioned in a thread about the installation of a "bumped" recovery.
NetDog75 said:
Hi,
I use the twrp3.2.3 and no problem.
Click to expand...
Click to collapse
OK, that is the version I used also. What android version was installed when you flashed the recovery? Mine is stock V30b.
Hi,
I'm not sure, because I changed to 8.1 (oreo).
Maybe V30N.....
I am having the same problem. There is no "unlock bootloader" in the developer options, and adb reboot bootloader just starts into android again. I might have to reflash the stock firmware, but nowhere in the install instructions for twrp does it say that you first have to unlock the bootloader, and nowhere does it even mention that there might not be such an option. This is genuinely strange.