Related
I cannot get JB still. I bought the phone from rogers and just use it on Telus.
Always when I try it gets stuck on bootloop.
Could I just borrow somebodies sim from rogers or fido and let them get the OTA?
not really sure how to get JB. Nothing has worked so far.
The OTA has absolutely nothing to do with what SIM you have in your device.
martonikaj said:
The OTA has absolutely nothing to do with what SIM you have in your device.
Click to expand...
Click to collapse
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Mackie011 said:
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Click to expand...
Click to collapse
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
martonikaj said:
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
Click to expand...
Click to collapse
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
And that is pretty much where I am at right now.
Not really sure how to make it work.
Mackie011 said:
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
Click to expand...
Click to collapse
Likely didn't wipe properly, chose the wrong ROM, or tried to switch between ROM makers unsuccessfully.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
Click to expand...
Click to collapse
When you flashed back to stock it didn't flash properly, or missed part (like recovery, bootloader or radio), so the OTA won't install properly.
If you want stock 4.1.1, just flash it completely. Stop trying to mess with an OTA.
This is the only guide I'd recommend: http://forum.xda-developers.com/showthread.php?t=1626895
Factory images... including 4.1.1 are right here: https://developers.google.com/android/nexus/images
As well, some have reported issues trying to flash JB if they had an old bootloader. Make sure you flash the LC03 bootloader before trying to flash a JB ROM. (It's already part of the guide mentioned above.)
Sent from my Galaxy Nexus using Tapatalk 2
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D
Hello all, my First post so please bear with me, Been using these forums for quite a while and all answers have been allready given, so no need to post... till now.
I have a Samsung Galaxy s3 i747 running android 4.1.2 OTA update and used CF-Autoroot. No problems there,
installed Rom manager, and cwm recovery touch. no problem
When I restart in recovery mode, also everything seems fine...
When I try to backup the phone however using cwm recovery it starts backing up everything including system but the just as it starts data the phone restarts.
Tried reinstalling cwm over and over different versions.. nada same result..
went into the settings to mount the various options as suggested to another user. same problem nada...
To be completely clear, I am trying to make a backup of my stock / rooted only Galaxy s3 i747 onto it's own storage NOT SDcard.
as I also could not figure that out either.
Any help would be greatly appreciated. -Erdericks1976
Sorry about misleading Subject. This is about making my first backup successfully..
Followup.
Well seems there are/were more problems here than I thought, it has begun randomly? restarting,..
Well. not Ramdomly. Whem specific apps are run it would restart.
I did a titanium backup and it would backup alot of the apps. but them would restart the phone when it got to 1 specific app.
I think I figured out what I did wrong here.
I have a Galaxy Note 2, and I may have flashed something from it by mistake......
so I have restarted my Gs3 From scratch Re-Following all instructions.. waiting to test and see if CWM works to back it up now..
It sure was faster with the Note2 rooted Kernel though. (if that was in fact what happend)
I'll update soon as its done..
Followup 2
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Erdericks1976 said:
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Click to expand...
Click to collapse
good for you, yu got it solved fast and easier than expected, XDA is your place for Android and root but also every kind of OS there is
anywz am not that old in XDA i joined in April and officially started rooting and modifying my phone since May and it has been great, bricked my phone 1st time but all in all i got the S3 in case for the loss. yu'll get used to this place and ROOT/custom roms
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
after rooting and during boot, I get the "Samsung Custom" with a unlocked padlock screen...so I assume that means it is unlocked??
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
Or are you talking about CARRIER unlocking the SIM? If so do you happen to have a reference for doing this to a Verizon Phone?
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
i got exact same problem only i can root my device so far any solution ?
Verizon locked bootloaders. I tried this with twrp and had that issue too
Sent from my SCH-I545 using xda app-developers app
I realize this a 2-year-old post, but would you happen to still have the stock firmware (I545VRUEMK2) for this thing? I have an older Jellybean unit that I need to fix (and want to keep JB as I can root it easily).
Thanks
I restored my stock backup and allowed the phone to do the ZVC update. In the past this always failed for some reason. This time it failed but I am now stuck in a continuous loop, always boots to CWM.
I'm pretty good about following instructions if someone could just point me in the right direction. I installed the Android SDK, hoping that would give me ADB and I could sideload but I'm just spinning my wheels and dont know where to start.
I have tried to restore a backup and also tried to install a rom, neither gets me past CWM.
ok, after some research, I installed a driver for my phone and now adb is working with my phone. Might have wasted my time with the SDK, dont know.
I tried flashing the ZVC radio but I'm still stuck in the CWM boot loop.
Well I've tried to flash everything I could find but nothing works, always boots to recovery. Ready to take a hammer to this phone!
cardboardbox said:
I restored my stock backup and allowed the phone to do the ZVC update. In the past this always failed for some reason. This time it failed but I am now stuck in a continuous loop, always boots to CWM.
I'm pretty good about following instructions if someone could just point me in the right direction. I installed the Android SDK, hoping that would give me ADB and I could sideload but I'm just spinning my wheels and dont know where to start.
I have tried to restore a backup and also tried to install a rom, neither gets me past CWM.
Click to expand...
Click to collapse
Have you tried this method? It helped me when I tried to undo the changes from freegee. If your phone has a working rom on it you can use this method if it wont boot. I basically messed up the recovery on mine and this fixed it.
http://forum.xda-developers.com/showthread.php?t=2230106
Once you get a recovery on your phone you can flash a rom if it still wont boot. If you want stock you can flash the zvc stock rom here: http://forum.xda-developers.com/showthread.php?t=2536636
dopy25 said:
Have you tried this method? It helped me when I tried to undo the changes from freegee. If your phone has a working rom on it you can use this method if it wont boot. I basically messed up the recovery on mine and this fixed it.
http://forum.xda-developers.com/showthread.php?t=2230106
Once you get a recovery on your phone you can flash a rom if it still wont boot. If you want stock you can flash the zvc stock rom here: http://forum.xda-developers.com/showthread.php?t=2536636
Click to expand...
Click to collapse
wow that was really easy! Thanks! Now I have TWRP 2.6 instead of the CWM I was using but no complaints as long as it works.
I still cant get the stock rom to upgrade OTA. After it downloads the Production ZVB to ZVC update (about 92mb) it tries to install it but always fails. I tried flashing the stock ZVC rom that can be found in the android dev sub forum but I had no data access even after selecting activate this device in settings. Any ideas?
cardboardbox said:
wow that was really easy! Thanks! Now I have TWRP 2.6 instead of the CWM I was using but no complaints as long as it works.
I still cant get the stock rom to upgrade OTA. After it downloads the Production ZVB to ZVC update (about 92mb) it tries to install it but always fails. I tried flashing the stock ZVC rom that can be found in the android dev sub forum but I had no data access even after selecting activate this device in settings. Any ideas?
Click to expand...
Click to collapse
You can find the zvc radio in the same place. Flash that since you were never on zvc. Or try restoring your EFS if everything is blanked out in about device of your settings.
Also since you have a working phone now, I like philz recovery. Flash it from inside twrp. At the moment I'm using a modified twrp to multi boot a few different ROMs but that's a little more advanced.
dopy25 said:
You can find the zvc radio in the same place. Flash that since you were never on zvc. Or try restoring your EFS if everything is blanked out in about device of your settings.
Also since you have a working phone now, I like philz recovery. Flash it from inside twrp. At the moment I'm using a modified twrp to multi boot a few different ROMs but that's a little more advanced.
Click to expand...
Click to collapse
yeah I did get the zvc radio but flashing it doesnt give me data when combined with the stock zvc rom. When flashing the ZVC radio I can see its labelled as ZVB but that might just be leftover from the previous flashable radio.
At this point I just need to figure out how to go back to the stock recovery and unroot so I can get OTA updates.
cardboardbox said:
yeah I did get the zvc radio but flashing it doesnt give me data when combined with the stock zvc rom. When flashing the ZVC radio I can see its labelled as ZVB but that might just be leftover from the previous flashable radio.
At this point I just need to figure out how to go back to the stock recovery and unroot so I can get OTA updates.
Click to expand...
Click to collapse
Why do you need the OTA? You now have the updated radio and ROM. ZVB radio is labeled ZVC and ZVC is the most current software. The ROM you just flashed is bone stock.
Now it's just a matter of getting data to work. Are all the numbers zeroed out? Also when you unlocked you should have an EFS backup to restore with.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Why do you need the OTA? You now have the updated radio and ROM. ZVB radio is labeled ZVC and ZVC is the most current software. The ROM you just flashed is bone stock.
Now it's just a matter of getting data to work. Are all the numbers zeroed out? Also when you unlocked you should have an EFS backup to restore with.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed. At this point there's no ota in sight over ZVC.
thanks for the help guys. Data works now, it was just real spotty at first. I kept trying "activate this device" until it finally worked consistently. I am concerned that it seems to lose data connection more often than before but I'd think if I flashed something wrong, or flashed the wrong radio, it wouldnt work at all, right? It wouldnt just be kind of crappy?
I'm sitting here at my desk watching the phone go from 3g to nothing to 3g to nothing, repeatedly. Changes at least once a minute.
cardboardbox said:
thanks for the help guys. Data works now, it was just real spotty at first. I kept trying "activate this device" until it finally worked consistently. I am concerned that it seems to lose data connection more often than before but I'd think if I flashed something wrong, or flashed the wrong radio, it wouldnt work at all, right? It wouldnt just be kind of crappy?
I'm sitting here at my desk watching the phone go from 3g to nothing to 3g to nothing, repeatedly. Changes at least once a minute.
Click to expand...
Click to collapse
Try going to Settings>More>Mobile networks>Network mode and tick CDMA. See if that helps. If it does and you want LTE, you'll need to do this every time. Just tick CDMA/LTE instead.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Try going to Settings>More>Mobile networks>Network mode and tick CDMA. See if that helps. If it does and you want LTE, you'll need to do this every time. Just tick CDMA/LTE instead.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It also sounds like a prl update is in order. But yes if you're not in an LTE area make due to check CDMA only because I have the same problem. Lose data like crazy when LTE/CDMA is selected. Have semi solid connection when only CDMA is selected.
Try updating prl and profile under system updates on stock.
When you do that, it'll put it back to LTE if it has weak service. So you might have to go back into Settings and make it CDMA again.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
When you do that, it'll put it back to LTE if it has weak service. So you might have to go back into Settings and make it CDMA again.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, every time I flash a rom I change to cdma only. I am nowhere close to an lte area, the closest is 30+ miles away in any direction. LTE kills my battery because it is always searching for LTE. Kind of sucks to get 4G back when I am actually in a market for it. But that shouldn't be a problem since I have been using the multiboot. What I had to do before was restore a stock backup and get a 4G lock after updating profile and prl, then restore the rom I want and I would have 4G.
Everything has been running pretty smooth for the past week but there is one issue that seems to be getting worse. When I turn on my phone I see the LG logo and then a blank, black screen with the backlight on. It will stay like this forever until I hold down the power button long enough to make the phone turn off. A week ago this happened occasionally but now its happening almost every time. In fact, today I cant get past it.
Any ideas?
cardboardbox said:
Everything has been running pretty smooth for the past week but there is one issue that seems to be getting worse. When I turn on my phone I see the LG logo and then a blank, black screen with the backlight on. It will stay like this forever until I hold down the power button long enough to make the phone turn off. A week ago this happened occasionally but now its happening almost every time. In fact, today I cant get past it.
Any ideas?
Click to expand...
Click to collapse
Try going to recovery and wiping cache. It won't clear any data if you don't select data. Try that and a reboot.
Are you still using stock? If so is it totally stock or do you have a custom kernel? <<< just curious, it shouldn't be relevant.
EDIT: did you use this thread to get stock? http://forum.xda-developers.com/showthread.php?t=2536636
@engine95 will correct me if I'm wrong but use the newest section,
the ont that says
New March 2 2014
New ZVC with all LG markings, kernel also. Only difference is it's rooted. YOU DO NOT HAVE TO UPDATE, unless you want to. With this, if you re-lock and then remove root, you will have a factory looking phone.
It is also zipaligned
New Download
Here's the Stock LG flashable kernel. All LG Markings
LG Stock Kernel
Click to expand...
Click to collapse
cardboardbox said:
Everything has been running pretty smooth for the past week but there is one issue that seems to be getting worse. When I turn on my phone I see the LG logo and then a blank, black screen with the backlight on. It will stay like this forever until I hold down the power button long enough to make the phone turn off. A week ago this happened occasionally but now its happening almost every time. In fact, today I cant get past it.
Any ideas?
Click to expand...
Click to collapse
Everything dopy25 said above ^^^^^^
I remember this happening in the past, but I not sure of the cure.
Either you need to wipe everything, SD included, and restore or start fresh.
Or
Its your unlock. You said you have the LG logo and that unlock will eventually go bad. You need to use the mako unlock, I think it's called. It'll have the Google logo on boot up.
All of our phones will need to use this unlock sometime, so that's the one Shelnutt2 recommends.
Read about it in the root guide.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
You said you have the LG logo
Click to expand...
Click to collapse
I use the ZCV ROM zip in your post I as my stock so I can update prl, and Everytime it boots I see the the Google unlock screen, the LG logo, then the sprint logo and 4G animation stuff.
I also use the multi boot method so it is actually a secondary rom that way I don't have to flash over just to update PRL, could that have something to do with it?
dopy25 said:
Try going to recovery and wiping cache. It won't clear any data if you don't select data. Try that and a reboot.
Are you still using stock? If so is it totally stock or do you have a custom kernel? <<< just curious, it shouldn't be relevant.
EDIT: did you use this thread to get stock? http://forum.xda-developers.com/showthread.php?t=2536636
@engine95 will correct me if I'm wrong but use the newest section,
the ont that says
Click to expand...
Click to collapse
Yes I used that thread. I also got the ZVC radio from the link at the top of that thread. When I flashed it I saw in the text that scrolls up during the flash that it was labelled ZVB radio. I still wonder about that...
I'm still stock, no custom kernel.
I went to recovery, but the first time I tried I did it wrong and the phone booted up normally for the first time today. I then wiped cache and restarted the phone 5 times without it getting stuck. If it was cache, does this tell you anything? Will I have to wipe it once a week?
engine95 said:
Everything dopy25 said above ^^^^^^
I remember this happening in the past, but I not sure of the cure.
Either you need to wipe everything, SD included, and restore or start fresh.
Or
Its your unlock. You said you have the LG logo and that unlock will eventually go bad. You need to use the mako unlock, I think it's called. It'll have the Google logo on boot up.
All of our phones will need to use this unlock sometime, so that's the one Shelnutt2 recommends.
Read about it in the root guide.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well dopy25's suggestion seems to have worked.
I'll read up about the mako unlock but maybe there is something weird about my phone. When I turn it on a normal boot goes like this:
1. LG logo for maybe .5 second or less
2. black screen with backlight on
3. black screen without backlight
4. LG logo again for 1 sec
5. Sprint animated 4GLTE logo
6. Done
1 through 4 are kind of strange. Maybe I should just have one LG logo?
cardboardbox said:
Yes I used that thread. I also got the ZVC radio from the link at the top of that thread. When I flashed it I saw in the text that scrolls up during the flash that it was labelled ZVB radio. I still wonder about that...
I'm still stock, no custom kernel.
I went to recovery, but the first time I tried I did it wrong and the phone booted up normally for the first time today. I then wiped cache and restarted the phone 5 times without it getting stuck. If it was cache, does this tell you anything? Will I have to wipe it once a week?
Well dopy25's suggestion seems to have worked.
I'll read up about the mako unlock but maybe there is something weird about my phone. When I turn it on a normal boot goes like this:
1. LG logo for maybe .5 second or less
2. black screen with backlight on
3. black screen without backlight
4. LG logo again for 1 sec
5. Sprint animated 4GLTE logo
6. Done
1 through 4 are kind of strange. Maybe I should just have one LG logo?
Click to expand...
Click to collapse
You shouldn't have to occasionally wipe cache (I think), the reason I suggested it is because I was unsure if you did when you flashed the zip the first (last) time. However it doesn't hurt as far as I know to wipe cache, it will basically refresh all the apps and junk on your phone and be a clean boot but still have all your apps installed.
As far as the 2 LG logo's at boot, that very well could be what engine95 was talking about when he said you might be on the old/temp unlock method. But I think you should be on the good unlock if you used the teeny bin.