[HELP] - G2 Q&A, Help & Troubleshooting

I wanted to install Rayglobe 2.5 but unfortunately i selected full wipe in aroma. Rom wasnt installed correctly (frozen on 56%) and now im stuck in bootloop.
The i wanted to flash the original rom with lg mobile setup, but unfortunately the flash program keeps crashing on my win 8.1 machine.
Is there any way i can get my rom on TWRP so i can flash again? any help would be apreciated. Wasnt able to get the USB OTG working so far

fixed
Nevermind, ive been able to get the flashprogramm running. This thread can be deletet

Related

[Q] Need your help, Phone doesnt boot

I have an issue with my phone
Installed this rom (http://forum.xda-developers.com/showthread.php?t=2537495). Everything was working but since I have installed a xposed module and rebooted, the ROM is always loading and never start (google loading image)
Before intalling the ROM, I had to install 4.3 modem through ODIN.
I also have TWRP installed.
The thing is now I'm unable to boot in TWRP, my phone only want to boot in ODIN menu
What I should do now ?
- Is there a way to force boot to TWRP in order to be able to reinstall the custom rom or my nandroid backup ?
- If not, my only chance is to install stock rom with ODIN ?
Please help me, I really dont know what to do right now
Thanks
nevermind , I was able to boot into recovery mode to reinstall the custom room
thread can be closed. thanks

[Q] stuck in CWM recovery after accidental OTA update

lg g2 att rooted with stock ROM
i actually already found a fix here
http://forum.xda-developers.com/showthread.php?t=2451696
but i tried it and it didn't work.
the phone connects fine to my computer and ADB works even though it's in recovery, but after copy/pasting the code i'm still getting the same problem.
i've tried a full wipe, and trying to install an old backup. i've tried installing the stock rooted rom again, still ending up at CWM recovery.
any other options?

[Q] LG G2 ATT won't boot past recovery

lg g2 att rooted with stock ROM
i actually already found a fix here
http://forum.xda-developers.com/show....php?t=2451696
but i tried it and it didn't work.
the phone connects fine to my computer and ADB works even though it's in recovery, but after copy/pasting the code i'm still getting the same problem.
i've tried a full wipe, and trying to install an old backup. i've tried installing the stock rooted rom again, still ending up at CWM recovery.
any other options?

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Can´t flash stock ROM + lost touchscreen

Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
eldeecko said:
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
Click to expand...
Click to collapse
I was lucky one with August firmware. Problem solved, can be closed.

Categories

Resources