Related
So, I have read that it's an issue with all Froyo ROM's on the EVO... You can't see paid/protected apps in the Marketplace; supposedly, the apps not showing are not verified to work on Froyo.
Could someone just patch the build_prop like they did on the Nexus One before Google released the official fix?
N1 Fix Thread for Reference: http://forum.xda-developers.com/showthread.php?t=693102
If anyone wants to tackle it, the dev of the N1 fix explained what needs to be done here: http://forum.xda-developers.com/showthread.php?t=693102
I don't have an EVO, nor am I much of a developer; but I just rooted my friend's EVO and was looking for a fix for him when I realized that the N1 had a very similar issue when it was running leaked versions of Froyo.
Just throwing it out there... I could be way off.
I think this should be easy to do. Theoretically you should be able to take buildprop swticher v0.3.1.zip and replace /buildprop/build.2.1 with the build.prop from stock and /buildprop/build.2.2 with the build.prop from CM6 and then follow the directions from that post.
I'm about to test it out myself and see if it works...
Let me know... If it does, could you post the build.prop files that you used?
EDIT: Awesome to see another SC member!
Okay, first attempt boot looped. I think build.2.1 needs to be a 2.2 build.prop modified to look like 2.1 because the stock 2.1 build.prop won't work with 2.2. Should've looked at that more instead of rushing Going to see if I can find the lines to change real quick, gotta go back to work in a few minutes...
It also cleared my Google Account settings haha... trying a new modification but may not be able to upload anything until tonight!
Thanks for your help... Can you post your build.props before going back to work? If so, I will try to work on this more if you aren't able to get it before going back.
Thanks
Just printed and compared the build.props for the N1 fix and see that there are only 2 lines that were changed. If someone wants to provide me with a 2.1 build.prop and the CM6 build.prop, I might be able to get this working.
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
I was just about to post saying what I tried didn't work and I was hoping you'd pop in here. I was thinking about digging into it more this weekend but if you haven't been able to get anywhere I doubt I could either.
Well... that blows... Sorry guys
Wish I could've been of more help!
Geniusdog254 said:
Don't bother with it man.
I'm the one posted the Nexus thread. I already tried changing the build.prop fingerprints & it didn't fix the issue.
Only thing keeping me from using CM6
Click to expand...
Click to collapse
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Geniusdog... what all does the ro.build.fingerprint line do?
spiicytuna said:
After you changed the lines in build.prop did you try reseting Market?
settings > Applications > Manage Applications > ALL > Market > Clear data
Click to expand...
Click to collapse
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
We need a setting like most of the android browsers to allow us to spoof ourselves as stock 2.1 EVO.
Geniusdog254 said:
Yep. Even tried pushing it while still in recovery, right after wiping and flashing the ROM. Still a no go
Edit: the to.build.fingerprint is the "fingerprint" it shows when it accesses the Market. So its how the Market decides what apps to show, and sees what kind of device it is & its version
Click to expand...
Click to collapse
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
ok this is what we did on the Hero when we was with 1.5 and got the leak of 2.1 the market didnt show all the apps so we just change it with the nexus one, so i am guessing maybe we can get a 2.2nexus one build.prop and push it to the Evo, make sure to clear the market chache though , it took like 5-6hours for the apps to start showing up on the Hero!! just an Idea
jabbawalkee said:
Hmmm...editing fingerprint and description *SHOULD* work but it did not work when I tried adding the fingerprint/description from Avalaunch's Froyo ROM. It seems that Ava's Froyo ROM fixed the missing apps issue. It's so very bizarre that we can't get certain market apps to show on CM6 and drives me crazy. There has to be some type of solution, I'm just not sure what it is yet
Click to expand...
Click to collapse
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
datajosh said:
Have you tried just using the whole build.prop from Ava's ROM? Should work ok since they're both 2.2, no idea if it'll fix the issue though.
Click to expand...
Click to collapse
bootlooops
Edit: nvm, was incomplete.
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
It takes some changes to get the phone to boot with them, or to get radio access with them.
I've already tried a stock Nexus fingerprint, but it still doesn't give access. Like I said, I even pushed the file before even booting the phone (I.E, wipe, flash CM6, push file in recovery, then reboot) and it still didn't work.
Ava's build prop comes up, but no Market. Something else is going on.
Geniusdog254 said:
Sense build.prop files & AOSP build.prop files don't play nice together. Neither do CDMA files & GSM files.
Click to expand...
Click to collapse
Duh, forgot it was Sense for a minute there. I feel like looking into it more but I'm not sure if anyone's going to find a solution.
Hi there, my problem is: when I open any camera app, I can see only the camera app's user interface, nothing else. Both of the cameras are not working.
What I've tried: downgrade to 4.3 4.4.4 5.0.2, factory reset, full internal storage format, clear camera app data. I am on locked bootloader.
Any ideas my friends? I used my camera more than a half an hour in a day :crying:
Here are some screenshots:
I will try to post them, I can't do it right now.
postimg(dot)org/gallery/3bzfiiz0w/
G4B33 said:
Hi there, my problem is: when I open any camera app, I can see only the camera app's user interface, nothing else. Both of the cameras are not working.
What I've tried: downgrade to 4.3 4.4.4 5.0.2, factory reset, full internal storage format, clear camera app data. I am on locked bootloader.
Any ideas my friends? I used my camera more than a half an hour in a day :crying:
Here are some screenshots:
I will try to post them, I can't do it right now.
Click to expand...
Click to collapse
First obvious guess would be hardware. Was it working fine until you did something, or was it just all of a sudden?
The only other thing I thought of was that there's sometimes other folders in the camera app folder, like 'arm' or 'lib', etc. You probably would know if you did something to that, though.
Last thing I did, I was recording a video. I watched the video, then I wanted to go back to the camera, and it said camera not avaible, I restarted the phone, and then it started the black screen issue. BTW, I can take pictures too, I can feel it's focusing sometimes but if I look into the image file with a hex editor, it's got only zeroes in it.
G4B33 said:
Last thing I did, I was recording a video. I watched the video, then I wanted to go back to the camera, and it said camera not avaible, I restarted the phone, and then it started the black screen issue. BTW, I can take pictures too, I can feel it's focusing sometimes but if I look into the image file with a hex editor, it's got only zeroes in it.
Click to expand...
Click to collapse
Here's my stock apk if you want to give it a shot - https://mega.nz/#!otshkQaQ!_YbCzHpA5mWdO2u1uR1e6x5bybE0l6y0EzXtfjjQzgg
levone1 said:
Here's my stock apk if you want to give it a shot - https://mega.nz/#!otshkQaQ!_YbCzHpA5mWdO2u1uR1e6x5bybE0l6y0EzXtfjjQzgg
Click to expand...
Click to collapse
I tried it,but it's the same issue :crying:
But thank you for trying to help me
It must be some sort of software issue as it's very unlikely hardware would have failed on both cameras at the same time
Is there any way to 'reinstall' the camera firmware?
G4B33 said:
Is there any way to 'reinstall' the camera firmware?
Click to expand...
Click to collapse
Maybe try one of the ports in dev forums....
levone1 said:
Maybe try one of the ports in dev forums....
Click to expand...
Click to collapse
I've got 8 camera apps now I tried a bunch of camera apps.
G4B33 said:
I've got 8 camera apps now I tried a bunch of camera apps.
Click to expand...
Click to collapse
Have you already done 'diagnostics' test in settings, or *#*#7378423#*#* service test, and they both fail? Only other thing I can think to try would be replace whole folders in /system with working stock ones.
Yes I tried them, both of the cameras still doesn't work.
What if delete everything in the root folder?
levone1 said:
Have you already done 'diagnostics' test in settings, or *#*#7378423#*#* service test, and they both fail? Only other thing I can think to try would be replace whole folders in /system with working stock ones.
Click to expand...
Click to collapse
Hey dude, I just realized that, I can't play video in hardware codec mode, so maybe it's 'just' a codec problem?
G4B33 said:
Hey dude, I just realized that, I can't play video in hardware codec mode, so maybe it's 'just' a codec problem?
Click to expand...
Click to collapse
Have you messed with any help options in developer option menu? Try those maybe
levone1 said:
Have you messed with any help options in developer option menu? Try those maybe
Click to expand...
Click to collapse
I tried to switch them off
G4B33 said:
I tried to switch them off
Click to expand...
Click to collapse
Sorry, 'help' Is a typo in my previous post. Supposed to say 'hw'. (stupid auto correct)
levone1 said:
Sorry, 'help' Is a typo in my previous post. Supposed to say 'hw'. (stupid auto correct)
Click to expand...
Click to collapse
Yeah, already tried to switch them on and off :/
G4B33 said:
Yeah, already tried to switch them on and off :/
Click to expand...
Click to collapse
2 final guesses - bad kernel, (have you flashed a custom kernel? If not, reflash stock one via Ft), or some 3rd party app that messed with your software. Just try uninstalling stuff one-by-one.
levone1 said:
2 final guesses - bad kernel, (have you flashed a custom kernel? If not, reflash stock one via Ft), or some 3rd party app that messed with your software. Just try uninstalling stuff one-by-one.
Click to expand...
Click to collapse
I'm on locked bootloader, so I cannot install any kernel, and I tried to install 4.3- 5.1, with flashtool, but I'll try with Sony PC suite, maybe that will helps,who knows. Thank you so much for helping me.
Did anything work for you?
I am having the same issues
Installation Instructions:
https://wiki.cyanogenmod.org/w/Install_CM_for_ls970
Click to expand...
Click to collapse
Changelog:
20160814:
Updated using branch cm-12.120160127:
Updated to CM-12.1 using codebase cm-12.1-YOG7D
Updated libs from mako, which fixes GPS, Encryption, & some dirty log messages.
Click to expand...
Click to collapse
Special Thanks:
Looking at the commit log, I've got to say thank you to Shelnutt2 and Ricardo Cerqueira. Seth, for his work on porting this device & permission to post this build, and Richardo for maintaining the gproj kernel.
Click to expand...
Click to collapse
I've been using this with Ting. Seems more stable than the CM-11 build that I was using. Mms & cell data are the two things that do not work out of the gate for me. Wondering how this shapes up with Sprint. I vaguely remember cell data working, but I don't think the default mms app did. However, I was able to use a third party mms app for pictures.
If this works well for people I'll see what I can do about getting my changes pulled upstream.
XDA:DevDB Information
UNOFFICIAL CM12.1 for LS970, ROM for the Sprint LG Optimus G
Contributors
fuzzy7k, Shelnutt2, Ricardo Cerqueira
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-01-28
Last Updated 2016-08-17
What gapps version to use?
Thanks for providing this! I've installed it, to replace my cm-12-20151108-NIGHTLY-ls970.zip ROM. But I haven't been able to find a gapps download that will work with this (all Google services keep crashing) or fail to installed (Status 6). Any help will be appreciated.
Thanks!
gapps version
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate." Have you run into this issue? Any known fixes?
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate."
Click to expand...
Click to collapse
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
geodosch said:
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
Click to expand...
Click to collapse
Yeah I just went through unrooting and going to stock (where it worked fine) and now tried again to install without luck. I don't understand this problem or what could possibly be the issue at this point.
Edit: I have noticed that I'm not seeing my 5 GHz network although it was available in stock.
Profile switcher
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
geodosch said:
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
Click to expand...
Click to collapse
Hey geodosch, same experience here with pop up errors with one difference, I was not able to get into Play Store... I only have four com.google.* green droid icons, and after clicking them I get 'App isn't installed'. Which gapps did you install, any other tips?
Many thanks!
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
A couple of issues
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
curiousGeorge said:
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
Click to expand...
Click to collapse
Did you click the "Downloads" tab near the top of this topic? (Between "Discussion" and "Reviews") There should be a link there to "cm-12.1-20160127-UNOFFICIAL-ls970.zip", dated 2016-01-28.
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
geodosch said:
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
Click to expand...
Click to collapse
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Ah, looks like I was right. It's the silly SELinux thing. The trick is to go here http://forum.xda-developers.com/showthread.php?t=2524485 and set the phone to permissive. Which you can totally do because you can go into the build info and click build number until you get "developer mode" enabled and enable root access in apps. Then everything works perfectly, even from a seemingly glitched install, regardless of GApps version. Pretty nice eh?
I'm gonna let everything update and then try reenabling SELinux, for kicks.
[edit]Ah, rebooting screws everything up again until the SELinux changer finally loads and changes things to permissive. So it doesn't exactly stick at boot. Still looking for a permanent fix...
curiousGeorge said:
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Click to expand...
Click to collapse
I'm running ClockworkMod 6.0.4.7. It's been a while since I originally installed the CM ROM, but I know I didn't have any luck with TWRP, though I can't say for certain that it was at fault... it may have been due to some other issue which I later fixed, and switching to CWM may have been incidental.
I've found that using the official CM recovery fixed my gapps woes.
On another note, GPS isn't working for me.
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
geodosch said:
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
Click to expand...
Click to collapse
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
geodosch said:
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Click to expand...
Click to collapse
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
geodosch said:
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
Click to expand...
Click to collapse
It's there, under "Power menu". Just search for power.
Nicene Nerd said:
On another note, GPS isn't working for me.
Click to expand...
Click to collapse
I read somewhere that you may need to get a lock in a ZVC build before flashing. Try that. It sounded like hog wash to me, and didn't work when I tried it. But, after updating the libs, all was fine. So, maybe both conditions must be met. On a positive note, I rarely have GPS enabled, but when I flip the switch, it comes on. So, it's not like you need to leave it on across reboots.
fuzzy7k said:
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
Click to expand...
Click to collapse
fuzzy7k said:
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
Click to expand...
Click to collapse
Glad to see you taking I look here. I really don't want to replace my Optimus G, since all phones now seem to be either low-end performance or over-sized. So I'm glad I can still keep mine going with these builds.
fuzzy7k said:
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
Click to expand...
Click to collapse
I hadn't tried adb before rebooting (Murphy's Law: whenever it happened I was often doing some time-constrained task, so I just rebooted as quickly as I could.) But the next time it happens I'll connect and check the logs. It's interesting that you mention multiple profiles, because it seems to have happened several times in my car, and I have profiles set-up to switch when the car bluetooth connects/disconnects.
If you're going to be poking around in the code, another issue that I've been having is the default app for the browser no longer seems to work consistently. I know this worked on an older CM12 build, and think it used to work on this one. But when something launches a browser I'm very often prompted for which one (Chrome or Browser.)
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
fuzzy7k said:
It's there, under "Power menu". Just search for power.
Click to expand...
Click to collapse
In the power menu, I see an option to switch users (which is disabled, since I don't have multiple users set-up), but I don't see an option for Profiles.
Hi all,
The latest update has some issues- the OS boots and I am immediately presented with a system.ui has been stopped dialogue. I'm unable to open the app drawer, open an app, open the notification drop-down. The popup appears almost immediately after dismissing. I think the Testers really missed something here.......
I'm going to have to try and locate the previous version and hope I can install it through twrp.
Has anyone else seen this happen?
typhoonikan said:
Hi all,
The latest update has some issues- the OS boots and I am immediately presented with a system.ui has been stopped dialogue. I'm unable to open the app drawer, open an app, open the notification drop-down. The popup appears almost immediately after dismissing. I think the Testers really missed something here.......
I'm going to have to try and locate the previous version and hope I can install it through twrp.
Has anyone else seen this happen?
Click to expand...
Click to collapse
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
rdmack said:
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
Click to expand...
Click to collapse
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Brax33 said:
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Click to expand...
Click to collapse
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
rdmack said:
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
Click to expand...
Click to collapse
I'm not running stock. Other people seem to be having similar issues in the Viper Rom discussion.
Brax33 said:
I'm not running stock. Other people seem to be having similar issues in the Viper Rom discussion.
Click to expand...
Click to collapse
on what rom you are? and you @typhoonikan ?
...and on what rom version you are, still marshmallow I assume.
A logcat will be really helpful.
rdmack said:
Haven't had this happen to me
if you check on apkmirror you'll find the previous versions there =)
Click to expand...
Click to collapse
I was unable to install the apks located there in the traditional way. I tried to install them through TWRP via adb push file.apk /system/app but it didn't work. I'm unaware of how to install APKs outside of the system otherwise? Regardless, downgrading, if this method is viable, didn't work. I had to completely wipe clean and start fresh.
Brax33 said:
This just happened to me.... It's just flashing the HTC 10 stock background over and over and over and phone is heating up very fast. Have tried starting in safe mode, rebooted several times, no joy..... Anyone have any ideas?
---------- Post added at 09:40 AM ---------- Previous post was at 09:04 AM ----------
Do you encrypt your phone? I feel like the update didnt transfer encryption presets and new app is trying to unlock without decryption codes or something.
Click to expand...
Click to collapse
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
rdmack said:
I do mate, it's stock still. I didn't have to change anything regarding that, fired up as normal and asked for my PIN to decrypt device.
Just thinking, if you can battle it go and uninstall the update via settings and apps
Click to expand...
Click to collapse
The bug doesn't allow the user to enter any screen. So doing this is not an option
j to the 4n said:
on what rom you are? and you @typhoonikan ?
...and on what rom version you are, still marshmallow I assume.
A logcat will be really helpful.
Click to expand...
Click to collapse
Viper 3.5.0. I haven't upgraded to ANdroid 7.0 for reasons.
typhoonikan said:
I was unable to install the apks located there in the traditional way. I tried to install them through TWRP via adb push file.apk /system/app but it didn't work. I'm unaware of how to install APKs outside of the system otherwise? Regardless, downgrading, if this method is viable, didn't work. I had to completely wipe clean and start fresh.
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
The bug doesn't allow the user to enter any screen. So doing this is not an option
Viper 3.5.0. I haven't upgraded to ANdroid 7.0 for reasons.
Click to expand...
Click to collapse
Not sure if HTC is to blame, or we...or you being still on marshmallow.
Next time please post in the viper thread, then I would have seen your post much earlier to debug your issue.
we found the issue.
run:
adb shell settings put system tweaks_hquicksettings Tweaks
..and it will be fixed. when you resetup your toggles, don't pick any of the two sync toggles.
I'll create a flashable zip to remove those soon.
typhoonikan said:
Wipe and start over. I had to. I have work calls that I can't be absent for. Thanks HTC. My phone was out of service for ~3 hours while I figures this out and the phone got completely usable again after flash+settling.
Click to expand...
Click to collapse
You should have been able to fix it without wiping by booting to recovery and dirty flashing the ROM.
EDIT: No, this actually won't work. Sorry
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Have this issue on an M8...
Will your fix work on my device too?
Found your solution in the m8 thread...
Thank you sir
j to the 4n said:
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Click to expand...
Click to collapse
Thank You! Flashing this file fixed the issue and saved me a huge headache. Now to take away the HTC Lockscreen app's
"auto update" rights since it clearly can't be trusted.
drumz0rz said:
Thank You! Flashing this file fixed the issue and saved me a huge headache. Now to take away the HTC Lockscreen app's
"auto update" rights since it clearly can't be trusted.
Click to expand...
Click to collapse
read the info on our homepage.
Not sure who is to blame, htc or we.
You can install the update, with either the fix installed or the sync toggles removed.
or you dirty flash the fullrom on top, that way the sync toggles stay working.
..what I'm wondering, why so many people are still on marshmallow...
j to the 4n said:
..what I'm wondering, why so many people are still on marshmallow...
Click to expand...
Click to collapse
There's a few xposed modules I like.
Is nougat really that big a difference? I have it on my tablet and it's very similar to marshmallow.
eoinzy said:
There's a few xposed modules I like.
Is nougat really that big a difference? I have it on my tablet and it's very similar to marshmallow.
Click to expand...
Click to collapse
guiness is also just a usual beer.
Well I like Marshmallow and Nougat. But I don't like Guinness!
If Guinness had Xposed modules then I'd drink it!
I have this problem on my m8 as well. Unfortunately I was not able to solve this problem with your post. I cannot execute the adb command since adb is telling me that my device is offline (I booted into the OS with the screen going on and off).
I also flashed the zip file, but it didn't work out either. I am not sure which version of viper I have (I assume it's the 6.0.1), so I tried different zips but no success...
Could anyone tell me what I did wrong? I really don't want to do a full reset.
obaern said:
I have this problem on my m8 as well. Unfortunately I was not able to solve this problem with your post. I cannot execute the adb command since adb is telling me that my device is offline (I booted into the OS with the screen going on and off).
I also flashed the zip file, but it didn't work out either. I am not sure which version of viper I have (I assume it's the 6.0.1), so I tried different zips but no success...
Could anyone tell me what I did wrong? I really don't want to do a full reset.
Click to expand...
Click to collapse
another way would be to go to twrp->advanced->file manager
navigate to /data/app/ and delete the com.htc.lockscreen folder do the same in /data/data
boot up, then go back to recovery and flash the fullrom on top.
if nothing helps, you can do a twrp backup, then clean flash. Now you can restore your apps and data with titanium backup.
Been looking for a solution to this ! My gf phone had the exact same issue, dirty flashed and still no good etc.
I shall try the packages J posted. Thanks so much!
Sent from my HTC One M9 using Tapatalk
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
j to the 4n said:
Flashable fix: https://www.dropbox.com/s/7pdthav90nsp6bw/HTC10_3.5.0_Lockscreen_Update_FC_Fix.zip?dl=0
more info here: http://venomroms.com/attention-mars...ystore-lockscreen-update-can-softbrick-phone/
Click to expand...
Click to collapse
Just downloaded this. And it saves as .... File.Bin is that correct ? Thanks
Sent from my HTC One M9 using Tapatalk
Well, I do not know when or how but Whatsapp app is broken on my device! Just not starting anymore, I only get some force crash screen of about 1 second and that's it...
I have a Note 8T with latest EEA software 12.5.4.0 MIUI 12.5, rooted with Magisk, custom recovery (OrangeFox)
Funny story but enabling dual apps for Whatsapp, basically another user, I managed to start and use the app, as a secondary app because the base app is still dead!
Now, my question is:
How do I get Whatsapp to function normally again???
Things I tried:
1. clean cache and data - no fix
2. uninstall/ install app - no fix
3. enable miui optimizations - no fix
4. fix/ repair data partition in OrangeFox recovery - no fix
Is there anything else I could try in order to fix this issue? It might be somehow related with the user part of the data partition? But why only this app is affected then?
I'm just baffled by this turn... don't know what to do anymore...
Your browser is not able to display this video.
MadK9 said:
Whatsapp app is broken
Click to expand...
Click to collapse
try with :
uninstall/reboot/install
if still not work
go to : Data/system/dropbox
delete everything
open wsp and send the generated crash log (from that folder)
Well, tried twice uninstall/ install procedure... Same result...
Thank for this info. I'll try.
MadK9 said:
Well, tried twice uninstall/ install procedure... Same result...
Click to expand...
Click to collapse
i said uninstall/!REBOOT!/install
when you reboot, the package manager will delete the app leftover
the app crash because there is some data left from a previous version
try deleting "com.whatsapp" folder from
/data/data/
and from
/user_de/0/
also whatsapp folder on internal storage
Holly mackerel!!!
You know how many times I rebooted this device???
But, now, it worked without deleting anything except the dropbox content you mentioned earlier!
It just went smooth, install, setup, restore backup and all without a glitch!
THX A BUNCH!!!
Anyway, I would really love to know how was this possible in the first place as I did nothing specially regarding this app... and found myself in this situation of not being able to use it anymore... why only this app? Was something some update maybe that broke something?
MadK9 said:
You know how many times I rebooted this device???
Click to expand...
Click to collapse
dosn't matter how many time
what matters here is the timing (reboot after uninstall, once booted install)
MadK9 said:
But, now, it worked without deleting anything except the dropbox content you mentioned earlier!
Click to expand...
Click to collapse
this has nothing to do with this problem, it has only crash logs of apps ...
MadK9 said:
I would really love to know how was this possible in the first place as I did nothing specially regarding this app... and found myself in this situation of not being able to use it anymore... why only this app? Was something some update maybe that broke something?
Click to expand...
Click to collapse
it's always the updates
Thanks again loopy!