I just got a GPAD for my wife. It is the v500 version.
I rooted and installed the latest cyanogenmod. I had the 4.2.2 stock ROM on before.
I had TWRP 2.6.3.2 installed to get CM11 on it. Everything was fine with CM11 but wanted to put LRS 2.5 on it.
I downloaded LRS 2.5. I also had the 4.2.2 and 4.4.2 base files on the internal memory. For some reason, I thought I needed to install the 4.4.2 base files after I wiped everything before I installed LRS 2.5. Well, it INSTALLED TWRP 2.7.0.0 with the 4.4.2 base files and sent my phone into a recovery bootloop. When it goes into recovery, it starts installing some script automatically and keeps rebooting itself.
Right now, it is stuck on a dimmed out version of the LG logo. I can't do anything but reboot it into the TWRP but I can't do anything. It just keeps rebooting itself.
What can I do. Please someone help.
Thank you so very much.
luv2increase said:
I just got a GPAD for my wife. It is the v500 version.
I rooted and installed the latest cyanogenmod. I had the 4.2.2 stock ROM on before.
I had TWRP 2.6.3.2 installed to get CM11 on it. Everything was fine with CM11 but wanted to put LRS 2.5 on it.
I downloaded LRS 2.5. I also had the 4.2.2 and 4.4.2 base files on the internal memory. For some reason, I thought I needed to install the 4.4.2 base files after I wiped everything before I installed LRS 2.5. Well, it INSTALLED TWRP 2.7.0.0 with the 4.4.2 base files and sent my phone into a recovery bootloop. When it goes into recovery, it starts installing some script automatically and keeps rebooting itself.
Right now, it is stuck on a dimmed out version of the LG logo. I can't do anything but reboot it into the TWRP but I can't do anything. It just keeps rebooting itself.
What can I do. Please someone help.
Thank you so very much.
Click to expand...
Click to collapse
Please move your question to the q&a thread.
I don't know how. Maybe a nod could help me. Sorry
Go download mod and use lg firmwire tools for reinstall 4.4.2
Related
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
SOLVED: Used TWRP instead of CWM to flash.
I flashed [ROM][KRT16M] AOSP Google Android KitKat 4.4 GEEB [Nov.2] using CWM and my ATT LG e970 has no cellular or wifi now.
stock rom rooted and unlocked using freegee
backed up stock 4.1.2 using cwm
I went into recovery and cleared system cache and dalvik cache.
flashed the rom
flashed the gapps
flashed SuperSU
rebooted and saw 4.4 launcher.
tried to turn on wifi and did not work.
no cellular signal from ATT either
I tried rebooting it and it displays the stylized android logo for greater than 2 minutes before the screen flashes and boots into the lock screen still without wifi or cellular.
help.
EDIT: I was digging trough the thread and it said that CWM6.0.3.8 had conflicts with SuperSU that led to no service
I restored my nandroid backup and my phone works fine.
What can I use to flash [ROM][KRT16M] AOSP Google Android KitKat 4.4 GEEB [Nov.2]? TWRP and how do I get it? Trough ROM Manager?
Use TWRP instead of CWM.
OMGMatrix said:
Use TWRP instead of CWM.
Click to expand...
Click to collapse
Yea, I guess CWM is my problem. I flashed Houstonn's stock PA and it had the same no cellular problem. I will try to install TWRP and flash instead.
Thanks.
EDIT: How do I install TWRP using fastboot? I installed CWM via ROM Manager and that was easy, but I can't find a working installer for TWRP. How do I install using fastboot command from my PC? Do I need to install anything?
EDIT: Installed TWRP
Well, I installed TWRP 2.6.3.0 using fastboot from my PC.
Did backup to external sd card.
Flashed PA and BanKs 4.3 Gapps.
Factoryreset/clearcache and cleared dalvik before and after every flash.
Now my camera works, unlike before when I flashed on CWM 6.0.3.8 where the camera would just crash. "About Phone" now shows the phone's IMEI.
Unfortunately I cannot get service. ATT is detected but it is stuck on registration.
There is a version of twrp that acardinal posted in his slim bean 4.3 thread (they're testing a 4.4 skim bean alpha), it's recommended for v4.4...not sure if the updated twrp is recommended or required. Might be worth looking into.
There is also an updated boot loader in Houstonn's 4.4 geeb thread...don't know if it'd be of help or not.
At minimum I'd bring up your issue in Houstonn's thread. Maybe one of those folks has seen your issue.
Have you tried flashing any radios?
Sent from my Optimus G using XDA Premium 4 mobile app
DraginMagik said:
There is a version of twrp that acardinal posted in his slim bean 4.3 thread (they're testing a 4.4 skim bean alpha), it's recommended for v4.4...not sure if the updated twrp is recommended or required. Might be worth looking into.
There is also an updated boot loader in Houstonn's 4.4 geeb thread...don't know if it'd be of help or not.
At minimum I'd bring up your issue in Houstonn's thread. Maybe one of those folks has seen your issue.
Have you tried flashing any radios?
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. This time, I used TWRP instead of CWM to flash and then I rebooted the phone a couple of times and it now works fine.
Guess it was just CWM causing issues with all my rom flashes.
I recently flashed my Lenovo P780 which was running 4.4.2 to MIUI V5 4.8.27 ROM using the guideline mentioned in this thread http://forum.xda-developers.com/len...iui-v5-4-6-2-jb-4-2-lenovo-p780-dual-t2795361
I also used the recovery image mentioned this thread http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605 using mobileuncle.
I followed every step mentioned in the thread and flashed the rom. Now my device is booting but is stuck at boot. All I can see is MI.com logo. It is stuck like this for more than 30 mins.
I am unable to go back to recovery mode also. I don't know what to do. Please someone help!!
Ok. I solved the issue. Since I flashed the ROM when my Lenovo was running stock kitkat 4.4.2, the MIUI was stuck in bootloop.
What I did was I reflashed my P780 with LIFE ROM V7 using Flashtool. Then I flashed MIUI using TWRP. Now it works fine.
eashwar83 said:
Ok. I solved the issue. Since I flashed the ROM when my Lenovo was running stock kitkat 4.4.2, the MIUI was stuck in bootloop.
What I did was I reflashed my P780 with LIFE ROM V7 using Flashtool. Then I flashed MIUI using TWRP. Now it works fine.
Click to expand...
Click to collapse
Yes, I also did the same thing. Life ROM is Savior with TWRP recovery built in. Whenever, I had a wrong flash and my mobile is dead, I returned to this by flashing with SP Tools, boot straight into TWRP and then restored my previous working ROM or tried flashing another ROM.
Welcome to MIUI world. I am sure you will enjoy this ROM. Go for OTA update to 4.8.30 which worked like breeze for me. Try the Android V5 Dark theme. You will love it.
ganapathyraman_s said:
Yes, I also did the same thing. Life ROM is Savior with TWRP recovery built in. Whenever, I had a wrong flash and my mobile is dead, I returned to this by flashing with SP Tools, boot straight into TWRP and then restored my previous working ROM or tried flashing another ROM.
Welcome to MIUI world. I am sure you will enjoy this ROM. Go for OTA update to 4.8.30 which worked like breeze for me. Try the Android V5 Dark theme. You will love it.
Click to expand...
Click to collapse
Oh! I was going to ask whether OTA update to 4.8.30 was safe. Thanks for letting me know.
My lenovo softbricked after I tried to OTA update MIUI 4.8.27. Then, as you guys said, I installed Life Rom V7 and when I tried installing either MIUI 4.6 and 4.8.27 through TWRP, Roms got installed without any boot issue but I couldn't open any of the apps, even system apps like Dialer and File Explorer. Any suggestions? I would really love to go back to MIUI. May be there is a way to repack it and install through Flashtool?
Sent from my Lenovo P780 using XDA Free mobile app
eashwar83 said:
I recently flashed my Lenovo P780 which was running 4.4.2 to MIUI V5 4.8.27 ROM using the guideline mentioned in this thread http://forum.xda-developers.com/len...iui-v5-4-6-2-jb-4-2-lenovo-p780-dual-t2795361
I also used the recovery image mentioned this thread http://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605 using mobileuncle.
I followed every step mentioned in the thread and flashed the rom. Now my device is booting but is stuck at boot. All I can see is MI.com logo. It is stuck like this for more than 30 mins.
I am unable to go back to recovery mode also. I don't know what to do. Please someone help!!
Click to expand...
Click to collapse
I am still stuck with this problem. flashed using TWRP on 4.2 JB version for P780. Not sure what the problem is ?
maverickvarun said:
I am still stuck with this problem. flashed using TWRP on 4.2 JB version for P780. Not sure what the problem is ?
Click to expand...
Click to collapse
Soooo... MIUI is for Jelly Bean not for KITKAT.
DO NOT FLASH OVER KITKAT.
IF YOU FLASH OVER KITKAT YOU WILL HAVE ALOT OF PROBLEMS LIKE: YOUR SD CARD WILL NOT WORK(THIS IS THE SMALLEST PROBLEM), BOOTLOOP,BOOTLOADER CORUPTED, ETC ETC.
SO BE WARNED...
If you want to test MIUI do this:
1. Flash stock s124 ROM;
2. Download Framaroot and root your phone;
3. Install Mobileuncle Tools;
4. Get TWRP 2.6.3.0 no other;
5. Flash TWRP with Mobileuncle Tools;
6. Download MIUI and put it in your phone SD Card;
7. Install from market Reboot Manager, give root right and reboot to recovery;
8. From SD Card flash MIUI wipe cache dalvik etc etc;
9. reboot and voila MIUI.
10 Good Luck.
So I have been running cm12 for a few days, tried flashing Barrin,sacs v2 and cloudy 1.2 , all of which I have ran successfully before flashing cm12. I make it to the setup on each one and the phone freezing during set up and reboots. iI am at work so I don't have access to the lg flashtool, but I am scratching my head here.I even reflashed twrp, tried invisibleks philz recovery. Nothing works
Lol that happened to me too so I've been on cm12 since it dropped ... I did get cm11 nandroid to work also but my phone won't work stock
I was able to flash barrin v1 , then dirty flashed v2 and v2.1 . stock zv6 flashed first though. It was weird , plus my extsdcard needed to be reformatted.
Try stock zv6 that worked for me. Oh and I flashed a SuperSU zip..I don't know if that did anything just something I did
You may have to wipe internal sdcard.
Glad you got it going I wasn't really that pressed lol I only tried 2x and that was it
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Drake9897 said:
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Click to expand...
Click to collapse
Bump, would really like some help :/
Back to stock
Drake9897 said:
Bump, would really like some help :/
Click to expand...
Click to collapse
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
I'll try that! Thanks! (sorry for late reply)
just flashed stock and got twrp back, tried to flash my RLS 19 backup and it completes at 3gb out of 1.2gb and 170% out of 100%. ugh :/ also twrp won't install via goo manager, have to use twrp manager .
TheSt33v said:
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
Click to expand...
Click to collapse
z
Also I'm running danvdh's lollipop GPE as well. It's actually the reason i updated twrp and started to get this issue. i'm running the same version of twrp as you and still no hyperdrive backup can restore. ):