Did anybody try Enabling ART after bootloader unlock?
When i'm trying to switch from Dalvik to ART phone is rebootong, but nothinh actually happened.
And I see in settings it still using Dalvik run time, not ART
GGinz said:
Did anybody try Enabling ART after bootloader unlock?
When i'm trying to switch from Dalvik to ART phone is rebootong, but nothinh actually happened.
Click to expand...
Click to collapse
I've done it on a locked phone. Aside from an EXTRA long boot up, it should be about the same, I gather.
fat-fingered and Maxx-ed out.
GGinz said:
Did anybody try Enabling ART after bootloader unlock?
When i'm trying to switch from Dalvik to ART phone is rebootong, but nothinh actually happened.
And I see in settings it still using Dalvik run time, not ART
Click to expand...
Click to collapse
It's not compatible with Xposed framework. Are you using that? It auto disables.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
GGinz said:
Did anybody try Enabling ART after bootloader unlock?
When i'm trying to switch from Dalvik to ART phone is rebootong, but nothinh actually happened.
And I see in settings it still using Dalvik run time, not ART
Click to expand...
Click to collapse
It takes forever to boot the first time, you sure you waited long enough?
jfriend33 said:
It's not compatible with Xposed framework. Are you using that? It auto disables.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
Click to expand...
Click to collapse
Thanks! Looks like that's the problem. I'm using Xposed framework
GGinz said:
Thanks! Looks like that's the problem. I'm using Xposed framework
Click to expand...
Click to collapse
Probably a coincidence, but after I switched to ART then back to DALVIK and then wiped cache etc my Moto Maxx DE went into a Force Close frenzy that could not be recovered from. I was unable to flash anything so it completely toasted phone. I didn't do any flashing of ROMs or anything odd. Froze some apps via Titanium backup but other than that the only thing I did was switch from DALVIK to ART and back. BOOM! TOAST! I'll never use ART again!
Related
After installing miui this morning I kept getting a force close message for google.process.acore
I know people use miui for this phone is there anyway to fix this
Sent from my HTC Glacier using XDA App
GroundControl2MT said:
After installing miui this morning I kept getting a force close message for google.process.acore
I know people use miui for this phone is there anyway to fix this
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Did you wipe the handset prior to flashing the OS.
yes I factory wiped and then installed 1.10.7 but still get force closes
GroundControl2MT said:
yes I factory wiped and then installed 1.10.7 but still get force closes
Click to expand...
Click to collapse
did you verify the MD5SUM of the download to make sure you didn't get a corrupt file?
Did you by any chance install any of those leaked Nexus Prime apps, like the market and/or Google Plus app? Those have been known to cause constsnt FC's. If not, re-download, re-wipe then re-flash.
Sent from my HTC Glacier using xda premium
GroundControl2MT said:
After installing miui this morning I kept getting a force close message for google.process.acore
I know people use miui for this phone is there anyway to fix this
Click to expand...
Click to collapse
I had this problem when I first installed MIUI 1.9.xx. I solved it by doing TheDerekJ's SUPER.DUPER.WIPE(adding "-file" to the name). Prior to that I only wiped data, cache, and dalvik check.
I Uninstalled music 4 and did it tried again with another full wipe and it worked so i guess it was a problem
GroundControl2MT said:
I Uninstalled music 4 and did it tried again with another full wipe and it worked so i guess it was a problem
Click to expand...
Click to collapse
I don't think it was music 4 as I had no issues with it. My problem was solved by formatting system, cache, data, and dalvik cache. I'm guessing I had some crap from my other roms lingering.
jsyi84 said:
I don't think it was music 4 as I had no issues with it. My problem was solved by formatting system, cache, data, and dalvik cache. I'm guessing I had some crap from my other roms lingering.
Click to expand...
Click to collapse
Is formatting system part of super duper wipe? if not ... how would you format system, cache, data, and dalvik?
jon_htc said:
Is formatting system part of super duper wipe? if not ... how would you format system, cache, data, and dalvik?
Click to expand...
Click to collapse
I formatted via CWM. Reboot phone into CWM--->CWM Recovery--->mounts and storage
At least this is how I've always done it.
Please help guys. I just got this phone and my parents will kill me.
I installed the Franco kernel after rooting and tried to install the drivers for chain fire 3d.
It's got my phone in a loop.
I tried wiping data and cache and dalvik cache and rebooting but it doesn't work.
Please help.
VikramK123 said:
Please help guys. I just got this phone and my parents will kill me.
I installed the Franco kernel after rooting and tried to install the drivers for chain fire 3d.
It's got my phone in a loop.
I tried wiping data and cache and dalvik cache and rebooting but it doesn't work.
Please help.
Click to expand...
Click to collapse
recovery mode, factory data reset ?
opticaldh said:
recovery mode, factory data reset ?
Click to expand...
Click to collapse
Yes that is what I performed after wiping cache.
Reflash ROM?
Sent from my Nexus 4 using xda app-developers app
yeah, factory reset http://forum.xda-developers.com/showthread.php?t=2010312
air2k57 said:
Reflash ROM?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am flashing now.
VikramK123 said:
I am flashing now.
Click to expand...
Click to collapse
after flashing and ur still in bootloop, then go to Recovery Mode (the android with a red triangle), do a factory data reset. Then you're good to go.
VikramK123 said:
I am flashing now.
Click to expand...
Click to collapse
Chainfires open gl drivers won't work on most 4.1+ devices. Also looking over the app description on the play store, the supported devices are all nvidia or exynos based devices. Our phones use a Qualcomm chipset. And the force 4x msaa function is built into the nexus 4. It's under developer options.
Sent from my Nexus 4 using Tapatalk 2
same issue, flash not working
opticaldh said:
after flashing and ur still in bootloop, then go to Recovery Mode (the android with a red triangle), do a factory data reset. Then you're good to go.
Click to expand...
Click to collapse
Hey all. Im having the same issue, and my recovery mode is just blank, even after hitting volume up button.
Please help!
do this
RedEyeZ88 said:
Hey all. Im having the same issue, and my recovery mode is just blank, even after hitting volume up button.
Please help!
Click to expand...
Click to collapse
Its HOLD POWER BUTTON click on VOLUME UP ONCE - menu will appear
CC
Can someone tell me how to flash the factory rom from a mac. I tried factory data reset but it didn't work. I'll try again just to be sure.
VikramK123 said:
Can someone tell me how to flash the factory rom from a mac. I tried factory data reset but it didn't work. I'll try again just to be sure.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Solved!
I used AndroidRootz Mac Toolkit and Voila!. It came back to life. Could someone tell me why the regular wipe data/factory reset did not work?
VikramK123 said:
Solved!
I used AndroidRootz Mac Toolkit and Voila!. It came back to life. Could someone tell me why the regular wipe data/factory reset did not work?
Click to expand...
Click to collapse
The open gl drivers from the chainfire app borked your kernel drivers.
Sent from my Nexus 4 using Tapatalk 2
Hi Team,
I tried to switch to ART on my Nexus 4, but my phone goes into a loop where it didnt turn into ART, I had to force re-boot to bring it back to life as it was trying to convert all Apps into ART so I left the whole night to convert, but by morning, it was not complete and hence force-rebooted as I needed my mobile. Is this a regular thing?
When I try to redo the process again, it still goes into that recursive loop, where the Logo keeps playing and nothing happens..
Is there a way I can still get onto ART despite this?
I am using Stock Nexus, without a lot of playing around with it.
BR, Harsha
Are you using xposed? It's not compatible with art
Sent from my Nexus 5
jd1639 said:
Are you using xposed? It's not compatible with art
Sent from my Nexus 5
Click to expand...
Click to collapse
xposed revert back to dalvik.
-----
if you are on stock, and didnt mod any system app, you can use art normaly.
however ART can take up to an hour(my phone took that, with 224 apps) to fully boot
so you really need to wait...
jd1639 said:
Are you using xposed? It's not compatible with art
Sent from my Nexus 5
Click to expand...
Click to collapse
I am not using Xposed..
opssemnik said:
xposed revert back to dalvik.
-----
if you are on stock, and didnt mod any system app, you can use art normaly.
however ART can take up to an hour(my phone took that, with 224 apps) to fully boot
so you really need to wait...
Click to expand...
Click to collapse
Like I mentioned earlier, I had left the mobile for upgrade for a whole night. Thats a minimum of 7 hours.
Do you think, it may take 7 hours for 155 applications?
Is there a way I see, which app is causing this issue?
K H C said:
Like I mentioned earlier, I had left the mobile for upgrade for a whole night. Thats a minimum of 7 hours.
Do you think, it may take 7 hours for 155 applications?
Is there a way I see, which app is causing this issue?
Click to expand...
Click to collapse
hmm its weird..., yeah you can, but you will need to get a custom recovery to do that(at least for the method i know)
When I turn on my s5 att varient it shows a padlock unlocked and says custom, all I have done was install SD card and change runtime system from dalvik to art. Anyone have any ideas? Can the phone really be unlocked?
Switching to art makes it custom. Going back to davlik makes it normal again.
Sent from my SM-G900F using Tapatalk
gnandez said:
When I turn on my s5 att varient it shows a padlock unlocked and says custom, all I have done was install SD card and change runtime system from dalvik to art. Anyone have any ideas? Can the phone really be unlocked?
Click to expand...
Click to collapse
And how did you change runtime system from delvik to art?
spinwizard said:
And how did you change runtime system from delvik to art?
Click to expand...
Click to collapse
It's under developer options
simacca said:
Switching to art makes it custom. Going back to davlik makes it normal again.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
I switched back yesterday and it stayed the same. So I just switched it back but rebooted twice this time and now it's gone. I wish it was just that easy to unlock the phone. Thanks for the info. Also why do you think the lock is unlocked?
gnandez said:
I switched back yesterday and it stayed the same. So I just switched it back but rebooted twice this time and now it's gone. I wish it was just that easy to unlock the phone. Thanks for the info. Also why do you think the lock is unlocked?
Click to expand...
Click to collapse
Haven't got a clue about the padlock as I've got a stock handset.
Sent from my SM-G900F using Tapatalk
ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
DopeShow said:
ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
Click to expand...
Click to collapse
Open up Wanam and go to security hacks. In there it will have an option for "fake system status"
jagrave said:
Open up Wanam and go to security hacks. In there it will have an option for "fake system status"
Click to expand...
Click to collapse
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
DopeShow said:
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
Click to expand...
Click to collapse
Sorry man. I don't really use xposed a lot or s-health, so idk if there is another fix or not for that.
DopeShow said:
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
Click to expand...
Click to collapse
You could give the xsecurestorage module a shot, you should be able to get shealth to work with xposed. Thr fix i know should be just disable secure storage, clear davlik cache and cache in recovery, then clear data of the s health app and reboot once more and it should work. Otherwise i dont know, there are quite a few threads on both disabling the padlock and getting xposed to play nice with shealth, just search around, supposedly triangleaway will remove the padlock i wouldnt count on it though.
Sent from my SM-G900A using Tapatalk
Rakuu said:
You could give the xsecurestorage module a shot, you should be able to get shealth to work with xposed. Thr fix i know should be just disable secure storage, clear davlik cache and cache in recovery, then clear data of the s health app and reboot once more and it should work. Otherwise i dont know, there are quite a few threads on both disabling the padlock and getting xposed to play nice with shealth, just search around, supposedly triangleaway will remove the padlock i wouldnt count on it though.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I did the s health fix changing the securewstorage=true to false and reboot then reinstall exposed and nada s health wont even open I get that lil white window that pops up sayin s health has closed, so is there any other ways of getting this damn custom lock off my boot screen?
DopeShow said:
I did the s health fix changing the securewstorage=true to false and reboot then reinstall exposed and nada s health wont even open I get that lil white window that pops up sayin s health has closed, so is there any other ways of getting this damn custom lock off my boot screen?
Click to expand...
Click to collapse
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ive read turning off secure storage is not enough to get it working. Sit tight and i'll edit this post with some clearer instructions.
Edit:
Start by making for sure you have the xposed framework uninstalled, dont just uninstall the xposed installer app, you need to actually go in to the app and uninstall the framework, you should be able to keep the installer app installed though.
Next with a root enabled file explorer and open your build.prop file and just double check you have ro.securestorage.support set to false.
Now go in to the app info for s health, uninstall the updates, and clear the data and repeat for healthservice, then reboot in to stock recovery or safestrap and clear the cache and davlik cache.
Boot up and install xposed then for good measure reboot into recovery again, and clear the cache and davlik cache again, boot up and s health should work.
Past that i cant really help, this is all compiled from suggestions ive read, so im not sure how well all of it works due to the fact i dont even have s health installed, but good luck, hope you get it working.
Sent from my SM-G900A using Tapatalk
Rakuu said:
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ivr read turnin g off secure storage is not wniugh to get it working. Sit tight and i'll edit this post with some clearer instructions.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
no I did that to cleared the data and cach for s health in the all applications, I did everything in order and s health wont work.
Rakuu said:
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ive read turning off secure storage is not enough to get it working. Sit tight and i'll edit this post with some clearer instructions.
Edit:
Start by making for sure you have the xposed framework uninstalled, dont just uninstall the xposed installer app, you need to actually go in to the app and uninstall the framework, you should be able to keep the installer app installed though.
Next with a root enabled file explorer and open your build.prop file and just double check you have ro.securestorage.support set to false.
Now go in to the app info for s health, uninstall the updates, and clear the data and repeat for healthservice, then reboot in to stock recovery or safestrap and clear the cache and davlik cache.
Boot up and install xposed then for good measure reboot into recovery again, and clear the cache and davlik cache again, boot up and s health should work.
Past that i cant really help, this is all compiled from suggestions ive read, so im not sure how well all of it works due to the fact i dont even have s health installed, but good luck, hope you get it working.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Thanks I appreciate you helpin me out, that only part I hadn't done in the past was boot into safestrap and clear cache and delvic cache, I thought it said to just go into the app info and clear cache and data there, but I guess after I get done doing a backup and saving the backup to my pc i'll give it another try with your instructions. thanks for taken the time out to help me bro.
DopeShow said:
Thanks I appreciate you helpin me out, that only part I hadn't done in the past was boot into safestrap and clear cache and delvic cache, I thought it said to just go into the app info and clear cache and data there, but I guess after I get done doing a backup and saving the backup to my pc i'll give it another try with your instructions. thanks for taken the time out to help me bro.
Click to expand...
Click to collapse
Just for refrence, thought id note safestrap recovery is not required to clear the cache and davlik cache, it works fine if done from stock recovery.
Sent from my SM-G900A using Tapatalk
Rakuu said:
Just for refrence, thought id note safestrap recovery is not required to clear the cache and davlik cache, it works fine if done from stock recovery.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
well thank you I just went through the steps you gave me and I finaly have wanam exposed installed and s health is working fine, only problem is I installed wanam so I could make the custom padlock on the boot screen be gone and I did what this other guy told me to do and it didn't work its still there
EDIT
YAYYYYYYYYYYYYYYYYYYY it did work and it took away the custom Unlocked Padlock damn im so happy.
DopeShow said:
well thank you I just went through the steps you gave me and I finaly have wanam exposed installed and s health is working fine, only problem is I installed wanam so I could make the custom padlock on the boot screen be gone and I did what this other guy told me to do and it didn't work its still there
Click to expand...
Click to collapse
You can check a couple things, check the module list and see if theres a check next to wanam indicating its enabled, if its not then enable it and reboot. If you have an sd card then long press on wanam in the module list or in yout launcher and go to its app info and see if its on the sd card, there should be a button that says either "move to sd card" or "move to device storage" if its the latter its on your sd card and that tends to mess things up, so move it to your phone's storage and then reboot, go to the module list and disable then reenable wanam then reboot.
Sent from my SM-G900A using Tapatalk
DopeShow said:
ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
Click to expand...
Click to collapse
triangle away worked for me even though it's not official for it. just hit reset flash counter and reboot the phone
Rakuu said:
You can check a couple things, check the module list and see if theres a check next to wanam indicating its enabled, if its not then enable it and reboot. If you have an sd card then long press on wanam in the module list or in yout launcher and go to its app info and see if its on the sd card, there should be a button that says either "move to sd card" or "move to device storage" if its the latter its on your sd card and that tends to mess things up, so move it to your phone's storage and then reboot, go to the module list and disable then reenable wanam then reboot.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
everything is working 100% perfectly now that s health is working and I got the custom padlock gone from my boot screen using wanam and this phone is just badass right now with al the customized changes ive done with it and its running fast as hell
rnh said:
triangle away worked for me even though it's not official for it. just hit reset flash counter and reboot the phone
Click to expand...
Click to collapse
I didn't wanna brick my phone so I didn't attempt to use triangle away but I was able to remove the custom padlock from my boot screen using wanam
DopeShow said:
everything is working 100% perfectly now that s health is working and I got the custom padlock gone from my boot screen using wanam and this phone is just badass right now with al the customized changes ive done with it and its running fast as hell
Click to expand...
Click to collapse
Glad i could help
Sent from my SM-G900A using Tapatalk