Good day
After using different methods to try and install a variety of ROMS inclduing CM11, MUIU, FirefoxOs and KitKat 4.4.4.2 Brannded, I'm stuck in the TWRP 2.6.3.2 gui after using flashify and not making a backup. When I sideload and install miui_g2_ws008_4.5.19_5b586f93ad_4.2 it installs sucessfully according to the log, but I get stuck in boot loop after gapps has been loaded in 1st boot. With cm-11-20140522-NIGHTLY-d802, openrecovery-twrp-2.7.0.0-d2vzw, philz_touch_5.15.0-d2vzw, TWRP_v2.3.3.0_P350 I get the Error Executing Binary Zip. When I sideload openrecovery-twrp-2.7.0.2-t03g it installs successfully, I select reboot, it ask me to install SuperSU I say yes and then get stuck in LG boot loop. LG flash tools get stuck at "waiting for connection" when I try to flash it with LGD800AT-01-V10d-310-410-AUG-14-2013 and LGD800_20130904_LGFLASHv160.
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Please help I don't know what to do next!
Related
Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.
DRayX said:
Hello, I could us a little assistance. I was trying to install CM on my new Verizon LG G2 (VS980). I was able to root using ioroot, dump aboot.img, lokify CWM 6.0.4.4, loki_flash the recovery, and boot into CWM. When I tried to sideload the CM 10.2 image, I got some error about unable to lokify boot (it was missing /system/bin/loki.sh). It looks like the problem is that the pre CM 11 images have an old version of loki that fails regularly. It said it had aborted the installation, but something got totally hosed, as when I attempted to reboot, I got into a "secure boot unsuccessful" loop. I've made a verison of the CM 10.2 zip with the latest version of loki_patch and loki_flash from github, but I can't seem to get into recovery using the buttons (might be doing it wrong as the only time I went into recovery I just did adb reboot recovery) to try flashing another rom or return to stock. I can get in to download mode by holding up during boot, but I don't have easy access to a non-linux machine to use the lg mobile support tool. Is there any way to return to stock without a windows computer?
Edit:
Update, I was able to get back into recovery by unplugging the USB (apparently it doesn't like to boot into recovery if the USB cable is connected). Installed my patched CM 10.2 and everything worked like a champ.
Click to expand...
Click to collapse
how did you patch cm 10.2
hii guys i can't install twrp on my play.....whenever i enter the command i get the error
"error: cannot load twrp-lux-2.8.7.0"
also the windroid tool says twrp flashed successfully but when i reboot into recovery it boots into stock recovery with "no command" on display
any help appreciated
What are you typing when trying to flash?
fastboot flash recovery nameoffile.img
Not sure if you are having the same issue I did.
Are you flashing TWRP then using the reboot command to restart your phone immediately?
If so, try flashing TWRP again. Instead of rebooting, try to access the recovery menu right after flashing. This worked for me. The post I saw related to this mentioned the Moto was overwriting something when rebooting. I haven't had any issues since.
So I tried flashing CM13 via TWRP and I did, but whenever I try to access the recovery it just shows the LG logo and the boot certification error. When I try to install a recovery via Autorec it shows an error when installing the loki tool, so I don't know what to do. Any help? CM13 works fine and I can boot to it, but I'm wondering how I can access my recovery again. Thanks
failed1234 said:
So I tried flashing CM13 via TWRP and I did, but whenever I try to access the recovery it just shows the LG logo and the boot certification error. When I try to install a recovery via Autorec it shows an error when installing the loki tool, so I don't know what to do. Any help? CM13 works fine and I can boot to it, but I'm wondering how I can access my recovery again. Thanks
Click to expand...
Click to collapse
well my way was to fgo back to KK using flash tools. is it boots try using flashify.. if it boots into system.
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
lg g2 bricked
hevydevy said:
I got cm 13 running on my d801 g2 the other day and I'm not a fan of it so I'm planning on flashing to cloudy g2 2.2 but now i am unable to boot into twrp. I enabled root, installed twrp and even enabled advanced reboot to boot directly into recovery but i keep getting secure booting error Cause: boot certification error which is what i was getting on stock android before getting cm13, i fixed the issue before with the kitkat auto rec app but I've read that auto rec can cause a hard brick if used in marshmallow. Trying to get into twrp through twrp, cm advanced reboot, hard key(power and vol down) recovery, flashify and adb reboot recovery command all cause the same error message. Any advice? I tried flashing twrp 3.0.0.4 and that put me into fastboot as does any other twrp version I've tried in flashify
Click to expand...
Click to collapse
does ur phone goes in download mode?
kalpesh patil said:
does ur phone goes in download mode?
Click to expand...
Click to collapse
It will give me the download mode message then goes to a black screen. My computer brings up 15 disc partitions with only one partition containing data, one folder called image with files include adsp, cmnlib, mc_v2, modem, playread, wcnss and widevine they all have duplicates with different file types b00-b26 and mdt .
Hello,
I am experiencing issues with TWRP on my Samsung SM-J530F. After installing TWRP, my phone is stuck in a bootloop, but I can still boot into TWRP.
The problem is that when I try to install ROMs using ADB or TWRP, my device is detected as just a dot (".") in TWRP, so I cannot proceed with the installation.
I have also tried using ODIN to install a ROM, but it didn't work.
When I tried to use ADB with the "--force" command to sideload the ROM, I received an error message: "adb.exe: sideload requires an argument."
I am looking for a solution to install a compatible ROM on my Samsung SM-J530F.
Edit:Only TWRP Detects my phone as a dot.
nvm it works with orangefox