My friend tried to install Cyanogen Mod 11 on his Lg g2 from Sprint. But he downloaded the wrong version, and it resulted in the screen turning black with white lines.
The picture below shows what it does.
Is there any way I can get back to the stock Android that comes with the G2? I've tried hard resetting it and it doesn't seem to work.
There's no cracks and the phone hasn't been dropped. It was working properly before trying to install CyanogenMod.
Thank you in advance for your help.
Side load the proper version with zv8 radio.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Side load the proper version with zv8 radio.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
how do I do that?
:silly:
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems/LGLS980_ZV8_RADIO.zip
Put phone into twrp, advanced, side load.
On computer, adb sideload lgls980_zv8_radio.zip
Sent from my Nexus 7 using Tapatalk
Related
I tried to install that paranoid android rom.I keep getting an error 7. it says no target device found. I've tried 1.9 .4, 1.9 .5, 1.9.6 and now 1.9 .7. It looks like an awesome rom but I can't install it. I get the same error with the cm 10. Presently I'm running the vicious ROM (jellybean). I wipe everything before trying to install the ROM but nothing works. I can install the maguro version with no problems other than I don't have phone service. I want this ROM bad and need some guidance.
Mr. Keith
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
El Daddy said:
How are you trying to flash the ROM? In recovery?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes, clockwork mod. I've also tried to manually do it in recovery, still get the status 7 error. I tried the supersu mod, no success. I have the Verizon gnex. This is week 2 of failed attempts. Do I have to start with a stock rom first?
Hope you are getting roms from Verizon thread not i9250
atifsh said:
Hope you are getting roms from Verizon thread not i9250
Click to expand...
Click to collapse
This.
The reason why you didn't have service with a maguro ROM is because that is for the gsm version.
You want the toro builds. Hopefully you can get your radio back.
if not you'll have to flash the stock Google image.
Sent from my Nexus 7 using xda premium
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
eksasol said:
If you mean status 7 error, I have that with my Vibrant and have to change to a different version of clockworkmod. Try flashing an older version of CWM in fastboot.
Click to expand...
Click to collapse
This is likely the OP's issue. There are just too many incompatibilities with the newer recoveries. If you stick with 5.5.0.2 (for maguro), and 5.5.0.4 (for toro), you will see that you will have significantly less issues...
I have a Verizon galaxy nexus with paranoid rom all you do is go back to stick ics and use recovery to flash and it might get stuck in boot screen just take out battery and put back in and should just start up
Sent from my Galaxy Nexus using xda app-developers app
Sucess!!
Thank you, thank you, all of you. I finally installed the rom last night and its truly awesome. I didn't know that rom manager allows you to revert to older cwm versions. That did the trick. I now have some catching up to do.
Thanks again,
Mr. Keith
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
What phone do you have? what kind of gnex
vzw. https://www.xda-developers.com/android/verizon-finally-rolls-out-jelly-bean-jro03o-to-galaxy-nexus/
op, get in recovery, wipe data/factory reset, reflash your rom.
if you can't, then try to get in bootloader/fastboot mode, and from there to recovery. doesnt work? reflash recovery.
still doesnt work? start fresh.
oh, wait a sec, you trying to OTA? what build are you currently on?
sent from my i9250
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Give it time. The restart is taking longer with the JB boot loader on the GNex. Its verifying file systems. It may take several minutes, and then will boot into the OS with the X boot animation. Been discussed in several threads.
Sent from my Xoom using xda premium
jacobydarkon said:
So I've tried installing the JRO030 update on my Gnex twice now. Both times ended with it being stuck at the boot logo AFTER a complete shut down. I followed the instructions to a t. Is there anything else I could do to fix it? I'm no noob here, but I'm lost at this point.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Have you tried doing a factory reset? Attempt a factory reset and if it gets stuck on the Google boot logo, your phone is missing its recovery image, so you will need to manually flash Jelly Bean with the factory images from Google. Were you able to install the 4.0.4 update when it first came out?
Verizon Galaxy Nexus.
I'm on imm76k.
I did not know it took so long. Can you give me a link to one of the threads?
I tried a factory reset.
Yes, I did. It updated just fine.
Thanks for all the help.
Sent from my Galaxy Nexus using Tapatalk 2
jacobydarkon said:
I did not know it took so long. Can you give me a link to one of the threads?
Click to expand...
Click to collapse
http://rootzwiki.com/topic/30417-boot-time-unbelievably-slow/
Sent from my Xoom using xda premium
Thanks. The update came yesterday and I decided to try one more time and it worked, mostly because I was patient this time. Lol. Interesting that no one really knows what it does from that tread. Only theories so far.
Sent from my Nexus 7 using Tapatalk 2
I tried to flash the
Liquid JB v2.1 beta2 rom and the gapps jb 20121212-signed package. I used the Unified toolkit to root. It rooted fine. I rebooted in recovery, installed the Liquid rom, then the gapps, then I tried to reboot. Got nothing but a black screen.
Took the battery out, tried the wall charger, USB charger. Nothing works.
Try to Odin back to stock
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Tried that, cant get my computer to recoginize the phone. The screen is pitch black like there is no power.
Wado1 said:
Tried that, cant get my computer to recoginize the phone. The screen is pitch black like there is no power.
Click to expand...
Click to collapse
What did you use to flash your ROM. Bottom line is you need to try to get into download mode. I believe the key combo is hold down power + volume down + home. If that boots you into download mode just flash back to stock.
Sent from my SAMSUNG-SGH-I747 using xda premium
I used the 7.0 Toolkit to flash my ROM, I've been trying to get into download mode for hours with no luck.
Wado1 said:
I used the 7.0 Toolkit to flash my ROM, I've been trying to get into download mode for hours with no luck.
Click to expand...
Click to collapse
Post the link where you got the 7.0 toolkit and the link where you downloaded the ROM.
Sent from my SAMSUNG-SGH-I747 using xda premium
Toolkit: http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/Samsung_Galaxy_S3_ToolKit_v7.0.exe
Rom: http://goo.im/devs/liquidsmooth/4.2.1/Beta2/Liquid-JB-v2.1-Beta2-endeavoru.zip
I got them both from there respective links in the ATT S3 Forums.
CRAPPPPPPPP, I see what I did. I should have flashed d2att. Damn. I flashed the newest because I thought they were nightlies.
Is there anyway to unbrick it besides doing the jtag?
Wado1 said:
Is there anyway to unbrick it besides doing the jtag?
Click to expand...
Click to collapse
Not likely. JTAG will probably be the only option.
Sent from my SAMSUNG-SGH-I747 using xda premium
Wado1 said:
Is there anyway to unbrick it besides doing the jtag?
Click to expand...
Click to collapse
You didn't make a backup before flashing?.. Can you get the phone into recovery?
I made a nandroid backup and thats on the SD card but I can't get into download or recovery. All I get is a black screen no matter what I press or do.
Wado1 said:
Toolkit: http://goo.im/devs/mskip/toolkit/samsung_galaxy_s3/Samsung_Galaxy_S3_ToolKit_v7.0.exe
Rom: http://goo.im/devs/liquidsmooth/4.2.1/Beta2/Liquid-JB-v2.1-Beta2-endeavoru.zip
I got them both from there respective links in the ATT S3 Forums.
CRAPPPPPPPP, I see what I did. I should have flashed d2att. Damn. I flashed the newest because I thought they were nightlies.
Click to expand...
Click to collapse
Looks like you're most likely hard bricked. That's an HTC One X ROM. Looking at the installer script, it uses mount points that don't match the d2att. It writes the system files to mmcblk0p12, which is the modem on our phone. Also, it writes the kernel to mmcblk0p4, which is also incorrect (I think it's for boot screen images?). Sorry.
Wado unfortunately I've hard bricked two S3's so I know how you feel it's a sinking feeling indeed. I have learned from my foolish mistakes though. I feel for you man.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
att service can fix bricked phone
The guy's at my AT&T service shop have a program they claim that will fix bricked phones they used it on mine to fix a sound issue
Where you able to get it fixed?
Sent from my Nexus 7 using Tapatalk HD
Accidentally installed the newest Verizon radio on my Sprint Galaxy Nexus. I've tried writing back my old radio 3 times but I still cannot connect to 3G. WiFi and regular cell/texts seem OK. Any advice?
Sent from my Galaxy Nexus using Tapatalk 2
auradefect said:
Accidentally installed the newest Verizon radio on my Sprint Galaxy Nexus. I've tried writing back my old radio 3 times but I still cannot connect to 3G. WiFi and regular cell/texts seem OK. Any advice?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
you may have to odin back to stock if flashing radios to recovery does not work.
chasew83 said:
you may have to odin back to stock if flashing radios to recovery does not work.
Click to expand...
Click to collapse
please dont use odin.
learn fastboot.
I've done fastboot in the past with terminal emulator. That will make a difference versus the recovery method?
Also, just curious about why not to use Odin? Never used it but wondering your reasons.
Sent from my Galaxy Nexus using Tapatalk 2
auradefect said:
I've done fastboot in the past with terminal emulator. That will make a difference versus the recovery method?
Also, just curious about why not to use Odin? Never used it but wondering your reasons.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
there is no real good reason to not use odin, some people just prefer fastboot and we should all learn it. you can odin back to whichever odin file is available then do manual updates to ga02 so you are on the latest radios. will start you over from complete scratch (wipes phone completely), so back up you storage before using.
zepius: that was a nice trolling post though, not helpful at all.
Odin isn't officially supported through Google. Even though this device is made by Samsung, and happens to have the options for Odin, there is no official support for it. Google provides images to be flashed via fastboot.
Besides, fastboot should already be installed and setup as it is part of the unlock/root process. So why someone would go out of their way to use Odin, when fastboot should already be setup and they should have some knowledge of how to use makes no sense to me.
The only thing I can think of that would make me use Odin, is if my USB port completely died and I wanted to get it back to stock.
flash the stock image from google using a tool kit or a terminal
and this should fix the issue but dont hold me to it
Anyone have a link for the correct image? Don't want to screw this up.
Sent from my Galaxy Nexus using Tapatalk 2
auradefect said:
Anyone have a link for the correct image? Don't want to screw this up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images#mysidspr
Hello,
I am very new to rooting, and just rooted my Sprint LG G2 with 4.4.2 KitKat through IORoot 25 and then used AutoRec as my TWRP. I then downloaded Cyanogenmod11 from its website onto my phone, and tried to flash install it through AutoRec. However, when I try to install the CM11 ROM, I get the "MD5 not found" message, and when I try to reboot after this, my phone goes into what I think is Bootloop (the LG home screen continuously turns on for a couple seconds, then stops for a split second, and then turns back on for a couple seconds). Fortunately, I am was able to hard restart my phone by holding Power and Volume Up together while this screen is on, and I was able to restore my phone with the backup I made, and my phone is now working fine with the stock ROM. Has anyone else had this problem before, and if so is there a better way for my to install custom ROM, and/or fix that MD5 message? Does anyone know what that MD5 message means?
One other note, I have been doing some reading and I currently have ZVC radio. I'm not sure what this means exactly, but would this make a difference?
Thanks!
If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app
secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Interesting, thanks. Are there any ROMs that work for 4.4.2 that people have been using, or am I pretty much stuck with the stock ROM until CM is updated?
Cloudyfa has some in the G2 android development forum. There are some others that will work with sprint.
http://forum.xda-developers.com/showthread.php?t=2687613
[INDEX][REPO][AIO] LG G2 - ROMs | Kernels | MODs | Recoveries [UPDATED][9 June 14]
Has some info in it also
Sent from my Nexus 7 using Tapatalk
secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Click to expand...
Click to collapse
Hi, would you mind explaining further why it wont work, coz i have the exact problem that LGGuy83 is/was experiencing (i used autorec too and cm11 gives me an lg logo boot loop) and this is the closest thread to getting an answer
What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk
secret.animal said:
What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk
Click to expand...
Click to collapse
thanks for ur reply,
Im not sure what "radio" version, but i know its updated to VS980-26A
anyway i sorted the problem by using the cm11 version on this link
http://forum.xda-developers.com/showthread.php?t=2702958
i simply downloaded the one here and installed, (skipped all the steps and just put it in the internal memory and flashed it)
Now its working well. ill let you know if any problems arise.