Related
Not sure what it is but a couple of people on the Verizon Site say they are being pushed a update
Even though it say's ed05 on the PDF
It is EH03
Here is the updated PDF from Verizon.
That PDF is ED05 and not the update I just downloaded and applied.
Firmware version
2.3.5
Baseband version
S:i500.04 V.EH03
Kernel version
2.6.35.7
Build number
SCH-I500.EH03
I just opened it and is definitely EH03, you have to refresh the page if you have opened the pdf page from Verizon's site recently to make it show the correct page.
Here ya go: http://dl.dropbox.com/u/20768745/samsung_fascinate.pdf
good to know...was gonna be a tad irritated if it wasnt eh03 lol
First problem i have encountered is my picture share to bluetooth and then send to my computer keeps failing. I guess I will be doing a factory reset sooner than i had originally planned.
I have tried removing the device from the bluetooth list, but it seems i can't find delete anymore.
I have removed the phone from the computer, added it again, and still can't share pictures over the bluetooth. I will try a few other things later on after work.
Waiting to see how my battery life will be after streaming bluetooth music another 4 hours of my work day.
sd card encryption
Has anyone seen that the new GB update is supposed to contain SD card encryption? I have been waiting for that for the last year. Is it true and does it work?
I have the leaked eh03 package installed a few days ago on my phone, I was wondering if this OTA build is the same as the leaked one. Thanks!
Enetico said:
I have the leaked eh03 package installed a few days ago on my phone, I was wondering if this OTA build is the same as the leaked one. Thanks!
Click to expand...
Click to collapse
its the same (havent diffed it but id all but guarantee it) whenever a build is changed the version # changes...and this was in vzw's testing system for a few weeks, so it wouldnt have been changed, then updated with same name
nitsuj17 said:
its the same (havent diffed it but id all but guarantee it) whenever a build is changed the version # changes...and this was in vzw's testing system for a few weeks, so it wouldnt have been changed, then updated with same name
Click to expand...
Click to collapse
I checked the update pdf and it states the download manager app being included which is not in the leaked version, I am assuming that it might have other minor improvements. I have to wait for the OTA update to be posted to install, my phone has a bad esn and I believe that is the only way to install the new update. BTW, it might be too early but does anyone know where I can download the OTA update. Thanks!
Does this version of GB still have all the Bing integration built-in?
brazilian812 said:
Does this version of GB still have all the Bing integration built-in?
Click to expand...
Click to collapse
Yes it does.
Samsung & Verizon... slow down already for crying out loud. We barely got froyo 7 months ago and now you're releasing Gb only a year after the source was released! Can't take it anymore !
"the relentless pursuit of the perfect rom"
nitsuj17 said:
its the same (havent diffed it but id all but guarantee it) whenever a build is changed the version # changes...and this was in vzw's testing system for a few weeks, so it wouldnt have been changed, then updated with same name
Click to expand...
Click to collapse
I thought the same thing but the changelog pdf says the update includes an sd card encryption option. Has anyone seen or found this?
Enetico said:
I checked the update pdf and it states the download manager app being included which is not in the leaked version, I am assuming that it might have other minor improvements. I have to wait for the OTA update to be posted to install, my phone has a bad esn and I believe that is the only way to install the new update. BTW, it might be too early but does anyone know where I can download the OTA update. Thanks!
Click to expand...
Click to collapse
iirc download manager was in the full leak
skiddingus said:
I thought the same thing but the changelog pdf says the update includes an sd card encryption option. Has anyone seen or found this?
Click to expand...
Click to collapse
then someone pull it from their phone and ill diff it
So I rooted my wife's Fascinate and put CWM on it (no change in ROM other than root+recovery), and when I try to install this update it just boots to CWM. I figure it is trying to call a command to the original recovery which isn't there anymore.
Does anyone know how I can get this update under my strange configuration? This is probably the weirdest question ever, but can I flash the stock recovery back??
nm3210 said:
So I rooted my wife's Fascinate and put CWM on it (no change in ROM other than root+recovery), and when I try to install this update it just boots to CWM. I figure it is trying to call a command to the original recovery which isn't there anymore.
Does anyone know how I can get this update under my strange configuration? This is probably the weirdest question ever, but can I flash the stock recovery back??
Click to expand...
Click to collapse
Odin back to ed05 which is the latest VZW release. (Package by pentafive). Let it fully load, then try to push the update through settings, about phone, system update.
I don't see the point in doing this but that's how I would do it
"the relentless pursuit of the perfect rom"
nm3210 said:
So I rooted my wife's Fascinate and put CWM on it (no change in ROM other than root+recovery), and when I try to install this update it just boots to CWM. I figure it is trying to call a command to the original recovery which isn't there anymore.
Does anyone know how I can get this update under my strange configuration? This is probably the weirdest question ever, but can I flash the stock recovery back??
Click to expand...
Click to collapse
This is the package thread url
http://forum.xda-developers.com/showthread.php?t=1013312
"the relentless pursuit of the perfect rom"
Yeah I was trying to do it without wiping anything, shrug.
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
hammerchucker said:
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
Click to expand...
Click to collapse
Sorry to hear that you have this issue. What happens when you install and update manually? Have you tried doing a full wipe, flashing an older version from like two days ago and update from OpenDelta. To see if the issue is still there. (Remember to make a Nandroid backup before doing this or you will lose your data)
Let me know,
hammerchucker said:
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
Click to expand...
Click to collapse
You posted several times, well you probably posted in the wrong place. We have a bug report website at http://jira.omnirom.org and your issue has never been brought to my attention.
I doubt everyone with the Note 2 has no mobile services, so have you at least checked common locations like APN settings?
XpLoDWilD said:
You posted several times, well you probably posted in the wrong place. We have a bug report website at http://jira.omnirom.org and your issue has never been brought to my attention.
I doubt everyone with the Note 2 has no mobile services, so have you at least checked common locations like APN settings?
Click to expand...
Click to collapse
That's a Sprint device so it may suffer from "odd" issues other Note2 variants don't have... I need to look into it but Utkarsh may have been blind-supporting the L900 in which case we may need to pull that device until it gets a proper maintainer who actually owns the device.
Entropy512 said:
That's a Sprint device so it may suffer from "odd" issues other Note2 variants don't have... I need to look into it but Utkarsh may have been blind-supporting the L900 in which case we may need to pull that device until it gets a proper maintainer who actually owns the device.
Click to expand...
Click to collapse
I can only vouch for my L900 Note2, but it runs Omni nightlies swimmingly...on the L900 boards I've seen several reports of oddities with 4.4 ROMs, most commonly from people who did the rooted de-Knoxed 4.3 update with a "wifi fix".
It ain't a baseband thing...as I have the MK4 (latest) baseband....and I've never flashed a full 4.3 OTA ROM be it stock OTA or rooted with that "fix".
Skripka said:
I can only vouch for my L900 Note2, but it runs Omni nightlies swimmingly...on the L900 boards I've seen several reports of oddities with 4.4 ROMs, most commonly from people who did the rooted de-Knoxed 4.3 update with a "wifi fix".
It ain't a baseband thing...as I have the MK4 (latest) baseband....and I've never flashed a full 4.3 OTA ROM be it stock OTA or rooted with that "fix".
Click to expand...
Click to collapse
OK, so only some people are having these issues... Weird. If it's working for most people and there's someone actually fixing reproducible issues, then the device goes on.
SELinux Mode Changer is the answer
Entropy512 said:
OK, so only some people are having these issues... Weird. If it's working for most people and there's someone actually fixing reproducible issues, then the device goes on.
Click to expand...
Click to collapse
I had same issue with my n7105. After surfing through the web, I found the answer as "SELinux mode changer". If you had a 4.3 with Knox installed earlier, you might face this issue. Its because by default SELinux mode is 'Enforcing' and I had to change it to 'Permissive'. After that it works fine.
I also had trouble with SuperSU, so had to apply .zip from TWRP.
hope this helps
I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome
Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)
Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app
killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.
This does not happen at all to me(using stock 5.1 with Franco Kernel).
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).
Your battery is dying, I've been getting the same problem until I replaced the battery today.
richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?
I've been getting the same issues on my N7 since updating.
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.
Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng
gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.
I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk
Finally some attention from Verizon! Aside from the obvious fact that the few of us still with Vk810's, I'm also looking forward to a few of the development projects finally having what they need to complete.
http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
KDZ http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1C0KL032R7A3O65BE508U/VK81035A_08.kdz
When???
Looked at the pdf and (unless I missed it) there is no date availability indicated.
Just tried my update feature and it says my software is currently up-to-date with 24A!
Obviously verizon will do their usual "it will come when it comes"!
rant said:
Finally some attention from Verizon! Aside from the obvious fact that the few of us still with Vk810's, I'm also looking forward to a few of the development projects finally having what they need to complete.
http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
Click to expand...
Click to collapse
harryzee said:
Looked at the pdf and (unless I missed it) there is no date availability indicated.
Just tried my update feature and it says my software is currently up-to-date with 24A!
Click to expand...
Click to collapse
It's common for KDZs of official releases to be available before the OTAs get sent out. First they create the KDZ, and then they create the "diff" files necessary to OTA from the last official update (24A_00) to the newest official update. That said, I never believe that a release is official and final until everything else arrives, but that doesn't keep me from flashing it. The presence of the KDZ and of the PDF give good evidence this is final official. On the VS985 G3, we had three leaks of lollipop, 23A, 23B and 23C_00. Then the official release was 23C_01. Sometimes someone is able to get a hold of a leak's OTA file, but not for more than a few users here and there, as what happened on the VS985.
Even once the OTA is made it's very often not rolled out to everyone at once, it's staggered. So while your IMEI (and mine) might say no update, there may be other IMEIs of VK810.4Gs which do report 35A_08 as an available update. I don't think we're sure if they go in numerical order of IMEI or what determines what order they go in.
We might not see the OTA for weeks. Who knows.
You can use LG Mobile Tool 2014 (not the official LG/Verizon flash tool) on a Windows PC to flash this 35A_08 KDZ. You can try "Normal" mode which will keep your data, or "CSE" mode which will wipe everything including internal storage (not the additional Micro SD card).
roirraW "edor" ehT said:
You can use LG Mobile Tool 2014 (not the official LG/Verizon flash tool) on a Windows PC to flash this 35A_08 KDZ. You can try "Normal" mode which will keep your data, or "CSE" mode which will wipe everything including internal storage (not the additional Micro SD card).
Click to expand...
Click to collapse
It amazes me that the Verizon VK810 got this update before the V500. Although thinking back on it we did get a Korean "leak" as well...
muiriddin said:
It amazes me that the Verizon VK810 got this update before the V500. Although thinking back on it we did get a Korean "leak" as well...
Click to expand...
Click to collapse
It amazes me, too! Not expected at all. Maybe they work best when hordes aren't clamoring for an update, kinda like our generous devs here on XDA.
Update Concern
roirraW "edor" ehT said:
It amazes me, too! Not expected at all. Maybe they work best when hordes aren't clamoring for an update, kinda like our generous devs here on XDA.
Click to expand...
Click to collapse
Is anyone "concerned" over the wifi issue with the LG G3 update (5.01) that may or may not impact the gPad?
I have kept both my Lg G3 and gPad "stock" this time around and when the G3 updated a short time ago, I could connect with but no longer utilize my home wifi. I have to connect to another close by xfinity wifi in our condo unit that is open and it works fine!
There is a supposed work around that I am just too stubborn to do it as I wish to remain stock with these two units. Those of us impacted by the Verizon/LG issue (apparently "legions") are still waiting for a fix to be uploaded which as of today is still not forthcoming.
However, this experience concerns me regarding this update for the gPad unless the 5.02 has taken care of the 5.01 issue.
harryzee said:
Is anyone "concerned" over the wifi issue with the LG G3 update (5.01) that may or may not impact the gPad?
I have kept both my Lg G3 and gPad "stock" this time around and when the G3 updated a short time ago, I could connect with but no longer utilize my home wifi. I have to connect to another close by xfinity wifi in our condo unit that is open and it works fine!
There is a supposed work around that I am just too stubborn to do it as I wish to remain stock with these two units. Those of us impacted by the Verizon/LG issue (apparently "legions") are still waiting for a fix to be uploaded which as of today is still not forthcoming.
However, this experience concerns me regarding this update for the gPad unless the 5.02 has taken care of the 5.01 issue.
Click to expand...
Click to collapse
I just wanted to chime in that I likely won't be able to test whether this too will have the WIFI issue since I haven't had the issue on my Verizon G3 at home, work or elsewhere. I know it's real, I've just been lucky. Someone else will have to let us know.
You can always roll back to 24A_00 or any other KDZ though, just as on the G3.
KyPbP said:
KDZ http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1C0KL032R7A3O65BE508U/VK81035A_08.kdz
Click to expand...
Click to collapse
<3
I installed it, seems to work fine after a cache wipe. I did lose root.
roirraW "edor" ehT said:
I just wanted to chime in that I likely won't be able to test whether this too will have the WIFI issue since I haven't had the issue on my Verizon G3 at home, work or elsewhere. I know it's real, I've just been lucky. Someone else will have to let us know.
You can always roll back to 24A_00 or any other KDZ though, just as on the G3.
Click to expand...
Click to collapse
I have been unable to have my Verizon G3 at home reproduce this issue either. I do not doubt that the problem exists, unfortunately I am unable to determine if the problem also occurs on a G-Pad (V500). I have a V500 with the Korean lollipop release installed and am testing it currently, trying to see if I am going to run the US Image stock when it is released. The wifi issue as I have read about in the Verizon G3 forums does not appear to occur for me on my wifi access points.
;60871525 said:
I installed it, seems to work fine after a cache wipe. I did lose root.
Click to expand...
Click to collapse
If you want root on 35A_08, you can roll back to (flash) the 24A KDZ, re-root with Stump, go through the brief hoopla to get TWRP installed (I've done it so many times I don't know it like the back of my hand but I'm very comfortable with it), and flash my completely stock ROM that's almost done uploading in the Development section. You WILL have to separately flash the latest SuperSU.zip by @Chainfire (detailed and links in my ROM OP) to have root before you leave your custom recovery.
I saw yesterday that the update was rolling out. Manually checked on the tablet twice this morning and it said no update available. Then, not a half an hour later I got the OTA notification. Just finished downloading and updating itself - took about 40 minutes. I did lose Root.
After I finished downloading the kdz file and checked again then I got the OTA version. It took 2-3 reboots after I finished installing before the lag went away. Now it is faster than ever.
Sent from my VK810 4G using XDA Free mobile app
Lollipop OTA Success
rfarrah said:
I saw yesterday that the update was rolling out. Manually checked on the tablet twice this morning and it said no update available. Then, not a half an hour later I got the OTA notification. Just finished downloading and updating itself - took about 40 minutes. I did lose Root.
Click to expand...
Click to collapse
My update came through this (5/21) afternoon.
Absolutely no problems or issues with the download or install.
Running smoothly with v 5.02 and with absolutely NO issues with my home wifi!
Now if only Verizon and LG would pull their collective heads for their collective orifices and put out a v. 5.02 for the LG G3 to correct the wifi issues with 5.01, I would feel my life had been fulfilled!
Absolutely no WiFi issues with the gPad update so "go figure"!
Running nicely, but work to get installed
Got it installed and it appears to be running well. I will post more when I have had some more time with it and tested more features.
I did have a tough time getting it installed, probably because I was rooted. I was getting "Err 0x13e" on the updater screen and then error 402 when it rebooted into KK and said it failed.
What I did to get it installed:
- Unrooted - still errors
- Used Verizon upgrade software to "repair" the tablet
- download LG drivers and install
- connect tablet and run installer that is mounted on Windows
- Repair stated that it would preserve data, etc., then said that method failed and it would need to erase data to repair
- Chugged for a while repairing and succeeded
- On reboot, it was still running KK and all of my data was still intact (hmmm...but good)
- Then, updated to LP with the OTA
The Verizon tool doesn't even install for me. It says installing, then it disappears.
Edit: Never mind, Lollipop's up and booting
Hello guys.... this is one of my first posts here so go easy on me...
Trying to get to the bottom of an issue I'm experiencing on my Nexus 4 16GB after updating.
So I had been postponing updating to Lollipop for months... (was still on 4.4.4 stock cuz I didn't quite like the new UI) and decided to update Sunday (Aug 10th) morning. Big mistake, apparently.
The OTA 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome! Regular google apps are generally non-responsive and supper laggy.
For Ex: Can't open Play Store, the app tries to open but all I see is a white app window,same with Photos, or maps... ironically Whatsapp and certain other non-google apps are opening.
So I currently can't even use my N4 much, I'm trying to find out a what's causing this and if I need to revert the upgrade or flash a ROM or something,
My 4.4.4 was rooted FWIW, and now it's not. Not sure if it's helpful, but I have about 1.3GB free internal storage, and 1GB free memory when I run. So I don't think the issues are being caused by an app I installed or some service running wild. Any help is appreciated, thanks!
combatplane57 said:
Hello guys.... this is one of my first posts here so go easy on me...
Trying to get to the bottom of an issue I'm experiencing on my Nexus 4 16GB after updating.
So I had been postponing updating to Lollipop for months... (was still on 4.4.4 stock cuz I didn't quite like the new UI) and decided to update Sunday (Aug 10th) morning. Big mistake, apparently.
The OTA 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome! Regular google apps are generally non-responsive and supper laggy.
For Ex: Can't open Play Store, the app tries to open but all I see is a white app window,same with Photos, or maps... ironically Whatsapp and certain other non-google apps are opening.
So I currently can't even use my N4 much, I'm trying to find out a what's causing this and if I need to revert the upgrade or flash a ROM or something,
My 4.4.4 was rooted FWIW, and now it's not. Not sure if it's helpful, but I have about 1.3GB free internal storage, and 1GB free memory when I run. So I don't think the issues are being caused by an app I installed or some service running wild. Any help is appreciated, thanks!
Click to expand...
Click to collapse
You could try flashing a factory image of 5.0.1 and see if that helps.
theminikiller said:
You could try flashing a factory image of 5.0.1 and see if that helps.
Click to expand...
Click to collapse
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
combatplane57 said:
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
Click to expand...
Click to collapse
If you're rooted ota's won't work
Sent from my Nexus 9 using XDA Free mobile app
combatplane57 said:
Thanks. Yeah, this seems to have fixed it. Factory flashed it with the stock 5.0.1. Had to wipe it clean but a working phone is a working phone.
So it seems that if you're unlocked and rooted, you're shouldn't install OTA updates?
I read somewhere here (can't find the link rite now) that after 5.0, the OTA updates don't work right, if it detects the bootloader has been unlocked and/or you're rooted? Is this correct?
Click to expand...
Click to collapse
You might try upgrading to 5.1.1 LMY48I, it is all the bug fixes for 5.+, and should be more stable.