Related
Is there a way to stop the auto updates on Rezound?
I have a bionic, and might sell it since I'm a HTC fan and love HTCs. But the biggest problem I have ran into is the auto updates not updating since I ran the root/custom ROM thing on the phone. I had it plugged in last night and woke up to my boss banging on my door to wake up for work since it tried to auto update. If I can just disable the automatic OTA updates I would be happy.
I'm sure there's a simple setting to change somewhere...and I apologize since I haven't had acomputer for like a year and I have only spent the year before programming so the only thing I really know mobile wise is Windows Mobile... Sadly, I miss WinMo lol.
/Help an old man.
Edit: by not updating I mean it will try to update automatically without my permission, and will load the bootloader screen and will just error out on the bootloader screen and will not reboot the phone so my alarms will not go off in the morning... I cannot have this. if this is the case, the rezound is for sale tomorrow...but I don't want it to be. I know there has to be a simple setting somewhere...
Edit2: I really need to change my signature lol. I haven't changed it in 2+ years.
codybear said:
Is there a way to stop the auto updates on Rezound?
I have a bionic, and might sell it since I'm a HTC fan and love HTCs. But the biggest problem I have ran into is the auto updates not updating since I ran the root/custom ROM thing on the phone. I had it plugged in last night and woke up to my boss banging on my door to wake up for work since it tried to auto update. If I can just disable the automatic OTA updates I would be happy.
I'm sure there's a simple setting to change somewhere...and I apologize since I haven't had acomputer for like a year and I have only spent the year before programming so the only thing I really know mobile wise is Windows Mobile... Sadly, I miss WinMo lol.
/Help an old man.
Edit: by not updating I mean it will try to update automatically without my permission, and will load the bootloader screen and will just error out on the bootloader screen and will not reboot the phone so my alarms will not go off in the morning... I cannot have this. if this is the case, the rezound is for sale tomorrow...but I don't want it to be. I know there has to be a simple setting somewhere...
Edit2: I really need to change my signature lol. I haven't changed it in 2+ years.
Click to expand...
Click to collapse
whats auto updating ???? your apps or your phone firmware ????
charismakid said:
whats auto updating ???? your apps or your phone firmware ????
Click to expand...
Click to collapse
phone firmware. It tries to update the phone firmware and has been with some
BS update I already have in my rom but it boots into the bootloader and fails there and stays in the bootloader and just chills in the bootloader all night. Which causes my boss banging on my door ten minutes before my shift. lol.
codybear said:
phone firmware. It tries to update the phone firmware and has been with some
BS update I already have in my rom but it boots into the bootloader and fails there and stays in the bootloader and just chills in the bootloader all night. Which causes my boss banging on my door ten minutes before my shift. lol.
Click to expand...
Click to collapse
Should only try to update if it detects your firmware version as 1.02.605.6, the first Gingerbread build that shipped with the phone. It is trying to apply the 2.01.605.11 Over-The-Air update from February, the latest official build released.
Usually fails from being on a Custom ROM, low battery, or bad download. Aside from stock ROM, only had this update issue on one old custom GB ROM from the Development section.
So, what ROM setup do you have? There is probably a solution on the forum to edit build.prop firmware version or something to get the update refused. Will take a look. Long term solution is to back up data and update to a newer GB ROM based on the OTA firmware, or do all the stuff to get ICS, Unlock the phone, and S-off once you read up more.
i was once on winmo too i had an omnia but if you have a custom rom on the rezound it will not update
First off, thanks for the replies. Been busy with work lately and haven't had a chance to hop back on to reply.
PhantasmRezound said:
Should only try to update if it detects your firmware version as 1.02.605.6, the first Gingerbread build that shipped with the phone. It is trying to apply the 2.01.605.11 Over-The-Air update from February, the latest official build released.
Usually fails from being on a Custom ROM, low battery, or bad download. Aside from stock ROM, only had this update issue on one old custom GB ROM from the Development section.
So, what ROM setup do you have? There is probably a solution on the forum to edit build.prop firmware version or something to get the update refused. Will take a look. Long term solution is to back up data and update to a newer GB ROM based on the OTA firmware, or do all the stuff to get ICS, Unlock the phone, and S-off once you read up more.
Click to expand...
Click to collapse
You know, I spaced that out. I know I was running the latest before I flashed it, and I just assumed it was an up to date ROM. I'll have to check and see what version of GB it is, otherwise I'll just get a ICS ROM on it this weekend since I have time. I guess that's what you get for rushing through and doing it drunk.
I am running the Business Gingersense ROM btw.
yojoe600 said:
i was once on winmo too i had an omnia but if you have a custom rom on the rezound it will not update
Click to expand...
Click to collapse
It attempts to update, but boots into the recovery (I think I might have said bootloader in my OP), and then fails to install the update due to the custom ROM, but sits in the recovery menu and does not reboot automatically.
But I think the post above yours explained why it was happening...I was assuming it was an up to date GB ROM since I read the update was from February and it's been a few months, but now that I have time this weekend I'll be able to get things fixed.
Thanks again to both of you for replies. (And sorry for the bump in the threads guys)
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
JeansenVaars said:
Hi all, I have a Z5C E8305, it just updated to 7.1.1 latest release xx.160.
Since then my battery lasts much less, everything is leggy, even whatsapp or camera, and for instance, switching out from chrome and going back again, lost the current page and caused a reload (before it didn't, for example for form completing).
I tried Sony companion for a repair, and it is actually much less leggy, but still slow, higher ram usage, battery drains and chrome cache resets and is slow on window switching (actually any window reloads when switching now) and slow icon loading when hiding all windows.
I read a lot through rooting but it is way too painful (unlocking bootloader, rooting, wrtp or clocked flash boot plus flash new room, too much for me and it didn't really work smoothly when I tried)
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
cyberwytch said:
LineageOS is definitely better right now for most things than the official 7.1.1. I actually just switched from LineageOS 7.1.1 to stock 7.1.1, hated it, and actually downgraded to stock 6.0.1 with Xposed. I feel like that gives me the most control, but I might switch back to LineageOS depending on if they start doing nightlies or anything interesting like that.
Click to expand...
Click to collapse
I'd love to try it, but unlocking bootloader plus installing a new one (clockwork or the other one), plus the mix up between my non-standard edition E8305 and most current release not being any guides up-to date. Its daunting for a newcomer like me.
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
sky.walker said:
I saw on Sony's website forums that a factory reset helped with battery and memory usage. I am going to try that when I have a few days off as the lag is annoying me. But I also have audio stutters when listening to music and audio books now.
Click to expand...
Click to collapse
Clean install is your best bet in fixing most issues
Factory reset helped at first but after a week of using it it became slow again
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
cyberwytch said:
No matter what I did, full wipe in FlashTool included, 7.1.1 never had any free ram and I could only background one, maybe two apps. Everything was slower than I've ever seen in a stock rom in any device I've owned!
Currently I've reverted to 6.0.1 and it provides a pleasing combination of speed, battery life, and tweakability with xposed.
Yesterday I took a gander at patching the one xposed feature I actually need into 7.0, but I gave up after a few hours. Maybe I'll try another weekend sometime, but writing/debugging smali is painful! I think I'll just stay on 6 for now and hope xposed makes it to 7 someday!
Click to expand...
Click to collapse
Any chance you can help me revert to 6 or 7.0?
JeansenVaars said:
Any chance you can help me revert to 6 or 7.0?
Click to expand...
Click to collapse
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
try disable Movie Creator app
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks. Im back to 5.1.1 and running smooth. Not sure how long to wait before giving Last version another shot
JeansenVaars said:
What is the next thing I can do? I wouldn't mind using either LineageOS if it is easy to install otherwise I'll be gold with 7.0 again
Thanks,
Jv
Click to expand...
Click to collapse
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
mceyhan4 said:
try disable Movie Creator app
Click to expand...
Click to collapse
sky.walker said:
I did this; copied from the sony forums:
"Android 7.1.1 is not the culprit, but the recently updated Movie Creator app!
1: Disable MOVIE CREATOR
2: Reboot in SAFE MODE
(while phone is on, press Power button, hold Reboot option for 1 second)
3: Reboot again to normal mode
4: Enjoy 2 days of standby time"
My phone seems much better now.
I also disabled the Sony music app as I was having audio troubles, but not sure if it was necessary.
Click to expand...
Click to collapse
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
what was firmware just prior to 32.4.A.0.160 (7.1.1) ???
Hello could you kind folks please guide me what was official (not rooted) Sony Z5C firmware prior to the above monster? I want to go back but don't know which one it was? Please link me to official version just before this latest ( 32.4.A.0.160 (7.1.1)) NASTY update! Many Thanks.
JeansenVaars said:
You guys think the guilty was the movie creator? My phone was barely usable. Full ram usage, battery drain and everything was laggy and hanging
Click to expand...
Click to collapse
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
BlackFriar said:
Yes, surprisingly.
I went from ~15MB of free memory (and the associated problems complained about: laggy transitions, program openings, home page icons, etc). back to ~250-300MB free and typical performance.
Actually usable performance is a little better given they have one of the cortex A57's more aggressively clocked.
I'd try. You can always restore if you desperately want Movie Creator and see no benefit.
Click to expand...
Click to collapse
What about the issue with browser page reloading every time you switch to a different app and then back again to the browser? OP reported this issue, and I've been having it, too. Did that get resolved for you with the disabled Movie Creator crap?
trax7 said:
1. Just backup everything you need (backing up whole apps isnt recommended though when you switch android versions).
2. Download and install Flashtool.
3. Open XperiFirm from inside Flashtool, select and download the firmware you need. It will bundle it automatically in a flashable ftf file.
4. Once you are sure you backed up everything, flash away.
Wipe everything. If you have TWRP and dont want to lose it, dont wipe FOTAKernel.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Sent from my E5823 using Tapatalk
Superrman said:
camera not as good without stock roms (unless install&backup DRM\FIX ) which not so easy
BUT you can roll back with fashtool without unlock btloader (im staying witch stock 7.0) untill sony fix(if they'll fix), or warranty is over.. which will comes 1st
Click to expand...
Click to collapse
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Kiers said:
can you give link to the official flashtool and where to get ftf 7.0 android file for sony z5c?
Click to expand...
Click to collapse
Google "Flashtool" - it's literally the first result there. Also, Flashtool has XperiFirm, which can download almost all firmwares for Xperias and pack them into ftf format automatically.
---------- Post added at 05:40 PM ---------- Previous post was at 05:38 PM ----------
Tomixxon said:
Wait. So can you actually downgrade with bootloader locked? I'm asking because I'd like to keep my ta partition untouched.
Click to expand...
Click to collapse
Yes, just flash an older version with Flashtool, it's how we got TA backup to be possible
About This Rom
This is a debloated stock rom based on stock F800K_30H. Most likely the last update the V20 will get.
Installation Procedure for F800 L/K/S
Download the F800***.7z to a PC and extract with 7-zip app on Windows PC or the equivalent on OSX / Linux . This will expand to a single 6GB system.img file. Copy over to internal storage on your device.
Update TRWP recovery to 3.4.x.x using TWRP.
Download also the F800 boot imgage and F800K-ezv2020.zip kernel.
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Boot into twrp and flash the system image.
Install>Install_Image(bottom right)>navigate to system.img file and select system image partition.
Repeat the same procedure for the boot.img, flash on boot partition.
Flash ezV2020 Kernel and then Magisk. Done.
If you are coming from Oreo download also the Pie partitions and flash that first, then as above. Also wipe data so have your apps backed up.
In the case your were already on PIE no need to wipe data but do wipe Dalvik / ART cache and Cache in TWRP before reboot. Device will be slow for a while and will speed up as Dalvik cache is rebuilt in the background. Sometimes that can take a while especially if you don't let the device rest.
==========================================================
Update Nov 2022: You now need to flash in twrp this Chrome update to pass initial setup screen after phone reset or fresh flash.
F800 - Google Drive
drive.google.com
Release v2
This is based on K rather than L for no good reason (new: flash the K partitions in my repo and ezv2020 K kernel), but makes no difference as all carrier apps have been deleted. This is a 'start again' version rather than an update to ver 1 and is recommended to update due to reports of better performance.
Added
QLens
V30 and G6 themes ( I like the black one with dark grey accents)
Sim unlock app (I think it's for phones locked to sim, not sure if it is or if it works)
Wap Push Service (for carrier settings sent via text msg)
Collage Wallpapers from G6 - only works on Lock Screen, dunno why, i'll try fix.
LG Smart World. You must hide it in Magisk first, then software update. Don't know how to change Korean language, sorry.
If you don't care for any of these additions delete them from /system/product/app , using a root browser
RCT (root check tool) remover has already been applied.
Known issues (minor)
Touch screen is not responsive after coming out of Laf Download Mode at times. To recover this simply reboot into recovery and reboot. It's not that serious and doesn't occur after a normal reboot. You just need to be aware of the fix in case you experience it.
If you have any apn issues do the 'reset apn settings to default' in the apn settings menu. Cuz my carrier apn didn't show up initially.
==========================================================
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
TarAntonio said:
After 3 flashed now your files worked. By one hour without reboot or chrash. Pie is very nice and you have super debloated the stock rom. Only calendar app Google crash. Normally i used lg calendar. Congratulations. Saturday i will test with my sim
Click to expand...
Click to collapse
Install Mixploer from here http://mixplorer.com/
Download the attachment provided and extract the folder to Internal Storage
Using Mixplorer copy and paste the Folder named LGCalendarProvider to...
root>system>product>priv-app
(you may be asked to grant root permission here)
Make sure you can see the LGCalendarProvider Folder is in priv-app folder, now reboot.
Google calendar is working for me now.
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
TheRoyalDuke said:
Thank you. I did not try mobile data but i crossflashed and can confirm that everything else works, including wifi on the H910. I'm so excited to have stock pie with root on the V20.
Click to expand...
Click to collapse
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
ezzony said:
Great!
I did think wifi files needed to be adapted per device but this may not be for all devices. Hard for me to know which is why it is good people report back their findings, thanks. Hows bluetooth?
Click to expand...
Click to collapse
Bluetooth works fantanstic. Connected my portable speaker and it played smoothly, never disconnected.
TheRoyalDuke said:
Edit: F800L30H_Partitions is needed to get fingerprint working.
Click to expand...
Click to collapse
Thanks for that. It might be just the modem that is needed. Can you get into download mode after flashing the partitions? Be careful. That is why I said in the OP don't flash Pie Partitions on non-F800 although you may not have seen that as I added it later.
I have a zip somewhere to flash back oreo partitions. I'll upload it later.
edit: just checked my us996, fingerprint is working fine without flashing pie partitions. Please delete your edit as I don't want anyone flashing pie partitions on non-f800 devices because of the laf download problem.
I will have to figure out what exactly is going on but until then I don't support of advise anyone to flash Pie partitions on any non-F800 device.
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
TheRoyalDuke said:
I can get into download mode but the screen is static. Dont really care, tbh, because this is my spare phone. As long as i have stock pie and TWRP, i'm happy.
Click to expand...
Click to collapse
Ah good. Because there was an issue with the new Pie LG LAF (download mode) not being detected in LGUP. Experienced that myself. The danger is then if you accidentally deleted TWRP or somehow got corrupted there would be no way to ever flash the phone again and you'd be stuck with what you have. That is why I'm being extra cautions.
Note:
I still don't advise anyone to flash pie partitions on non-f800. There are so many variants it's not certain or knowable if all will be okay for all of them.
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloated right?
xxseva44 said:
Just to confirm, for the us996 we need to flash the f800L_30H_BOOT img, oreo4pie and the f800L_30H_Debloat right?
Click to expand...
Click to collapse
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
ezzony said:
You need to do exactly the same as you did last time. Sorry I haven't gotten around to providing instructions, I'll do it soon. The part you are missing is you need to flash the us996-ezv2020 pie kernel after you flash the f800l_boot.img. Do not flash the partitions for non-f800.
Click to expand...
Click to collapse
Ahh okay, thx for letting me know
Edit: So i flashed it and at first it was very stable but then it crashed to that green apps watchdog bark, i then rebooted and it crashed and showed the purple secure watchdog bite screen a couple of seconds after unlocking the phone. not sure if this is relevant but when it crashed it was downloading about 40 apps, and i was trying to log into instagram. Maybe it was just a fluke, i'll see if it happens again
Edit2: So i rebooted and everything seems fine again
Edit3: okay so it crahsed again, same thing happened, it crashed to the green watchdog bark screen although this time it went from that screen to the purple watchdog bite screen without rebooting or anything. When it crashed, i went to unlock it and it froze while i was unlocking the phone
Could this have anything to do with the fact that my phone was originally a vs995? Cuz i converted it to a us996, I noticed that there was a vs995 pie kernel, should i flash that and see if the crashes stop? I'm not too sure if it would do anything especially since i was running alpha omega oreo with your us996 oreo kernel just fine but it's worth a shot but just to be sure, for now i'll reflash the us996 kernel again and see if the crashes return
update: It worked fine for the past hour but crashed to the watchdog bite screen again, i'll try flashing the vs995 pie kernel and see if the crashes stop. Okay so i successfully flashed it, now i just have to wait and see
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
xxseva44 said:
Ahh okay, thx for letting me know
Update: success, 2 hours with no crashes, the vs995 pie kernel fixed my issue
T.L.D.R: I flashed the us996 kernel on my vs995 converted to a us996 which in theory should have worked but didn't, which resulted in random crashes
Click to expand...
Click to collapse
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
ezzony said:
That's odd. My device is the same as yours. A vs995 crossflashed to us996. Had no issue with the us996_santa-ezV2020 kernel. Hasn't crashed once, working very well, very fast and smooth.
I have uploaded the us996 oreo partitions as a flashable zip, if you or anyone needs it. Say you want to flash back oreo easily. If staying on Pie you'd have flash back the F800 boot.img and us996 kernel.
No need to do anything yourself if it's working fine.
Click to expand...
Click to collapse
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
TheRoyalDuke said:
Although the fingerprints worked after flashing the f800 partitions on my h910, the kernel would constantly crash. So i pulled modem from my oreo dump and flashed it in TWRP. This time fingerprint stopped working but my phone hasn't crashed in hours. I also inserted a sim card to test mobile data, it did not work. However, i was able to make phone calls and send a text message. Thank you so much for this rom.
Click to expand...
Click to collapse
You could try flashing the modem only. The pie modem, in twrp. I'd be curious to know what would happen. I have just uploaded it. Worth a try. The fingerprint for some reason uses files in the modem partition. Why there are there I don't know.
Be advised everyone all this mixing and matching pie with oreo may result in unforeseeable negatives. We can only know what works by trial and error. And, your welcome!
xxseva44 said:
Yea i was also confused, especially since i was running your oreo kernel just fine with alpha omega but it worked, Either way this rom is running very smooth and fast. I also did a geekbench 5 run and to my surprise, it preforms better with a single core score of 340 and multi core of 704 compared to 286 single and 636 multicore, But anyways thx for developing this for us v20 users
Click to expand...
Click to collapse
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
ezzony said:
You didn't get the us996Santa oreo and Pie us996Santa kernels mixed up did you? That would defiantly cause a crash if you put Oreo kernel on Pie. I think the vs995 and us996 kernels are interchangeable anyway. Little difference between some of them.
I don't bother with the benchmarks myself, I can just tell by the fluidity of the device if it's better! Not surprised by the results given what I'm experiencing.
Click to expand...
Click to collapse
Yea i double checked, i flashed the us996 pie kernel twice actually, but had the same results
Okay so before i added anything, i tried to open the alexa app again, this time it worked fine and didn't cause my phone to crash, so this time i'm going to open a lot of apps and see if that will trigger the crash
Edit: nope, that did not cause it to crash either, i have no idea what's causing the crashes, maybe it has something to do with the cache because i remember when i tried rebooting after the second crash, it was stuck at the boot animation, it only rebooted after i cleared delvik and cache. Maybe the cache is getting corrupted after a while?
Update: Phone has been running fine for 1 day
Update2: Phone crashed this morning while scrolling to instagram, these crashes seem to be happening at random. Only thing the crashes have in common is that it would happen roughly every 20 hours to a day. Sometimes if i'm unlucky it just repeatedly crashes after a couple of reboots
Update3: Okay yea theres something funny going on with the cache because, i went to the gallery to look at some videos that i know would play but when i tried to play them it kept saying something went wrong, tried a reboot but still the same result. and when i'd watch videos on instagram they looked corrupted, tried force stopping and clearing the cache but still the same result. reboot didn't help either, only thing that fixed those issues was clearing the cache and delvik in twrp
Update: So i have found a temporary solution which is to clear the cache and delvik every once in a while
Idk if this is relevant but what did you come from before flashing this cuz i came from oreo so idk if that could have anything to do with the issue