I successfully updated my Nexus 7 to 4.4.3 and it was working great until last night the Wifi just stopped working. It will not search for wifi, or if it does let me turn it on it won't scan or find anything. I did flash a new kernel to it earlier, but it was working fine. I tried to reflash 4.4.3 and it just fails using fast boot, or adb sideload. I have tried searching the forum, but since 4.4.3 just came out it seems that I am the only one that I can see with this issue.
I also did a factory reset using TWRP but still nothing.
Details that may help are as follows:
Nexus 7 (2013)
Rooted w/ Franco Kernel ( unless it will reflash the stock )
TWP 2.7 installed
Any help would be appreciated. I will keep working on doing a factory restore and then reflashing back to 4.4.3 and see if that works.
Pilz474 said:
I successfully updated my Nexus 7 to 4.4.3 and it was working great until last night the Wifi just stopped working. It will not search for wifi, or if it does let me turn it on it won't scan or find anything. I did flash a new kernel to it earlier, but it was working fine. I tried to reflash 4.4.3 and it just fails using fast boot, or adb sideload. I have tried searching the forum, but since 4.4.3 just came out it seems that I am the only one that I can see with this issue.
I also did a factory reset using TWRP but still nothing.
Details that may help are as follows:
Nexus 7 (2013)
Rooted w/ Franco Kernel ( unless it will reflash the stock )
TWP 2.7 installed
Any help would be appreciated. I will keep working on doing a factory restore and then reflashing back to 4.4.3 and see if that works.
Click to expand...
Click to collapse
Custom kernels have to be remade for 4.4.3
Don't use any for now
Sent from my Nexus 7 using XDA Premium 4 mobile app
rap3rman said:
Custom kernels have to be remade for 4.4.3
Don't use any for now
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This.
Anyone using a customer kernel needs to wait until the kernel is updated to 4.4.3.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Pilz474 said:
I successfully updated my Nexus 7 to 4.4.3 and it was working great until last night the Wifi just stopped working. It will not search for wifi, or if it does let me turn it on it won't scan or find anything. I did flash a new kernel to it earlier, but it was working fine. I tried to reflash 4.4.3 and it just fails using fast boot, or adb sideload. I have tried searching the forum, but since 4.4.3 just came out it seems that I am the only one that I can see with this issue.
I also did a factory reset using TWRP but still nothing.
Details that may help are as follows:
Nexus 7 (2013)
Rooted w/ Franco Kernel ( unless it will reflash the stock )
TWP 2.7 installed
Any help would be appreciated. I will keep working on doing a factory restore and then reflashing back to 4.4.3 and see if that works.
Click to expand...
Click to collapse
At the very least you need to flash the stock 4.4.3 boot image if that's where you're at now. I would also flash the system image just to be safe and to make sure you clean up any leftover files from the custom kernel, If there are any.
This patch fix WIFI for me
http://dl-1.va.us.xda-developers.co....zip?key=q2JwQJCSmgrvN42LvgV5Pg&ts=1401912320
wantabe said:
At the very least you need to flash the stock 4.4.3 boot image if that's where you're at now. I would also flash the system image just to be safe and to make sure you clean up any leftover files from the custom kernel, If there are any.
Click to expand...
Click to collapse
I was stupid and updated the kernel without thinking, and as others have sad that is obviously the issue. This is what happens when you are sleep deprived and have full time summer classes.
I did a reflash of everything. For some reason my Nexus is really slow to accept new software. When I flashed 4.4.3 to it again it failed, and I went to bed because it was late. The next morning I went to fix it and it was booting up just fine, although because it accepted the reflash I had to re set up my apps which is no big deal.
Thanks again for the help, I will learn how to fix these things on my own someday.
Pilz474 said:
I was stupid and updated the kernel without thinking, and as others have sad that is obviously the issue. This is what happens when you are sleep deprived and have full time summer classes.
I did a reflash of everything. For some reason my Nexus is really slow to accept new software. When I flashed 4.4.3 to it again it failed, and I went to bed because it was late. The next morning I went to fix it and it was booting up just fine, although because it accepted the reflash I had to re set up my apps which is no big deal.
Thanks again for the help, I will learn how to fix these things on my own someday.
Click to expand...
Click to collapse
I'm glad you got it working again! I personally had to learn the hard way not to be flashing kernels or any other images when I had one eye open. I keep copies of all the unzipped factory images on my computer and over the last few years have managed to grab images from the wrong folder more than once. ; ) Using the sdk it was never a big deal straightening it out but still!
Related
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250
Hi Guys This is not new to me, but what I missing,I have a galaxy s3 from at&t, I flashed to many roms before,but now I try to go to 4.4 and I can't I get error 7 and msd 5 no found android with a red triangle in the chest ,even the, I when back to stock 4.11 rooted and install recovery. What I done till now : the friendly guide for the error 7, toggle the the restriction in the recovery options still the same problem, even the OTA update from At& can't be installed. Is driving me nuts any Help ? thanks.:good:
Are you running the latest recovery? 4.4 ROMs require the latest TWRP or CWM.
audit13 said:
Are you running the latest recovery? 4.4 ROMs require the latest TWRP or CWM.
Click to expand...
Click to collapse
Sorry to take to long to get back ,You where right, I believed that I had the last ,now is working fine thanks a lot I did flash to 4.4 ,
now no WiFi, I'm working on it
chi3sol said:
Sorry to take to long to get back ,You where right, I believed that I had the last ,now is working fine thanks a lot I did flash to 4.4 ,
now no WiFi, I'm working on it
Click to expand...
Click to collapse
Could it be the modem that you're running? Did Wifi work on previous ROMs?
I got it working, but start geting froze and buch of isues, did flash it again and then after flash the google app the screen turn black and the phone won't boot , I did went back to stock everything is fine
Is any way to check if some aystem file is mising
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
What ROM are you trying to flash?
I fix it thanks
Sent from my GT-P3110 using xda app-developers app
audit13 Thanks a lot
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.
helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7
Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.
Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app
Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk
Hello wonderful community!
I write this in equal parts shame and anguish. I thought I knew what I was doing, apparently something went wrong. Here's the situation.
Was on Paranoid Android 4.4 BETA 1 and flashed Paranoid Android 4.4 RC1
PA 4.4 RC 1 had Google sync problems, so I decided to jump to DJL4.4Custom FLO 06-03-14 (Latest) w/recommended GAPPS
WiFi wouldn't turn on. (Would hang saying "WiFi turning on...") <-- Main problem. Can't sync, etc.
Factory resetted and did a lot of wiping - to no avail.
Now stuck in an apparent bootloop of the startup animation of DLJ4.4.
Help please!?!
This absolutely sucks. If anyone can help, please let me know. I've been using WugFresh's toolkit when needed. I did all of the flashing above via Nexus 7 only however.
Any and all help is greatly appreciated!
Thanks in advance!
XQuisite said:
Any and all help is greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The lack of WiFi connectivity problem is ROM issue. If you have TWRP you can sideload a ROM onto it.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
LinearEquation said:
The lack of WiFi connectivity problem is ROM issue. If you have TWRP you can sideload a ROM onto it.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply. I've since tried to revert back to the ROM that I was using and the WiFi is still stuck in the "Turning on WiFi" part. Could I flash a kernel instead? All ROM, GAPPS, and Kernel zip installs have been done with full wipes.
XQuisite said:
Thanks for your reply. I've since tried to revert back to the ROM that I was using and the WiFi is still stuck in the "Turning on WiFi" part. Could I flash a kernel instead? All ROM, GAPPS, and Kernel zip installs have been done with full wipes.
Click to expand...
Click to collapse
Should be able to. I use ElementalX. Very stable and fast. You can flash AOSP kernel too. When 4.4.3 first hit there were some issues that were quickly patched. Some have not worked the patch into their ROM yet.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
LinearEquation said:
Should be able to. I use ElementalX. Very stable and fast. You can flash AOSP kernel too. When 4.4.3 first hit there were some issues that were quickly patched. Some have not worked the patch into their ROM yet.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
I've now tried to flash back to stock and the WiFi still doesn't want to fully turn on. =/ I'm going to try to flash some ROMs and Kernels to see what I get.
Thanks Linear. I'm discouraged but hopeful.
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.